Black Friday 2026 50% off every plan Our biggest deal of the year on #1 Joomla products.
Ends in 13d 05h 05m 35s
Claim 50% off
Solved SP Page Builder

SP Page Builder Pro 6.9.1 – Media Manager Error 508

Asked by Tanidis Triantafillos 1 month ago Last activity 1 month ago

Hello JoomShaper Support Team,

I am experiencing an issue with the Media Manager included in SP Page Builder Pro 6.9.1 on my Joomla website.
Please note that the issue is specifically related to the SP Page Builder Media Manager and NOT the native Joomla Media Manager.

My current environment is:

  • Joomla: 5.4.9
  • PHP: 8.3.35
  • SP Page Builder Pro: 6.9.1
  • Website: dev.agorazin.gr

When I open the Media Manager from within SP Page Builder Pro and browse the media folders, I repeatedly receive the following error notification:
“Request failed with status code 508”
I have attached a screenshot showing exactly what happens.

The folders and files are displayed in the SP Page Builder Media Manager, but the HTTP 508 error appears while using it. The problem occurs inside SP Page Builder's own Media Manager.

Could you please advise what may be causing these requests to return a 508 status code and how I can resolve the issue?

Thank you in advance for your assistance.
Best regards

Accepted answer

Marked as the solution
Ziaul Kabir Staff

It’s great to hear that your issue has been resolved.
If everything is working fine now, please mark the question as complete by accepting any of our answers.

Thank you!

11 more replies

Ziaul Kabir Staff

Hi Tanidis,

Thank you for the detailed information.

We restored your website locally using the Akeeba Backup and tested the SP Page Builder Media Manager on the restored site.

However, we were unable to reproduce the issue locally. We did not encounter the repeated index.php requests or the 508 error while using the Media Manager. But this issues present on your live site.

Since the issue is occurring only on your live website, this suggests that it may be related to the specific server environment or configuration of your live site.

Could you please check the server error logs and any security rules, such as ModSecurity or firewall rules, that may be affecting these requests?

Best regards,

Tanidis Triantafillos Asked this

Hello,

Thank you for your previous response.

I investigated the issue further using Chrome Developer Tools and I would like to provide you with some additional information.

I can confirm that one of the requests that repeatedly fails while browsing folders in the SP Page Builder Media Manager is similar to:

/administrator/index.php?option=com_sppagebuilder&task=/editor.folders&type=folders&filter=&path=%2Fimages&_method=get&timestamp=...

The request returns HTTP 508.
Although Chrome displays the status as “508 Loop Detected”, the actual response returned by the server is:

508 Resource Limit Is Reached
The website is temporarily unable to service your request
as it exceeded resource limit.
Please try again later.

The response headers also include:

Server: nginx
Retry-After: 14400
Content-Type: text/html

I have also recorded a short video showing the issue and how it occurs while browsing the Media Manager:
Video demonstrating the issue on YouTube.

Based on these findings and your previous recommendation, I have now contacted my server/hosting support and asked them to investigate the server logs and determine exactly which resource limit is being reached and which server component is generating the 508 response.

In the meantime, I would appreciate it if you could also clarify one point from the SP Page Builder side:

  • Is the number and frequency of requests generated by the Media Manager while browsing folders under /images expected behavior?

I am asking because the issue occurs specifically while the Media Manager is loading/browsing the media folders, and multiple requests are generated during this process. I would like to determine whether the server is simply enforcing a resource limit that needs adjustment, or whether there could also be an abnormal/repeated request pattern from the Media Manager that contributes to reaching that limit.

Once I receive the server administrator's findings regarding the exact resource limit being triggered, I will update this ticket with their response.

Thank you for your assistance.

Ziaul Kabir Staff

Hello Tanidis,

Thank you for the additional information and for checking the request through Chrome Developer Tools.

The details you provided are helpful. The response clearly indicates “508 Resource Limit Is Reached”, which is generated by the server rather than by SP Page Builder itself. This also matches our local testing, where we restored your site from the Akeeba Backup and could not reproduce the issue.

Regarding your question, the Media Manager does make requests while browsing folders and loading the media files. This is expected behavior. However, we do not see an abnormal request loop or excessive request pattern in our local testing.

Since the issue occurs only on your live server and the server is returning a resource-limit response, we recommend continuing with your hosting provider to determine which specific resource limit is being reached (such as CPU, memory, PHP processes, entry processes, or another hosting restriction).

