mathieuhays

This plugin duplicates menu items within a menu, not the menu itself.

Hi amiens80,

Regarding the position of the duplicates, the same could be argued for the other way round. If I make the duplicates fall under the same parent some people are going to complain it’s buried somewhere in their large menu and would rather have it at the bottom.

I’ll look into maybe adding an option page where that behaviour can be toggled.

Regarding the “copy-of” bit, I don’t think it’s a good solution. It would mean you would have to edit all the menu items to remove said “copy-of”. I’ll play around with potentially highlighting the duplicated items in some way, probably a change of border color or similar.

Avada is a paid third party theme. I don’t have access to it so I can’t support it. Even if I had access to it I can’t promise I could make it work as it’s dependent on how Avada developers implemented their custom options on menu items.

Regards,
Mathieu

It’s working fine for me. It’s possible it’s conflicting with another plugin you have installed.

Do you mind sending me the list of plugins you’re using so I can check if that’s something I can fix on my side?

Thanks

“Description” field issue now fixed in version 1.0.1 ??

Thanks for reporting the incompatibility, I’ll have a look to see if that’s something I can fix my end.

PS: sorry for the delay, didn’t get a notification for the new thread

Hi,

Sorry for the delay. I didn’t get a notification for the new threads here for some reason.

It’s now fixed.

It was due to a bug in the WordPress Core that only affects our use-case so I’ve implemented a workaround.

I’ve done a quick test in WordPress 5.6. It seems to work fine. I’ve updated the “Tested up to” tag which should stop Wordfence from flagging the plugin as vulnerable. Please let me know if the plugin is still listed as vulnerable during your next scan.

Thanks for letting me know. This has been on my scope for a bit. I’ll do my best to push an update in a week or two.

I’m having the same issue. site_url needs to be replaced by home_url as mentioned by @htmltiger.

Thanks for reporting this @marg9, I’ll look into it.

I think someone already reported issues with UTF-8 encoding. I never managed to reproduce it though. My main language does have special characters too so I always made sure to use UTF-8 but I think there might be a use-case where it breaks.

Hi @pixelbrad,

Thanks for reporting it!

Storing the table name is definitely something I want to go away from but I’m a bit stuck due to backward-compatiblity as you mentioned.

I’ll probably do an update that will migrate the table of the oldest installs.
This will only affect people that installed the plugin when it was version 1.0.0 so probably not that many people.

Hi mickey981,

The plugin uses the languages set in the WordPress admin when a translation is available. If a translation is not available the plugin defaults to English.

As of today the available languages are:
– English
– French
– German
– Spanish
– Serbo-Croatian
– Dutch

If a WordPress user sets a different language for their own profile it should pick it up as well but I haven’t tested it yet.

There’s no multi-language support at the moment.

Hope that helps

• This reply was modified 6 years, 9 months ago by mathieuhays.

Perfect thanks!

Sorry I missed that.

I’ve had the same issue and find out it was because the author moved to the REST API. The submit request was sent without the rest’s nonce so the WordPress REST API downgraded the request to a logged-out user for security purposes.

The author has to add the nonce to the submit request to fix this.
I have specified which part of the plugin code has to be changed to fix this issue there: https://www.ads-software.com/support/topic/fix-user-info-access-after-submission/

Please note that the code provided there is not fully tested so use it at your own risk (just grab a fresh copy of the plugin on www.ads-software.com if something breaks).
and obviously editing any plugin’s file is NOT recommended.

Hi tristandenyer,

Thanks for providing more details.

I managed to replicate the “content field missing” bug. I’ll publish an update to fix this tonight.

I still haven’t managed to replicate your initial issue though. Are you still experimenting this issue? If that’s the case, please can you send me detailed steps to reproduce ?

Can you replicate this issue accross different browsers?

Is it still an issue after reloading the page?

Sorry for all the questions but that’s the only way I can try to pinpoint what’s going wrong.

Thanks