Dobbydoo

Hey Sybre,

Thanks for your response! That should be fine, I’ll keep an eye out.

Keep up the great work! Have a great day too.

Okay, I think I found it. I went through the databases again, with some other search terms.

In wp_postmeta, looking for _genesis_title , I found the following example:

[:nl] Garantie – MountShop.nl [:en] Warranty – Mount-Shop.com

When I changed this to “[:nl] Garantie [:en] Warranty ” everything looks fine.

Any idea how this could occur? I’m thinking it’s caused by importing Yoast SEO to The SEO Framework, although it’s still weird I think.

Hi, I used the code and it helped me change the color of the footer. But I also want to change the color of the menu buttons, can you help me please?

Okay guys, I have the solution ??

– For the color picker, add the TinyMCE Color Picker plugin.

– For all the other things TinyMCE 4.0+ and WordPress 3.9+ related : Click here !

Enjoy !

I can’t add anything to this WP installation.

Since all the sub-menus of the plugin depend on the user having the publish_posts credential, is there a reason why you can’t check for the same permission for the parent menu?

Can you add it in to the plugin? I can’t modify functions.php. Looks like it’d be around line 3832 of lib/the-events-calendar.class.php (looking at the code for 3.5.1).

With the social media icons on bot the header looks a bit unstructured and empty. To deal with I want to set another line above the menu with the same distance to it. Like:

____ (wished)

menu
____ (existing)

I searched for it in the css file but am not used to css, so didnt find the right line to copy..

Thank you in advance!

Hi Thorsten,

Woah, fast and great support! Excellent, it’s working flawlessly now!

Thanks a lot! You miss a donate button now ??

Keep up the good work!

Sincerely,

Dobbydoo

Thanks for the quick reply Ajay ??

I’ll give it a try on a test site. Good luck with the pro version!

Ok simple enough, that’s good to know ??

Polylang 1.4 was worth the update. I especially liked the get_pages filtering.

I found a small bug in the new quick edit admin menu for categories. Language is displayed as default even though it’s not. It’s just an issue with the UI value not being set to the real value.

Quick edit for posts and pages displays correctly, haven’t tested tags.

Thanks for this tool!

Yeah the XML needs to be loaded each time it seems, but translating with it is cleaner. I got a test site messed up because I combined the PHP and XML techniques, disabled one or the other, cleaned up and generally testing many things to find a good workflow.

In the end the XML is better. And it’s probably not slower for the normal user visiting the site, sounds like it’s only loaded for that Strings translation tab… (Is that correct?)

ronalddehommel, Chouby’s XML works. If it doesn’t, try doing something in the theme settings and saving, that did the trick for me.

You found that it is catcheverest_options because it is used with the register_setting function, right ?

But how do you find out about the 3 subkeys ? Using a different theme I tried a bunch of things and nothing appeared in the strings translation tab.

I had to use PHP directly as succinctly described here. Upside is that you only have to register once, then it stays in the strings translation tab and you can remove the PHP, so no slowdown. I’m not sure it’s the same with wpml-config.xml, which may have to be loaded each time. Or not… ??

Heh, sounds like you have a nice can of juicy worms waiting for you. Good luck !

Thanks a bunch ??

I’ll give it a try. The reason I suggested this is because Yoast’s WordPress SEO includes a bunch of Open Graph meta tags by default. Since it’s made by SEO experts I figured they had a good reasoning behind this and Polylang could benefit from it as well ??

I’ll be answering myself: Use icl_register_string to have the string you want appear in the “Strings translation” tab in the admin area.

Then use icl_t or pll__ in your site where you want the string to display.

icl_unregister_string will allow some cleanup, but beware, the string partially remains in the database, in the polylang_mo post_type entries of WordPress wp_posts table.

This is expected behaviour, so that you don’t lose your hard worked translations when you disable or uninstall Polylang. If you want to clean up any remnants, use the “Clean strings translation database” in the strings translation tab. Any entry listed in this tab won’t be cleaned up, only those you unregistered or pertaining to uninstalled plugins.

Checkout wp-content/plugins/polylang/include/wpml-compat.php to learn how to use the functions I just talked about.