What you show me at
2:23 is what I said in my first reply:
Also note that ANGIE will only change the URLs stored in posts, pages metadata and core WordPress options. It will NOT touch the URLs you have hardcoded in your template or URLs which are stored in the options of third party plugins. You have to do this yourself.
These URLs you show me are configured in third party plugins. ANGIE, the restoration script, cannot and will not touch them, exactly as I said and as we have documented. You prove me right at 2:40 when you show me the options of a third party plugin stored as metadata in the database.
FYI, there is a very valid reason why we don't touch serialised data (which you mistakenly called "unserialised" in your video). Serialised data in PHP cannot be edited directly. They have to be unserialised first. However, unserialising this data requires the PHP classes they are using to be already loaded, otherwise a fatal error occurs. This is why, for the last 10 years, the core PHP developers have warned AGAINST using serialised data as a form of permanent storage. Sadly, WordPress is committing a software architecture crime by not only allowing, but RECOMMENDING(!!!) its developers to use serialised data.
While we can use a workaround to change URLs in serialised data, our testing shows that it only works in 90% of the cases. In the rest 10% the serialised data is screwed up and the restoration ends up losing data on the site. I cannot possibly put my name on a piece of code that will screw my users one in ten times it's used. It's irresponsible to publish code which does that. Therefore we do not touch serialised data.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
