NO BUG: Login issue with Form Element in Beta 2.1

Bugs
1

Browser: Chrome 141.0.7390.55
OS: Windows

Hi team,

I have created a login form using Bricks form on all my websites. But on the Beta 2.1 test site, which I tried to login for the first time today, the login does not happen at all and the form stays in the loading state. But other websites have no problem. Could this be related to version 2.1? Or maybe it’s related to the server?

There are no errors in the browser console. I even tried logging in on my mobile phone, but nothing happens.

2

Hi @HOSEIN,

this is weird. Can you replicate you setup on some other server as well? Maybe on try.bricksbuilder.io?

What happens if you downgrade to 2.0.2 version?

I’m also using a custom form for login in my local installation, but no problems on my end.

Please let me know,

thanks.
Matej

1 Like
3

Hi Matej,

I went back to 2.0.2 and the problem was solved. I went back to 2.1 and it’s fine now. I’m not sure what happened. I’ll update here if I find anything.

Thank you

4

Hi @HOSEIN,

thank you for your update. Maybe it was some kind of caching, or who knows what. Please let me know if it happens again and if you can replicate it.

Thank you,
Matej

1 Like
5

Hi Matej,

I was finally able to somehow reproduce this problem. As you guessed, it’s a caching issue and it happens in a specific sequence as you can see in the video below (Sorry the video is a bit long :slightly_smiling_face:). I’m using the wp fast cache plugin.

6

I see. So, if you disable the caching plugin, the issue is gone?
Can you replicate the same with the default login form?

I think in this case, it might be best to write to the WP Fast Cache plugin devs, as they may have a clue why this is happening and what is WP Fast Cache plugin doing behind the scene.

Best regards,
Matej

7

Hi Matej,

if you disable the caching plugin, the issue is gone?

Yes

Can you replicate the same with the default login form?

No, there is no problem with the default login form, because by default, caching is disabled for it.

I think in this case, it might be best to write to the WP Fast Cache plugin devs, as they may have a clue why this is happening and what is WP Fast Cache plugin doing behind the scene.

Sure, thank you Matej. but I had a question before. If Bricks disables caching for the login page by default, won’t the problem be solved? Because wp fast cache can’t recognize what a custom login page is. Am I right?

On the other hand, the cache problem also exists for Bricks Maintenance mode. Because after disabling Maintenance mode, Maintenance mode will remain until the cache is cleared. Although this is not a serious issue. We can clear the cache to solve the problem. But it is something that exists.

Thanks again

8

HI @HOSEIN,

In this case, it’s probably best to disable caching for that specific page manually. I suppose the caching plugin has that option, right?

It probably doesn’t recognize it, but there is most likely a way to prevent some pages from being cached. I don’t think Bricks should do anything automatically in this regard, as different users might have different use cases.

Same as above, actually. If you disable maintenance mode, then you should also clear the cache, and it should work. The maintenance mode page should/could be cached anyway.

Overall, I don’t think Bricks should clear the cache of other plugins in any way.

Best regards,
Matej

1 Like
9

Hi @Matej,

alright, Thank you

1 Like