samuraiprojects

The workaround fixed the issue for me. My login widget was stuck to the left side of the page, and is now returned back to the center.

Great plugin.

I agree the menu is not ideal, and has to be closed using only the open/close button, rather than clicking anywhere away from it.

I submitted a request on the Github for the ability to place each accessibility option with a shortcode, as its own toggle button, wherever the designer pleases. This would make the option(s) one-click/tap and allow them to be placed in a dedicated area.

I do wish the developer of this was more active, it’s a fantastic plugin.

• This reply was modified 3 years, 4 months ago by samuraiprojects.

Hi, thank you for the reply.

I have performed a conflict test, and have isolated this behaviour to be caused by:

– Master Addons for Elementor plugin

When disabling this plugin, the UM menu returns to a single instance, and within that single instance, there is 1 occurrence of ‘Settings’.

When re-enabling the plugin, it inserts a menu directly underneath Ultimate Member’s positioning, and a second Ultimate Member menu appears overtop of it. It’s possible the plugin causes whatever is above it, to exhibit this odd visual behaviour. Aside from the visual anomoly, each instance of the UM menus point to the correct places.

I’ll log an issue with the makers of Master Addons for Elementor plugin, to alert them of this issue, which may or may not have any direct relation to UM.

This is resolved. Thanks!

Hi, thanks for the reply. I have performed conflict testing and in short, this was related to the content.

What made this issue more strange is that using the exact same copy-pasted HTML between this form, and another, ahowed that it worked in the other plugin.

Once I switched themes to Twenty Twenty One, the content was replaced with default content. I copy-pasted that after switching the theme back, and the shortcodes were resolved. I’ll take a closer look at the syntax when customizing the form from this point, as I think the issue came down to [] vs {}

This is resolved.

I have done more testing:

– I rolled back UM plugin a couple of times to see no change in behaviour, when going back as far as 2.18

– Better Notifications For WordPress uses its proper notification, with shortcodes INTACT, when using the ‘Send Password Reset’ link, contained in the Users grid. This proves the site is able to construct and send the shortcodes.

However, that exact same email should also be dispatched when someone creates a password reset request, but zero email gets dispatched.

So, at present, the only email that is possible to dispatch, based on the actions of the user requesting it, are if the Password Reset email in UM, is set to enabled.

The exact same email body that successfully sent via the manual ‘Send Password Reset’ link via a totally different plugin, works – while the one sent via UM, just shows shortcodes without having resolved them to anything.

I am unsure what else I can safely provide in a public forum to further define the issue.

It should also be noted that I have 2 ‘Settings’ within each instance of the menu, so there’s a total of 4 of the same menu item. What is this?

See for yourself: https://imgur.com/TNNEqKB

Update: I checked today and notice the following:

– The Inner Section names that were previously reset to their default names, have returned.
– I made an edit to a template and the edit saved and was immediately available at the front-end.

I need to do more testing to ensure this is consistent, and will report back if there are further issues. The odd thing is that this wasn’t resolved when I updated to 3.2.2, but has begun working after some time. In any case it looks like I am able to once again move forward. Thank you to the Elementor team.

Updating to 3.2.2 has not resolved any of the issues I refer to above, that started in 3.2.1

@seanalvarenga Well done! This works like a charm, thank you so much.

It’s also possible this is not from iThemes. I am also following up with the developers of the other plugin, to understand where this verbiage even comes from. The URL contains an ithemes link so if you can confirm there’s no default email body/template with the above, I’d consider this not an iThemes issue.

Confirmed this isn’t related to iThemes. Sorry bout that.

• This reply was modified 3 years, 9 months ago by samuraiprojects.

Just to tag a potential easy development workaround that could allow users to get around this more easily:

If it is not possible to change the plugin to allow High Contrast and/or Negative Contrast to be disabled:

– Give the list items their own individual class names, so they can be styled/hidden. As of now they take on the Body text and may not necessarily fit within a site’s nav style

I installed Elementor 3.0.5 and the issue is resolved – I am now able to load Revisions, and the display layer successfully finishes drawing.

While the issue occurred, the page only partially loaded, and appeared to lock up / make heavy use of the CPU while attempting to draw the rest of the object, and would never finish.

I did not make any configuration changes on any machine or browser I tested this with. I noted the performance of the live website remained the same, so I don’t believe it was ever related to my hosting provider.

In any event, this issue is resolved. Many thanks!

My screen won’t update when I make a change, but it’s updating in the background. I just deleted an inner section by accident and saved without realizing it, because nothing changed on the screen. Now I’m sitting in the Revisions tab watching the loading icon spin forever, because it can’t update the screen. I see no way out of this without an update. Progress halted.

Uncaught TypeError: Cannot read property ‘querySelector’ of null
at cbpHorizontalSlideOutMenu._init

I still get this error as well. Unusure why it’s marked resolved, unless there is a statement that this may also happen for other reasons?

I’m just tossing me two cents in to:

– add to the list of users who would kindly request you STOP using !important in your CSS!

– and to thank Norm1 for the dequeue solution, which will come in handy