Compatibility with Polylang and ACF

I use e2pdf on a multilingual site in combination with Polylang and Advanced Custom Fields.

Until now, a field group had to be created in ACF for each language and assigned to that language. The fields in the group could have the same names, e.g., myfield. Now, after updating to Polylang 3.7, two different field groups are no longer necessary, only one. The translations of, for example, selection field values are now handled in Polylang in a string translation.

I have myfield, which has the value “Apfel” (apple), and I translated this to “Apple” in Polylang.

Unfortunately, this translation is not recognized by e2pdf. Is this something you can adjust in your plugin, or what can I tell Polylang to make their plugin compatible with yours?

Thank you very much for your help.

https://polylang.pro/documentation/support/guides/working-with-acf-pro/

Hello,

Unfortunately, this is a task that we need to review. We'll do the review next week and let you know. It’s probably necessary to add a compatibility fix on our side.

---

We would really appreciate your feedback at WordPress.org!

Okay great, thank you for your answer. Will you get me in the loop here?

Yes, we will update this thread so you will receive a notification as soon as there are any updates on the issue.

---

We would really appreciate your feedback at WordPress.org!

Hello,

Our team did a quick review of the issue, and it has been confirmed. The update with a fix will likely be available by the end of next week. We will notify you as soon as it's available so you can update.

---

We would really appreciate your feedback at WordPress.org!

Hello,

Thank you for looking into this so quickly.
That sounds wonderful, thank you. Will the shortcodes in the templates continue to work, or should they be adjusted after the update?

Hello,

Yes, the shortcodes in the templates will continue to work as usual. We will let you know if any changes are required after the update is released.

---

We would really appreciate your feedback at WordPress.org!

Hello,

We've just released an update to the latest RC version 1.30.04, which should resolve the issue. Please follow the steps here to update the plugin to the latest RC version: https://e2pdf.com/docs/install#rc-version.

After updating, make sure that either "Partial" or "Full" translation is enabled under "E2Pdf" → "Settings" → "Translation".

Please let us know if you encounter any issues.

---

We would really appreciate your feedback at WordPress.org!

Hello,

Thank you for that really quick fix. I was able to install the RV version and got everything working. I did not encounter any issues or bugs.
Just to clarify: what is the difference between partial and full translation?

Thank you very much for that great support.

Thank you for the feedback. We are glad to hear that the issue has been resolved.

Regarding the full translation: once it is set and the E2Pdf Template is saved (or re-saved), you will be able to translate the strings used in the E2Pdf Template via Polylang (Languages → Translations).

Therefore, if you are not using a pre-uploaded PDF, it is possible to create a multilingual PDF using a single E2Pdf Template.

P.S. Please keep in mind that this functionality is still in beta, so some bugs/changes may occur.

---

We would really appreciate your feedback at WordPress.org!

Wow that sounds really great and makes using e2pdf on multilingual websites much easier. I will try that as soon as the feature is fully released.