meta user
network profile
| bio | website | |
|---|---|---|
| location | Eastern, KY | |
| age | ||
| visits | member for | 1 year, 11 months |
| seen | Sep 7 '12 at 2:05 | |
| stats | profile views | 1 |
|
Sep 3 |
comment |
Which filters or actions to use after a media upload and delete? and don't forget edit_attachment (in case you care if the image is rotated or scaled after being added) |
|
Sep 3 |
answered | Media Library, hook on delete user action |
|
May 1 |
awarded | Supporter |
|
Jul 2 |
awarded | Student |
|
Jun 29 |
awarded | Scholar |
|
Jun 29 |
accepted | Transients API and multisite |
|
Jun 29 |
comment |
Transients API and multisite So, what you're saying is that the calls to $wp_object_cache->set() go to a 3rd-party cache plugin and if that is 'multisite aware' the transients will be kept separate, but if not and it just uses the transient name directly (e.g. as the APC or memcached key) then they'll clash across sites (and Atlas sitemap will display as whatever site it happened to be last cached by) |
|
Jun 29 |
awarded | Editor |
|
Jun 29 |
revised |
Transients API and multisite added 476 characters in body |
|
Jun 29 |
comment |
Transients API and multisite So, I discovered that when looking at the source for set_transient(). However, when it calls wp_cache_set() it doesn't seem to do anything special to the transient name. Also wp_cache_set() just passes the cache key directly to $wp_object_cache->set(...). Sooo, does the wp_object_cache prefix the key with the blog_id or something? If not, then transients will collide between sites when caching is enabled, but not when just being stored in the (per-site) options table. |
|
Jun 29 |
answered | How to get shortcode to work inside a foreach loop called within a shortcode? |
|
Jun 29 |
answered | 'Global' settings page for multisite plugin |
|
Jun 29 |
asked | Transients API and multisite |
