Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #25648, comment 10


Ignore:
Timestamp:
10/21/2013 08:52:36 PM (10 years ago)
Author:
SergeyBiryukov
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #25648, comment 10

    initial v1  
    1 The issue appears to be introduced in WordPress SEO 1.4.16 to fix a conflict with NextGEN Gallery, and is reported to be fixed on the part of NextGEN Gallery:
     1The issue appears to be introduced in WordPress SEO 1.4.16/18 to fix a conflict with NextGEN Gallery, and is reported to be fixed on the part of NextGEN Gallery:
    22http://wordpress.org/support/topic/new-bug-filling-up-log-files-taking-down-site-20gig-and-counting/page/2?replies=46#post-4692124
    33http://plugins.trac.wordpress.org/browser/wordpress-seo/tags/1.4.16/inc/class-sitemaps.php#L129
    44http://plugins.trac.wordpress.org/browser/wordpress-seo/tags/1.4.16/readme.txt#L106
     5http://plugins.trac.wordpress.org/changeset/775999/wordpress-seo#file25
    56
    67We could add an `is_array()` check in `do_action()` before calling `reset()`, `current()`, or `next()`, but I don't think we should hide developer errors.