Apache Solr for TYPO3 CMS

Michiel Roos wrote:

Currently my filter looks like:

Resultaat verfijnen Content Type o pages 88 o file 81

The customer does not understand 'file' and 'page'.

You can do that with TypoScript:

 renderingInstruction = CASE
 renderingInstruction.key.field = optionValue
 renderingInstruction.pages = TEXT
 renderingInstruction.pages.value = Pages

But i also think this can be done diffrent.

Thank you Timo!

That works great.

Here is my snippet for posterity:

plugin.tx_solr {
    search {
        faceting {
            facets {
                type {
                    renderingInstruction = CASE
                    renderingInstruction {
                        key.field = optionValue
                        pages = TEXT
                        pages.value = Pages
                        file = TEXT
                        file.value = Documents
                    }
                }
                language {
                    renderingInstruction = CASE
                    renderingInstruction {
                        key.field = optionValue
                        0 = TEXT
                        0.value = English
                        1 = TEXT
                        1.value = Dutch
                    }
                }
            }
        }
    }
}

If you need different labels for different languages, you should wrap these TS sections with language conditions.

Thanks for sharing your solutions guys, great spirit! And I'm also happy that the extension is so flexible already! ;)

I'll leave this issue open for now, but will mark it as resolved once I move your snippets to the documentation in the wiki. Can you agree with that? I'm still open for easier solutions, although I think it won't get any more flexible than this.

Agreed

Just a short comment on #2:
I'm not sure what you mean by 'wrap these TS sections with language conditions', but for all TS-newbies (like myself), there is a very flexible and easy to use trick if you want to localize the labels. TEXT-types provide a lang-Attribute to localize their value, so Michiels' code could be extended to:

plugin.tx_solr {
    search {
        faceting {
            facets {
                type {
                    renderingInstruction = CASE
                    renderingInstruction {
                        key.field = optionValue
                        pages = TEXT
                        pages.value = Pages
                        pages.lang.de = Seiten
                        file = TEXT
                        file.value = Documents
                        file.lang.de = Dokumente
                    }
                }
                language {
                    renderingInstruction = CASE
                    renderingInstruction {
                        key.field = optionValue
                        0 = TEXT
                        0.value = English
                        0.lang.de = Englisch
                        1 = TEXT
                        1.value = Dutch
                        1.lang.de = Niederländisch
                    }
                }
            }
        }
    }
}

Aside of that, thanks Timo and Michiel for the solution you guys provided, you just saved me a couple of hours of work :)