? ? Success

User tests: Successful: Unsuccessful:

avatar richard67
richard67
24 Jun 2017

Pull Request for no issue.

Summary of Changes

This Pull Request (PR) improves the already merged PR #16577 as discussed there with @rdeutz .

  1. Delete the obsolete menu types and not rename them to ".._to_be_deleted".
  2. On renaming the "menu" menu type, use a new name which is more likely not already being used by a user-defined menu type. The new name is "main_is_reserved_133C585", with "133C585" being the hex value of "20170117", which is the date part of the schema update scripts' names. This should be crazy enough for not being used yet.

Testing Instructions

Code review.

Expected result

New name of menu type "main" is "main_is_reserved_133C585".

Obsolete menu type records "main" or "menu" for admin menu are deleted.

Actual result

New name of menu type "main" is "main_is_reserved".

Obsolete menu type records "main" or "menu" for admin menu are renamed to "..._to_be_deleted".

Documentation Changes Required

None.

avatar richard67 richard67 - open - 24 Jun 2017
avatar richard67 richard67 - change - 24 Jun 2017
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 24 Jun 2017
Category SQL Administration com_admin Postgresql MS SQL
avatar richard67
richard67 - comment - 24 Jun 2017

@rdeutz I did it now in a static way and not using the count as I discussed with you, because also using the count is not safe e.g. if someone has crazy menu type names "main_is_reserved_" with numbers at the end (which would be close to sabotage from my point of view). I think now the new name is strange enough for not being used yet.

avatar richard67 richard67 - change - 24 Jun 2017
The description was changed
avatar richard67 richard67 - edited - 24 Jun 2017
avatar richard67 richard67 - change - 24 Jun 2017
Labels Added: ?
avatar richard67
richard67 - comment - 25 Jun 2017

@rdeutz Assign to you?

avatar rdeutz rdeutz - assigned - 25 Jun 17
avatar richard67
richard67 - comment - 25 Jun 2017

@alikon @Quy In the mood for an easy test by review?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/16852.

avatar richard67
richard67 - comment - 28 Jun 2017

@rdeutz I noticed that this PR did not make it into RC2. Does it really need to be tested, and if so, is it enough to do code review? It contains the changes we discussed with PR #16577 , and if it will not go into 3.7.3 it will not make much sense or it has to be added a new schema update for update from 3.7.3 to 3.7.4 then. After our discussion in PR #16577 I thought it will be sufficient if you review it.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/16852.

avatar rdeutz
rdeutz - comment - 28 Jun 2017

My fault, sorry, going to merge it into the stable release next week

avatar rdeutz rdeutz - change - 28 Jun 2017
Milestone Added:
avatar richard67
richard67 - comment - 28 Jun 2017

Ok, thanks. Let me know if something is missing, e.g. if you want it to be tested.

avatar rdeutz rdeutz - change - 28 Jun 2017
Status Pending Ready to Commit
avatar joomla-cms-bot joomla-cms-bot - change - 28 Jun 2017
Milestone Removed:
avatar rdeutz
rdeutz - comment - 28 Jun 2017

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/16852.

avatar infograf768 infograf768 - change - 29 Jun 2017
Milestone Added:
avatar rdeutz rdeutz - change - 30 Jun 2017
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2017-06-30 05:28:13
Closed_By rdeutz
avatar rdeutz rdeutz - close - 30 Jun 2017
avatar rdeutz rdeutz - merge - 30 Jun 2017

Add a Comment

Login with GitHub to post a comment