banana7777

@a3rev,

I found the time to test your changes. At least for me now it is working great.
Also I can confirm that the counting is correct. I cannot see any double counts.
Thanks for your support.

Best,
Dirk

@a3rev,

I don’t know, but maybe no other is recognizing the issue. Yes, V2.0.3 is not fixing the issue!

I will give you a little bit more information what will happen with your “fix”. And you did not describe what the fix is for. I don’t see any need for such kind of fix and in my view, it is not a good idea to change a behavior of a plugin within another plugin. If you have a problem with YOAST SEO, talk to the developers of YOAST.
Okay, what will happen. I have not checked this with a standard WP post, but with different CPTs:
In YOAST SEO meta&templates you don’t need to change anything as with this configuration the post content field is used as meta description.

• Write something into the content of a post (CPT) and save it.
• You can check YOAST SEO facebook description. This is now empty (as it should be!)
• Open the post (CPT) in the front view
• Check this post (CPT) in the backend and you will see that now the content is in the YOAST SEO facebook description field (this is caused by your “fix”).
• Any change of the post content will not change the YOAST SEO facebook description. The value is written to the database in step 4.

• This reply was modified 7 years, 1 month ago by banana7777.

@a3rev

I have checked your changes and I’m really confused about the function:

fixed_wordpress_seo_plugin

What do you like to fix with this function?
Instead of fixing anything you are messing up things for me. You are still writing a description to the database with this change and the templates will not work anymore.

• This reply was modified 7 years, 1 month ago by banana7777.

@goyakpacking

I’m not familiar with GoDaddy, but typically you can switch between the PHP Versions. If it will not work you can go back. If you are not sure about it, you can contact their hotline.

If your plugins are up-to-date, the risk is low. But you need to test it. PHP5.4 is not supported over 2 years now. No security updates anymore. You should update to PHP7 or above as soon as possible.

It is because of your outdated PHP Version. PHP5.6 or higher is required.

Your PHP Version < 5.6.0?

The 3.2-beta-3 is now solving the issue!

https://github.com/johngodley/redirection/releases/tag/3.2-beta

Thanks

I can provide staging site access if you like…

https://github.com/johngodley/redirection/releases/tag/3.0.1

BTW: I downgraded the plugin to 3.0.1 and everything is working fine again. Check your changes!

It is not changing anything. Still the same.
I have checked that the actual JS File was loaded. And it was (/*! Redirection v3.2-beta-2 */)

As this was introduced with 3.1 or 3.1.1 I suggest that you rollback the changes in these versions!

To be a little bit more specific (for my case):
– Delete of a CPT
– The created (unabled) redirect cannot be enabled or deleted

I think it is introduced with the latest version.

Over a month no reaction. Nice support…

The same here. So for me confirmed…

The bug is in the premium and in the free version.
Rolling back to 6.0 solved this.