Allowed Memory Size
Marc Dechèvre
Hi,
I am using SP Page Builder on several Joomla 3 sites.
Probably since the last update (4.0.5) the homepage of several websites (using SPPageBuilder as home). The error message is
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 266240 bytes) in ---/components/com_sppagebuilder/helpers/articles.php on line 400So I investigated that file and the block that creates the issue is the following :
foreach ($rows as $row) {
if($include_subcategories) {
array_push($cats, $row->id);
if (self::hasChildren($row->id)) {
$cats = self::getCategories(array($row->id), $include_subcategories, true, $cats);
}
}
}If I disable the following 3 lines then the sites do work again :
if (self::hasChildren($row->id)) {
$cats = self::getCategories(array($row->id), $include_subcategories, true, $cats);
}Can you please provide asap a fix for this issue ? (this is a request for Support since I have a valid licence. Txs)
Rashida Rahman
Accepted AnswerHi there,
Thanks for contacting us and Sorry for the inconvenience. Please contact your hosting provider to increase the memory limit.
Would you please let me know what exactly version of ____ you have: a) PHP b) Joomla c) Template name and version
Best Regards
Marc Dechèvre
Accepted AnswerHi,
This issue was reproduced with 2 different hosting companies and I already tried increasing the Memory Limit to 768M for example as a temporary workaround. SP Page Builder still crashes.
But anyways, the issue is not the Memory Limit but the PHP file. Can you JoomShaper pls provide a fix for that asap? Txs.
Note: for Pages which do not call Articles, it works fine. It is only when you call articles that this articles.php file is called (quite logically).
Marc Dechèvre
Accepted AnswerHi. Txs for providing the fix or workaround in the coming workdays.
This is indeed a question
- to the support team
- by a customer paying a subscription
As a volunteer, I have given 2500+ answers on a Joomla forum. For free. I can't believe that 2 days after filing an issue (with technical details) I still don't have any proper feedback when I pay for a licence
Sorry for the bad mood, but every time it is the same (bad) experience.
Holger Groß
Accepted AnswerHello Joomshaper-Team,
I've the same problem after updateting to the last recent version of helix and sp-pagebuilder. Increasing memory isn't the solution: I give 2 GB and the same error is present.
Interesting fact: the problem hits not every page of the homepage.
Please help! I can not make any changes ...
Thank you.
Kind regards Holger
Marc Dechèvre
Accepted AnswerIs it really too much to ask to have an official reply from JoomShaper
- for a paid extension
- when the paying customer identifies a bug and provides a fix himself ?
Does the new release of today fix this issue (nothing is mentioned about "memory" in the changelog).
Rashida Rahman
Accepted AnswerHi Marc Dechèvre,
I'm really sorry for not being there for a while.
I have never received the following info that I asked at first place :(
Would you please let me know what exactly version of ____ you have: a) PHP c) Template name and version
These are important to know the environment details to investigate as well as report.
Best Regards
Holger Groß
Accepted AnswerHello Rashida,
we are working on Template "Doctor 2.2" with PHP 7.4 or 8.0 or 8.1 ...
Hope you can help because we had to downgrade to Pagebuilder 3.* to make the Site working for the customer
Kind regards Holger
Marc Dechèvre
Accepted AnswerHi Rashida,
Outside temperature is 10 degrees Celcius (in case you would also ask). I had provided already the relevant information, namely
- version of SP Page Builder, namely 4.0.x (4.0.5 to be precise)
- I could reproduce the issue on 4 websites : PHP7.4.33, PHP7.4.33 again, PHP7.4.25 and PHP8.0.21
- as explained, it is not on all websites bc as seen in the workaround I sent the issueonly trigger when you pull Articles in the builder
- so it is not related to a template as you could understand from my initial post, it is purely SP Page Builder related (to make it plain, the issue is also there with Protostar)
So now that you have all information, I am happy to read the real answer of JoomShaper :)
cmfionline
Accepted AnswerI had the same issue with newsberg, same php (7.4 or 8.x), sql 8.x, sppb 4.x and with no response, i was forced to downgrade to sppb 3.x. I am very much interested to know the response
Rashida Rahman
Accepted AnswerHi all,
Actually, Helix3 based templates supports PHP 7.4 maximum and Helix Ultimate base templates support PHP 8.0 maximum. This is why I asked about those info. Sometimes only downgrading PHP version solves this error as we have noticed previously. However, we have got response from some user that SP Page Builder version 4.0.6 solves the issue for them as well. Have you tried to update SPPB to 4.0.6, please?
Best Regards
Marc Dechèvre
Accepted AnswerHi Rashida,
I have upgraded to 4.0.6 (when I reported the issue, the latest version was 4.0.5). My manual workaround in l/components/com_sppagebuilder/helpers/articles.php has been reverted by the patch... and the issue does occur any more.
So the issue was indeed caused by SP Page Builder itself and it means that your team fixed the root cause. Txs (but next time I suggest that your Support just replies "hey txs for reporting this bug. The root cause was XXX and we will fix it in the next release".
Rashida Rahman
Accepted AnswerHello,
Actually, without investigating we can not simply say that. As from our previous experience, we faced this same type error statement for different reasons. Our other support member has reported the issue to the developer and hence the issue has been addressed and fixed in the new version. I was not so quick for some other reasons, sorry about that.
Thanks for your patience.
Wishing all of you Best Luck!