Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Replacing the title tag in my theme didn’t work either.

    Specifically, the way WP SEO and Query Multiple Taxonomies rewrite titles don’t play nicely together.

    Or maybe neither of them played nicely with my own title rewriting.

    Whatever. I really just wanted to disable Yoast’s title rewriting.

    There are a number of posts here with solutions that worked for some people, but none of them worked in this particular case, so I did it the dirty way. Just hacked it out.

    Important Note: It is not normally good practice to change a plugin’s core files.

    Main reason is that you will have to repeat this step each time you update the plugin.

    Anyway, here’s the simple fix.

    In your plugins folder, find /wordpress/seo/frontend/class-frontend.php

    You can get this via FTP, or even just go to your wordpress backend plugin page and hit edit.

    In that file, search for the wp_title filter.

    The version I most recently had to hack had it on line 32, and it looked like this:

    add_filter( 'wp_title', array( $this, 'title' ), 15, 3 );

    I think an older version used to have different numbers toward the end of the line. It should be the only line that starts with add_filter and has wp_title in there.

    Just add a couple of slashes in front of this line.
    That identifies the line as a comment only, not to be executed.

    It effectively stops the whole ugly thing in its tracks.
    // add_filter( 'wp_title', array( $this, 'title' ), 15, 3 );

    Of course, this will disable all the title functionality of the plugin, which might be another problem altogether.

    But if you were happy with your titles before, this is the quickest way to get them back. Especially if the solutions in the other threads haven’t worked.

    I think I found a solution to this problem, at least for some WP 3.5 users.

    As counterintuitive as it sounds, disabling debug mode fixed it for me.

    If you are running 3.5 and have WP_DEBUG defined as true in wp-admin, try setting it to false and see if it helps.

    This solved several other problems for my 3.5 installation as well, as noted here.

    OK, more information:

    It actually IS regenerating the thumbnails!

    The file times were updated in FTP, so I suspected this might be what was happening.

    I changed the featured image size in my theme’s functions via set_post_thumbnail_size and ran the regenerate all thumbnails again.

    Still got the error messages:

    Debugging Information

    Total Images: 7
    Images Resized: 0
    Resize Failures: 7

    function () { if (a) { var t = a.length; (function r(t) {v.each(t, function (t, n) {var i = v.type(n);i === “function” ? (!e.unique || !c.has(n)) && a.push(n) : n && n.length && i !== “string” && r(n);});}(arguments), i ? (o = a.length) : n && (s = t, l(n))); } return this; }
    function () { if (a) { var t = a.length; (function r(t) {v.each(t, function (t, n) {var i = v.type(n);i === “function” ? (!e.unique || !c.has(n)) && a.push(n) : n && n.length && i !== “string” && r(n);});}(arguments), i ? (o = a.length) : n && (s = t, l(n))); } return this; }
    function () { if (a) { var t = a.length; (function r(t) {v.each(t, function (t, n) {var i = v.type(n);i === “function” ? (!e.unique || !c.has(n)) && a.push(n) : n && n.length && i !== “string” && r(n);});}(arguments), i ? (o = a.length) : n && (s = t, l(n))); } return this; }
    function () { if (a) { var t = a.length; (function r(t) {v.each(t, function (t, n) {var i = v.type(n);i === “function” ? (!e.unique || !c.has(n)) && a.push(n) : n && n.length && i !== “string” && r(n);});}(arguments), i ? (o = a.length) : n && (s = t, l(n))); } return this; }
    function () { if (a) { var t = a.length; (function r(t) {v.each(t, function (t, n) {var i = v.type(n);i === “function” ? (!e.unique || !c.has(n)) && a.push(n) : n && n.length && i !== “string” && r(n);});}(arguments), i ? (o = a.length) : n && (s = t, l(n))); } return this; }
    function () { if (a) { var t = a.length; (function r(t) {v.each(t, function (t, n) {var i = v.type(n);i === “function” ? (!e.unique || !c.has(n)) && a.push(n) : n && n.length && i !== “string” && r(n);});}(arguments), i ? (o = a.length) : n && (s = t, l(n))); } return this; }
    function () { if (a) { var t = a.length; (function r(t) {v.each(t, function (t, n) {var i = v.type(n);i === “function” ? (!e.unique || !c.has(n)) && a.push(n) : n && n.length && i !== “string” && r(n);});}(arguments), i ? (o = a.length) : n && (s = t, l(n))); } return this; }

    However, it successfully created new images in the expected sizes and seems to have regenerated all the existing sizes since the timestamps have been updated on these.

    I am getting the identical debugging message.

    Total Images: 7
    Images Resized: 0
    Resize Failures: 7

    function () { if (a) { var t = a.length; (function r(t) {v.each(t, function (t, n) {var i = v.type(n);i === “function” ? (!e.unique || !c.has(n)) && a.push(n) : n && n.length && i !== “string” && r(n);});}(arguments), i ? (o = a.length) : n && (s = t, l(n))); } return this; }

    This is on a brand new install of 3.5 (having lots of issues with 3.5 already)

    With all plugins disabled the message is the same. From the main screen to regenerate all thumbnails or from the media page and attempting to regenerate thumbs for a single message, same problem.

    Just for the sake of thoroughness, I tried chmod 0777 on uploads directory, the subdirectories and all image files. Problem persists.

    Interestingly, I have a WP 3.4 installation on the same server and the plugin is working fine there.

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