I can't install Carpentry template
I can't install Carpentry template using the Brizy Starter Template. I'm hosted at Hostinger. Why
?
-
Hi Jovelito,
To help us investigate this issue, could you please provide temporary access to your WordPress admin dashboard? This will allow us to take a closer look at your setup and identify the cause of the issue.
Kindly send the following details to communitysupport@brizy.io:
- Community https://support.brizy.io/hc/en-us/community/posts/38328017024914
- WordPress Admin URL:
- Username:
- Password:
We’ll review it as soon as we receive the access.
Best regards,
Ariel H.0 -
Email sent last night. Kindly reply asap. My work is interrupted. Thanks.
0 -
Hi Jovelito,
Thank you for reaching out.
Upon checking, we can see that the server is returning 500 error when attempting to import the Carpentry pre-built layout.This generally means that something on the hosting/server side is preventing the request from completing.
Since your website is hosted with Hostinger, could you please check your hosting control panel and see if ModSecurity is enabled? If it is, please temporarily disable it and then try importing the Carpentry template again.
If the issue persists, please provide us with temporary access to your Hostinger hosting control panel so we can further check the server configuration and see what is causing the 500 error.
Best regards,
Ariel H.0 -
I disabled modsecurity per your instructions. Same error.
Hostinger says the problem is on Brizy's side.
I'm being passed around./
0 -
I'm already talking to a human agent. Not Kodee.
0 -
Here's the error log. Message from Rizka, Hostinger support. :
[26-Aug-2026 02:51:15 UTC] PHP Fatal error: Uncaught Error: Cannot call constructor in /home/u689818968/domains/th*****dge.com/public_html/wp-content/plugins/brizy/import/importer.php:39
Stack trace:
#0 /home/u689818968/domains/thelastingedge.com/public_html/wp-content/plugins/brizy/import/import.php(44): Brizy_Import_Importer->__construct()0 -
Hello Jovelito,
The error "Something went wrong, Bad news, your starter template was not installed. Something went wrong and we couldn’t do it. Please contact us" appears to be a Brizy related error rather than a hosting issue. We have escalated it to our developers and are working on a solution. We will keep you updated as we make progress on fixing this error.
0 -
3 days to resolve this type of issue. I've been passed around. Why is this happening?
0 -
Hello Jovelito,
Understanding the sequence of events may help clarify why the issue was not addressed immediately and how it was escalated:
- August 24, evening: You reported the issue to the Support Team.
- August 25, morning: When the office opened, the Support Team came to know about the bug and began investigating. Initially it was not clear whether the issue was related to the hosting environment or caused by a bug in Brizy. By noon, two other customers had reported the same issue, indicating that this was not an isolated case.
- August 25, evening: Based on the reports received and the investigation so far, the Support Team suspected that the issue could be related to a bug in Brizy. The issue was therefore escalated to the Development Team for further troubleshooting and, if confirmed, a fix.
This timeline is important because the underlying cause was not immediately apparent. Once the Support Team had enough information to suspect a Brizy-related bug, the issue was promptly escalated to the Development Team for further investigation. As a result, we accepted responsibility this morning and stoppped requesting that you contact your hosting provider for a solution.
0 -
Hi Jovelito,
Thank you for your patience.
We installed the final beta version of Brizy on your website to resolve the issue. We also successfully installed the Carpentry Starter Template, so you can continue working on your website in the meantime.
The official version containing this fix will be released in the WordPress repository soon. You should receive an update notification in your WordPress dashboard within the next few days. Until then, you can safely continue using the beta version currently installed on your website.
My apologies for the inconvenience.
Best regards,
Ariel H.0 -
Explain the issue please. What happened? Am I the only one affected? Why?
Plugins are still deactivated. Modsecurity is still disabled in .htaccess. What do i do next?0 -
Hello Jovelito,
The error mentioned above was caused by a bug with Brizy. A fix for this issue is included in Brizy 2.8.23-beta, which has now been installed in your WordPress instance. With this version of Brizy, the starter template issue is resolved. You can now reactivate ModSecurity and other plugins and check whether everything works as expected.
0
Please sign in to leave a comment.
Comments
12 comments