Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Well, that fixed it for me, but another issue crops up.

    Fatal error: Allowed memory size of 94371840 bytes exhausted (tried to allocate 188360 bytes) in /home/bschollnick/schollnick.net/wordpress/wp-content/plugins/wordpress-seo/inc/class-sitemaps.php on line 325

    Suggestions?

    I know I have alot of posts, but….

    Thread Starter bschollnick

    (@bschollnick)

    It appears that 0.23 fixes the issue with 0.22 not outputing a valid XML file…
    But it appears that we have a re-occurrence of 0.21’s occassional coruption of the XML file…

    I sent you another XML file via Email…

    I am not sure that Apple Mail is preserving the Date/time stamp, so…

    The XML file is a timestamp of 10:01 pm, and the xml.gz is 8:11pm.

    It appears that the XML file was regenerated at 10pm, which I believe I had made a minor edit of a page… before I crashed for the night…

    Could it be that the XML file is not being updated correctly after a edit of a existing page? And I suspect that the Gzipped version is untouched? Possibly WordPress-Seo died before it could re-gzip the bad xml file?

    I am making an guess here…. And haven’t looked at the source, so I’m probably wrong…

    Also, where can we set the path for the sitemap.xml in wordpress-seo? I just realized that I had mapped it to the \sitemap.xml in the google xml sitemap, but wordpress-seo is working off the wordpress subdirectory… (eg, \wordpress\sitemap.xml)

    I don’t see any place to set the location of the XML files…

    bschollnick

    (@bschollnick)

    I saw this issue to with the robots.txt plugin… As soon as I de-activated the robots.txt editor, everything worked was working fine…

    Thread Starter bschollnick

    (@bschollnick)

    That was it…

    A few suggestions:

    1) When WP Super Cache is enabled, clear the cache, or perform some sort of sanity check on the cached data. I had two posts “disappear” since they were created while the cache was disabled. A quick clearing of the cache resolved this…

    2) If the CDN is empty, then substitude the host URL… Or clarify the wording on the page, it says “Offsite URL”, which in my case didn’t apply…

    3) Alternatively, add a “Enable CDN” checkbox & logic.

    Thanks for the fast reply and support…

    – Ben

    Thread Starter bschollnick

    (@bschollnick)

    No… I didn’t enable CDN support, but I had been trying to use OSCDNL linker earlier…

    So I think the question becomes, how do I ensure it’s disabled?

    Thread Starter bschollnick

    (@bschollnick)

    Well, I didn’t see anything in WP-health that was wrong…

    As far as I can tell, AskApache Password Protect or WP htaccess Control seems to have been part of the cause… I remove removing AAPPro and it worked fine afterwards… But I’ve had that plugin loaded for quite a while… I don’t remember any recent updates, but…

    Now, I have to figure out why Akismet seems to be horribly bogging down the system…

Viewing 6 replies - 1 through 6 (of 6 total)