[wp-hackers] Custom Post Types Clean-Up
dyordan1 at ramapo.edu
Tue May 21 13:28:10 UTC 2013
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:
>> Hey Dobri,
>> You still need to refresh the rewrite rules on plugin activation/deactivation: http://codex.wordpress.org/Function_Reference/flush_rewrite_rules
>> Op 20 mei 2013, om 22:55 heeft Dobri <dyordan1 at ramapo.edu> het volgende geschreven:
>>> I might be missing something but I've been doing a lot of custom post_types recently and clean up seems to be a huge pain. Here's the deal:
>>> I have a plugin that uses register_post_type in an init hook to do the initial setup of a post type (call it "custom").
>>> Let's say for argument's sake I wanna focus on a page - http://mysite.com/custom/potato/.
>>> I type that in before ever enabling the plugin and it's a 404.
>>> I enable the plugin, play around with it, create a potato page.
>>> Now http://mysite.com/custom/potato/ links to that page and all is good.
>>> Now I disable the plugin.
>>> I try http://mysite.com/custom/potato and now instead of a 404, I get the home page displayed while the url stays the same.
>>> In fact, http://mysite.com/custom/[anything]/ will also result in the homepage being displayed without modifying the url.
>>> Question: Is it just my setup and I should start disabling stuff or is that normal behavior? If it is, shouldn't we do something about it?
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers