Re: Custom Post Types Clean-Up
Dobri <dyordan1 <at> ramapo.edu>
2013-05-21 13:28:10 GMT
OK, so update:
On Twenty Twelve, at least when I enable the above-mentioned empty plugin, clean up is complete. However,
it is still not sufficient to register a deactivation hook that runs flush_rewrite_rules. So, is there a
more appropriate place to flush the rules to make sure everything is cleaned up?
P.S. this is how I register my function that contains the flush_rewrite
register_deactivation_hook( __FILE__, 'clean_up');
On Tue, 21 May 2013, at 8:54 AM, Dobri wrote:
> Hey Marko,
> Yes, I know that, sorry I forgot to mention it. I have a activation hook for the plugin that runs init and
flushes rules and a deactivation hook that runs just flush rules. Still, after deactivation, the issue I
described is still there. I know that the code runs since I'm tracing to the error log when the
activate/deactivate functions are called. I've also tried having another empty plugin with just
flush_rewrite_rules in activate/deactivate and then once I've deactivated the original "custom" post
type plugin, activate the other one so it's activate function flushes the rules. Even then, way after the
original plugin has been deactivated and after three flush_rewrites, the same issue is observed. I'm
testing it on twenty eleven now to convince myself it's not a theme-specific issue.
> Thank you!
> On Mon, 20 May 2013, at 5:13 PM, Marko Heijnen wrote: