Bug #93423

wrong https in slug of one page

Added by Franz Holzinger 8 months ago. Updated 6 months ago.

Needs Feedback
Should have
Link Handling, Site Handling & Routing
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


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 {
#noBlur = 1
wrap = <ul> | </ul>
NO = 1
NO.ATagTitle.field = description // title
NO.allWrap = <li> | </li>
NO.ATagBeforeWrap = 1
NO.stdWrap.htmlSpecialChars = 1


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=11


pages-https-10.csv (1.96 KB) pages-https-10.csv Franz Holzinger, 2021-02-04 18:18

Related issues

Related to TYPO3 Core - Bug #90436: Some weird behaviour with autogenerated site configNew2020-02-19


Updated by Georg Ringer 8 months 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 8 months 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 8 months 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 8 months 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: 10

Both 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 8 months ago

These issues look somehow related?




Updated by Franz Holzinger 8 months 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 8 months ago

  • Related to Bug #90436: Some weird behaviour with autogenerated site config added

Updated by Riccardo De Contardi 6 months ago

  • Category set to Link Handling, Site Handling & Routing

Also available in: Atom PDF