Ernesto Baschny

Just as an idea: You could support v12 and forward-support v13 already (by not using deprecated functions in v12), keeping the "2 releases spirit" but avoiding the hassle of keeping...

Reading through these other issues: Maybe a generic solution to cope all "wishes" would be to have it configurable which information is used to generate the "site hash": * for...

@sorenmalling one potential solution is to index the site identifier too: ``` plugin.tx_solr.index.queue.pages.fields { ... siteIdentifier_stringS = TEXT siteIdentifier_stringS.data = site:identifier ``` And use it in the filter: ``` plugin.tx_solr...

Thanks for the pointer, @christophlehmann! I will give it a try. There also exists EXT:solrconsole (from DKD, I think its EAP-only) which has these commands, but not as scheduled tasks,...

Maybe its only in the hierary facet, but this is indeed our use-case. In this case we have a `sys_category` facet and want to have the categories with most documents...

I am currently not even sure who is maintaining the extension. For our use-case we just want to maintain compatibility, because on a "fresh installation" I would not install direct_mail...

Totally agreed, since it was removed as a requirement in composer.json some time ago, I stumbled over the issue just on the upgrade, where the jumpurls were not working anymore....

BTW, it was removed here: https://github.com/kartolo/direct_mail/commit/3c2187407bb8365ca61ba324e112e174969260b6 which was part of the big v11 update: https://github.com/kartolo/direct_mail/pull/288

That looks great, @kartolo thanks! But if jumpurl is only "suggested", this should be noted in the documentation that this is required if you want to use the "click tracking"...

I came to the same problem today, the hint was in the logs: ``` Jun 24 16:17:10 xxx telegraf[19525]: 2019-06-24T14:17:10Z I! Starting Telegraf 1.11.0 Jun 24 16:17:10 xxx telegraf[19525]: 2019-06-24T14:17:10Z...