Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • It looks like it was an incompatibility with one of my plugins:

    BackupBuddy, by the good folks at iThemes, was somehow disabling the WordPress 3.0 update notification system. They provided a manual update of their plugin, which fixed the problem.

    Great backup plugin, btw, in case anyone’s looking for an easy but comprehensive way to backup, restore and migrate your WordPress blog.

    http://pluginbuddy.com/purchase/backupbuddy/

    I don’t know if I should start a separate thread, but I have a similar problem.

    Within the admin area, I receive the little orange notifications that plugins need to be updated. But when I go to either the new Dashboard>Update area or the Plugins screen, there aren’t any plugins requiring updates.

    I compared the versions of my plugins against another blog where notifications work fine. I can then identify which plugins are out-of-date and manually update them via FTP.

    But why would the admin area not indicate which plugins need to be updated when some portion of WordPress knows enough to give me the little orange update indicator?

    This problem only appeared after updating to WordPress 3.0 and I have other blogs with 3.0 that don’t have this problem.

    Anyone have any idea what could be causing this?

    I’m having exactly the same problem with this plugin using exactly the same syntax. What this appears to do is change the URL from

    http://domain.com/category/name/page/2/

    to

    http://domain.com/category/name/page/http://domain.com/

    Which of course sends the user to a 404.

    I don’t want the redirection messing with any of the URLs other than:

    http://domain.com/page/2 <= and any number here

    Which is exactly what the thread starter described. Are we doing something wrong with regular expressions or is this a bug with the redirection plugin?

    I have also tried:

    Source URL: /page/(\d*)
    Target URL: http://www.domain.com/
    HTTP Code: 301
    Regex: Checked

    And:

    Source URL: /page/(\d*)
    Target URL: /
    HTTP Code: 301
    Regex: Checked

    No luck. Any ideas?

    Thread Starter Kudama

    (@kudama)

    Got it!

    I was just accidentally leaving in a variable from a sample I saw for a similar solution. So this works perfectly:

    add_filter('the_content', 'rewriteURL');
    
    function rewriteURL($URL) {
    $URL = str_replace('http://domain.com/my-permalink', 'http://domain.com/', $URL);
    return $URL;
    }
    Thread Starter Kudama

    (@kudama)

    So I tried adding this to functions.php:

    add_filter('the_content', 'rewriteURL');
    
    function rewriteURL($URL) {
    $input = str_replace('http://domain.com/my-permalink', 'http://domain.com/', $URL);
    return $URL;
    }

    This seems like it should do what i want, but I really don’t know for sure.

    When I load the page with the sitemap, it just stops loading at the_content (so my sidebar and footer don’t render). This only happens on the page that has the URL I want to change, so it seems to be doing something.

    Any feedback or ideas? Thanks!

    Thread Starter Kudama

    (@kudama)

    Understood — great! I appreciate that it won’t be done overnight or even within several weeks. I was just wondering if you were working on it. Thanks!

    In the mean time, I have a couple related questions. So I disabled CDN temporarily for one site just to do a speed comparison of it gzipped vs on the CDN.

    Now in YSlow I still get the following problems:

    CDN: F (expected here, of course)
    Add Expires Header: F
    Compress Components with gzip: B
    Configure Entity Tags: D

    So I checked another couple of sites where I hadn’t setup a CDN yet, and it got the same scores.

    I then checked with Google Page Speed and received a warning to “Leverage Browser Caching.” Upon looking at the details, this warning seems to be invoked by the same problems causing the Expires Headers and Entity tags scores in YSlow.

    Because YSlow indicated that the root domain wasn’t gzipped, I double-checked it at http://www.gidnetwork.com/tools/gzip-test.php, and sure enough, that tool indicates it isn’t gzipped either.

    So two questions:

    1. What can I do about the Expires Header and the Entity Tags. From the documentation I thought W3 Total Cache took care of these. Is there a setting I should adjust beyond the defaults?

    2. Why does both YSlow and http://www.gidnetwork.com/tools/gzip-test.php see my sites as not gzipped when I’ve double-checked that ‘gzip and deflate’ is set on each of my sites? Is this problem with the way those sites check for gzipping or is there something I could be doing wrong?

    The only settings I changed from defaults were HTTP Compression -> ‘gzip and deflate’ and Page Caching Method -> ‘disk (enhanced).’

    I hope I don’t sound ungrateful with my inquiries. I think your work is awesome and I’m super appreciative. I’m just trying to determine how to correct these minor imperfections with my YSlow and Page Speed scores (and I want to make sure my sites really are being gzipped) and I realize I’m probably just doing something wrong or misunderstanding some detail.

    Thanks!

    Thread Starter Kudama

    (@kudama)

    Gosh, I was really hoping for some kind of feedback on this matter. I’ll bump one more time and then I promise I’ll let it rest.

    Thanks in advanced to anyone who takes the time to read and respond. 🙂

    Thread Starter Kudama

    (@kudama)

    I really don’t mean to be rude, but…. *bump*

    Maybe if I state it more succinctly:

    Is it okay if I use the redirect plugin to do a 301 redirect from domain.com/post-name to domain.com if Post-Name is stickied on the front page?

    Would anyone see any problems with this solution?

    Thanks!

    Kudama

    (@kudama)

    I’m not sure if this is what you’re looking for, but try this (it’s really easy):

    Homepage Excerpts Plugin

    Install this plugin, then at Settings -> Homepage Excerpts you can define how many words to show on the homepage for each post before reaching the “read more” link.

    This will then show the number of words of each post you specify on the homepage.

    You can choose the number of “excerpts” to show on your home page at Settings -> Reading -> “Blog pages show at most”

    I hope this helps but I’m sorry if I misunderstood you.

    Thread Starter Kudama

    (@kudama)

    That didn’t work.

    But the p2pconverter plugin works perfectly. All I did was stop searching by “change page to post” or “page 2 post” and similar phrases to CONVERT page to post and this fantastic plugin dropped into my lap.

    I can’t believe how easy it makes it. You just a big ol’ button within the page edit area and voila! Conversion complete. In case anyone comes across this thread looking for this solution:

    http://wordpress.org/extend/plugins/p2pconverter/

    Thread Starter Kudama

    (@kudama)

    I can’t believe this was the solution, but I found something that may work.

    I completely delete the page for 12 hours. THEN I repost it as a post.

    For some reason, the wp database doesn’t like immediately reposting to the same slug/permalink, but if you wait a bit, it will do it fine… huh?

    Can anybody explain why this is? Is there a faster, more intuitive way to convert a page to a post?

    (I’ll mark the thread as resolved if this works consistently on a couple more pages.)

    Thread Starter Kudama

    (@kudama)

    I appreciate your taking time to respond.

    I don’t want two posts or two pages or two anything. I just want a single post at a single URL/permalink/slug.

    I just want to clear the database of any evidence of the page, then take the same text and drop into a new post.

    The problem is that the database for some reason keeps a reference to a page that no longer exists. So after I delete a page, I can never use that URL/permalink/slug ever again. That seems silly and there must be a way around it.

    That Restore ID plugin works great. Thanks!

    This does seem like an embarrassing oversight in 2.5. I certainly expect it will be resolved in the next core release.

    Thread Starter Kudama

    (@kudama)

    Thanks for the response and verification. 🙂

    It looks like I can just tell the search engines which sitemap I’m feeding them with the following in the Robots.txt:

    ‘Sitemap: http://www.domain.com/sitemap.xml&#8217;

    Thanks again.

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