? ? Pending

User tests: Successful: Unsuccessful:

avatar brianteeman
brianteeman
9 Nov 2020

This PR changes the default value for this setting that is found in com_content, com_contact and com_newsfeeds from the old showing of IDs in the url to the much improved new way of not displaying them.

This is only for new installs. It will not change an updated site.

avatar brianteeman brianteeman - open - 9 Nov 2020
avatar brianteeman brianteeman - change - 9 Nov 2020
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 9 Nov 2020
Category Administration com_contact com_content com_newsfeeds SQL Installation Postgresql
avatar ceford
ceford - comment - 11 Nov 2020

I have not tested with a new install but I did look at what happens when the "Remove IDs from URLs" is changed manually - looks OK. And I changed the wording of the associated Help screens. It was:

"URL Routing". (Legacy/Modern) Modern routing enables advanced features but may change your URLs. Legacy routing ensures full comptability for existing sites. This is configured per component.

and is now:

Remove IDs from URLs. (Yes or No) Whether or not to show the database id of a newsfeed in a link.

For newsfeed read article or contact or newsfeed. Is that correct?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/31370.
avatar brianteeman
brianteeman - comment - 11 Nov 2020

@ceford Nothing to do with this PR but the help screen was obviusly out of date as the text you quote refers to an option in Joomla 3 that was removed from joomla4

avatar adj9
adj9 - comment - 14 Nov 2020

I did a test with and without PR. The ID of the article and the contact, with the active PR, remains at the end of the URL and is what I see in the content area in the BackEnd.
Example

  • URL: ~index.php/contact-uncategory/1-c
  • BackEnd Screan:
    Schermata 2020-11-14 alle 17 52 16

Which ID are you talking about?

avatar brianteeman
brianteeman - comment - 15 Nov 2020

Its the id in the URL

avatar Bakual
Bakual - comment - 15 Nov 2020

@brianteeman If you change the default value in the XML, you also have to change the default values in the PHP files where the param is used. Those values always need to match. With your current code, the behavior would switch the moment the settings are saved, if there was no stored value for sef_ids before.

If you want to change it only for new installations, then it is sufficient to change only the installation SQL files. You have to leave the XML and PHP the way they are.

avatar brianteeman
brianteeman - comment - 15 Nov 2020

the behavior would switch the moment the settings are saved, if there was no stored value for sef_ids before.

Good spot - thanks

So just t confirm. By only changing the sql will mean - new installs default to "no id"
existing installs are not changed on update AND existing installs will not be changed when an unrelated setting is changed.

avatar brianteeman brianteeman - change - 15 Nov 2020
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - change - 15 Nov 2020
Category Administration com_contact com_content com_newsfeeds SQL Installation Postgresql SQL Installation Postgresql
avatar Bakual
Bakual - comment - 16 Nov 2020

Looks fine now.

avatar Quy Quy - test_item - 4 Dec 2020 - Tested successfully
avatar Quy
Quy - comment - 4 Dec 2020

I have tested this item successfully on 93fd855


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

avatar gostn gostn - test_item - 4 Dec 2020 - Tested successfully
avatar gostn
gostn - comment - 4 Dec 2020

I have tested this item successfully on 93fd855


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

avatar Quy Quy - change - 4 Dec 2020
Status Pending Ready to Commit
avatar Quy
Quy - comment - 4 Dec 2020

RTC


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

avatar brianteeman
brianteeman - comment - 16 Dec 2020

Any reason why this RTC pr has not been merged?

avatar wilsonge wilsonge - change - 18 Dec 2020
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2020-12-18 02:59:44
Closed_By wilsonge
Labels Added: ?
avatar wilsonge wilsonge - close - 18 Dec 2020
avatar wilsonge wilsonge - merge - 18 Dec 2020
avatar wilsonge
wilsonge - comment - 18 Dec 2020

Just had missed it in the list of things. LGTM!

avatar brianteeman
brianteeman - comment - 18 Dec 2020

thx

Add a Comment

Login with GitHub to post a comment