Store options as JSON instead of serialized data to make search and replace safe
Doing a search and replace (e.g migrating domains) breaks serialized data. There are workarounds, but a core change to using JSON to store options would fix the issue for good.
Even some filters or a constant to allow devs to switch the format would be a workable solution.
Once I've asked the same, and I've got an answer.
It's because of the Variables Types, that the serialization can hold the type and JSON has some problems with that.
RSS feed for this topic
You must log in to post.