Quote (AkuuZ @ Aug 28 2013 04:30am)
im not sure how this is to multiple locations, anyways this is what you do.
on your tools.html make sure your form action is pointing to template.php.
template.php gets all the information, then you do your mysql insert in template.php, then if you need to go back to tool.html, just do a php header(location) or a javascript window.location back to tool.html at the end of the data parsing/mysql query.
Thank you for this suggestion. I will give this a go today.
Quote (flyinggoat @ Aug 27 2013 10:28pm)
I do not understand how this task is difficult, even more so in php.
What stopping you from submitting data to your db from both the template file and the client's push from the same php script? Or is the simultaneous part design significant?
The simultaneous part is design significant. It doesn't have to actually process everything simultaneously, but the end-user for this tool should only have to click submit once.
Quote (carteblanche @ Aug 27 2013 06:19pm)
why are you putting php source code into a database table? if all the real data is in tools.html, why not just save that data? then have another table hold the template.
or do you mean something entirely different when you say source code?
When I say source code I mean HTML & CSS.
Basically, the tool I'm making is to design to simplify a 3rd-party tool that the end-user uses on a daily basis. The tool they use require the end-user to enter some source code themselves, along with a lot of other data. My tool is databased back so that once one my end-user creates an entry and submits it to their tool he/she never has to recreate the same entry. They can just call it up from the database and resubmit it to this other tool. The source code for any given entry is completely useless without the ~29 other columns worth of data.
This post was edited by grievance on Aug 28 2013 08:04am