Hi there!

Sorry for your issue.

Have you checked the following section also?

https://www.joomshaper.com/documentation/sp-page-builder/sp-page-builder-3#if-you-cannot-load-page-templates-or-sections-library-or-use-front-end-editor-span-class-h4-br-span

Kindly, do let me know if you have followed this.

Best Regards

Hi Rashida! allow_url_fopen is ON; PHP memory 512M; PHP max_excution_time= 300; PHP upload max filesize = 32M; OpenSSL? I guess - the sites all have SSL certs. WHM Panel and file_get_contents() are beyond my scope. Downscale to PHP 7.3 or even 5.6 won't work. Nor will 8.0 or 8.1.

Of the parameters I don't know or can't access, I suspect other things would be broken as well. But only this particular call is a problem. I'd invite you to run the front end on my sites, within SPP click on "Blocks", then have a look at the errors that appear - both a synatax error of an unexpected token ('.') and a Failed to Load Resource: cannot parse response.

I'm guessing there's a code glitch, but this is in two different sites, and uninstalling/reinstalling SPP didn't fix. So I'm guessing then it's a higher level thing that's affecting the whole hosting account, but I don't know where to look. As well, usually other things would break, but not here.

Andrew

Hi,

Kindly, ask hosting support to check if mod_security is enabled for your site. If yes, then kindly turn it off for both of your problematic websites, and check!

For your other parameters, your hosting provider can help you.

Note: The link of your cpanel is not working for me.

Best Regards

Hi Rashida!

1. Confirmed that " file_get_contents()" is valid and operational on my host.

2. They won't turn off "mod_security". But given GoDaddy host about 18% of American? World? websites, I suspect that's not a problem.

3. I've provided refreshed Cpanel log-on details. I think the old one was fine (minus the sentence ending period), but just in case, I've copied and pasted in the hidden section below.

4. I'm guessing that your php calls for "blocks" are close to identical on the other sections of the menu ("layouts" or "add-ons" for example) and they work, so likely all the other php provisioning / security / SSL issues are okay. The problem reports as a syntax error in SPP, which is leading to a parsing error on that specific call. But then it occurs on two sperate web sites, separate Joomla, Helix, and SPP installs. I'm out of ideas. :-(

Hi Rashida!

1. Confirmed that " file_get_contents()" is valid and operational on my host.

2. They won't turn off "mod_security". But given GoDaddy host about 18% of American? World? websites, I suspect that's not a problem.

3. I've provided refreshed Cpanel log-on details. I think the old one was fine (minus the sentence ending period), but just in case, I've copied and pasted in the hidden section below.

4. I'm guessing that your php calls for "blocks" are close to identical on the other sections of the menu ("layouts" or "add-ons" for example) and they work, so likely all the other php provisioning / security / SSL issues are okay. The problem reports as a syntax error in SPP, which is leading to a parsing error on that specific call. But then it occurs on two sperate web sites, separate Joomla, Helix, and SPP installs. I'm out of ideas. :-(

Hi Rashida!

Sorry for all the repeated posts below this. I kept posting, but the thing kept showing that I was posting a blank field. So signed out/then in again and found all these repetitive posts.....which your thing won't let me delete. :-(

Hi Rashida!

1. Confirmed that "file_get_contents()" is valid and operational on my host.
2. They won't turn off "mod_security". But given GoDaddy have 18% of the American? Global? hosting market, I doubt that's the problem.
3. I've provided refreshed Cpanel log in details.
4. I'm guessing your php calls for "blocks" are close to identical as those for "layouts" and "add-ons". Those calls work perfectly so likely the other PHP provisioning/security/SSL issues are not a factor. The problem reports as a syntax error in processing SPP code (I assume it's SPP), which in turn appears to be leading to a parsing error on that specific call. But then the identical problem (and reported error) is appearing in two separate web sites, separate Joomla, Helix, and SPP installs. I'm out of ideas. :-(

Hi! I have a similar error layouts and templates are not loaded in SPPB! I can't fix this error for more than a month, the correction steps in the SPPB documentation do not help.(((

Hi SonicShock,

No issues. I have tried your cpanel to visit now, this time succeeded!

However, could not find mod_security under security section there. I have shared a screenshot in the hidden content box.

Would you please contact your hosting provider again and request them to disable mod_security only for your problematic sites to check if this is causing the issue or not. It's important. Beause, we have experienced such cases many times before. Sometimes mod_security sets too sensitive rules, and these can causes blocking of many frontend features, even saveing doesn't works sometimes.

This is the reason I am requesting to disable mod_security repeatedly. Sorry about that!

Note: After disabling mod_security kindly clear your Joomla and browser cache deeply, and then check things.

Best Regards

Hello vlad,

Sorry to hear that.

Would you please give me your post link here?

Best Regards

Hi Rashida!

My host, GoDaddy, cannot, or more accurately, will not disable mod_security (on a shared hosting platform). I have to admit that few of your other users appear others are having this issue, but at the same time, if GoDaddy's mod_security rules were the problem, you'd have a LOT of complaints.

My understanding is that USUALLY if there's a mod_security block, it gets reported specifically as such back to the browser. Here, when attempting to call these blocks, the Javascript console reports both a syntax error, (an unxpected period), and a line of code, which I presume is generated by SPP, which cannot be parsed.

Only your coders would know for sure, but I'm guessing as well that a similar type call is made when the SPP user clicks on "layouts", "addons", etc., and those calls work perfectly.

Warmest regards, Andrew

Hi Friends! Is anybody looking at this?

Hi! I managed to solve this problem. When the server switches to php 7.x.x., templates and sections are loaded. When the server switches to php8.x.x., templates and sections are not loaded. It turns out an error on the SPPB side.

Thank you posting the update Vlad. I'm running PHP 7.4. I did try changing versions of PHP both up and down, although given your comment, I'm wondering if there's some legacy left behind in making those switches. There are other random things not working in the side box - for instance, page export. (It can be done elsewhere, just not there.) Also getting an error report in the Javascript console.

Hello,

I am really sorry for not being there!

Would you please ask your hosting provider to just exclude your site from being under mod_security to check if this is causing this issue or not? It should be possible to make an exception, then they would not have to turn of mod_security for all. Just to check, would you kindly request them?

If your site is out of it's range then clear your Joomla and browser cache deeply and check if it lets you to use the blocks section or not.

Best Regards

Hi Rashida! Thanks for that. GoDaddy won't do it for a shared hosting plan (even though I have a virtual dedicated resources.) I suspect mod_security isn't the problem anyway, as I'd get a report of such. I am getting a report of a syntax error on calling the blocks.

Hi, Rashida! I have a problem only with php 8xxx, When working on php 7.4, blocks are loaded, everything works.

Hi SonicShock,

I am really sorry to hear that... May I take a backup of your site?

Best Regards

Hi vlad,

Sorry to hear that:(

However, Blocks loads fine with PHP 8 at my end though, but I am happy that you can run it under 7.4 well...

Best Regards

There is clearly still an issue here that's partly related to PHP - Vlad can fix this with PHP 7.4 but that's hardly an acceptable fix. I've in the past given log-on credentials for my site, and wish that instead of just guessing, someobdy would look at the browser read-out and see that PHP syntax errors are being generated walhen calling the blocks session. I suspect the problem is more widespread than the complaints your getting - as in my case, I am just building whatever blocks manually on my own. But if I couldn't do that, I'd be here daily, as would, I suspect, a lot of other clients.