Nodrog2

https://fooplugins.com/foobox-woocommerce/
Sorry this is the page I was referring to

Update after some more beggaring about it seems now to be working.

Thanks for all your help

Thanks for the prompt response.

I carried out both actions and I can see that it is using your test.jpg However I am still getting the same problem.

Any other ideas? It works great on other sites with the same set up so I am baffled.

Gordon

This is something I would like to do also. The button clashes with the look and feel of the page.

Thanks

No The isue I have is specific to YOAST tags not duplicates but corrupt YOAST Tags. If I use the Yoast setting for the canonical URL for each page it goes away. Otherise the canonical setting is corrupted.

From another thread I found you can set the canonical URL in the advanced settings. By doing this and entering the full URL it immediatly fixed the problem. All the Yoast tags are correct.

I think this means that it is YOAST that is adding the superflous domain. I now have the correct

<link rel=”canonical” href=”https://www.domain.com/cornwall-visitor-information/royal-cornwall-show-2015-video/&#8221; />

instead of

<link rel=”canonical” href=”https://www.domain.comhttps://www.domain.com/cornwall-visitor-information/royal-cornwall-show-2015-video/&#8221; />

This domain duplication is only incurring in the YOAST generated tags. Or at least only n the tags immediately under the YOAST header. I do not think another plug-in is interfering with the tags generated by YOAST if it was I do not think adding the canonical URL in the Yoast POST advanced settings would fix it.

It is NOT an issue of duplicate tags but of corrupted YOAST tags. Great that I have found a fix for all new posts but I really do not want to go back through fixing every post and page in the site!

I am not clear where we report this as a bug. Can you help?

I think your issue was similar but not the same I had that with a theme Social settings that were adding the tags which were empty. I disabled the themes ability to set OG tags and that fixed the duplicate issue.

Thanks again for all your help.

I am not convinced to be honest. This came about on two sites immediately following an upgrade. It is ONLY on the tags created by Yoast and I think your issue is different. You are getting nutiple instances. I am not I am getting one corrupt YOAST tag bit multiple instances of the same tag. Where do I go to report this?

Thanks for your help,

Great. I see on another thread a user was talking about using the Yoast lug in settings for the canonical address. I can not see where that is. I can find no where in the Yoast settings that you indicates canonical address. Have I misunderstood?

Where in the plug in settings is the canonical URL entered. I must be staring at it but can not see. it anywhere in the Yoast settings.

https://developers.facebook.com/tools/debug/og/object/

@jeffreyd000 I have seen this also at times if you look at the output it is usually because an <og:=””> value is in twice or is empty. My sole issue is that <link rel=”canonical” href=”..” /> is being treated by Facebook as re-direct because it enters the domain URL in twice. The other tags seem to take the domain from this value. See below.

The following will be treated as a redirect by the crawler:

A HTTP redirect
A <link rel=”canonical” href=”..” /> tag
A <meta property=”og:url” content=”..” /> tag

What i happening for me is that the <link-rel tag at the start of the Yoast Tags has the domain entered twice. This completely screws up all of the Opengrapgh tags. This has happened since the upgrade and the last one did not fix. The frustrating thing is that it was all working so very well.

Yes that has done it. Many thanks and well done…

@raamdev Yes that is exactly what I am saying.

I updated the file and it made no difference so I switched off the all views protection and it all worked. I did a test to see what would happen if I switched the all view protection back on and it immediately went back to 404 error problem.

Thanks

OK I updated the php page but it made no difference. It only works if I switch off the alt views protection. This is not a big issue for me (Alt views).

Well done to all at SMember and thanks for getting on to this so quickly!

Thinking about it a little more.

If I use the default P? permalinks s2 member works for a page that exists but is protected. However with permalinks like that and I try to access a page that does not exist in any form. I get the server 404 NOT the WP 404.

If I switch back to a custom permalink the protected page gets the WP 404 and the non existing page gets the WP 404 no sign of the server 404 page.

Hope that is clear…