[TYPO3-Solr] Indexing custom Items

[hard.one Software GmbH]

Hi all

thanks to your hints, I was able to trigger the update via API.

Looking at the discussion and using the API, I would like to comment it 
in short.

Basically what I did is using a hook for the fe_users update and create 
to index new and updated users. BUT: I wanted to control the way what 
changes leed to an reindexing the user's record. This was made possible 
via the API call.
Same thing is for my custom items - not every change / update needs to 
trigger reindexing.

I'm a "control freak" - if it is in my hands and tools are provided to 
implement something the way I imagine it should be, then I really 
appreciate it.
Of course basic things like content and pages, should be indexed 
automagically. But this is, from my point of view, a basic requirement 
when using a CMS.
Doing to much automagic might be good for basic users - but for "power 
users"? In my eyes: It is no good. I have an API - I use it. And I 
believe this is a flexible and convienient way. And the most important 
thing: it is no effort to index the stuff, just two lines...

For me it is good the way it is - there are other things bugging me a 
lot more then the index updating of items, multi-language indexing with 
domain per language for example.

Best

Martin

On 03.10.2013 09:44, Dmitry Dulepov wrote:
> Hi!
>
> Stephan Schuler wrote:
>> This is a good point on one hand. If you consider Extbase as
>> privileged frontend mechanism to be covered by Solr, then we should do
>> the same for the old fashioned way.
>>
>> But the other hand is: Using plain pi_base has several other drawbacks
>> that are really unfriendly to integration of data and handling of them
>> inside of TYPO3.
>
> There are other ways to write extensions beyond pibase and Extbase.
> Extensions do not have to depend on those.
>
> What I am trying to say is that it would be good if Solr docs had a
> chapter for extension authors about using Solr from extensions. It is
> easy to notify Solr about data changes (just one API call). However this
> API call now does not check that the data should be indexed, it just
> blindly puts the record into the queue. Thus the API is not very useful.
>
> Solr has a TCEmain hook, which makes such check. That check should be
> moved to API level. Than it will be easy for extension authors to use
> the API without doing more checks.
>