luismoyano

Hi Maciej,

First, sorry to duplicate the case. But I thought I had written my previous post on the Yoast SEO WordPress page in case the problem was theirs, hahaha. That’s why I wrote another post on this support page, looking for your help as the developer of Permalink Manager.

OMG! I do so many things at the same time lately!

The good news is that the problem has been fixed after removing the last slash within the WordPress permanent structures. I honestly thought that the Permalink Manager settings overwrote those default WordPress settings, and there was no need for me to do anything there.

Now I see my mistake, and once I removed the last slash, the sitemap turned totally correct.

Thank you very much for responding so quickly, and again, sorry for having duplicated the query by mistake.

Have a nice rest of the week, and congrats for such a great plugin!

• This reply was modified 6 months, 2 weeks ago by luismoyano.

Hi, I can confirm that deleting the Sitemap Yoast cache does not fix the issue.

You can check my category sitemap online here in this image: https://ibb.co/31X04Q1

I’m using the plugin “Permalink Manager Lite,” and the categories are working perfectly on the website without adding the last slash to the URL. But, the category sitemap still shows that slash, so Google tells me that my Sitemap is not showing the canonical URL in the Sitemap.

How can I fix this? Manually? Should I delete the Yoast category Sitemap and add my own Sitemap for categories? Let me know!

Thanks ahead!

I’ll try and let you know! Thanks!

OK, I confirm that setting a featured image to the page sets that image as #primaryImage in the schema. It’s not the best solution ever, but it fixes what you need to solve as soon as possible.

Thanks!

Again, is anyone there? Or should I understand that you are not interested in fixing this?, or that you don’t know how to fix it?, or that I would have to look for another plugin to fix it? Please answer my question when you have a while. Thanks!

De nuevo, ?hay alguien ahí? ?Debo entender que no estás interesado en solucionar esto? ?O que no sabéis como solucionarlo? ?O debo entender que tendría que buscar otro plugin para solucionarlo? Por favor, responde a mi pregunta cuando tengas un rato…

I’m still waiting for a response, is anyone there? Please don’t wait too many days to say that the comment was closed due to inactivity. I’m sure you can offer me a solution from your development team. Thanks in advance!

Please, any idea about how to change that part of the schema and shows the real image? Thanks!

Hi There; the problem is that the first image is not loaded as an image/picture but as a background. That’s why Yoast gets the second image on the page. It is not a problem in the posts because they all have a Featured image. But in the case of my pages, all of them are loaded as background in the hero part, and that’s the issue and the reason for this support message.

Around two years ago, if my memory did not fail, the developers promised to allow users to change that behavior and choose the image that should go into the #primaryimage. Now I see that this has not been done yet. Am I wrong?

Can I inject the correct image on my pages by writing code in the functions.php? I hope so! Can you provide me with that code?

Thanks In advance!

This is happening to me too, and even worse, because fakes urls are being redirected to real URLs of posts or images. I think I’m moving from Yoast soon because Google is taking all those URLs a real, and place them inside crawled but not indexed which I’m sure it’s harming my website. OMG!

Solved!

I could finally solve the issue. It was totally my bad; well… it was a plugin.

But, maybe as a developer, I tend to look for the most complicated path to solve issues. A regular guy would have deactivated plugin by plugin to see if the problem was fixed. OMG!

Finally, I found some buttons clicked in a plugin (no idea why did happen) that completely deactivated several plugins in the front end, not only redirection. Now, everything is back to normal, so I deactivated all the redirections in my htaccess.

Thanks John for your kind help debugging this, and for such an amazing plugin!

Hi, I checked many things but still needed help with the plugin. I installed another previous version that didn’t help either. I deactivated the caching plugins, and it’s still not working.

In a previous message, I told you that this syntax (RewriteRule ^old-url/$ https://new-url/ [R=301, L]) didn’t work, but it works, but you must write it right after the code generated by FlyingPress, and before the ending </if module> tag inside htaccess. Otherwise, it doesn’t work.

So, at this moment, unless you give me some idea about how to solve it, I have deactivated redirection. Instead, I have written all my redirected URLs in the htaccess with the second syntax (redirect 301 /old-URL/ https://new-url/ ) to avoid that if I deactivate FP, all then redirections are removed from htaccess.

Any idea about what is happening? Until yesterday or the day after, everything was working perfectly!

Thanks ahead!

Hi John,
You should see an email in your inbox. Now it’s working correctly, but not with the syntax redirection uses, which is so weird because I never had problems with your plugin before!

Thank you for your fast answer!

I have exported all the urls from redirection to my htaccess, and I have discovered one thing.

Is there any reason why the first syntax works with some URLs but with not others, but the second syntax works perfectly with all of them? I’m using 325 redirected URLs at this moment, and have not updated my server in the last 2 years as far as I know.

1. RewriteRule ^old-url/$ https://new-url/ [R=301,L] (NOT WORKING)
2. Redirect 301 /old-url/ https://new-url/ (WORKING PERFECTLY)