Awaiting an answer SP Page Builder

Stratos Template - Request failed With status code 500

Asked by Hans 1 year ago Last activity 1 year ago

Hello

Fresh installation: Stratos V1.0.2 Quickstart Pack Joomla 5

PHP is 8.3

Wanted to enter my License key. When I go to:

SP Page Builder Pro - Settings - Options - License & Update:

Error comes in red: "Request failed with status code 500"

Even if I just go to Settings: Also the same error comes.

Updated to latest SP Page Builder and Helix: The same error comes.

When I go to Template Style, I can enter my License key there. Works.

However, the License key does not show up afterwards in SP Page Builder Pro - Settings - Options - License & Update.

The website is under construction, so external access is not yet possible.

The website is IP-restricted. If you provide your IP address, I can give you the credentials and you can check.

4 replies

Oldest first Newest first Most helpful
Atick Eashrak Shuvo Staff
1 year ago

Apologies for the inconvenience you're experiencing. The issue you're facing may be related to a mismatch in the database structure https://prnt.sc/9rGOlWL6KQKK.

To resolve this, please follow these steps:

  1. Update the database structure by navigating to System > Maintenance > Database in your Joomla backend and clicking the “Update Structure” button if prompted https://prnt.sc/wbEs3rtFFiFa.
  2. Reinstall the latest version of SP Page Builder Pro by downloading it from the following link: SP Page Builder Pro - Latest Version

This should resolve the issue.

If the problem persists after following these steps, please let me know. I’ll be happy to investigate further.
Thank you for your patience and understanding.

Best regards

Hans Asked this
1 year ago

Thank you very much. That solved the problem.

However, it is surprising that a fresh, new installation of the package on a system that meets all requirements causes such an error.

At the very least, this should be noted in the documentation.

Atick Eashrak Shuvo Staff
1 year ago

You're very welcome! I'm glad to hear the issue has been resolved.

You make an excellent point — it is indeed unexpected for a fresh installation on a fully compatible system to encounter such an error. I’ll make sure to forward your feedback to the development/documentation team so this behavior can be reviewed and clearly noted in the documentation for future users.

Thank you for bringing this to our attention.

Log in to reply.