
It would be easier for me to manually copy my K2 items into Joomla core articles, for example.
Do you know exactly what I should look for and where?
There is, but realize there are a lot of uses of the Registry class and the formatter API within it so even if we were to try and throw a patch together it wouldn't be a quick process. It also wasn't expected that there would be such damaged database records.mojito wrote:Urm ...you make some valid points but surely there is some kind of try catch for php ?
I tried the script and it worked perfectly. Thanks!mojito wrote:At the end of the day this code update was bad. They can defend it at a hard limit but there should have been a cleanup or warning or auto resetting of broken fields. I am going to have to take drastic action like this as well. Did you try robert wents script ? I would like to know if anyone did.
https://github.com/robwent/joomla-json-db-check
Luckily only 2 sites are broken, so it can be manageable. I just need to know what code needs to be replaced and where.mojito wrote:If you have 37 sites this is quite a bit of work - or you replace the file to the older version to HACK IT - but this is not ideal but not very harmful either IMO.
You may need to hire a joomla guy to get this fixed for you.
Oh ok. I do have PHPMyAdmin. I ran the file on both sites, then clicked the button because I still had the error. This was the only error in the output for both:mojito wrote:The code is fine. The issue is legacy or for whatever reason database json strings are not validating ok.
Do you have phpmyadmin setup for the 2 sites ?
OR have you uploaded the github file mentioned above ? Often running that fixes the database strings - try that first it is safe.
If you have updated to J3.6.3 and are receiving a "Error decoding JSON data: Syntax error" error then please read the following.
There was a little error in a JSON string for the presets in the template - we have now corrected this but for existing sites you will need to use PHPMYADMIN to edit the database to correct his...
Use this SQL command in PHPMYADMIN:
UPDATE `#_template_styles` SET `params` = '{"configuration":"82","preset":"rows_and_columns"}' WHERE `id` = 82
Please replace the "#" above by your table prefix.
The database will then be corrected and your site should then be ok.
Regards, Mark.
">" is more, not lessrobwent wrote:UPDATE `MYTABLES_users` SET params = '{}' WHERE length(params) > 65000
You are going to wipe out any parameters which are less than 65000 chars.