devcri

Cool! It’s working. I got rid of the ” at ” :)). Thank you, Robin!

Same problem in the german version. I would prefer to switch the “at” off completely instead of the translation to “um”.

Ok, that’s it. But it was enough to just visit/open Dashboard > Settings > Permalinks to reset the Permalinks. No need to select default (Plain).

It’s working now. Thank you!

Thank you, Benjamin. This is already getting close to the solution, but now I get a 404 error instead of the event showing up.

I edited the all-in-one-event-calendar-de_DE.po file with Poedit and generated the .mo file and uploaded both to my server. After that the URLs on the overview pages and in WordPress Admin show the URL correctly with small letters. But if I click on one of these URLs I get an 404 error. If I than change manually “veranstaltung” to “Veranstaltung” in the URL the event shows up. I already deleted caches (W3 Total Cache), than deleted all the existing events and made a completely new event. The problem persists. The event is linked correctly now, but doesn’t show up as the URL with the event stills uses the capital letter.

I searched also the .po file if there are more relevant strings with small written “event”, but didn’t find anything obvious. Any more ideas?

Hi,

thanks for your reply. I think the problem comes from the All-in-One Event Calendar Plugin, because other plugins like e.g. WooCommerce or bbPress generate URLs with lowercase letters. And I don’t think that the “WP Force Lowercase URLs”-Plugin is the right solution, as it redirects to lowercase URLs. But in this case this URL doesn’t exist. If I replace manually “Veranstaltung” by “veranstaltung” it will redirect me to the nearest URL matching the slug. Either way I would prefer the source of the problem fixed rather than installing another Plugin to fix the shortcomings of the first ;).

Perhaps the source of the problem is in the translation file of the All-in-One Event Calendar Plugin. Somehow the Plugin knows that /event/ should be /Veranstaltung/ in german. Do you manage the translations for slugs in the translation file? I have seen english URLs that have “/event/” in them. So the german category would be “/veranstaltung/” instead of “/Veranstaltung/”.

Wow, that was fast. I just made the update and it’s working!

Thank you for the lightning fast update!

Yes, you were right. Yesterday the update went smoothly. Thank you.

You are right. It didn’t succeed. There was no ‘woocommerce’ menu item.

I truncated the table “wp_wfCrawlers” and than checked “Google Crawlers”. Looked good. After that I activated “Immediately block fake Google crawlers”. Seems that now it is working fine.

Thank you!

I made the change in the nginx configuration like suggested in the post you have linked to.

I replaced:

listen [::]:80 ipv6only=off default_server;

with:

listen 80;
listen [::]:80;

Than I restarted nginx and activated:
“Immediately block fake Google crawlers”

Instead of getting this:
Wordfence Live Activity: Blocking fake Googlebot at IP ::ffff:66.249.64.51

I get now this:
Wordfence Live Activity: Blocking fake Googlebot at IP 66.249.64.51

Seems like Wordfence is still blocking a real Googlebot even now it’s seeing the IP Address in IPV4 Format.

I switched off the blocking feature for now, but wanted to give you feedback on this.

I have a Dedicated Server at 1&1 as Hosting Provider. The server is running Debian and nginx. I am not using a reverse proxy and no proxy service.

I disabled “Immediately block fake Google Crawlers” when I saw that it couldn’t identify Google.

Hi Sybre,

“Breadcrumb NavXT” works and does the job. I switched of the yoast seo plugin and migrated to your plugin.

Thank you for your support and advice!

Hi Sybre,

you rock! I only had “title” activated under “Supports” in my custom post type. As soon as I activated “editor” the SEO Settings Box appeared. So now I can edit the title tags for the custom post types, too.

The answer to your question:
title and og:title are the same, e.g.:

<title>Item - Name - Name</title>
<meta property="og:title" content="Item - Name - Name" />

Thank you very much!

Hi,

thank you very much for your answer. I will check it out. I got a little confused about the “LD+Json Breadcrumbs script” in the plugin description.

@mariofrombelgium:
The filter from Daniel worked as described, when I wrote my reply here. But now it doesn’t have any effect anymore. I now get the posts when trying: domain.tld/wp-json/posts/

I also would like to protect the whole API as I just want to access it from an App. Exposing usernames seems like a bad idea to me.