BUG After SPPB 6.8.0 Update, Error 500 When Saving - Question | JoomShaper

BUG After SPPB 6.8.0 Update, Error 500 When Saving

Laurent

Laurent

SP Page Builder 2 weeks ago

Hi,

Since latest SPPB update, from backend or frontend, when I save a page, the loading button does not stop and I get error 500. see Hidden Content area for details and credentials.

Thanks L.

0
4 Answers
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 2 weeks ago #231839

Hello,

Thank you for your questions.

  1. I identified the issue by investigating the website through the browser’s Developer Tools, particularly the Console and Network tabs. By checking the errors and requests triggered when saving the page, I was able to trace the source of the error to the Smart Search - Business Listings Finder plugin.

  2. Yes, based on the investigation, the issue appears to be caused by a compatibility/bug issue within the Smart Search - Business Listings Finder plugin. Since disabling the plugin resolved the problem and the SP Page Builder save functionality is now working normally, this confirms that there is a conflict involving that plugin.

Best regards

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 2 weeks ago #231807

Hello Laurent,

We sincerely apologize for the inconvenience.

I have checked your website and found that the issue does not appear to be related to SP Page Builder. The 500 error is being triggered by the Smart Search - Business Listings Finder plugin.

I have temporarily disabled this plugin, and after doing so, the page saving functionality is working normally from both the backend and frontend.

Could you please check the website on your end and confirm whether everything is now working as expected?

Thank you for your patience and understanding.

Best regards

0
Laurent
Laurent
Accepted Answer
2 weeks ago #231818

thanks for your feedback, works fine.

just 2 questions :

  1. what have you done to find problem is coming from Smart Search - Business Listings Finder plugin ?
  2. so it is a bug coming from this plugin?

Thanks

0
Laurent
Laurent
Accepted Answer
2 weeks ago #231840

ok thanks for your feedback

0