editing the background image crashed site

Hello,

running current version. I just used the theme editor to change the background image and somehow this caused the site to crash.

The background image did not update, and suddenly the background image has reverted to the default background image.
But the real problem is that my menu is gone and all articles are gone. when attempting to view an article i get this error;

Language corruption detected and fixed (when looking up language string #9736). This means that a database inconsistency had developed, but has fixed itself.

i was hoping just a CSS issue but looks like my menu and articles are gone? or just not linked?

 

Hello,

What version of Composr are you running? There was an issue editing theme images referenced in CSS, but we fixed this in 10.0.4.

Does this "Language corruption" error message recur? Usually these are a one-off occurrence, although it is a bug. It's likely not related to theme editing though.
Did you install with content translation?
What exact URL does the error message show at, if it still occurs?
Are you able to generate and share a stack trace for the error message, if it still occurs (there's a link to generate one, if you're logged in as an admin)?

Hello,

I was using 10.2 i think and now upgraded to the latest 10.4

it looks like my menu is gone, articles and perhaps the wiki.  im really worried about the wiki the most as i had a ton of infos.

i will do frequent backups now, my fault

i did have multiple languages on as i hope to support japanese soon

I am in safe mode looking around and getting the Language corruption detected and fixed (when looking up language string #9738). This means that a database inconsistency had developed, but has fixed itself. 
 

Hello, actually what was the bug with " an issue editing theme images referenced in CSS " ?  I think if I know what it caused I may be able to repair?

Are you able to send an SQL dump to chris@ocproducts.com? I'll see what I can find has happened. It sounds like some severe failure in the cms_translate table.

Did you run all the cleanup tools in one go? It sounds like maybe the cleanup orphaned language strings (or whatever it is called) may have had a severe issue.

Howdy, Here is my progress report;

1. deleted(drop) the cms_translate table and imported the cms_translate table from a backup from a few months ago.  This helped as in bringing the menu and the wiki back to life. The news articles are still missing. Still have the "Language corruption" error messages .

2. ran the file intergrity program and did everything it wants

3.  The error log had nothing new but now has two errors…   PHP Error : Call to undefined function parse_translated_text() in sources/lang.php on line 1193 @ Nandalow: HOKKAIDO INFOs - Nandalow

and

PHP Fatal error ;   Call to undefined function parse_translated_text() in /sources/lang.php on line 1193

4. I want to mention that I dont have FTP as an option so to upgrade I download the file and then upload the files manually with SFTP.  I never do anything with a SQL upgrade and wonder if it even exists? The SQL checker in tools says all is ok. Phpmyadmin CHECK tables has all OK.

5. For now I removed all my custom blocks & CSS and using the default.

6.  It is weird as the site is attempting to display the NEWS, it has a space for it but missing the title and content. If I try and edit the news article this error pops up;  410: ReferenceError: set_up_comcode_autocomplete is not defined
http://nandalow.com/cms/index.php?page=cms-news&type=_edit&id=26

7. another very interesting observation: when i click on the VIEW ALL to read all my news (announcements) News archive - Nandalow  the bread crumbs are not working, see enclosed image

I will keep exploring and trying different things. for now i turned off the NEWS on the main page and turned my site back on. I dont have any members but I have been telling many people this is a link portal for our island so it gets lots of visitors.


 

I am looking at this now and seeing what I find.

Ok, I've found the cause. Unfortunately you really did encounter severe data loss. There's no way I can restore that. I'm very sorry about this.

Here is a hot fix for what caused the issue:
0003262: Data loss cleaning orphaned language strings - Composr CMS feature tracker

This bug was introduced in v10. We changed the meta database structure which made the orphaned language string tool miss references to Comcode fields. So it thought all Comcode fields were orphaned, and proceeded to delete them.

This was not found until now because multi-lang-content isn't a default in installation, and because we advise to only run the cleanup tools needed and this one is only really needed by developers. So unfortunately you were the first person to stumble upon the problem. Again, I'm sorry about that, it's about as bad as a bug can get.
I'm going to disable this tool entirely unless you call the cleanup tools with a special hidden parameter.

Restoring from a backup is almost the best you can do. I would try and merge the old version of the table into the new one. I have sent you a file, replace_into.sql, which does a "REPLACE INTO" query on the cms_translate table data you sent me. This will merge in (with overwrite) any of the language strings from before you restored that table.

After importing replace_into.sql into phpMyAdmin, also go and edit the options of the cms_translate table and raise the auto_increment value to something higher than the largest language string ID, e.g. 100000.

(Click to enlarge)

Here's a summary of the situation regarding language strings:

• Non-Comcode ones in your old backup – restored when you restored cms_translate
• Comcode ones in your old backup – restored when you restored cms_translate
• Non-Comcode ones newer than your old backup – restored when you ran replace_into.sql which I just sent you
• Comcode ones newer than your old backup – unretrievable, regrettably

Regarding your latest post…

1 - Composr will self-repair to a degree. Each time you see a missing language string error, it should only be once. It will insert a blank language string in that ID slot. The problem is, the content is gone so you'll need to edit it back in.

3 - Ignore this. Sometimes PHP has issues with error reporting when under extreme conditions (basically). I don't think there's a bug specifically here, I think it's a side effect of some failure relating to the missing language strings that probably will work itself out.

4 - This is not really what we want users to do. If you don't have FTP, do you at least have SuEXEC on the server so that FTP is not needed for full file writing? The problem with manually uploading the files is that it will put up files for bundled addons you may have since uninstalled. However, there is nowadays an option for a special package tailored to what addons you have. You can find a link to it from inside the upgrader, inside transfer across new/updated files. It's the "generate a personalised manual upgrader" link. This will give you an archive that should be safe to extract.

6 - I think it's struggling to load a JavaScript file for some reason. I can suppress the error message in the next patch release (and I included this in the hot-fix at the start of my post) but otherwise please ignore. I'm not hugely surprised given various things must be broken right now.

7 - I think it's a couple of issues. But mainly your news category has lost its title, as it's a Comcode language string. You'll need to edit your news category and get it back in. I think the reason truncated HTML is displaing may be due to an overridden code file enabling what is called "kid gloves mode" in our engine (extra security filtering); I'm not certain but I couldn't reproduce it.

I'm hoping you can get things fixed up enough to continue on. If not, I recommend restoring your last full backup to a subdirectory and transferring over surviving content manually, then replacing your live site with this.
If you do that be careful to install the 0003262: Data loss cleaning orphaned language strings - Composr CMS feature tracker hot-fix lest the whole thing start again.

Hello,

Just wanted to say thank you and that I decided to rebuild from scratch.

I have the site back up running and love it. I am digging in and learning many things and I am in awe of all the features and the power the composr cms has. I am also doing many frequent backups :)

I plan on doing some mods etc and sharing here.

Cheers and thank you so much for a top quality software and support.

ironfeather said

Hello,

Just wanted to say thank you and that I decided to rebuild from scratch.

I have the site back up running and love it. I am digging in and learning many things and I am in awe of all the features and the power the composr cms has. I am also doing many frequent backups :)

I plan on doing some mods etc and sharing here.

Cheers and thank you so much for a top quality software and support.

From “Post #3,108”, 31st July 2017, 11:18 am

Awesome!

You are welcome! Looking forward for your contribution and sharing…