In the Edit page for a Submission form--- in the Visual editor when using the "Add PHP Code Snippet" feature I have discovered that it matters WHERE the cursor is placed on the page. Since I was trying to add an action that depended on a value that had been selected in the form I presumed that this Code snippet should show up AFTER the form in the visual editor. The only reference to WHERE the code would begin to work is the visual box that refers to the snippet in the visual editor in the Editor view.
In other words, if I place my cursor above the form I get a PHP SNIPPET reference in a yellow visual box above the form. If I place the cursor below the form I get a PHP SNIPPET box showing up between the end of the form and the footer.
Does this really mean that if the code snippet is looking for filled out values in the fields that it truly will not be invoked until the form values are selected?
But after trying several versions of PHP snippet code in the Visual Editor--saving--building--testing each version while "confirming syntax"I noticed that in the /include/details_events.php file, (or whatever name the detail events file would take), that ALL of the code snippets are saved, the good, the bad, the ugly, the ones I though I was overwriting, and that ALL of them named sequentially and are reported as TRUE at the top of the mydetails_events.php code. I got the impression that EACH snippet is being run one after the other even if they do not show up in the Visual editor for the Add record. And that if you work on this over the course of project that your events.php files are going to be loaded with OLD code that you intended to modify or delete.
I used notepad to remove references to the snippets I did not want saved, and the complete PHP code snippets themselves before doing a new save and build.
And beyond that strangeness, let's say you post several snippets on the ADD page:
Why doesn't PHPRunner have a COMPLETE page code view where we can see the ENTIRE page, snippets, events, pulled together in one big code view? So that we can see the Order in which code is being run, especially in situations where one code function might destroy or reset the values of another code function?
For instance, how would you know in a huge code sequence what is going on when you use PHP code snippets in the Visual editor for say, the ADD view, while at the same time adding an action in the Events editor say, on "Before Adding a Record"?
Not even with an external PHP editor is it possible to view the ASSEMBLED flow of code to see what is actually affecting the actions of a page.
PHPRunner is treating the process in little bits and you have done a lot of great thought on separating the elements of a PHP page from the styling and the content itself.
But it would really help in troubleshooting if you provided an EDIT function that now showed us where PHP code snippets are applied on the ADD page, for instance, and where they applied in a session in relation to Events which also may have code added for a new action or function.
And, I notice that every page is loaded with code for functions and features that I have never asked for. Thumbnails and video, for instance.
It would be nice for PHPRunner to allow us to select a stripped down version of page building that EXCLUDES extraneous code for our particular project.
When we select a new project or an existing template in the initial setup choose just the features that our project will use. So that the built pages are not crammed with a lot of code that must load all the time but whose functions will never be used for our project. And thereby also not include any javascript that must also load but does nothing for our project.
I will edit these things out by hand, so that my page load and execution is perhaps sped up, but it is a modular approach that would be very useful in PHPRunner in later versions.
Thanks for hearing me out....
Otherwise, I will say that PHPRunner 5.3 is the most elegant and flexible of any existing "pre-built" template applications!!
