Wordpress

History

Boone Gorges 48beba441b When generating a fallback `post_name` using the post ID, `wp_insert_post()` should clear the post cache immediately. If the post cache is not cleared at this point, the cache can become stale for operations performed before the cache is cleared later in the function. Specifically, the generation of a `guid` for new posts can use stale data, resulting in non-unique values. [33262] introduced a call to `get_post()` that introduced just such an invalidation problem. Fixes #5305. git-svn-id: https://develop.svn.wordpress.org/trunk@33630 602fd350-edb4-49c9-b593-d223f7449a82	2015-08-18 02:50:23 +00:00
..
phpunit	When generating a fallback `post_name` using the post ID, `wp_insert_post()` should clear the post cache immediately.	2015-08-18 02:50:23 +00:00
qunit	TinyMCE: wptextpattern: trim whitespace	2015-08-03 22:06:25 +00:00

Boone Gorges 48beba441b When generating a fallback post_name using the post ID, wp_insert_post() should clear the post cache immediately.

If the post cache is not cleared at this point, the cache can become stale
for operations performed before the cache is cleared later in the function.
Specifically, the generation of a `guid` for new posts can use stale data,
resulting in non-unique values. [33262] introduced a call to `get_post()`
that introduced just such an invalidation problem.

Fixes #5305.

git-svn-id: https://develop.svn.wordpress.org/trunk@33630 602fd350-edb4-49c9-b593-d223f7449a82

2015-08-18 02:50:23 +00:00

phpunit When generating a fallback post_name using the post ID, wp_insert_post() should clear the post cache immediately. 2015-08-18 02:50:23 +00:00

qunit TinyMCE: wptextpattern: trim whitespace 2015-08-03 22:06:25 +00:00