It shouldn't allow going further from the "give admin details" when the password doesn't meet validation rules.
Goes through, blocks later, without possibility to come back.
Normal environment, Joomla 5 installed with 5.2.x or something was allright. Don't remember.
Might be 5.3.3 characteristic.
| Labels |
Added:
No Code Attached Yet
|
||
If I enter a password for the admin user that is too short I immediately get a message that it is too short etc
But yes I can ignore that and proceed to the database section and then you do get stuck at the end. Its a single page and its a known issue that you cannot go back at the end - you have to restart
Please can you post some screenshots as I am unable to replicate the grey message that is hard to read that you describe.
@brianteeman I cannot find the issue. But recently thought that any error should go back to top. Was there a reason why we don't do that?
@chmst there are other issues about this. I think one was from @HLeithner
If you ignore the warning about a weak password and continue the rest of the installation steps then you end up with this page
Thank you, was not aware of this us case.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-09-26 07:39:46 |
| Closed_By | ⇒ | alikon |
It gets blocked with a screen without possibility to come back saying the admin password doesn't meet validation.
@Milo-W You can't use the back button (arrow left) of your browser to go back?
Nope, it goes all the way to the previous page, not even this exact installation process.
Besides, good UX says to validate "here & now", not two screens later...
@chmst there are other issues about this. I think one was from @HLeithner If you ignore the warning about a weak password and continue the rest of the installation steps then you end up with this page
![]()
Yes, part of my problem here is this page here. And you go back - it goes back not even to the beginning of the process but it goes back to the previous page you had visited...
BTW it's the same in Joomla 6...
@Milo-W If the mentioned pull request for 5.4-dev has received 2 successful human tests, it will be set to ready to commit (RTC) and then be merged soon into 6.5-dev. This then will be merged up into 6.0-dev so the issue will be fixed for 6.x, too.
So it does not need to make a new issue for 6.0, it just needs to test that PR to come forward.
You mean 5.5?
OK because I tested 5.4 and it didn't work better.
OK, downloading 5.4-dev.
5.4. There will never be a 5.5. And you have to test the pull request which I have mentioned.
Oh, 5.4-dev needs local environment... I'm not that far with all that : /
Can test 5.4 alfa/beta though...
I hope the change is not only about the characters check but also earlier validation...
5.4 Alpha or beta will not contain the fix from the PR. We have already released 5.4.0 stable. You can test the PR as described here: https://docs.joomla.org/Testing_Joomla!_patches/en#Prebuild_packages
5.4 Alpha or beta will not contain the fix from the PR. We have already released 5.4.0 stable. You can test the PR as described here: https://docs.joomla.org/Testing_Joomla!_patches/en#Prebuild_packages
Sorry but I am confused a bit : )
So if there won't be a 5.5, 5.4 is out... what version will this change come with?
I see 6.1 dev - if the error persists in 6.0, should I somehow track the solution in 6.1 too?
I see 6.1 dev - if the error persists in 6.0, should I somehow track the solution in 6.1 too?
@Milo-W I've told you that you shall test PR #46173 . That PR is obviously made for the 5.4-dev branch. If that gets tested and merged in time, the fix will go into 5.4.1 (and also in 6.0.1). If it does not get ready in time, it will go into 5.4.2 and 6.0.2.
I have no idea why you refer to 6.1-dev here.
Because you said:
"So it does not need to make a new issue for 6.0, it just needs to test that PR to come forward."
and I want to make sure it's OK in 6.1 as this issue is still present in 6.0.
Sorry but this is new to me, I don't know what it means to test a PR ; ) it means to make changes in the individual files?
To be honest, #46173 looks like just the characters thing but does it not allow going forward with installation if the password doesn't meet validation rules? Because another problem was you could go forward and then it didn't allow to go further on and yet you couldn't go back. So I see at least 2 mechanics here to be made up for.
@Milo-W You can tests #46173 by downloading pull installation package with applyed pach witch is available on https://artifacts.joomla.org/drone/joomla/joomla-cms/5.4-dev/46173/downloads/88788/. You can also expand "All checks" on GitHub and click on "Download" check.
@Milo-W You can't use the back button (arrow left) of your browser to go back?