when reverting to version 2.3.2 all fields are back again
Same issue for me, after yesterdays update. How did you revert back?
Hi guys, I wrote on main page – please do not update from version 2 to version 3. There are changes in saving some values.
If you want version 3 anyway I suggest you to:
1) set main storage to files (so it save the json)
2) update to v3
3) change/create missing fields.
Values should stay the same. It’s only about saving fields settings.
———
To revert back: just download older version from here:
https://wordpress.org/plugins/just-custom-fields/developers/
and replace all folder with them
Hi,
What do you mean by “set main storage to files”? Should I (we) tick “file-system” in the Settings page (and then, “current theme folder” or “global”?).
If I understand well, I should store config in files, then update, then re-create all fields with exactly the same names, and finally put the config back to the database?
Sorry for tedious questions,
Rémy.
@jweck i revertet by renaming /wp-content/plugin/just-custom-fields to just-custom-fields.bak and reupload the older version.
older versions can be found here: https://github.com/aprokopenko/justcustomfields/releases
i also don’t understand what “set main storage to files (so it save the json)” means.
Sorry If I was unclear about that.
This means to enable storing files in File system inside the theme.
After successful upgrade to v3 and re-creating missing options – you don’t need to switch back on Database. File system works similar.
If you still want Database – you need to Export your settings when you are on File system and then Import them back when you switch to Database.
We removed the option of copying fields between different storages in v3 to prevent errors when you merge existed settings.
Feel free to contact me on Skype.
My username is ab.prokopenko
i really wonder how anybody will “enable storing files in File system inside the theme”
is there a how-to or something?
overall, this seems a lot of work for 50+ websites for me – but thanks for your insight.
wasn’t there any way to upgrade the existing database to the new structure? will there be artefacts of the old version inside the database?
In version 3 we deleted very outdated component: Upload media.
So if you’re still using it – there is no way to return it back.
This is why we do not support upgrade from v2.
Maybe we will really make a simple stand-alone plugin which will upgrade old versions to new one. So you install, run upgrade and delete it after it.
Right now I’m collecting issues and feedbacks from plugin users.
