Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Messaging - remove duplicate submenu item #8057

Merged
merged 1 commit into from Nov 4, 2015
Merged

Messaging - remove duplicate submenu item #8057

merged 1 commit into from Nov 4, 2015

Conversation

pe7er
Copy link
Contributor

@pe7er pe7er commented Oct 11, 2015

This PR removes the duplicate menu item in the Messaging submenu.
IMHO offering less (duplicate) options is better for UX.

Testing instructions

Before this PR

Components > Messaging (shows list of private messages) has two submenus:

  • New Private Message (create new private message form)
  • Read Private Messages (shows list of private messages) which is a duplicate of the parent Messaging menu item

messaging-menu-before

Other components, like com_content, do not have such duplicate options.
See Content > Articles (shows list of articles) > has one submenu item Add New Article (create new article form)

messaging-menu-articles-example

After this PR

The administrator menu items are created from records in the database.
The database settings are created upon installation and therefore the testing procedure is a bit different:

  • Install the patch
  • remove configuration.php
  • install Joomla again
  • check the new menu settings:

Components > Messaging now has only one submenu: New Private Message

messaging-menu-after

Note: I have only removed the duplicate menu item in the MySQL files (Joomla core installation and all different sample data files), and in tests/system/webdriver/Pages/System/AdminPage.php and tests/unit/stubs/database/jos_menu.csv.
I have not yet changed it in Postgresql, nor in SQLAzure. I would like to have this PR tested before I'll make the necessary changes in those two databases.

@n9iels
Copy link
Contributor

n9iels commented Oct 11, 2015

For some strange reason, I can not apply this patch via the Joomla! Patch tester. Is this a problem in my test installation? Or are there people with the same problem?


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

@brianteeman
Copy link
Contributor

Quick comment without testing as I'm on a phone.

The 'add new' is usually governed by a setting in the admin menu module
On 11 Oct 2015 7:24 am, "Niels van der Veer" notifications@github.com
wrote:

For some strange reason, I can not apply this patch via the Joomla! Patch

tester. Is this a problem in my test installation?

This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at issues.joomla.org/joomla-cms/8057
http://issues.joomla.org/tracker/joomla-cms/8057.


Reply to this email directly or view it on GitHub
#8057 (comment).

@pe7er
Copy link
Contributor Author

pe7er commented Oct 11, 2015

Did you reinstall Joomla after applying the patch?

The submenus of the components under the Components menu are retrieved from the database. And the database settings are created upon installation. Therefore you'll need to reinstall Joomla with the patched SQL files.

@YouriiM26
Copy link

I can't not apply the patch. I have re-installed the newest joomla-cms-staging on my localhost.

This is the error what I get when I apply the patch:
Error
The patch could not be applied because it conflicts with a previously applied patch: installation/sql/mysql/joomla.sql

Hopefully can you fix this issue.


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

@mbabker
Copy link
Contributor

mbabker commented Oct 12, 2015

That's by design with the patch tester. What that means is that it has found a backup of that file in the administrator/components/com_patchtester/backups folder either from a previous patch or having not fully reverted a patch. When you're using the patch tester, you should ensure that you have reverted all patches before applying a new one, and if you still get this message after that, you need to delete any backups from that folder.

@YouriiM26
Copy link

I have looked in the administrator/components/com_patchtester folder and this folder is empty.


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

@patjun
Copy link

patjun commented Oct 24, 2015

I think the test description is not complete. The patch changes a file in the installation directory. I added the first list item.

@patjun
Copy link

patjun commented Oct 24, 2015

I have tested this item ✅ successfully on 1a41dfb

I tested the patch with the changed test description in my comment. With this description the patch works for me.


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

@matrikular
Copy link
Contributor

I have tested this item ✅ successfully on 1a41dfb

Patch works as described.

Remember to update the IDs and also the lft, rgt values for the other entries in that table for the final version of this PR.


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

@zero-24 zero-24 added this to the Joomla! 3.5.0 milestone Oct 24, 2015
@zero-24
Copy link
Contributor

zero-24 commented Oct 24, 2015

RTC @committer please take care on the comment by @matrikular


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

@joomla-cms-bot joomla-cms-bot added the RTC This Pull Request is Ready To Commit label Oct 24, 2015
@pe7er
Copy link
Contributor Author

pe7er commented Oct 24, 2015

@zero-24 Do you mean me?
Could you recommend a safe & easy method to update the IDs and lft, rgt values for the other entries in those tables?

@roland-d
Copy link
Contributor

roland-d commented Nov 4, 2015

@zero-24 The lft and rgt values do not need to be updated because the entries @pe7er is removing are not in the assets table. Only the main extension com_messages is in there but not the suboptions. The suboptions are only links to the component.

As for updating the ID's, I wouldn't go through the hassle. It would be a major hassle to reclaim number 12.

roland-d added a commit that referenced this pull request Nov 4, 2015
Messaging - remove duplicate submenu item
@roland-d roland-d merged commit 95b419b into joomla:staging Nov 4, 2015
@zero-24 zero-24 removed the RTC This Pull Request is Ready To Commit label Nov 4, 2015
@pe7er pe7er deleted the components-messaging branch November 5, 2015 00:08
zero-24 added a commit that referenced this pull request Nov 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants