Title: devcri's Replies - page 3 | WordPress.org

---

# devcri

  [  ](https://wordpress.org/support/users/devcri/)

 *   [Profile](https://wordpress.org/support/users/devcri/)
 *   [Topics Started](https://wordpress.org/support/users/devcri/topics/)
 *   [Replies Created](https://wordpress.org/support/users/devcri/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/devcri/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/devcri/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/devcri/engagements/)
 *   [Favorites](https://wordpress.org/support/users/devcri/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 31 through 45 (of 49 total)

[←](https://wordpress.org/support/users/devcri/replies/page/2/?output_format=md)
[1](https://wordpress.org/support/users/devcri/replies/?output_format=md) [2](https://wordpress.org/support/users/devcri/replies/page/2/?output_format=md)
3 [4](https://wordpress.org/support/users/devcri/replies/page/4/?output_format=md)
[→](https://wordpress.org/support/users/devcri/replies/page/4/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[bbp style pack] Missing word translated](https://wordpress.org/support/topic/missing-word-translated/)
 *  [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/missing-word-translated/#post-8134844)
 * Cool! It’s working. I got rid of the ” at ” :)). Thank you, Robin!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[bbp style pack] Missing word translated](https://wordpress.org/support/topic/missing-word-translated/)
 *  [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/missing-word-translated/#post-7722557)
 * Same problem in the german version. I would prefer to switch the “at” off completely
   instead of the translation to “um”.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Timely All-in-One Events Calendar] Capital Letters in Event URL](https://wordpress.org/support/topic/capital-letters-in-event-url/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/capital-letters-in-event-url/#post-7713362)
 * 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!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Timely All-in-One Events Calendar] Capital Letters in Event URL](https://wordpress.org/support/topic/capital-letters-in-event-url/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/capital-letters-in-event-url/#post-7713353)
 * 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?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Timely All-in-One Events Calendar] Capital Letters in Event URL](https://wordpress.org/support/topic/capital-letters-in-event-url/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/capital-letters-in-event-url/#post-7713339)
 * 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/”.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[bbP topic count] Change Font Size?](https://wordpress.org/support/topic/change-font-size-42/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/change-font-size-42/#post-7707752)
 * Wow, that was fast. I just made the update and it’s working!
 * Thank you for the lightning fast update!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Reusable Text Blocks] Seeing shortcode after updating to 1.5.1](https://wordpress.org/support/topic/seeing-shortcode-after-updating-to-151/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/seeing-shortcode-after-updating-to-151/#post-7325426)
 * Yes, you were right. Yesterday the update went smoothly. Thank you.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] WooCommerce Colors Message after Updating to 2.5.3](https://wordpress.org/support/topic/woocommerce-colors-message-after-updating-to-253/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/woocommerce-colors-message-after-updating-to-253/#post-7127727)
 * You are right. It didn’t succeed. There was no ‘woocommerce’ menu item.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Fake Google crawlers Identification – ipv6 mapping problem?](https://wordpress.org/support/topic/fake-google-crawlers-identification-ipv6-mapping-problem/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/fake-google-crawlers-identification-ipv6-mapping-problem/#post-6950762)
 * 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!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Fake Google crawlers Identification – ipv6 mapping problem?](https://wordpress.org/support/topic/fake-google-crawlers-identification-ipv6-mapping-problem/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/fake-google-crawlers-identification-ipv6-mapping-problem/#post-6950760)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Fake Google crawlers Identification – ipv6 mapping problem?](https://wordpress.org/support/topic/fake-google-crawlers-identification-ipv6-mapping-problem/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/fake-google-crawlers-identification-ipv6-mapping-problem/#post-6950732)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[The SEO Framework – Fast, Automated, Effortless.] Breadcrumb Migration from Yoast](https://wordpress.org/support/topic/breadcrumb-migration-from-yoast/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/breadcrumb-migration-from-yoast/#post-6947654)
 * 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!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[The SEO Framework – Fast, Automated, Effortless.] Migration of Custom Post Types – Double Homepage Title](https://wordpress.org/support/topic/migration-of-custom-post-types-double-homepage-title/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/migration-of-custom-post-types-double-homepage-title/#post-6956248)
 * 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!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[The SEO Framework – Fast, Automated, Effortless.] Breadcrumb Migration from Yoast](https://wordpress.org/support/topic/breadcrumb-migration-from-yoast/)
 *  Thread Starter [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/breadcrumb-migration-from-yoast/#post-6947588)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP REST API (WP API)] Force authentication for GET posts (and others) commands](https://wordpress.org/support/topic/force-authentication-for-get-posts-and-others-commands/)
 *  [devcri](https://wordpress.org/support/users/devcri/)
 * (@devcri)
 * [10 years, 11 months ago](https://wordpress.org/support/topic/force-authentication-for-get-posts-and-others-commands/#post-6126175)
 * [@mariofrombelgium](https://wordpress.org/support/users/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.

Viewing 15 replies - 31 through 45 (of 49 total)

[←](https://wordpress.org/support/users/devcri/replies/page/2/?output_format=md)
[1](https://wordpress.org/support/users/devcri/replies/?output_format=md) [2](https://wordpress.org/support/users/devcri/replies/page/2/?output_format=md)
3 [4](https://wordpress.org/support/users/devcri/replies/page/4/?output_format=md)
[→](https://wordpress.org/support/users/devcri/replies/page/4/?output_format=md)