Feature #36542
closed
Changed domain handling on "View webpage" from backend causes problems
Added by Sybille Peters almost 12 years ago.
Updated over 6 years ago.
Description
Due to fix for Bug #30892:
This new behaviour causes problems for us.
For a long time (due to bug or not) the domain currently used in the backend was used for loading a page with "View webpage". Due to the change in getViewDomain, the first domain from the domain records is now used.
On multi-site installations we use a generic domain for working in the backend and this should be consistent with the domain used for viewing the page from the backend.
We now have to patch the core or completely change handling.
Ideal would be to make this configurable !!!
Why would you preview with a wrong domain? Can you provide a usecase for using a different domain for previewing the content, then for actually publishing the content?
use case #1: using a reverse proxy for HTTPS. All backend access is redirected via the reverse proxy changing all the URLs from www.domain1.de to secure.domain.de/www.domain1.de etc.
use case #2: www.domain1.de, www.domain2.de, www.domain3.de are all hosted on a single TYPO3 installation. Some users have access to only one domain, some have access to all domains. In this case, it is best to access the backend via a common domain e.g www.alldomains.de.
If this is not made clear, I am happy to elaborate via private email.
We have the same problem. We have an "intern" domain for the backend and several domains for the frontend user and now every time when we view in backend the domain from domain record is taken and there're a lot of redirects...We would prefer the baseurl.
We have the same problem with a client. We have one main domain for the admins and several "subdomains" for editors. Preview of a hidden page is somewhat tedious for admins logging in on the main domain.
- Target version set to 8 LTS
Hi,
any news on that ? The "take the first domain record" mechanism kicks in, when previewing a page in another domain node in a multidomain env.
BUT: It seems that the userTSconfig settings are NOT present, when previewing a hidden page in another domain node. Therefore, the user is sees a 404 page in the frontend.
- Status changed from New to Needs Feedback
Hi, there is an undocumented FEATURE to set an alternative previewDomain in PageTSConfig.
TCEMAIN.viewDomain = example.com
If you have your backend running on https and your frontend not you can specify a protocol in this setting.
TCEMAIN.viewDomain = http://example.com
Does this solve the problem?
Yes it solves the problem.
However, it should be:
TCEMAIN.previewDomain not viewDomain.
And, the protocol part does not work for me, so
TCEMAIN.previewDomain = blahblah.uni-hannover.de/etc
works fine (the current https protocol is used) but
TCEMAIN.previewDomain = https://blahblah.uni-hannover.de/etc
results in a URL
https://https//blahblah.uni-hannover.de/etc
being generated.
- Status changed from Needs Feedback to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41095
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41095
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41122
- 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 
Updated by 
Updated by 
Updated by