Jose Zabaleta

Thanke Gulshan… You say:

Make sure Cache Level: Cache Everything Page Rule URL begin from https:// instead of https:// because your site is on HTTPS version.

The url in my page rule was viaje-iniciatico.com/*

I have changed it to https://www.viaje-iniciatico.com/ and now it works correctly: cf-cache-status: HIT

Thanke… Hug

Al realizar actualizaciones en otro de mis Sitios, he podido ver que el plugin no provoca el error al actualizar Divi, sino al actualizar WP a 5.6

Gracias de nuevo…

One last clarification… In my previous message I shared an idea… but I have to admit that it is not mine… This is how Yoast worked not long ago… In my opinion the change has been for the worse…

Best regards.

Thank you… I conclude with the following idea:

If I don’t set a title for Facebook, it will fall back to the SEO title.

In the same way, if I don’t set a title for Twitter, it would be interesting that SEO title will be used as an alternative.

Best regards.

So if I want the title published by Facebook to be “LALALA” and the title published by Twitter to be the title of the post separator title of the site… I have to enter “LALALA” in the title for Facebook and I have to enter title of the post separator title of the site in title for Twitter.

It would be interesting if leaving the title for Twitter empty, Yoast created twitter:title = SEO title configured in the plugin: https://www.viaje-iniciatico.com/yoast.jpg

Thanke

As you can see in the screenshot https://www.viaje-iniciatico.com/yoast.jpg I have configured SEO Title: Title Separator Site title

As you can see in the screenshot https://www.viaje-iniciatico.com/yoast2.jpg I entered Facebook Title: “LALALA” and left Twitter Title empty.

As you can see in https://www.viaje-iniciatico.com/prueba/ og: title = LALALA and twitter:title has not been created.

Therefore, the title that Twitter publishes is “LALALA”

Why hasn’t Yoast created twitter:title = Title Separator Site title?

Hi…

Everything is updated to the latest version.

As you can see in this test post: https://www.viaje-iniciatico.com/prueba/ Yoast has not created “twitter:title”.

Thanke.

Thanke…

I have established in the plugin configuration that “twitter: title” is made up of the post title, a separator and the site title…

If I leave the “twitter: title” field empty in the post, “twitter: title” should be composed of the post title, a separator and the site title… but Yoast doesn’t create “twitter: title”

Is this a plugin bug?

Thanke Kartik.. I do not want to export comments from my site to another … but from my site to Disqus … The Disqus plugin does not manage to export any comments and through the manual import I can not export all the comments. The question is, why does the xml file generated by my site not contain all the comments?

Thank you … I found the cause of the issue: “Sometimes the headers already sent error is caused by an extra space after closing the php ?> tag, so you can just remove that, and it will fix the issue”.

Best regards… Ug…

The last time I could access https://www.marketing-e-internet.com/wp-admin/ I deactivated all the plugins.

You said “Looks like the theme itself is having an issue” WHY?

Warning: Cannot modify header information – headers already sent by (output started at /home/marketi1/public_html/wp-config.php:100) in /home/marketi1/public_html/wp-includes/pluggable.php on line 1254

What does output started at /home/marketi1/public_html/wp-config.php:100 mean?

Thanke

Thank you. I do not understand the meaning of the warning but I do not see anything related to the theme (Divi) In any case it is not resolved by renaming the theme…