Bug #93423
closed
wrong https in slug of one page
100%
Description
The website example.com runs as http . The slugs of all pages show the correct http://example.com at the beginning text output. However one page shows a wrong protocoll https.
This error can also be seen in the frontend. Only one page has a link into https, the others to the http protocol.
page.10.marks.MAINNAV = HMENU
page.10.marks.MAINNAV {
special = list
special.value = 10,11,22
excludeUidList =
1 = TMENU
1 {
#noBlur = 1
wrap = <ul> | </ul>
NO = 1
NO.ATagTitle.field = description // title
NO.allWrap = <li> | </li>
NO.ATagBeforeWrap = 1
NO.stdWrap.htmlSpecialChars = 1
}
}config.yaml:
base: 'http://example.com/'
rootPageId: 2
websiteTitle: 'Demo Example'I find no possibility to change the slug of the page "Home id=10" from https into http.
The TYPO3 page tree is like this:
Demo id=2
several Sysfolders ....
Home id=10
Dienste id=11Files
Updated by Franz Holzinger about 3 years ago
- File pages-https-10.csv pages-https-10.csv added
Updated by Georg Ringer about 3 years ago
- Status changed from New to Needs Feedback
thanks for creating this issue!
this looks like https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/8.6/Breaking-79302-MovedPagesurlSchemeToCompatibility7Extension.html?highlight=protocol but this is gone since 8.6 or https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.0/Breaking-71306-DroppedProtocolFieldFromPageTypeLinkToExternalURL.html?highlight=protocol
I don't have any clue how this is possible, so can you compare this page with another one in e.g. phpmyadmin to find a difference?
Updated by Franz Holzinger about 3 years ago
All the pages work fine with http under slug, only page 10 (renamed into Falsch) provides only https.
No field url_scheme is available for pages. No compatibility7 has been installed or activated.
For finding of this error, all local extensions have been deactivated.
The difference between the old wrong "home" page (now called "falsch" and the newly entered "home" page (on the same positiion in the page tree where the other page has been before).
uid title crdate keywords description abstract tsconfig_includes rowDescription slug 10 Falsch 1389728335 NULL NULL NULL NULL NULL /falsch 35 Home 1612454062 /home
I have compared it with another page.
The only difference are these three columns:
keywords description abstract
Updated by Georg Ringer about 3 years ago
sorry absolutly got no clue what could be wrong here and also never saw this issue in any of my projects. you would need to debug the link building
Updated by Franz Holzinger about 3 years ago
- Complexity set to nightmare
I have found out now the reason for this error.
There has been a backup copy file typo3conf/sites/demoshop-orig and the old version of the config.yaml there. The real config file config.yaml under typo3conf/sites/demoshop has been activated in the TYPO3 backend.
However TYPO3 did also process the other old copy config.yaml. On the old config the page with id=10 has been set as the
base: 'https://mywebsite.com/'
rootPageId: 10Both identifiers have been used by TYPO3. Only the first should have been used however. TYPO3 did not tell me that it also wanted to use this old backup copy.
It still did not work after the deletion of the backup folder. Also the TYPO3 cache had to be cleared.
After this also the page 10 did show the http in the backend at the slug field.
Updated by Riccardo De Contardi about 3 years ago
Updated by Franz Holzinger about 3 years ago
Yes, this issue is very similar to Bug #90436. The only addition is that even http can be changed into https for only one page if a second, but not assigned site configuration is included, but this should not have happend.
Updated by Franz Holzinger about 3 years ago
- Related to Bug #90436: Some weird behaviour with autogenerated site config added
Updated by Riccardo De Contardi about 3 years ago
- Category set to Link Handling, Site Handling & Routing
Updated by Benni Mack over 2 years ago
Updated by Benni Mack over 2 years ago
- Status changed from Needs Feedback to Accepted
Franz Holzinger wrote in #note-11:
No "config.baseUrl" setup is used.
OK. After re-reading I think we should throw a big warning if there are two configurations with the same "rootPageId".
Updated by
Updated by Benni Mack over 1 year ago
- Related to Bug #90163: Site config still being used even if page is no longer site root added
Updated by Gerrit Code Review over 1 year ago
- Status changed from Accepted to Under Review
Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76516
Updated by Gerrit Code Review over 1 year ago
Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76516
Updated by Gerrit Code Review over 1 year ago
Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76516
Updated by Susanne Moog over 1 year ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 68e6b76a0dc0f9800f5aa95c4cb12a5e01c24800.