Sorry for your loss, but I ended up making a prototype to test on. With the ‘Delete database upon deactivation’ set to ‘No’. I ran the test and the plugin works correctly. You could of had a mishap 🙁 …but its one of the main reasons I added a backup feature 🙂
I had the same deactivtion/reactivation problem on two sites, even though the “delete database” button was set to “no”.
Did you happen to use the 0.1.0 version prior to 0.2.0?
For some reason everything worked fine on my end, even with a debug
Thanks, jokerbr313.
I am using WP 3.3.1 and plugiv V. 0.2.0.
I was able to repeat the phenomenon once, but then not again. Human error? I’ll let you know if I learn more.
Thanks, any extra info on this would be appreciated.
I’ll look over it one more time after I get everything setup for custom post types and custom taxonomies. Right now I’m wondering if this might be occurring the first time the user deactivates the plugin, but doesn’t occur afterwards.
It may have something to do with the APL saved options, which is why I was asking if you used the first version of the plugin before using the current stable plugin version.
Just logged in to my WP admin and was able to view a “post-list” page.
Then I deactivated the plugin and reactivated.
My custom settings had disappeared, and my “post-list” page refused to load at all.
When the shortcode was deleted, the page loaded properly.
I have just repeated this sequence and got the same results.
I haven’t checked to see if there might be a plugin conflict.
Hope this helps.
It does help. Gives me a lead on how to replicate it, even knowing its was one of the methods I knew to use in the plugin, but it helps to narrow it down. So, thanks again on that.
Well, just give me some time, and I’ll check it out a lil more in-depth again. Things for custom post types & taxonomies are looking good for the plugin though 🙂
Plugin Author
EkoJR
(@ekojr)
After some time getting all the core features set into place, I also decided to tackle this subject in the 0.3 release. So far, everything is in working order as of 0.3.b4. Sorry about the issue though.