Once your hosting provider provides the relevant server logs or identifies the resource limit being triggered, please share their findings with us. We will be happy to review them from the SP Page Builder side as well.

Thank you for your cooperation.

Best regards,

Tanidis Triantafillos Asked this

Hello,

I now have an update from my hosting provider after they investigated the issue directly on the server.

They checked the Plesk logs and identified an issue related to the SP Page Builder system plugin. More specifically, they identified the problem around line 83 of:

/plugins/system/sppagebuilder/sppagebuilder.php

As a temporary workaround, they commented out line 83 of this file.

After making this change, they reported that navigation in the Media Manager works correctly when allowing each operation to finish loading before proceeding to the next one. However, they also confirmed that the error has not disappeared completely.

This is particularly interesting because, before contacting the hosting provider, I had also found repeated PHP warnings in the server error log pointing to the same area of the SP Page Builder system plugin:

PHP Warning: Object of class stdClass could not be converted to int
in /plugins/system/sppagebuilder/sppagebuilder.php on line 83
PHP Warning: Attempt to read property "id" on int
in /plugins/system/sppagebuilder/sppagebuilder.php on line 86

The hosting provider also found the following JoomShaper forum discussion while investigating:
“Invisible Site After Last Update To SP Pagebuilder 6.9.1”

Since both the server logs and the hosting provider's investigation point specifically to line 83 of the SP Page Builder system plugin, could you please investigate this part of the code?

In particular, could you please confirm:

  1. Whether this is a known issue in SP Page Builder Pro 6.9.1.
  2. What is causing the stdClass could not be converted to int warning on line 83 and the subsequent Attempt to read property "id" on int warning on line 86.
  3. Whether commenting out line 83 is considered safe, or whether you can provide an official fix/patch for this issue.
  4. Whether this PHP issue could contribute to the repeated Media Manager requests and ultimately trigger the server-side 508 Resource Limit Is Reached response.

I can also provide the relevant server logs if required.

Thank you for your assistance.

Ziaul Kabir Staff

Hello,

Please download and install the latest version, 6.10.0, and let me know whether these issues have been fixed.

Thanks.

Tanidis Triantafillos Asked this

Hello,

I performed the update, but the exact same problem still persists.

Is there anything else that could be done to resolve our problem? Because our client is unable to work on their website.

Thank you very much.

Ziaul Kabir Staff

Hello,

Please, share your cPanel access.

Thanks.

Tanidis Triantafillos Asked this

Hello,

Thank you for your reply. I am sending you the access account you requested.

Ziaul Kabir Staff

Hello,

Could you please check this now? I noticed that many images have been deleted from your directory but are still present in the database and caused 404 on console. Please remove those images from the database as well.

Thank you!

Tanidis Triantafillos Asked this
1 month ago · edited

Hello,

Thank you very much for your prompt response and assistance.

After checking the Media Manager again, both my client, who manages the website, and I can confirm that the issue appears to have been resolved.

However, I would like to clarify a couple of points regarding the images that have been deleted from the directories but still have corresponding records in the database.

  1. Image deletion and database records

If we delete an image directly through the SP Page Builder Media Manager in the future, should its corresponding database record be automatically removed as well?

In other words, is the current situation caused by images that were previously deleted outside the SP Page Builder Media Manager, or is there a possibility that deleting images through the Media Manager itself could leave orphaned database records?

I would like to make sure that we won't encounter the same issue again or have to manually clean up the database whenever an image is deleted.

  1. Identifying and removing orphaned media records

Is there a recommended way to identify all orphaned image records in the SP Page Builder database, meaning images that are still registered in the database but whose actual files no longer exist on the server?

Example: https://prnt.sc/HUyPdw3gUghG

Does SP Page Builder provide any built-in cleanup or synchronization functionality for this purpose?

If not, could you please provide a safe method, such as a specific SQL query or another recommended procedure, to identify and remove these orphaned records without affecting any valid images or other website content?

I would like to clean up the existing database entries properly and prevent similar issues in the future.

Thank you again for your valuable support and assistance.

Ziaul Kabir Staff

Hello,

There is no separate cleanup method available in the SP Page Builder itself. Please delete the files directly from the SP Media Manager or, if necessary, from the database.

You may use ChatGPT or Claude to help generate the appropriate SQL commands based on your database structure.

Thanks!

Log in to reply.