Hi Sandi,
I appreciate your feedback. I will send ALL of my projects to you and "your team" from now on!
Actually, I did basically all you say, including hitting the RESET in Editor, if I could get that to happen before Crash dump.
When you say you copied and pasted code and buttons from the old 5.3 to 6 are you saying you were doing this in Events or in Style Editor?
One further thing I had to do manually was to edit the phpr file as an xml file to fool it in some places.
What PHPRunner still does not do, and I have lobbied and lobbied for this and have been rejected over and over by the developers, is to create options that allow me to copy a complicated form with modified headers and lots of lookup wizards and CLONE the darned thing in a couple of seconds.
What Sergey and crew keep rejecting as "silly" and "unnecessary" because it is not how THEY do things in their own environment is that there can very often be a NEED, a dire NEED, to take all of the setup, all of the wizarding, all of the STYLING, every setting that took HOURS to create and test to satisfaction for ONE FORM and use it as a complete template inside the same project.
If I have to create a new form there is nothing that PHPRunner does to help automate the process. NOTHING.
There is no Auto-Wizard that says "Create a New Form" that skips past Tables and Views and just addresses the End Product, a FORM.
I ought to be able to say Yes, Create a New Form based on (Options List) and I see both Reports and the Fully Styled Fully Wizarded Final Product.
I click once on the FORM name I want and I INSTANTLY have a new Form that uses the same CSV Language Editor settings, the same lookup wizard settings, everything that my Custom Form 1 had, now implemented on Custom Form 2 (copy of Custom Form 1).
And then, PHPRunner allows me to select a different table, a differently named table to INSERT and EDIT to. And if this table has 2 fewer columns than the table Custom Form 1 was based on, no problem, Edit the new Custom Form 2 (the Clone) and simply remove the unnecessary columns and Save. Every other piece of Tab styling, Language setting, Text Editing on Headers, look up wizards is still preserved.
That is what I want from PHPRunner. As of now I have to do all of this by manually editing the PHPR file to circumvent PHPRunner's insistence on dropping all styling and customizations for a Custom View as soon as I try to modify the sql query to save the Custom View to a different table.
This kind of thing would help enormously in my work for updating projects!
We made the jump with 3 huge projects in 5.3 to 6.0 and it took us just one day each. Here's our tips;
Open your old 5.3 project in 5.3 and then open the new 6.0 project in 6.0 add all your snippets, code and buttons; cut and pasting from the open 5.3 project into the new 6.0 project. This step took all day because we really have a lot of code and buttons in Events/Editor. Since 6.0 removes your snippet if you reset a page, we keep the old 5.3 project handy in case we end up needing to reset a 6.0 page. We didn't have to do a lot of the Visual Editor work that we had in the old 5.3 because we really did spend a lot of time creating our new template and layouts for each page (edit6.ly, add6.ly, list6.ly.) The ability to do this along with the new StyleEditor is great!
We did the changes to fix our mysql_query code and now everything is working fine and it is a beautiful project in 6.0 and well worth the time. It took a full day to do the snippet stuff and a full week to do the rest. I hope this helps. Good luck and don't forget to get your template done first.
