David G. Johnson

The plugin author has posted an update that fixes the problem. I’ve confirmed that version 1.0.1 of this plugin is working properly on the site where I had a problem with version 1.0.0.

Thanks for linking to the previous version for lazy people like me! The 1.0.0 version definitely brought my site down, so it’s back to the (working) previous version for now.

Upgrading to 1.0 produced the same errors on my site. Renaming the plugin folder causes WordPress to automatically deactivate it, so that was my first step. Then I came here looking to report the error and found this and other posts.

@sdellenb posted a helpful link to the previous version of the plugin, which I’ve uploaded to my site and now have the functionality back.

Hey there — I’m experiencing the same issue (although I use the OptimizePress plugin, not the theme).

Quick question: are we waiting on an update for OptimizePress or Akismet?

Also: If downgrading Akismet, do we simply use v. 3.1.7 from the repository, or is there a special procedure for downgrading?

Thanks!

I just noticed that I can see & edit existing redirects in the latest version. Came here to mention it, and realized that @gmangesh had already pointed it out.

Although we can’t add new redirects via the plugin (at least not the free one), this is a good compromise.

Props to the Yoast crew for doing this.

Yep, @mikegood — it was mentioned previously, but it’s easy to miss in this thread:

The Redirection plugin has served me well for quite a long time now. I had only recently started to think of using this feature inside of Yoast…

Hope this helps!

Thanks, @tacoverdo. I appreciate the responses.

So the bottom line is: We need to upgrade to Premium

OR

We need to locate all of our existing redirects using the method @diywebmastery wrote about and get them handled another way so that when Yoast deprecates the existing redirect functionality, the redirects will not be broken.

OR

We need to never update the Yoast SEO plugin again (not practical).

Now if I could only remember which sites I’ve used this feature on…

@niagaracollege you might take a look at the Redirection plugin. It’s what I’ve used for many years now to handle redirects. I had really only recently (in the last year or so) begun to utilize the 301 redirect function in the Yoast SEO plugin. (Didn’t know it was there before then!)

Yes… thank you very much, @diywebmastery — very helpful indeed!

Thanks for your detailed response, @tacoverdo

I understand the rationale: difficulty in managing, and site load times.

It is hugely helpful to know that all the redirects still work.

If I understand you correctly, for now the plugin still performs the query on pageload to check for the redirect, is that right? Is there a plan to deprecate this in the future for the sake of speeding up site load times?

I hadn’t thought about trying to keep track of the redirects, as I had no need to do so. The database was doing that for me.

Perhaps it would be helpful to understand a little bit better how the premium version helps manage redirects. Does it accomplish this without sacrificing load times? I’ve seen the video that you guys published about it, so the UI makes sense to me. My question is really directed to what’s under the hood… is it substantially different or does it perform the same query at page load that you referred to in your response?

I’m not worried about you moving the whole SEO plugin to premium — it would destroy your lead generation and the business model would fall apart. What I am worried about is getting surprised with a change and not knowing how my sites are going to be impacted.

Perhaps it would help to include just a bit more detail in the changelog? Currently, the entry reads:

Removed the possibility to redirect a post in the advanced tab of the Yoast SEO metabox.

While its wording was, I’m sure, quite intentional, it did leave us questioning whether the existing redirects would continue to work or not.

Perhaps something like this would help:

Removed the possibility to add new post/page redirects in the advanced tab of the Yoast SEO metabox. (Existing 301 redirects still function.)

One final thought: it would also be helpful to know where the redirects get stored in the database. That way I could at least find them since they’re hidden in the UI.

Thanks again!

@tacoverdo – ultimately I did find a reference to it buried in the changelog, but it was not in the “What’s New in 2.3” that the plugin aggressively presents to users.

I’ll confess that I find this change a little poorly documented. Also, I’ve marked this topic unresolved as your answer only creates more questions (for which I’ve been unable to find any info in the documentation.)

For now, we won’t be updating the plugin on most of the sites my team & I administer because I don’t know:

• What happens to existing 301 redirects when the plugin is upgraded?
• Where can I find all of the posts for which we’ve previously used this feature? (I didn’t bother to keep track!)
• How can I find out about major changes like this in the future before running an update? I need to be able to plan for loss of critical functionality and understand the implications.

Look… you guys are well respected and produce fine software. I don’t mean this post to sound terse, nor do I intend to come across as ungrateful for the work you guys do. It’s just that my confidence is a little shaken after this incident.

Thanks for your help.

Did you ever find a resolution to this issue? I’ve got a similar set of circumstances for a different WooThemes theme.

Thanks!

Thanks for the response!

We’ll switch to Frizzly on some of our sites and wait until this feature is ready on some others.

Thanks again for the great plugins!

Hey Patrick,

Thanks for the response. Yes, I’ve seen that one. It doesn’t look like anyone is maintaining it any more, and it would also be tricky to implement given the change to how WooCommerce handles conversions… which (unless I’m mistaken) was the reason your plugin became necessary.

I actually wouldn’t need a plugin at all for conversion codes of any kind if WooCommmerce still used a WordPress page for transaction success.

Thanks again.

Hi Luke,

It looks like your titles (“The Promise”, “Seminars”, “Team”, etc.) are wrapped in <h2> tags which are contained within a div with the following classes: sixcol first clearfix

That div displays to the left and the way your CSS is set up, the div containing your text has to display to the right of that.

They div containing your text is set up with a very similar class configuration: sixcol clearfix

I’m guessing it’s your theme that is configured to display things this way, but I don’t know enough about your theme to tell you exactly what to do to fix it.