Forum Replies Created
- euwid_burkhardParticipant2 years, 7 months ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27839
Hi again,
unfortunatly it’s still not working. Our hoster “Exigo” is still listed on your website as a hoster: https://www.wpsolr.com/de/guide/configuration-step-by-step-schematic/apache-solr-hosting/Maybe you could get into contact with them about this problem?
For now we decided to not update anymore and stay on Version 22.0.
euwid_burkhardParticipant2 years, 7 months ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27746Hi again,
I sent the archive with the config files from /wpsolr/core/classes/engines/redisearch_php/admin/conf/5.0/wpsolr-v5.zip to our hoster. I will write here again as soon as I know if it worked.euwid_burkhardParticipant2 years, 7 months ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27744Hi,
unfortunatly we can’t the index from within WPSOLR. The index is already created by our hosting. I just asked our hoster for a new index. We now got a different path but even with this fresh index the error still persists. I was able to send the first 100~ posts to the index, after that the same error from my initial forum post.euwid_burkhardParticipant2 years, 7 months ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27742Just tried to change the path. Seems to be not possible for us. We get an “Forbidden” error.
euwid_burkhardParticipant2 years, 7 months ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27741No, until now we used the path we get from our hoster (/solr/euwid8_de)
euwid_burkhardParticipant2 years, 7 months ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27740Hi again, extra info to my last response: Our hoster said they changed the value in the schema.xml file from “plong” to “long” now. Still the same issue.
I deleted every index in the WPSOLR backend and configured a new index with a newer used WPSOLR index name. It was possible to index 140 posts with an increment of 10. After that the same error as before.
euwid_burkhardParticipant2 years, 7 months ago in reply to: Bug: No indexing possible with 22.1, even with the fix #27738Hi,
we already tried to create a new index via “Configure another index” multiple times with different names in the “WPSOLR index name” field. Same error while trying to index everytime.I meant “plong”. We will try changing it to “long” as well.
Is there a complete schema.xml file we can use (and send to our hoster)? Can we use one of the schema.xml files from the plugin directory?
Thanks in advance.
euwid_burkhardParticipant4 years, 8 months ago in reply to: Empty "misc" output since WPSOLR Pro 21.5 #13771Okay, thank you. We’re gonna keep the old version for now since we need to keep the filtering and same look for our customers.
I tested the theme search template with “our url/?s=” on a local staging and the meta information shows in this scenario.
euwid_burkhardParticipant4 years, 8 months ago in reply to: Empty "misc" output since WPSOLR Pro 21.5 #13769Hi again. I just checked: We are using the theme option in screen 2.1. The result stays the same when I turn it to WPSOLRs custom search templates so I think that’s not the problem. Even without changing anything the problem occurred with the update from 21.4 to 21.5. Any ideas? Thanks in advance!
euwid_burkhardParticipant4 years, 8 months ago in reply to: Empty "misc" output since WPSOLR Pro 21.5 #13689Sorry, I forgot some additional information:
– I tried to debug the issue in the file: /wpsolr-pro/wpsolr-templates/twig/search/result.twig
– I added my for loop after line 57 – these lines here:
{# Meta information #}
{% block result_metas %}
<div class=’p_misc’>
– I also tried to change the search template in the settings (part 2.1), no difference.
– I also tried overwriting the template files via child-theme. The results are the same.euwid_burkhardParticipant5 years, 5 months ago in reply to: Cannot search text containing special characters #8320Hi,
thanks for your insight. Indeed deactivating WPSOLR shows that it seems to come from the theme. Thanks for you insight.
Best regards,
Vincent Burkhard – EUWID