1
votes

I've created a simple extbase/fluid based news extension with a listview showing the latest news. I'm also using indexed_search to search the whole website. The problem is, that the indexed_search not indexing any words of my news.

How can I use indexed_search for my own extension? I can't find anything helpful on the web for hours. I would be very thankful for every hint or keyword. Fluid template of the listview of my extension:

<f:for each="{berichts}" as="bericht">
        <div class="bericht">
            <div class="bericht_titel">
                <h1>
                    <b>[<f:for each="{bericht.kategorien}" as="kategorie" iteration="i">{kategorie.name}<f:if condition="{i.isLast}"><f:then></f:then><f:else>, </f:else></f:if></f:for>]</b>&nbsp;<f:link.action action="show" pageUid="65" format="html" arguments="{bericht: bericht}">{bericht.titel}</f:link.action>
                </h1>
                <span class="glyphicon glyphicon-menu-right" aria-hidden="true"></span></div>
            <div class="bericht_text">
                <f:if condition="{bericht.bild}">
                    <a href="{f:uri.image(src: bericht.bild.originalResource.publicUrl)}" class="bericht_bild"><f:image image="{bericht.bild}" alt="" /></a>
                </f:if>
                <f:format.html>{bericht.text}</f:format.html>
                <div class="clearfix"></div>
                <f:if condition="{bericht.anhaenge}">
                    <div class="bericht_anhang">
                        <b>Anhänge:</b><br />
                        <f:for each="{bericht.anhaenge}" as="anhang">
                            <div>
                                <a href="{anhang.originalResource.publicUrl}" target="_blank">
                                    <f:if condition="{anhang.originalResource.title}">
                                        <f:then>
                                            {anhang.originalResource.title}
                                        </f:then>
                                        <f:else>
                                            {anhang.originalResource.originalFile.name}
                                        </f:else>
                                    </f:if>
                                </a>
                            </div>
                        </f:for>
                    </div>
                </f:if>
            </div>
        </div>
</f:for>

Generated HTML of one "Bericht"

<div class="bericht">
    <div class="bericht_titel">
        <h1><b>[Allgemeines]</b>&nbsp;<a href="/aktuelles/bericht/?tx_companyaktuelles_p1aktuelles%5Bbericht%5D=3&amp;amp;tx_companyaktuelles_p1aktuelles%5Baction%5D=show&amp;amp;tx_companyaktuelles_p1aktuelles%5Bcontroller%5D=Bericht&amp;amp;tx_companyaktuelles_p1aktuelles%5Bformat%5D=html&amp;amp;cHash=d6c3c8ef294eee899bc15150443b0775">Test</a></h1><span class="glyphicon glyphicon-menu-right" aria-hidden="true" style="transform: rotate(90deg);"></span>
    </div>
    <div class="bericht_text" style="display: block;">
        <p>Dies ist ein Test</p>
        <div class="clearfix"></div>
    </div>
</div>
1
is your extension output cached (indexed_search only indexes cached content)? this also means: don't call your page with BE-login and expect a filling of the index, as there will not be any caching while you are logged in in the BE. and last: is your content inside the appropiate markers?Bernd Wilke πφ
@BerndWilkeπφ my content is within the markers <!--TYPO3SEARCH_begin--><!--TYPO3SEARCH_end-->. Normal content could be found. In my extension I only defined cachable actions (configurePlugin) If that is enough to active caching?Ralf
I also called the page without logged in in the BE.Ralf
you might need to use cHash parameter to verify your parameters. Are cHash paramters in the generated URLs (if you deactivate realurl)?Bernd Wilke πφ
@BerndWilkeπφ I'm not using a single view, only listview. So, I don't need cHash parameters?Ralf

1 Answers

1
votes

Now it's working. There was something incorrect with the page itself, but disable cache wasn't active. So if someone else has the same problem; try inserting the plugin to another page and test it. I had to delete the page and create it again.