Addendum: I could no longer understand the error myself.

And I did some testing. This error only occurs if you have activated the additional button "Next" in the profile settings and save with it. With "update and close" it does not occur.

Hi chris,

Not sure what you mean by the 'next' button. Perhaps a screenshot would help.

I am able to reproduce the issue in my local instance when changing the permalink from one to another. Will log this in our tracker.

I am in the profile setting. There I activated the "Next-Button" (picture). In preparation, because I split the registration into "important data" and "unimportant data".

But at the moment I only have one page. Whether I now use "Update and Close" or "Next" to save does not matter. Both buttons have the same function (save).

If I had 2 pages, "Next" would take me to the next page and then safe.

But I repeat. I currently have only one page.

If I now change the perma-profile-link and press "Next", I end up on the error page.

Hey chris,

I do not recall seeing 'Update and Close' and 'Next' options in the frontend profile edit page. This is what you should see currently regardless of the number of steps: https://take.ms/H8Rh6

Hi Raymond,

This setting must be enabled in ES/Settings/User/General settings.

"Profile Edit Behavior" from "default" to "step-by-step".

Hey Chris,

Ah I see what you mean. The fix for the logged issue should cover both profile edit behaviors.

By the way, there is a fix available if you want to give it a try.
JoomlaFolder/components/com_easysocial/controllers/profile.php

Remember to backup the original file beforehand.

Hi Reymond, nice work. But if I try to change the perma-link a few times in a row, I get the following error.

1213
Deadlock found when trying to get lock; try restarting transaction

Supplement: So I changed it 20 times in a row and got this error 2 times. But all further attempts work.

So it seems to work.

Good work Raymond. Thanks

I think this error is related to something else and probably it's coming from your database. Since that is a different issue altogether and if you are still experiencing issues with this, please start a new ticket.