Affects Version/s: 7.2.X, 7.3.X, Master
Fix Version/s: None
Sprint:Upgrade|23.11-7.12|Bravas, Upgrade|14.12-28.12|Callos, Upgrade|4.1-18.1|CarneEnSarsa, Upgrade|1.18-2.1|CazónEnAdobo, Upgrade|2.1-2.15|Ensaladilla, Upgrade|2.17-3.3|Espeto, Upgrade|3.3-3.17|Gallinejas, Upgrade|3.17-3.31|Gazpacho
Anytime we add a new layout friendly URL keyworks we need to warn users about the need of modifying the layout which is using that new value.
Steps to reproduce:
- Startup 6.2
- Create a site page with /a as friendly url
- Upgrade to Master/7.3/7.2 and verify that everything went well
- Try to access that site
The upgrade log does not show any warning about the use of /a as friendlyURL and you can't access to that site page
The upgrade log shows a warning saying that you need to modify the friendlyURL because right now is a reserved keyword. You can't access to the site page anyways.
An option should be to create a new method in the VerifyProperties class which check if layouts exist with the new friendly URL keyword. We have to search by group and private layout since that's the unique index we need to use:
create unique index IX_B556968F on Layout (groupId, privateLayout, friendlyURL[$COLUMN_LENGTH:255$], ctCollectionId);
Apart from this, we can create a breaking change entry for the new reserved URLs (/a for example), a SF rule to require that would be helpful too.