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

SQL: Wrong title for Contacts submenu #8212

Merged
merged 7 commits into from Nov 1, 2015

Conversation

infograf768
Copy link
Member

This PR to solve #8200

The submenu title is incorrect in the db, therefore it does not use the right string COM_CONTACT_CONTACTS

Patch and make new installation or run the sql request (change #_ to your db prefix) on an existing site:

REPLACE INTO `#__menu` VALUES
(8, 'menu', 'com_contact_contacts', 'Contacts', '', 'Contacts/Contacts', 'index.php?option=com_contact', 'component', 0, 7, 2, 8, 0, '0000-00-00 00:00:00', 0, 0, 'class:contact', 0, '', 12, 13, 0, '*', 1);

In en-GB, the values of COM_CONTACT and COM_CONTACT_CONTACTS are the same (Contacts) in the en-GB.com_contact.sys.ini language file.
Therefore to test in en-GB, just modify the value of COM_CONTACT_CONTACTS

Result in French:
screen shot 2015-10-30 at 09 24 42

NOTE: I have just updated sql in /administrator/components/com_admin/sql/updates/mysql/3.5.0-2015-10-30.sql
I have not touched at postgres and sqlazure there. To who knows how to, please propose a PR for that.

@mbabker
Copy link
Contributor

mbabker commented Oct 30, 2015

If you're only changing the one field an UPDATE foo SET bar query will be more efficient here. And the same syntax works for the other database types too (they just use different quoting structures).

@infograf768
Copy link
Member Author

@mbabker
Will try

@infograf768
Copy link
Member Author

Thanks @alikon :)

@infograf768
Copy link
Member Author

We need here one more test to RTC.

@peterpeter
Copy link
Contributor

@test
Tested successfuly on a fresh installation. Submenutitle/COM_CONTACT_CONTACTS could be overwritten while the mainmenu stays the same.

@peterpeter
Copy link
Contributor

I have tested this item ✅ successfully on f3795d0

(finally found the 'Test this'-button ;)


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

@infograf768
Copy link
Member Author

RTC as we have 2 good tests


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

@joomla-cms-bot joomla-cms-bot added the RTC This Pull Request is Ready To Commit label Nov 1, 2015
@zero-24 zero-24 added this to the Joomla! 3.5.0 milestone Nov 1, 2015
roland-d added a commit that referenced this pull request Nov 1, 2015
SQL: Wrong title for Contacts submenu
@roland-d roland-d merged commit 757473b into joomla:staging Nov 1, 2015
@joomla-cms-bot joomla-cms-bot removed the RTC This Pull Request is Ready To Commit label Nov 1, 2015
@ratenfanger
Copy link

Just updated a Joomla installation (in a test environment) from 3.4.8 to 3.5 (using MySQL). The title of menu item with ID 8 was changed from "Geschiedenis" to "com_contact_contacts" as stated in this PR.
The changed menu item is shown on the frontend, so it is not the backend menu item which should be updated. I think I got a frontend menu item with ID 8 because I'm running this site since Joomla 1.5. A long time ago I migrated to 2.5 (and updated every release since then).

I think other people with (somehow) non-default menu item IDs may/will have the same problem. My proposal is to only change the title for menu items which matches the follow criteria:
a) only backend menu items (client_id = 1)
b) with title = 'com_contact'
c) in a submenu (level = 2)

For MySQL the following query does the job from phpMyAdmin:
UPDATE jml_menu SET title = 'com_contact_contacts' WHERE client_id = 1 AND level = 2 AND title = 'com_contact'

If you agree I wil be happy to change the queries and submit another PR. I also can help testing for MySQL because I did not upgrade my production installation yet.


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

@brianteeman
Copy link
Contributor

@ratenfanger you are commenting on a pull request that was merged five months ago

@ratenfanger
Copy link

@brianteeman sorry I thought this was the correct place to discuss my findings. Should I create a new issue and mention this PR?

@brianteeman
Copy link
Contributor

brianteeman commented Mar 22, 2016 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants