Hi there,

Thanks for reaching out.

PHP 8.2 is supported by the latest version of SP Page Builder, so the PHP version itself should not be the issue.

Since you're getting a 500 error when trying to edit any SP Page Builder page, we would need to see the actual error message to determine the cause.

Could you please enable Joomla Debug and set Error Reporting to Maximum under System → Global Configuration, then try opening the page editor again?

Once the error appears, please share the complete error message/stack trace with us. If possible, please also check your hosting's PHP/server error log and share the corresponding error.

Additionally, please let us know:

• Your exact Joomla version
• Your exact SP Page Builder version
• Your exact Educon template version
• Whether you are using any security/firewall or optimization extensions such as Akeeba Admin Tools, JCH Optimize, or Cloudflare

A 500 error can also be caused by server security rules such as ModSecurity, JavaScript compression, or other extensions interfering with the SP Page Builder editor.

Once you provide the exact error, we can investigate it further.

Best regards,

The text still reads the same after turning the Joomla Debug and Error reporting to maximum: Request failed with status code 500.

joomal 5.4.8 SP Page Builder v6.8.0 Educon template version 4.0.3 No security/firewall or optimization extensions

Hi Damjan,

Thanks for the version details.

One important note first: "Request failed with status code 500" is generated by the editor's JavaScript layer — it only tells us the server returned a 500, it does not show the actual PHP error. That is why enabling Joomla Debug did not change what you see on screen. The real error is inside the server's response, so we need to pull it out from there.

1. Get the actual error from your browser (most important step)

   • Open the SP Page Builder editor for any page
   • Press F12 to open Developer Tools and switch to the "Network" tab
   • Reload the page (F5) and let the error appear
   • Find the request marked in red with status 500 (it will be an index.php request with option=com_sppagebuilder)
   • Click that request and open the "Response" (or "Preview") tab

   That tab contains the real PHP fatal error / stack trace. Please copy the full text and paste it here.

2. Check your server error log

   In cPanel (or your hosting panel) open "Errors", or the raw error_log file, which is usually in your site root or in a logs folder. Please share the entries from the moment you triggered the error.

While you collect that, a few things are worth trying. Please take a full backup first:

• Reinstall SP Page Builder 6.8.0 over your current installation. Download the package from your JoomShaper account and install it again without uninstalling. This re-runs the database schema updates — an incomplete update is one of the most common causes of a 500 in the editor. Afterwards go to System > Manage > Database and click "Fix" if anything is listed there.
• Clear all caches: System > Clear Cache > Delete All, then delete the contents of the /administrator/cache/ folder via FTP or File Manager, and test in an incognito window.
• Increase PHP memory_limit to 256M (cPanel > MultiPHP INI Editor). The editor is memory-heavy, and an exhausted memory limit returns exactly this error.
• Open configuration.php and confirm $live_site is empty: public $live_site = '';

If the error text is not clear, or you would prefer us to check directly, please share a temporary Joomla Super User login plus FTP/cPanel access in the "Hidden Content" field below (only our support team can see it), and we will investigate on your site.

Best regards,

Incorrect use of <label for=FORM_ELEMENT> The label’s for attribute doesn’t match any element id. This might stop the browser from correctly autofilling the form and accessibility tools from working correctly.

To fix this issue, make sure the label’s for attribute references the correct id of a form field.

2 resources Violating node Violating node Learn more: The label elements

Hi Damjan,

Thanks, but that isn't the error we need — the <label for=...> notice is a harmless accessibility warning Chrome shows on almost every page. The real PHP error is only in the Network tab.

Please try this:

1. Open the SP Page Builder editor, press F12, click the Network tab (not Console/Issues).
2. Press F5 and let the error appear.
3. Find the row with status 500 — an index.php request containing option=com_sppagebuilder.
4. Right-click it → "Open in new tab". Copy the full text that appears and paste it here.

Also helpful: your server error log (cPanel → Metrics → Errors, or error_log in your site root) and /administrator/logs/error.php, from the moment the error occurs.

Two quick things meanwhile:

• Create a brand-new blank page in SP Page Builder — does that one open, or also fail? This tells us straight away whether it's a component/server issue or your page data.
• Please confirm you reinstalled SP Page Builder 6.8.0 over the top and ran System → Manage → Database → Fix, and raise PHP memory_limit to 256M.

If you'd rather we look directly, share a temporary Super User login plus FTP/cPanel access in the Hidden Content field below (visible only to our support team) and we'll investigate for you.

Best regards,

{"success":true,"message":null,"messages":null,"data":{"message":"Session mismatched."}}

This happens when I press the Save button after I've changed something in the text on whatever page.

Here it is what it says in the Metrics/Errors> [Fri Sep 11 16:39:30.198393 2026] [:error] [pid 1231683:tid 1231731] [client 144.48.151.52:36246] File does not exist: /home/aikikai/oneclip.aikikai.org.mk/index.php, referer: https://oneclip.aikikai.org.mk/index.php/en/pages/blogoneclip-2/296-patem

The folder /administrator/logs/ is empty.

Succesfuly created brand-new page and saved it without trouble. Also tried on anothe page to change some text and it worked, but returning to the specific page the error apeard again....

Hi Damjan,

Thanks — that response tells us what's happening.

"Session mismatched." usually isn't a session problem. When you click Save, the page content and Joomla's security token go to the server in one request. If that request is too big for a server limit, PHP drops the whole thing — token included — and you get this message. The 500 comes from the same limit.

It fits what you're seeing: a new page saves, a small edit elsewhere saves, only this one large page fails.

Quick check (30 seconds): open the failing page, press F12 → Network, click Save, select the index.php?option=com_sppagebuilder request and note its payload size. Compare it with a page that saves fine. If the failing one is much bigger, that's the cause.

Fix 1 — cPanel → MultiPHP INI Editor:

post_max_size = 128M
memory_limit = 512M
max_input_vars = 10000
max_execution_time = 300

Fix 2 — your host. ModSecurity is a server module, not a Joomla extension, so it may be active even though you have no security extensions. Its default request limit is 128 KB. Ask your host to raise SecRequestBodyLimit, SecRequestBodyNoFilesLimit and LimitRequestBody, and to check the ModSecurity log at the moment you press Save.

Then clear all caches and retest.

One more thing: if you pasted an image directly into a Text/HTML addon on that page, replace it with a file from the Media Manager — that alone can make a page too large to save.

Let us know the payload size and we'll take it from there.

Best regards,