I upgraded a Joomla 3.10 site to SP Pagebuilder 4.0.5 and frontend displays error 500 - Forum | JoomShaper
Awaiting an answer SP Page Builder

I upgraded a Joomla 3.10 site to SP Pagebuilder 4.0.5 and frontend displays error 500

Asked by Chris Odediran 4 years ago Last activity 3 years ago

After upgraing to SP pagbuilder 4.0.5, the frontend is on Error 500 while the backend is working.

I don't have a recent backup and need urgent help.

7 replies

Ginius

There could be a lot of issues.

Did you clear your cache?
What template are you using?
What PHP version are you using?
What Joomla version are you using?
What when you, temparay, disable your htacces or (seo setting in Joomla)?

Most of the time when you clearing you cache of your browser and joomla solves a lot.

Hace you look into the logfile of hosting to see what caused the 500 error?

Chris Odediran Asked this

I cleared the cache.
The template is Shaper Hope
I haven't disabled htaccess but have disabled some Javascript/CSS settings.

This is what is showing on the error log:
"2022-10-09T11:52:08+00:00 INFO 5.157.13.6 joomlafailure Username and password do not match or you do not have an account yet."

PHP Built On Linux cp-47.webhostbox.net 4.19.150-76.ELK.el7.x86_64 #1 SMP Wed Oct 7 01:33:43 CDT 2020 x86_64
Database Type mysql
Database Version 5.7.23-23
Database Collation utf8_general_ci
Database Connection Collation utf8mb4_general_ci
PHP Version 8.1.5
Web Server Apache
WebServer to PHP Interface litespeed
Joomla! Version Joomla! 3.10.11 Stable [ Daraja ] 14-August-2022 14:18 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable

Ginius

Could it be that you disable frontend login or that a superadmin can't login?

Rashida Rahman Staff

Hi Chris Odediran,

Thanks for your query.

Is your issue solved now? I have visited the link: http://www.gurneyelectric.com/ And it is accessible now!

However, if issue persists, kindly check with lower PHP versions. SPPage Builder supports PHP 8.0(Maximum).

Best Regards

Aris T

I had a similar problem and was able to fix it by increasing the memory_limit in the MultiPHP INI Editor configuration in cPanel.

Rashida Rahman Staff

Thanks @Aris for sharing your experience with us :)

Have a Good Day!

Chris Odediran Asked this

Thanks, that worked.

Log in to reply.