Forum Replies Created
- mcl7Participant3 years, 5 months ago in reply to: Errors when sending data to Algolia #22582
The only errors in the algolia logs were two 404’s here:
/1/indexes/gb_product_index/settings?getVersion=2mcl7Participant3 years, 5 months ago in reply to: A few minor questions #22581Not sure where to upload files but I just added them to gofile and you can see them here:
It’s the AIO SEO settings in WPsolr screenshot and then a screenshot of the AIO SEO Settings.
Essentially the issue is that the custom meta defined in the AIO SEO settings is not be reflected on the site when WPSolr is enabled. It appears to be only a problem with taxonomies …the product page meta defined in the screenshot reflects accurately on the website.
Let me know if you have any other questions. I spoke with the developer of AIO SEO and they are not familiar with WPSolr.
mcl7Participant3 years, 5 months ago in reply to: A few minor questions #22576On my first issue, I uninstalled WPSolr and All in One SEO worked as expected. If I activate though I am dealing with the issue with facets not being generated and used in the URLs and no titles or metadata using my data.
Any thoughts here on what I should do?
mcl7Participant3 years, 5 months ago in reply to: Errors when sending data to Algolia #22574Ok, not sure whats going on but I took a break and all the import errors are gone. Im guessing algolia made a change on their end?
mcl7Participant3 years, 5 months ago in reply to: Errors when sending data to Algolia #22573I would also add that I ended up deleting indexes several times last night and ever time receieved the error that is shown here (even though it did actually successfully delete the index every time)…its the same error (on line 281 as when sending data to algolia in the first error I pasted):
An error or timeout occured.
Error code: parsererror
Error message: SyntaxError: Unexpected token { in JSON at position 2
“”{“nb_results”:0,”status”:8,”message”:”Error on line 281 of file \/nas\/content\/live\/sitename\/wp-content\/object-cache.php: Undefined index: delete”,”indexing_complete”:false}
mcl7Participant3 years, 5 months ago in reply to: Errors when sending data to Algolia #22572I gave it a shot after it failing at 100, 10, 1, etc. All attempts regardless of the batch size or whether or not I tried each batch size with a fresh index and one that already existed. All tests resulted in the error shown above.
That’s what’s weird though is that sometimes a batch of 100 or even 500 will go through and then stop when an error is found. However, if you run just one and an error is displayed it stops indexing.
Never does it incrementally show a document count being indexed up (and reflecting the batch size specified) as it did with my ElasticSearch tests.
What made it even more strange is that it did actually import 5k products but I have only been able to actually to do that twice so it’s not really a reliable solution. Just odd that different batch sizes result in different behavior.
mcl7Participant3 years, 5 months ago in reply to: Errors when sending data to Algolia #22569I deleted everything. I wanted to figure out the error before relying on it. There are 20k products currently. I was able to get up to 9000 imported (in two blocks of 5k) but then failed at reaching any higher than 7000 being indexed in Algolia.
mcl7Participant3 years, 5 months ago in reply to: Errors when sending data to Algolia #22567I did have another Algolia plugin but deactivated already before installing WpSolr.
Also, does populate in Algolia. Kinda weird that I was able to successfully upload 5k (without a success message indicating how many records were uploaded). Usually, though it feels like every record throws an error almost immediately.
mcl7Participant3 years, 5 months ago in reply to: Errors when sending data to Algolia #22563Forgive repeated posts here…just trying to get to the bottom of this early this week. I would love to get this up and running during the trial.
I *think* I am having the same issue as this guy:
Is there an easy way to change the post_modified (if that’s my problem)?
Just curious why it ran so smoothly with ElasticSearch and Algoli (which is usually super fast) is having a hard time?
mcl7Participant3 years, 5 months ago in reply to: Errors when sending data to Algolia #22562Also getting this error when just deleting data from Algolia:
An error or timeout occured.
Error code: parsererror
Error message: SyntaxError: Unexpected token { in JSON at position 2
“”{“nb_results”:0,”status”:8,”message”:”Error on line 281 of file \/nas\/content\/live\/sitename\/wp-content\/object-cache.php: Undefined index: delete”,”indexing_complete”:false}
Its strange though…if I do a small batch I get this error. However, I just tried a batch of 5000 and they all imported to algolia although there was no success message saying X number of records were imported?
mcl7Participant3 years, 5 months ago in reply to: Errors when sending data to Algolia #22561Also getting this error when just deleting data from Algolia:
An error or timeout occured.
Error code: parsererror
Error message: SyntaxError: Unexpected token { in JSON at position 2
“”{“nb_results”:0,”status”:8,”message”:”Error on line 281 of file \/nas\/content\/live\/sitename\/wp-content\/object-cache.php: Undefined index: delete”,”indexing_complete”:false}
mcl7Participant3 years, 5 months ago in reply to: No Results on WooCommerce Category Pages with Algolia #22559A quick update here:
I kept running into errors trying to send data to Algolia. Not sure what the deal is but I just went ahead with the “Test index using Elastic Cloud” and used the same exact configuration as I was attempting with Algolia. With Elastic, there were no errors at all but I did notice while it was indexing that there were categories that still didn’t have any products.When it finished I noticed that there were categories that are showing products. Doing some poking around it looks like the issue is with the high-level categories that don’t themselves have products BUT their children (or sometimes grandchildren) do have products.
So I guess my questions are:
– Do products need to be assigned to all the parent categories as well as the actual category they are assigned to?– Is there a way to avoid adding all the products to their parent categories in order to have the facets reflect the accurate number of products in all products children to each attribute?
The only other problem I have is the errors seen only when trying to push data to Algolia which I will dig further into and post in a new ticket.