[TYPO3-Solr] Solr Extension for typo3 - Wrong URL
Hauke Meyer
meyer at visionconnect.de
Mon Jul 1 13:35:48 CEST 2013
No, I didn't. It is a simple task "never do anything when you pull
anything out of a bucket when you can do it while putting it inside".
But while doing it "the right way" I came across an interesting
misbehavior inside typo3. The typolink call to generate the url produces
strange paths when called via the scheduler (I needed forceAbsoluteUrl
inside typolink).
example:
plugin.tx_solr.index.queue.pages.fields.url {
typolink.parameter.field = uid
typolink.forceAbsoluteUrl = 1
typolink.useCacheHash = 1
typolink.returnLast = url
}
And because we use realurl "absRefPrefix" according to the documentation
is not an option. And we run into a bogus path building (complete
filesystem path inside url). We cover this with a trick. The problem was
calling the scheduler from "/", the solution was to call it from inside
the virtual host folder.
@Dimitry Or is it possible to use your ext:pagepath instead of raw typolink?
Hauke
Am 01.07.2013 10:02, schrieb Dmitry Dulepov:
> Hi!
>
> Hauke Meyer wrote:
>> plugin.tx_solr.search.results.fieldRenderingInstructions.url.default>
>> plugin.tx_solr.search.results.fieldRenderingInstructions.url.default
>> = COA
>> plugin.tx_solr.search.results.fieldRenderingInstructions.url.default {
>> 5 = TEXT
>> 5.value =http://
>> 10 = TEXT
>> 10.field = site
>> 15 = TEXT
>> 15.value = /
>> 20 = TEXT
>> 20.field = url
>> 20.htmlSpecialChars = 1
>> 20.htmlSpecialChars.preserveEntities = 1
>> }
>
> Never ever do this in TYPO3. This is plain wrong.
>
More information about the TYPO3-project-solr
mailing list