addons login no longer works after last update

SAME HERE

Hi @chris297 , @abbigliamentodalavoro ,

You will be glad to know that we have fixed the EA Login Register Form – Security token did not match error in our latest update v.5.4.1

So Please update the latest version of Essential Addons for Elementor v.5.4.1. After that, please regenerate your EA assets from Dashboard > Essential Addons then, switch to the ‘Tools’ tab and hit the ‘Regenerate Assets’ button. Check out this screenshot: https://d.pr/i/iBccDw

Hopefully, it will fix the issue.
Let me know how it goes.
Thank you

@abidhasan112 i followed your steps and cleared the cache, now everything works

It Worked for Me

Hello! I am still having this issue on my side. I cleared the cache and renewed the assets and still users cannot login through the EA login form.

@mahbubshovan
I’ve removed your last reply here, it looks like you are about to ask user to let you log on onto their site.

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.