• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Sitebuilder 4.2 Error: Site compilation has been failed

I

isabel.estevao

Guest
Hi,

I receive the following sitebuilder error when I try to edit a specific site:

Internal Sitebuilder error.
File: /usr/local/sitebuilder/include/SB/Helpers/Wizard/Edit/Html/Site.php; Line: 42
Message: Site compilation has been failed; Code: 0

And when I try to publish that same site it returns the following error:

Notice: Undefined offset: 4096 in /usr/local/sitebuilder/include/Base/SyntaxException.php on line 49

Internal Sitebuilder error. File: /usr/local/sitebuilder/include/SB/Actions/Status.php; Line: 283
Message: PHP : Argument 1 passed to SB_Actions_Status::importMessages() must be an instance of SB_Actions_Status, boolean given, called in /usr/local/sitebuilder/include/SB/Actions/Admin/Site/Publish.php on line 69 and defined; Code: 4096

Any ideas?


Regards,

Isabel
 
As I remember there was such an issue in 4.2 version but it was successfully corrected in new release 4.5. It looks like this situation related to file name for one of the page. I can suggest you to accomplish upgrade to avoid such situation in future. For now, you can try to resolve this situation in the following way.
1. Log into Mysql 'sitebuilder3' database and make following selection:

mysql> select id, parent_id, title, file_name from site_page where file_name='0';

it should output some page with '0' file name.

2. If there is an output, just update file_name for this page from '0' to something else, like 'test' or 'page100', something unique.

3. After that you will need to find 0.php page directly on Sitebuilder server and rename it to the same name which you used in database:

# find /usr/local/sitebuilder/htdocs/sites/ -name '0.php'
As soon as files are found, just rename them to 0.php.

If you are not sure about the actions, just perform following two commands and let me know the output:

in database: mysql> select id, parent_id, title, file_name from site_page where file_name='0';

and on the server: # find /usr/local/sitebuilder/htdocs/sites/ -name '0.php'
 
Back
Top