SP Property Problemas Repeated 500 Error With SP Property – Ongoing Issues Despite Stable Server And Backend - Question | JoomShaper
SP Page Builder 6 is Here! Learn More →
Back to the questions

SP Property Problemas Repeated 500 Error With SP Property – Ongoing Issues Despite Stable Server And Backend

JH

Jonnathan Huertas

Extension 4 months ago

Dear Support Team,

I hope this message finds you well.

I'm writing once again regarding ongoing and repeated HTTP 500 errors related to the SP Property component on our Joomla website (showroomcol.co). These issues have become frequent and disruptive, directly impacting site performance and client satisfaction.

We want to emphasize that we have already reviewed our server environment thoroughly — including IP configuration, PHP settings, and server logs — and everything is working as expected on our end. The Joomla backend is fully operational, and the problem seems to be directly tied to the SP Property component.

If you check our support history, you’ll find that we’ve submitted multiple tickets over time reporting different issues with SP Property. While previous fixes have temporarily solved the problem, the errors keep coming back.

This is now creating serious concern: our client is frustrated, and our company’s reputation is at stake. We are asking for your urgent and thorough assistance to implement a permanent solution, not a short-term workaround.

Please prioritize this request and help us resolve this matter once and for all.

Best regards,

0
1 Answers
Order by
Oldest Newest Votes
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 3 months ago #195699

Thank you for your message, and we sincerely apologize for the inconvenience caused.

After reviewing your site and server configuration, we discovered that the root directory contained an incorrect index.php file — not the default one used by Joomla. It appears that WordPress was previously installed in the same directory, or an attempt was made without properly cleaning up the environment.

To resolve the issue, we have replaced the incorrect file with Joomla’s default index.php, and the frontend is now functioning correctly. For your reference, we have renamed the previous file to old_index.php in case you need to access it later.

Going forward, we kindly recommend being extra cautious when installing a new site—especially when working on a live or business-critical environment—to avoid conflicts like this.

Please let us know if you need any further assistance.

Best regards

0