WPML breaks AAM Advanced Access Manager Settings

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Compatibility

This topic contains 9 replies, has 2 voices.

Last updated by Bruno Kos 1 year, 9 months ago.

Assisted by: Bruno Kos.

Author	Posts
July 18, 2023 at 3:27 pm #14060597
andiG	WPML is causing issues with Advanced Access Manager AAM Plugin. The setup I have is a multilingual site (content default: German) with French and Italian translations. Overall summary: when WPML is active and a new post/page is saved, it affects AAM Plugin Processing. The following case is reproducible! I recorded 2 videos to show it to: hidden link 0 to 00:47, we check settings in AAM for a post, that was created before WPML was activated and setup (correct settings are shown) After 00:47, a new post is created and after we bring up AAM GUI to check the settings, but settings are not restricted/applied. If you open up the link to the post, it is shown to all users, but it should show the “Access denied” page. If I deactivate WPML, and do the same process again, the settings are applied correctly and the direct access shows “Access denied”! hidden link It affects not only Posts, Pages with categories are affected too. How can this issue be fixed, so that WPML is working correctly together with AAM? Best, Andi
July 19, 2023 at 8:04 am #14063065
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	Hi, Thank you for contacting WPML support! Advanced Access Manager AAM does not seem to be officially compatible with WPML and we have very few cases with the plugin. That being said, can you install it here: hidden link and then reproduce the issue and show me where can I see it? I will then check with our compatibility team. However note that we may not be able to provide either a workaround or solution for this, as it may require input and cooperation from their developers, so can you ask them if they are interested into joining our https://wpml.org/documentation/support/go-global-program/ and tell us what have they replied? Regards, Bruno Kos
July 19, 2023 at 9:28 am #14064059
andiG	Hello Bruno Thanks for your reply. I installed it on the instance, but surprisingly it behaves differently than on our installation. I will have to investigate a bit more and I will get back to you asap with more details. Best, Andi
July 19, 2023 at 12:06 pm #14065901
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	I see - let us know if you need further assistance, perhaps it is just a matter of some setting, something you can compare between our sandbox and your installation.
July 19, 2023 at 1:44 pm #14066805
andiG	Hello Bruno I found the cause of the issue. WPML adds taxonomies for "Translation priorities" and this affects the access right system of AAM. I saw another WPML support post, where a supporter mentioned to just delete the entries on the admin screen (Optional, etc.). /wp-admin/edit-tags.php?taxonomy=translation_priority But aren't they created again on a plugin update? Is there a hook, to remove this setting completely? And is there no issue elsewhere within WPML when these 3 entries are deleted? Thanks for more details! Best, Andi
July 20, 2023 at 8:05 am #14069839
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	It is not possible to remove taxonomies from here, these are registered here as they are registered anywhere in WordPress. I'm not aware of any hook that would allow this functionality to be altered. But instead of trying to change core files, we could submit this case to our compatibility team so they could find a way to get this working with WPML, even though this is not always possible and sometimes requires input from plug-in developers. If interested in such scenario, can you reproduce the issue in the sandbox as well and show me where can I see it?
July 20, 2023 at 12:48 pm #14072345
andiG	Hello Bruno I just did a quick test with this code add_action( 'init', 'wpname_unregister_taxonomy' ); function wpname_unregister_taxonomy() { unregister_taxonomy( 'translation_priority'); } This works and no errors are showing up in the log. So the question here is, if you could think of possible areas that might have issues with this unregistered taxonomy? I do belive, that many webmasters with multilingual sites do not really depend on your "translation priority" flag. Non of our customers (and many use multi language websites) do not care about it at all. To have an option within WPML to disable it and remove it from the backend would be a nice thing to see!
July 20, 2023 at 1:57 pm #14073035
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	Strictly speaking, without testing this in various scenarios, I cannot give a definite answer whether it would have any repercussions towards translations. However I don't think it would matter so I think you should be safe using it. You do have a point here, in my experience which counts in years and thousands of cases, I do not recall that anyone ever asked about that translation priority feature or had issues with it.
July 20, 2023 at 2:20 pm #14073343
andiG	Hello Bruno So, will WPML think about making the interface cleaner and implement an option for those rare peoples, that really want to have this option displayed and remove it from the GUI by default? Would love to see this in an update! Thanks for now!
July 20, 2023 at 2:40 pm #14073513
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	I created a feature request in our system, perhaps it gets traction. There is also another option instead of using your filter - you can disable translation priorities taxonomy translation abilities here. However I'm not sure if this will work because it would only make it non-translatable, the same action would not remove already existing translations for it, neither would unregister taxonomy as your hook does it.