[#34510] - [4.0] Pre-update check "More Detail" and "Less Detail" toggles of the PHP checks are broken.
- Closed
- 14 Jun 2021
- Medium
- Build: staging
- # 34510
Steps to reproduce the issue
On a current 4.0-dev branch which includes the latest commits from stuff having been merged up from 3.10-dev today, make a new installation if you haven't done one yet.
Then go to the Joomla Update Component's options and set the update channel to the custom URL of the nightlies so that the pre-update checker is shown after saving.
Now toggle a few times one of the "More Detail" and "Less Detail" links in the legends of the 2 PHP checks "Required PHP & Database Settings" and "Recommended PHP Settings" at the top.
Important: Click on the arrow symbol for toggling, not on the "More Detail" or "Less Detail" texts.
Expected result
The toggle just changes the text and the arrow icon.
Actual result
The link text is added again and again with each toggle:
System information (as much as possible)
Current 4.0-dev branch from today, June 14 2021.
Additional comments
Might be something to be fixed in the JS of the Joomla Update Component.
joomla-cms-bot
- | Labels |
Added:
?
|
||
probably after the recent merge from @wilsonge
@brianteeman Remove the "probably" ;-)
Strange: Now after having been logged out for a while, it works, and I can't reproduce this issue here.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-06-14 11:01:41 |
| Closed_By | ⇒ | richard67 |
I've just tried again with a fresh and clean 4.0-dev and still can't reproduce it, so I guess it was some kind of caching issue.
I use nightly build and don't see the issue, too. So we are fine.
To reproduce it, click on the arrow and not the text.
| Status | Closed | ⇒ | New |
| Closed_Date | 2021-06-14 11:01:41 | ⇒ | |
| Closed_By | richard67 | ⇒ |
| Title |
|
||||||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-06-14 16:47:12 |
| Closed_By | ⇒ | joomdonation |
it is a change in the markup that is impacting on the js. probably after the recent merge from @wilsonge