Ryan Boren

@shapeshifter3, how’d it go?

Zeyn has released a patch.

https://themeforest.net/item/zeyn-multipurpose-wordpress-theme/8848292/comments#comment_9814364

Background: https://core.trac.www.ads-software.com/ticket/21434

I wouldn’t mind bringing back wp_cache_reset() with lots of phpdoc explaining how and when to use it in a plugin. I think the current behavior should remain the default, however, since it saves lots of queries.

https://core.trac.www.ads-software.com/ticket/18536#comment:88

3.4 moves from using time() to microtime() for the doing_wp_cron lock. This increases the size of the URL but should not exceed limits. Alas, I’m not sure what’s going on here.

Patches should include only changes to the .dev files. We test patches with SCRIPT_DEBUG on. A post commit hook called bumpbot minifies changed .dev files with YUI Compressor.

I’d rather not invalidate existing keys (which could cause meltage) or add to the key length to support this edge configuration. How about WP_CACHE_KEY_SALT, default it to an empty string so that existing keys are not invalidated, and some phpdoc suggesting setting it to a random prefix and/or the hash of the abspath?

filter had to be unset due to security problems with it. You could try doing kses_remove_filters() before inserting the post and kses_init_filters() after inserting the post if you are trying to avoid the kses filtering of the post fields. Just be wary since that defeats most of the security measures for inserting posts.

Ticket opened: https://core.trac.www.ads-software.com/ticket/16703

add_feed() just registers the callback for feed queries. add_feed(‘custom’, ‘callback_function_that_outputs_the_feed’). You don’t have to worry with what is in the url. ?feed=custom or /feed/custom/ or /feed/custom/?hey=you will trigger the callback.

I opened a ticket for turning off canonical redirects for unregistered feeds:

https://core.trac.www.ads-software.com/ticket/16704

A change in 3.1 is tripping up the plugin’s in_event_category( ) function. 3.1 now sets the ‘cat’ query var when resolving /%category%/%postname%/ permalinks. 3.0 did not.

A quick fix is to change this block of code in in_event_category():


if( $cat_id == $this->eventCategory() ) {
return true;
}


to this:


if( !is_singular && $cat_id == $this->eventCategory() ) {
return true;
}


We’ll look at fixing this in WP for 3.1.1.

There are many event calendar plugins. Could you link to the one you are using? Also, which permalink structure exhibits the problem? Which web server are you using? Apache, IIS6, IIS7, IIS7.5?

Feeds should be registered with add_feed(). Plugins that use add_feed() rather than going going around it will not break like this in 3.1.

Canonical redirects for categories were fixed in 3.1. This fix results in the bad behavior you are seeing if the plugin does not use add_feed(). We might change WP to avoid doing canonical redirects for unregistered feeds, but plugins really should be using add_feed().

Tracking this bug on this ticket.

Even in 3.0, using this style is hit-or-miss. It completely circumvents parse_query().