Closed jordanvector closed 6 years ago
Hi @jordanvector ,
I have tried this on latest 2.2 (not EE though) and works as expected. To help us debug this further, can you please check if there are any JS errors in browsers console and if there is anything in the PHP/Apache log?
I see that you have quite few extensions, so it is possible that some combination of them with Fastly module simply does not work.
I've run into the same issue. The reason of the issue is in that the Fastly module stores serialized data in Magento database, but starting from the 2.2.0 release Magento replaces usages of unserialize with json_decode: https://devdocs.magento.com/guides/v2.2/release-notes/backward-incompatible-changes.html#database-data-format-changes
In my case Magento thrown an exception when I tried to open Advanced > System page in admin backend:
1 exception(s):
Exception #0 (InvalidArgumentException): Unable to unserialize value.
Exception #0 (InvalidArgumentException): Unable to unserialize value.
#0 vendor/magento/module-config/Model/Config/Backend/Serialized.php(55): Magento\Framework\Serialize\Serializer\Json->unserialize('a:0:{}')
The serialized data:
MariaDB [main]> select * from core_config_data where config_id=35\G
*************************** 1. row ***************************
config_id: 35
scope: default
scope_id: 0
path: system/full_page_cache/fastly/fastly_advanced_configuration/geoip_country_mapping
value: a:0:{}
1 row in set (0.00 sec)
Magento has an upgrade guide for module developers: https://devdocs.magento.com/guides/v2.2/ext-best-practices/tutorials/serialized-to-json-data-upgrade.html
Fastly should upgrade the fastly/magento2 module in order to make it compatible with the 2.2 release.
@jordanvector as workaround you can find and replace all serialized data in the Magento DB under the system/full_page_cache/fastly/ section. You can use some converter like the following: http://solutions.weblite.ca/php2json/index.php to convert the serialized value "a:0:{}" into JSON "[]".
Brilliant, that was definitely the issue. Thanks a lot @yyevgenii
@jordanvector please reopen the issue, because it seems to be fixed in module itself.
This has been fixed in master #114 . Please give it a shot and let us know if it doesn't fix the issue.
Actually try this first
https://github.com/Inchoo/fastly-magento2
It won't work with 2.1. It will need to be run only on 2.2.
We have released the upgrade method with version 1.2.34 of the module. Here are the 2.1 => 2.2 upgrade instructions
Seems like that resolved the issues, can we close the ticket?
Unfortunately I cannot find any error logs for this but I will keep looking