Forum Replies Created

Viewing 15 replies - 16 through 30 (of 34 total)
  • Thread Starter serialboxhpc

    (@serialboxhpc)

    This is the error I get in my logs right after activating the plugin:

    PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 24 bytes) in /mnt/xxxxxxxx/web/content/wp-includes/class.wp-dependencies.php on line 134

    How much memory does this plugin need? Seems a little excessive that a social widget would cause my wordpress site to run out of memory.

    As soon as I delete the plugin files, the site starts working again.

    well.. i manually uploaded the files 3 times in a row.. and it now works. dunno what the prob was but obviously some missing files somewhere. couldn’t tell you which ones tho

    well.. i manually uploaded the files 3 times in a row.. and it now works. dunno what the prob was but obviously some missing files somewhere

    I hate people like Scrobby.

    Why not tell the rest of the world which 2 files didn’t get uploaded?

    I have the same prob. Ran the automated upgrade. After it unpacked files I got a blank white screen.

    According to my log files, the error is

    [Thu Jun 17 15:35:11 2010] [error] [client zz] PHP Fatal error: Call to undefined function is_multisite() in /var/www/vhosts/smydomain.com/httpdocs/wp-includes/wp-db.php on line 505

    I replaced the path with a fake domain as to not post my actual domain here.

    this is BS.

    I then tried to manually upgrade but to no avail. still doesn’t work. cannot log in to wp-admin to complete upgrade.. can’t do anything.. wtf?

    Thread Starter serialboxhpc

    (@serialboxhpc)

    Thanks for the quick response.

    Well after completely removing it and reinstalling it, my pages are now loading, but they are not being compressed with gzip at all.

    in fact, my yslow and pagespeed scores got worse after turning on the plugin.

    All tests that I run either through gtmetrix.com and https://www.gidnetwork.com/tools/gzip-test.php indicate gzip compression is NOT enabled.

    In fact, even caching appears to not be working according to the debug output. I am testing from a different browser where I am NOT logged in at all.

    Is there something Im missing? I haven’t messed with the settings and left them at default for now.

    Here is the new debug information.

    W3 Total Cache: Page cache debug info:
    Engine:             disk (enhanced)
    Key:                2010/05/05/integrated-content-management-systems-like-wordpress-and-drupal-saves-time-and-money/_default_.html.gzip
    Caching:            enabled
    Status:             not cached
    Creation Time:      1.030s
    Header info:
    X-Powered-By:       W3 Total Cache/0.8.5.2
    Set-Cookie:         wpmp_switcher=desktop; expires=Sat, 28-May-2011 16:39:23 GMT; path=/
    X-Pingback:         --
    Content-Type:       text/html; charset=UTF-8
    X-Mobilized-By:     WordPress Mobile Pack 1.2.0
    Link:               <https://wp.me/pxEmp-7F>; rel=shortlink
    Pragma:             public
    Expires:            Fri, 28 May 2010 17:39:24 GMT
    Last-Modified:      Fri, 28 May 2010 16:39:24 GMT
    Cache-Control:      max-age=3600, public, must-revalidate, proxy-revalidate
    Vary:               Accept-Encoding, Cookie
    Etag:               651d34aa940d6f9ca10f5da90b2502d1
    Content-Encoding:   gzip
    Thread Starter serialboxhpc

    (@serialboxhpc)

    Now my site is completely broken even after disabling and uninstalling the entire plugin.

    Safari can’t open the page “https://mydomain.com/blog”. The error is: “cannot decode raw data” (NSURLErrorDomain:-1015)

    All I did was install w3 total cache, enable it, realize it doesn’t work, and disabled and removed it.

    I replaced my actual domain in the error above with a fake one as to not publicize my site

    Thread Starter serialboxhpc

    (@serialboxhpc)

    If I enable debugging, this is what is shown in the source code. I removed my domain name from the output below.

    W3 Total Cache: Page cache debug info:
    Engine:             disk (enhanced)
    Key:                _default_.html.gzip
    Caching:            enabled
    Status:             not cached
    Creation Time:      3.282s
    Header info:
    X-Powered-By:       W3 Total Cache/0.8.5.2
    Set-Cookie:         PHPSESSID=493a15551ae277e0eb7d7f517580d524; path=/
    X-Pingback:         --
    Content-Type:       text/html; charset=UTF-8
    X-Mobilized-By:     WordPress Mobile Pack 1.2.0
    Link:               <https://wp.me/xEmp>; rel=shortlink
    Pragma:             public
    Expires:            Fri, 28 May 2010 17:15:33 GMT
    Last-Modified:      Fri, 28 May 2010 16:15:33 GMT
    Cache-Control:      max-age=3600, public, must-revalidate, proxy-revalidate
    Vary:               Accept-Encoding, Cookie
    Etag:               ea772a010d32319cdc7020e1585a4b6b
    Content-Encoding:   gzip
    Thread Starter serialboxhpc

    (@serialboxhpc)

    hah well whaddaya know ?? thanks again for the response. I forgot to mention that I did upgrade supercache after getting those errors which also may have fixed the prob. Guess I was getting my versions confused.

    On a side note… this is the single greatest plugin ever created for WordPress. thank you!

    Thread Starter serialboxhpc

    (@serialboxhpc)

    thanks for the reply but thats slightly incorrect. supercache uses aspects of wp-cache. In the supercache admin section there is a setting called “half-on” which uses wp-cache instead of supercache.

    Logged in users receive wp-cache pages and other visitors would get supercached pages.. my issue was wp-cache pages were being served to everyone.

    To fix the problem I deleted my cache folder and recreated it. That seemed to do the trick.

    thanks for the suggestions

    @bechster

    worked for me right away.. thanks

    why on earth would wordpress decide not to give us the choice of whether we want revisions or not? It is a complete waste of resources and right now I’m stuck and can’t figure out how to move forward.

    I have a fairly large table with data in a post that I edit sometimes 3 or 4 times a day. Its at the point now where I can no longer edit the post because it seems like wordpress is trying to compare my post with every revision resulting in a 30 sec timeout as seen here:

    Fatal error: Maximum execution time of 30 seconds exceeded in /mnt/w0001/d46/s17/b02e53cb/www/wp-includes/wp-diff.php on line 287

    I ran a query on my database to delete everything that had post_status=’revision’ which successfully removed the revisions however i STILL cannot access this post to edit it.

    I tried the many plugins and code hacks to disable revisions and they dont actually disable the revision feature.. it seems like they just hide the revisions from your posting options. The reason I say this is because with the plugins/hacks to disable revisions, after creating a new post with a large table in it and making about 10-15 changes to it saving after each one I eventually get the wp-diff.php error. So the revisions are still being created, wordpress is still comparing them and still failing.

    My only option now with this post is to go directly into my database, copy the content, and create a new post out of it. Then I can edit that one a couple of times until I hit the limit again, and create a new post again.. cycle continues.

    If anyone knows how to completely remove post revisions from WordPress please let me know otherwise I’ll simply downgrade back to 2.5 and stay there.

    @notthepainter

    Thank you! You solved my problem. I had already upgraded at that point though so I couldnt create a new user before the upgrade.

    I so did not want to clear my cookies.

    So after following the directions on upgrading exactly, I then made one further change. When I went to do the upgrade.php part I created a new user on my Macintosh, logged in as that user, then went to Safari and did the upgrade.

    That way I could have a cookie-free environment.

    Following your example, since I use Firefox as my main browser, I simply opened up Internet Explorer and was able to log in right away. Not wanting to delete all my cookies in Firefox I just went to the Cookies config section under Options and deleted only the cookies for my own website and left the rest there.

    As soon as I removed the cookies for my own blog I was able to log in.

    mafro your solution worked perfectly. exactly what I wanted to do.

    Thread Starter serialboxhpc

    (@serialboxhpc)

    i appreciate the help. Just going to give up for now and then test it when I get to work from a bunch of different machines to see if I can replicate it anywhere else except my own.

    what ive found is that if i remove

    <div style="clear:both;"></div>

    then the line goes away but that also messes up the rest of my layout.

Viewing 15 replies - 16 through 30 (of 34 total)