tmobilon

Thanks Raul!

I will change the order of the import rules here, too.

Best,

Yes, without merging everything is fine.

But i’ve always used this option, and it always worked fine. But since the last update (or some before that), when i merge my css, some pages break a little.

Hi Matthias,

I decided to keep it like this for now, as everything seems to be working fine with the fixes.

I have another question, though. I want to use www as the sub to map the custom post type, but the plugin seems to be striping out the www from the mapping.

It works when i use any other subdomain, but not with www. Is there a way to disable this stri_replace?

I even tried to use set www.www.domain, but it doesn’t work either.

Kind regards,

Hi Matthias,

Just an update: i’ve managed to replace the wrong URLs using nginx sub_filter. It’s just a quick fix, not the final solution. It replaces the tecnoblog.net/meiobit/arquivos/ path with bau.tecnoblog.net/meiobit/, everytime a html/xml file is generated.

Not great, but works for now!

Hope we can find aa definitive fix in the plugin. ??

Hi there,

Sure, here is an example:

https://bau.tecnoblog.net/meiobit/2015/raspberry-pi-zero-so-existe-por-sugestao-de-eric-schmidt-influencia-google-fazer-mais-com-menos/

If i open the post editor and hit “update”, the canonical changes to the mapped subdomain. But doing so doesn’t change the domain in sitemaps.

Also, the Yoast index was generated after the plugin activation, and after publishing the post. So it’s not a cache related issue.

The mapping:

bau.tecnoblog.net/meiobit -> tecnoblog.net/meiobit/arquivos

Done:

https://github.com/Yoast/wordpress-seo/issues/15246#issuecomment-644954757

Hi there, just to add one information:

We also have HTML cache in NGINX, so what happens is that the metadata from the preview also goes to the HTML cache, that lasts for 48 hours. To flush that, i would have to go from post to post, and hit the “update” button.

We publish almost 40 posts everyday, so that’s not a very practical solution.

I also didn’t change any configs in our setup: no new plugins, configurations, etc. The bug simply started after upgrading to Yoast 14.x version.

Of course, if i disable Redis Cache, the problem goes away. But as i mentioned before, we are using the same setup and this problem didn’t exist before upgrading.

So, does Yoast really need to store this keys in the object-cache while in post preview?

• This reply was modified 4 years, 5 months ago by tmobilon.

I’m having the same problem. By now i know that must be something with CloudFlare. I know because i don’t get this error when using a direct link.

But i don’t know why is this happening and how to fix it… =/

I’m using the version 1.3.5 here, and having the same problem

I’m still trying to find out how to show the galleries like matt does at the listages, and how to show picture exif informations.

Thanks mitten for the help!

Good point.

With sub posts, you would have a more organizated gallery style, and they also, would not go to the feeds. If you use posts under a category, then your albuns (posts) would be listed at the homepage, and also go to the feeds.

Wich one do you like a more? I’m still in doubt.

I’m with the very same doubt, and i’d like to know how to do all that stuff that Matt did in his Gallery.