Corey Worrell

Thanks very much, that seems to have fixed it!

I should also note that because of our server setup (running as cgi process) we cannot set the header in .htaccess file as it will be ignored.

Awesome, thanks very much!

Great, I knew it had to be something like that. Looks like it should do the trick. Thanks very much.

I realize now that I had to manually go to the Reading Options page and change the language to Spanish from the admin bar dropdown, and then set the home page and posts page again. After that the link was correct. I had assumed that creating a translation of the English posts page would set it as the post page in the respective language.

Even now, when going to the Reading Options, with language set to show all, it shows the Spanish pages preselected in the dropdowns. Changing to English shows them set to a dash “-“. Kind of confusing behavior. Posts page in admin shows the correct pages as “Front Page” and “Posts Page” though.

I don’t think we’re understanding each other.

If a client is managing their website, they don’t care whether content is coming from the database or coming from a template, or what. They just want to translate anything that is shown on the website… So why should a user need to go to the Polylang String Translation page to edit certain strings there, but then need to use another plugin’s page to edit other strings?

WPML handles this by searching the theme files for instances of __() and the like and letting you translate them through their String Translation page. Exactly like you would expect.

I know you’re saying it’s not Polylang’s responsibility, but from a user’s standpoint, it really ought to be.

Anyways, thank you for your help.

Okay, I guess what I expected is that I would be able to use __() throughout my theme, and then Polylang would allow me to edit the translations of those strings through the Strings translation page in the admin. Is this possible?

I understand I can use the default .mo files, but those are not easily editable by the client, unless we install another separate plugin. But it seems this should be handled by Polylang.

Thank you.

Hi @emregan,

This plugin was only made to work with ACF v5 and above. I’m not sure how it’s even running with ACF 4?

The latest version of ACF 5 includes this field built in now, so this plugin is obsolete.

Thank you.

Thanks very much @daltonrooney. Glad that it worked well for you!

@duongcuong96,
The memory limit was set to 128MB, which should be fine, and has been fine for the website until now. You can see that the errors were happening during the BackWPup cron job, and it only happened with the WordPress XML option checked. After unchecking it everything runs fine and no errors.

Also have been experiencing this problem. Our site uses WooCommerce as well. The log files show thousands of lines like the following:

[10-Aug-2017 16:12:12 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /.../wp-includes/cache.php on line 123
[10-Aug-2017 16:12:12 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /.../wp-includes/load.php on line 677
[10-Aug-2017 16:16:27 UTC] WordPress database error Not unique table/alias: 'tm' for query SELECT  t.*, tt.*, tm.meta_key, tm.meta_value , tm.meta_value FROM wp_terms AS t  INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id LEFT JOIN wp_termmeta AS tm ON (t.term_id = tm.term_id AND tm.meta_key = 'order')  LEFT JOIN wp_icl_translations icl_t
                                    ON icl_t.element_id = tt.term_taxonomy_id
                                        AND icl_t.element_type IN ('tax_faq_category','tax_tribe_events_cat') LEFT JOIN wp_termmeta AS tm ON (t.term_id = tm.term_id AND tm.meta_key = 'order')  WHERE tt.taxonomy IN ('faq_category', 'product_type', 'product_visibility', 'product_cat', 'product_tag', 'product_shipping_class', 'tribe_events_cat') AND ( ( icl_t.element_type IN ('tax_faq_category','tax_tribe_events_cat')  AND icl_t.language_code = 'en'  )
                                    OR icl_t.element_type NOT IN ('tax_faq_category','tax_tribe_events_cat') OR icl_t.element_type IS NULL )   GROUP BY t.term_id ORDER BY tm.meta_value+0 ASC, CAST(tm.meta_value AS SIGNED) ASC, t.name ASC  made by do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, BackWPup_Cron::run, BackWPup_Cron::cron_active, BackWPup_Job::start_http, BackWPup_Job->run, BackWPup_JobType_WPEXP->job_run, get_terms, WP_Term_Query->query, WP_Term_Query->get_terms
[10-Aug-2017 16:17:27 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /.../wp-content/plugins/woocommerce/includes/abstracts/abstract-wc-data.php on line 586
[10-Aug-2017 16:17:27 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /.../wp-includes/pluggable.php on line 69

Thank you, I have released a new version which adds a notice and a page that runs the migration to the plugin now.

I have created a gist with a migration script that can be run that will update your database to preserve the “target” values of all fields.

https://gist.github.com/coreyworrell/b3c04e56d665bc40fcf60f2d8e7eef4c

Glad you found it useful!

And it looks like you shouldn’t lose any of your links and link titles when disabling this plugin. But the link target is handled differently, so it appears a migration will have to be done to preserve those.

This plugin saved as either a 0 (self) or 1 (_blank). ACF saves as “” (self) or “_blank”. I will work on a migration script that should safely update those values across the database. Will post back here and update the readme when complete.

Thank you.

Hi @revxx14,

ACF Pro just added built-in support for the link field. That must be why you’re seeing duplicates.

I haven’t had time yet to see how ACF implemented it, but it might require a simple data migration to get your existing links to work with the new link field. Or if you only have a few places, I would make sure they are both set to the same values and then disable and delete this plugin.