This topic is locked

A Procedure Question on PHPRunner 8

2/18/2015 2:35:16 PM
PHPRunner General questions
A
Anapolis author

[size="3"]I have been using PHPRunner since 2010 and have dutifully upgraded to each new version.
Typically I have 4 projects every 2 to 3 weeks that I have to begin.

So I am still updating, modifying several projects while starting on new ones.
These clients usually ask for something new, some groovy view, different types of data exports & reports as they get used to using these different web applications.[/size]
I routinely save, save, save during the development days and every Save As goes into a new output and project folder under a new name so that I can as much as possible return to a certain "moment in time"
[size="3"]So, my question here: How do I prototype new pages in an existing already working "finished" online project? [/size]
[size="3"]

  • I need to produce new pages that may use tables already in the project file, or to create new tables to base additional pages on.
  • That prototyping can affect the whole project and make it unreachable online if an update of existing pages or just a minor rearrangement of a menu needs to be uploaded.
  • The files necessary for those changes may now contain code calling for elements of my prototyped pages and will cause an error on logging in or before.
  • If I prototype these pages inside a separate copy of the project folder, but I never upload these pages online from that folder, I can see how they work but when the development is extensive there is no easy way to export the working prototypes back into my "live" project folder.
  • And if I try working on prototype new pages and views in the existing live production folder that does upload to the online site it is not as simple as then unchecking all of the pages and deleting the menu link before uploading other needed changes.

[/size]
Does someone have a time-tested series of steps or procedures for having to return to projects and post updates or new views?
A pretty reliable way to keep the pages "under development" from interfering with a project already running online with daily users?

I have things that I do, step-by-step, but it is laborious and I keep thinking someone has already developed a better PHPRunner wheel that I could use, too.
Thanks for any tips!

HJB 2/18/2015

A pretty reliable way to keep the pages "under development" from interfering with a project already running online with daily users?

end of citation

Seems as if you missed to yet discover (since 2010 ;-) the built-in "SAVE AS TEMPLATE" feature while the as well built-in CONNECTION selection feature is enabling to switch between "under development" and "online project" with ease, thanks to the best RAD tool worldwide and its developers.

P.S. "Working with projects" within the PHPR v8.0 MANUAL is getting more specific on that ...

A
Anapolis author 2/19/2015



A pretty reliable way to keep the pages "under development" from interfering with a project already running online with daily users?

end of citation

Seems as if you missed to yet discover (since 2010 ;-) the built-in "SAVE AS TEMPLATE" feature while the as well built-in CONNECTION selection feature is enabling to switch between "under development" and "online project" with ease, thanks to the best RAD tool worldwide and its developers.

P.S. "Working with projects" within the PHPR v8.0 MANUAL is getting more specific on that ...


Thank you for taking the time to read and reply, walk2fly.
The "interference" I described has nothing to do with how I use the multiple connection feature. I could not develop if I was not using multiple localhost and online connections.

I supervise some 40 projects all on separate databases and several different hosting accounts.
I am talking about keeping track of the under-the-box changes to the PHPR script itself once new pages are added but are not finished and not intended to be included in the online project.

I was asking is there a method I have missed that keeps the phpr file from including new table dependencies, for instance, that will be included if I upload a modification to pages or forms that have already been installed online.
I cannot see ahead of time which files Runner is thinking have been modified and it is intending to upload. They may refer to the prototype pages in a way that creates a dependency, say on a "missing table" that belongs to the prototype-in-development. Thinking I am simply modifying an existing form after the upload I may have introduced an error to the project because it is requiring pages and tables that are not intended to be added until finished and approved.
As for the Template feature, yes, I do use that quite a bit.
In the Manual, which I have read over and over, there is this reference which I would like more explanation about from the PHPRunner staff.

After you enabled Lock pages modified in Visual Editor automatically option, all pages that you manually modify will be locked from further automatic modifications. You can still modify locked pages manually.


What does "Lock pages" and "Automatic modifications" Mean?
How does that work, what is it modifying specifically, how does it determine what it will modify automatically if the option is checked?

HJB 2/19/2015

After you enabled Lock pages modified in Visual Editor automatically option, all pages that you manually modify will be locked from further automatic modifications. You can still modify locked pages manually.
Revision history limit defines the number of page revisions to be saved in Visual Editor.
Use Format HTML code option to auto-format HTML code of pages in Visual Editor.
unquote excerpt out of manual
Got your point ..., it is my understanding that LOCKING of a page is preventing automatic modifications like e.g. HTML code auto-formatting (and may be else?) which means that once you run drag and drop sessions of fields, you can feel somehow safe on your work done. In regard to "saved revisions" I understand that (depending on the set limit of page revisions) one can RELOAD "still under construction pages" at will to run testing and further completion works.
Certainly ADMIN shall give us some additional inspirations here at his earliest convenience.