php 7 framework builder issues / debugging

I have a little problem which I can hope someone can help me with.

I have a site which uses framework builder quite extensively, and I am attempting to update and upgrade it so it is compatible with php 7.

I am slowly working through the problems, such as getting rid of mysql connections and updating deprecated files such as the ecart definition.

I now have many pages working ok, but some will simply give me an error like this…

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in C:\xampp\vhosts\xxxx.php on line 1

Weird thing is, if I comment out the line which includes the ‘plugin’ page, the ‘parent’ page loads ok
If I just load the plugin page, that also loads ok.
If I then take the code from the plugin page head and body and paste it into the ‘parent’, this also works,

The problem may not be the same across all pages, but I am just trying to find a procedural method to debug this.

Any help appreciated

Can I get FTP access to the page? The issue might be just the size of the plugin content. Framework builder loads the plugin into a string so it can go through and update all of the image paths. If that string is extremely large it can reach memory limits.

I'd love to have a chance to debug it and see if it is something I could address, but you may just need to increase your memory limit on that page.

Hi Ray

Couple of things

The pages were working fine with version 5.4 (or 5.5), and I am not running live, only on xampp on my laptop, so can’t give ftp, though can do screenshare if you are willing- unless you can have another suggestion.

We can do a screen share tomorrow morning and I'll look into this with you.

As a (belated) update to this thread, I just came across another instance of this problem, after a working site was updated from php 5.x to 7.x

The error messages are not the most helpful, as it implies the paths to the framework and library files are not correct, even though they are known to be.
The problem in my case, was when the parent page and the plugin page both had the same name.

If the plugin page was loaded directly, no problem.
If the parent page did not include the plugin page, it would load fine

The problem was resolved when I renamed the plugin page.

Hope this helps somebody if you encounter this problem

My server needs to be migrated to a new machine. php5.6 is my current version but EOL now. When I have to migrate php7 will be the default. Are there any issues with any WebAssist products?

I'm working on updating everything to php7. Currently Design Extender needs to be updated for menu writer and Power CMS, and PowerStore has not been updated. I'm hoping to have those done by the end of the year.

Thanks for clarification. I will have to move server by October. Will my 3 shopping carts still work if I can keep a lower php version available? I am not sure that will be an option though.

Yes. You just have to have it on a php version before 7. Any 6, 5, or 4 version will still work.

I checked with server gods and they assured me that they will migrate the older 5.6 php to new machine. A great load off my mind.
So, with that in mind, when I do have php7 for everything else, are there any issues (besides cart) that I need to know once server transitions? My most used WA is data assist and cart. Before I migrate, is there anything I need to know/change? Remember that I ran into issues when mysql went to MariaDB and caused a number of unforeseen problems. I don't want to migrate until I fully understand what I need to look for. (Color me "scared!")