Bug #93423
closed
wrong https in slug of one page
Added by Franz Holzinger almost 4 years ago.
Updated almost 2 years ago.
Category:
Site Handling, Site Sets & Routing
Sprint Focus:
On Location Sprint
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=11
Files
Related issues
2 (2 open — 0 closed)
- Status changed from New to Needs Feedback
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
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
- 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.
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.
- Related to Bug #90436: Some weird behaviour with autogenerated site config added
- Category set to Site Handling, Site Sets & Routing
Franz Holzinger wrote in #note-7:
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.
Are you using config.baseUrl ?
No "config.baseUrl" setup is used.
- 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".
- Sprint Focus set to On Location Sprint
- Related to Bug #90163: Site config still being used even if page is no longer site root added
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by