Title: Mike's Replies | WordPress.org

---

# Mike

  [  ](https://wordpress.org/support/users/mike/)

 *   [Profile](https://wordpress.org/support/users/mike/)
 *   [Topics Started](https://wordpress.org/support/users/mike/topics/)
 *   [Replies Created](https://wordpress.org/support/users/mike/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/mike/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/mike/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/mike/engagements/)
 *   [Favorites](https://wordpress.org/support/users/mike/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 107 total)

1 [2](https://wordpress.org/support/users/mike/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/mike/replies/page/3/?output_format=md) …
[6](https://wordpress.org/support/users/mike/replies/page/6/?output_format=md) [7](https://wordpress.org/support/users/mike/replies/page/7/?output_format=md)
[8](https://wordpress.org/support/users/mike/replies/page/8/?output_format=md) [→](https://wordpress.org/support/users/mike/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Public Post Preview] [Plugin: Public Post Preview] Stopped Working](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/)
 *  [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [13 years, 8 months ago](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/page/2/#post-3005581)
 * Dominik:
 * That dev version appears to have fixed it for me (I can copy the permalink preview
   url and it works for logged-out users). Thanks!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Public Post Preview] [Plugin: Public Post Preview] Stopped Working](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/)
 *  [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [13 years, 8 months ago](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/#post-3005572)
 * I don’t have that plugin. Here is my list
 * Akismet
    Better Blogroll FD Feedburner Get Author Profile Hide or Show Comments
   Image Caption IntenseDebate Jetpack Latest Posts by Author Scheduled M.I.A.s 
   Simply Exclude Sucuri Security Text Control Vaultpress W3 Cache Wickett Twitter
   Widget WP Print WP Touch
 * Phew, that’s a lot!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Public Post Preview] [Plugin: Public Post Preview] Stopped Working](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/)
 *  [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [13 years, 8 months ago](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/#post-3005567)
 * AEG-wiz: That hack to append the &p=XXXX works for my quirky permalinks. It is
   a much easier hack than earlier.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Public Post Preview] [Plugin: Public Post Preview] Stopped Working](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/)
 *  [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [13 years, 8 months ago](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/#post-3005564)
 * Thanks for the reply:
 * /%author%/%year%/%monthnum%/%day%/%postname%/
 * (this is a bit quirky)
 * and using W3 Total Cache, however, disabling it doesn’t fix things. My users 
   now solve this problem by replacing the permalink in the preview url and finding
   the postID to revert to the old format. Works that way, but a bit clunky!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Public Post Preview] [Plugin: Public Post Preview] Stopped Working](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/)
 *  [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [13 years, 8 months ago](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/#post-3005522)
 * I have found that if I replace the permalink structure with ?p=POSTIDHERE, the
   preview links work for non-logged in users. So I wondered if it had something
   to do with the htaccess/permalink rules. I disabled my caching plugin that modifies
   that file, but I couldn’t remove the issue. I have started to deactivate other
   plugins, but to no avail. It seems intimately tied to permalinks and user login
   hooks, so perhaps my custom theme + new plugin update is the culprit?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Public Post Preview] [Plugin: Public Post Preview] Stopped Working](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/)
 *  [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [13 years, 8 months ago](https://wordpress.org/support/topic/plugin-public-post-preview-stopped-working/#post-3005515)
 * Similar problem: preview links now only work for logged in users and result in
   404 otherwise. The url seems to have changed:
 * Old (v2.0.1) of the plugin):
    [http://example.com/?p=2012041336&preview=true&preview_id=2012041336&public=1&nonce=1ae17b81c2](http://example.com/?p=2012041336&preview=true&preview_id=2012041336&public=1&nonce=1ae17b81c2)
 * New (v2.0)
    [http://example.com/2012/09/02/post-title-string/?preview=1&_ppp=e42872b7c6](http://example.com/2012/09/02/post-title-string/?preview=1&_ppp=e42872b7c6)
 * I reverted to 2.0 and the same behavior exists. Thanks!
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [wp_get_archives and 3.0](https://wordpress.org/support/topic/wp_get_archives-and-30/)
 *  Thread Starter [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [15 years, 10 months ago](https://wordpress.org/support/topic/wp_get_archives-and-30/#post-1552794)
 * Yes, 96MB limit got it working. The plugin didn’t help though. 96MB seems kind
   of ridiculous. Something about the 3.0 upgrade did something to the memory usage
   of wp_get_archives().
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [wp_get_archives and 3.0](https://wordpress.org/support/topic/wp_get_archives-and-30/)
 *  Thread Starter [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [15 years, 10 months ago](https://wordpress.org/support/topic/wp_get_archives-and-30/#post-1552680)
 * Easier than I thought to set up the error log. It is a memory issue:
 * `[25-Jun-2010 01:48:58] PHP Fatal error: Allowed memory size of 33554432 bytes
   exhausted (tried to allocate 102286 bytes) in /home/REMOVED/wp-includes/general-
   template.php on line 1025`
 * So not really a bug, but I would think that 8MB would be enough. Upping it to
   32MB didn’t help. Is that a unreasonable amount? There are about 1250 posts in
   the full postbypost output.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [wp_get_archives and 3.0](https://wordpress.org/support/topic/wp_get_archives-and-30/)
 *  Thread Starter [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [15 years, 10 months ago](https://wordpress.org/support/topic/wp_get_archives-and-30/#post-1552678)
 * Thanks for the responses. I need to set up a PHP error log on my server. I don’t
   think that is the problem as the site is on a dedicated server with 8Gigs of 
   RAM. PHP’s memory settings seem ok as well:
 *     ```
       max_execution_time = 30     ; Maximum execution time of each script, in seconds
       max_input_time = 60	; Maximum amount of time each script may spend parsing request data
       memory_limit = 8M      ; Maximum amount of memory a script may consume (8MB)
       ```
   
 * Will get back to you.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [wp_get_archives and 3.0](https://wordpress.org/support/topic/wp_get_archives-and-30/)
 *  Thread Starter [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [15 years, 10 months ago](https://wordpress.org/support/topic/wp_get_archives-and-30/#post-1552605)
 * Indeed, WP Super Cache appears to be the culprit (even if upgraded to the most
   recent version).
 * So I next tried W3 Total Cache as well and it again broke the wp_get_archives.
   So it seems that caching + unlimited archive listing do not agree.
 * Any idea what the underlying issue could be?
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Hacks for 2.9.2](https://wordpress.org/support/topic/hacks-for-292/)
 *  Thread Starter [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [15 years, 11 months ago](https://wordpress.org/support/topic/hacks-for-292/#post-1504865)
 * Will do. My priority was removing the hack. But I suspect it will come back in
   a day or to. Here is a summary of what is happening:
 * [http://blog.sucuri.net/2010/05/seo-spam-network-details-of-wp-includes.html](http://blog.sucuri.net/2010/05/seo-spam-network-details-of-wp-includes.html)
 * It is important to note that you can’t see the code if you simply visit your 
   site. The hacks are smart enough to check for Google IPs or referrals. So I recommend
   signing up for Google Webmasters:
 * [http://www.google.com/webmasters/](http://www.google.com/webmasters/)
 * and then using the “Labs –> Fetch as Googlebot” to check if you have been infected.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Hacks for 2.9.2](https://wordpress.org/support/topic/hacks-for-292/)
 *  Thread Starter [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [15 years, 11 months ago](https://wordpress.org/support/topic/hacks-for-292/#post-1504845)
 * I can now confirm that 2.9.2 has some sort of hole in it. I made a completely
   clean install of 2.9.2 on Rackspace Cloud Sites. Within three days, all queries
   were re-directing to a Canadian pharmacy. This is very pressing. I have used 
   WordPress since .01 and never had this problem. Trying to stay on top of these
   hacks is a full-time job.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Hacks for 2.9.2](https://wordpress.org/support/topic/hacks-for-292/)
 *  Thread Starter [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [15 years, 12 months ago](https://wordpress.org/support/topic/hacks-for-292/#post-1504617)
 * Oh and I know a moderator is going to post something like:
 * [http://wordpress.org/support/topic/268083?replies=28#post-1065779](http://wordpress.org/support/topic/268083?replies=28#post-1065779)
 * but I have followed every single tutorial and site. I have run about 25 sites
   since WP was released (user 47 on the forum!), and this is the first time I have
   ever encountered a hack. I have exhausted the standard methods and the “delete
   everything and re-install” no longer works.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Automatic upgrade with no error message](https://wordpress.org/support/topic/automatic-upgrade-with-no-error-message/)
 *  Thread Starter [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [16 years, 4 months ago](https://wordpress.org/support/topic/automatic-upgrade-with-no-error-message/#post-1316885)
 * On one of the 6 sites it doesn’t work on, deactivating the “WordPress Database
   Backup” plugin made it work. But it still fails on five other sites with few 
   plugins.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Automatic upgrade with no error message](https://wordpress.org/support/topic/automatic-upgrade-with-no-error-message/)
 *  Thread Starter [Mike](https://wordpress.org/support/users/mike/)
 * (@mike)
 * [16 years, 4 months ago](https://wordpress.org/support/topic/automatic-upgrade-with-no-error-message/#post-1316881)
 * I added it to the root htaccess and one in the wp-content and wp-admin folder,
   but it didn’t work.

Viewing 15 replies - 1 through 15 (of 107 total)

1 [2](https://wordpress.org/support/users/mike/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/mike/replies/page/3/?output_format=md) …
[6](https://wordpress.org/support/users/mike/replies/page/6/?output_format=md) [7](https://wordpress.org/support/users/mike/replies/page/7/?output_format=md)
[8](https://wordpress.org/support/users/mike/replies/page/8/?output_format=md) [→](https://wordpress.org/support/users/mike/replies/page/2/?output_format=md)