[#30383] - [4.0] Move admin module "mod_version" to position "status" on update from 3.10
- Fixed in Code Base
- 19 Aug 2020
- Medium
- Build: 4.0-dev
- # 30383
- Diff
- richard67:4.0-dev-move-admin-mod-version-on-update
User tests: Successful: Unsuccessful:
Pull Request for Issue #30381 .
Summary of Changes
This Pull Request (PR) modifies the update SQL script for each database type which moves to the new templates when updating from 3.10 to 4 so that the Joomla Version backend module "mod_version" is moved to the "status" position of Atum, where it is located when making a new installation of J4.
Testing Instructions
Test 1: Reproduce the issue
-
Update a recent 3.10-dev branch or 3.10 nightly build to latest 4.0 nightly by using either the custom update URL or the downloadable update package from https://developer.joomla.org/nightly-builds.html.
-
After successful update and login to backend, check if you can find the icon marked with a red ellipse in the following screenshot.
Result: The icon can't be found anywhere in the backend.
Test 2: Test the patch of this PR
Same as test 1, but this time don't use the regular custom update URL or the downloadable update package for J4 nightlies.
Use the custom URL or package which have been built for this PR.
You can find a page with a link to an installation package for download as shown in the following screenshot with the green ellipse (if necessary expand the "Show all checks" to see that):
Result: The icon is shown at the right place as shown in the screenshot of Test 1.
Actual result BEFORE applying this Pull Request
No version is displayed.
Expected result AFTER applying this Pull Request
Version should be displayed in the upper right "status" position in the backend.
Documentation Changes Required
None.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | SQL Administration com_admin Postgresql |
| Labels |
Added:
?
|
||
I've reverted the new update sql scripts and have put the update statement into the same update script which changes the templates, so it only runs when updating a 3.10.
Looks ok on review
I have tested this item
Thank you!
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/30383.
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/30383.
| Status | Pending | ⇒ | Ready to Commit |
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/30383.
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-08-19 07:33:38 |
| Closed_By | ⇒ | infograf768 | |
| Labels |
Added:
?
|
||
Tks.
Hmm, wait, maybe I should not make new scripts which would also run when updating a previous 4 beta version but put the statements into the oldest update SQL so it runs only when updating a 3.10?