There was an issue with the 2.5.0 release, where the original columns stored settings were not being displayed. (the original settings were still stored however). We quickly released (within 30min) the 2.5.1 to fix this particular bug. If you upgrade from 2.4.x to 2.5.1 you should not see any loss of column settings.
I was able to reproduce the bug you mentioned with 2.5.1. The problem is the default WordPress columns do not display anymore if you haven’t visited the overview page first.
If you run into this problem: just make sure to visit the overview screen (e.g. post, user, media) first before you store any settings. This will make sure all default columns are properly loaded and you won’t lose any column settings.
I will release a 2.5.2 version which fixes this particular issue.
Thread Starter
M3
(@emmtre)
OK I’ll do some more tests and try to fix these sites. Any database records I should delete if I have installed 2.5.0. I’m still having problem after updating to 2.5.1 and settings are lost. I have deleted all column settings via the restore default settings button.
It’s best not to use the “restore default settings” button, because it will delete all stored column settings. This is useful if you want to go back to the original WordPress columns. It won’t restore any of your previous column settings.
Thread Starter
M3
(@emmtre)
I know the restore default settings button will delete all stored column settings but I had to that and try to start all over again since something happended in the update process from 2.4.10 to 2.5.0 to 2.5.1 and settings were not saved.
Hopefully you can continue to work with 2.5.2, it has the same storage key as the 2.4.x versions. Any default WordPress columns are also displayed correctly now. Sorry about the inconvenience, we test our plugin quite extensive, but this one slipped through =(
Thread Starter
M3
(@emmtre)
No problems. I looks like it’s saved now. Many thanx for the quick fixes! 🙂
I found another problem with two plugins but I’ll make a new post about that.
