Bug #72164
closed
"absRefPrefix = auto" does not work if PageGenerator is not used
0%
Description
If a URL is generated in a CLI Task and the PageGenerator is not used the "auto" value of absRefPrefix is not replaced but added to the URL.
I've currently the probelm in the Solr extension that all my URLs a prefixed with "auto" as "auto" is now the default setting.
I would expect that "auto" is always replaced now matter when and where it is used.
Maybe this problem does also happen due to misusage of core api.
Updated by Sascha Egerer almost 9 years ago
- Description updated (diff)
May a simple \TYPO3\CMS\Frontend\Page\PageGenerator::pagegenInit() would help. But it is currently only called for FrontEnd requests.
Updated by Mathias Brodala almost 9 years ago
Workaround: use absRefPrefix = / if that's the only value you need on all system.
Updated by Sascha Egerer almost 9 years ago
Mathias Brodala wrote:
Workaround: use
absRefPrefix = /if that's the only value you need on all system.
Yes i already used that but we should fix that ;)
Updated by Jigal van Hemert over 8 years ago
- Status changed from New to Needs Feedback
The problem is more that EXT:solr tries to build a FE environment (needed for TS for example) and this is not the same as the normal FE context of TYPO3 itself.
If you create URLs and use typolink.forceAbsoluteUrl = 1 the URL's will also be malformed if the scheduler task is run from CLI. Most of the times these URLs will have the path on the file system in them.
This is caused by the fact that several server variables that are used by the core to form the current host, path, url, etc. are not filled (correctly).
If this is the same problem as you experience then this issue is IMO a conceptual problem in EXT:solr.
Updated by Alexander Opitz about 8 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
Candidate for patchlevel)
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.