Strange Error
Posted
#1193
(In Topic #296)
Anyone know whats causing this and how to resolve??
Critical error – bailing out
This is an error that has been elevated to critical error status because it occurred during the primary error mechanism reporting system itself (possibly due to it occurring within the standard output framework). It may be masking a secondary error that occurred before this, but was never output - if so, it is likely strongly related to this one, thus fixing this will fix the other.
Unfortunately a query has failed [DELETE FROM cms_cache WHERE (lang='EN' AND the_theme='The_Bassline_Cartel' AND cached_for='side_stats' AND identifier='40cd750bba9870f18aada2478b24840a') LIMIT 1] [Incorrect key file for table './cmscartel/cms_cache.MYI'; try to repair it] (version: 10 RC10, PHP version: 5.4.45, URL: /)
Details here are intended only for the website/system-administrator, not for regular website users.
» If you are a regular website user, please let the website staff deal with this problem.
Depending on the error, and only if the website installation finished, you may need to edit the installation options (the _config.php file).
ocProducts maintains full documentation for all procedures and tools. These may be found on the Composr website. If you are unable to easily solve this problem, we may be contacted from our website and can help resolve it for you.
Posted
Moderator
See:
Composr Tutorial: Manually editing your database with phpMyAdmin
Open Source CMS with advanced social, interactive and dynamic features. Fully flexible, themeable and extendible: suitable for building powerful websites.
Posted
Posted
Moderator
Posted
The following queries will make the actual database consistent with the expected database:
UPDATE cms_privilege_list SET p_section='SUBMISSION', the_default=1 WHERE the_name='set_own_author_profile';
There were no issues between the meta database and the actual database. They could potentially be removing legitimate modifications you or a non-bundled addon has made.
Your action was successful.
Posted
Moderator
That definitely wouldn't be the cause of the issue, so it must have been something else such as trying a newer RC, or reuploading something, or the PHP version having been changed in the interim.
2 guests and 0 members have recently viewed this.