↳ Joomla 1.5 (Tidligere langtidssupporteret version indtil sep.↳ Ældre versioner (disse vedligeholdes ikke længere fra officiel side).↳ Installation, backup, opdatering og flytning - Godt igang.↳ Joomla! 3.x (Anbefalet til nye installationer.↳ 3rd Party/Non Joomla! Security Issues.↳ Joomla! 1.0 - End of Life 22 July 2009.↳ Search Engine Optimization (Joomla! SEO) in Joomla! 1.5.↳ Migrating and Upgrading to Joomla! 1.5.↳ Search Engine Optimization (Joomla! SEO) in Joomla! 2.5.↳ Migrating and Upgrading to Joomla! 2.5.↳ Access Control List (ACL) in Joomla! 2.5.↳ Search Engine Optimization (Joomla! SEO) in Joomla! 3.x.
↳ Migrating and Upgrading to Joomla! 3.x.↳ Access Control List (ACL) in Joomla! 3.x.Joomla! 3.x - Ask Support Questions Here.↳ Search Engine Optimization (Joomla! SEO) in Joomla! 4.x.↳ Migrating and Upgrading to Joomla! 4.x.Joomla! 4.x - Ask Support Questions Here.
#PHP JSON DECODE JOOMLA UPDATE#
If you prefer to JSON data, update your code to replace the serialize operations with json_encode() and you'll be fine. If you prefer to use serialize/unserialize, then ensure nothing in the code is trying to read that column's data and process it as a JSON string (generally you'd want to look for something similar to `$registry = new JRegistry($source) or $registry->loadString($source) ` as it's the Registry's internal API that's ultimately handling the JSON encode/decode operations). 3.6.3 added an error check for this condition which is why it now exposes the incorrectly formatted data for that particular operation. Before Joomla 3.6.3, this error was just ignored, so while things just "worked", it was working without that data. The fact you were serializing data meant that the serialized data was never actually being unserialized and loaded into the Registry instance that's trying to use that data, because running json_decode() on a serialized string will result in a NULL return with an error stored in a separate function.
Without having seen your code, all I can assume is this.
0 kommentar(er)
