Posted: July 20, 2017 at 4:00 am
I am perfectly aware that Polylang is NOT supported.
Having said that I did have some major breakthroughs in integrating it none the less and was humbly hoping for some help from your side.
I altered the po/mo paths in plugins so I could use loco translate easily.
Now here is where I got stuck:
1. I use the calendar plugin for visitors to pick their date and time. They click the [ESPRESSO_CART_LINK] link in the tooltip and get to their cart. – WORKS WITH POLYLANG (and some jQuery)
HOWEVER – when I change the subdomain back to the original, the payment process works.
I am quite sure I am missing something in the logic behind passing the params for the attendees.
Also! Would it not solve most of my Polylang related issues if you allowed for more than one page to have the [ESPRESSO_EVENTS] shortcode, or if the stored?
I assume the following combination would work for:
Can you help me?
With regards to EE3 allowing more than one page to have the
What I can suggest instead is work with EE4 to add this. The reason is because EE3 development is done, it’s only being supported for those that can’t use EE4, and only getting security fixes and minor updates that relate to keeping the payment gateways up to date. The other reason is if you come across some code within EE4 where you can use a new filter hook or a new action to help integrate your Polylang solution, you can submit a pull request on Github and the developer team will work with you to get your pull request merged into core.
First of all thank you very much for taking the time to respond. I specifically chose EE3 for its recurring events capability, so there is no way (for now) to switch to EE4 for us.
Could you point me to the right file which POSTs the attendee information? I could then try and send the attendee information to the right place.
Would it be possible to use posts instead of pages for the required shortcodes, to keep the id consistent? That way I could at least embed the post instead of using a page, so at least the menu would stay the required language.
I will investigate further. I am sure there is a clever way to keep the language consistent in EE and keep my multilingual wordpress installation running.
That’s not remotely possible.
Just a follow up.
I did eventually manage to implement EE3 in conjunction with PolyLang.
It is a rather “dirty” solution, but it works very well.
1. I am using https://github.com/grappler/polylang-slug plugin to allow for the same slug for two or more pages having the required EE3 shortcodes.
I still think that simply using point 1 (polylang-slug) while keeping EE3 links non absolute (without the domain), would make Polylang work nicely with EE3.
It works flawlessly for me at least 🙂 .
If someone needs more details let me know.
The support post ‘Polylang integration custom built’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.