andi2021
Forum Replies Created
-
Thank you for your assistance. I manage multiple WooCommerce sites and am seeking help to disable the ‘itemReviewed’ schema. I’ve encountered errors related to it across several domains but have been unable to resolve the issue through my own settings. If possible, could you provide an email address where I can formally request this be disabled? I would greatly appreciate your support.
Yes for example: https://tshirtatlowprice.com/products/build-westville-finish-date-2035-shirt/
I test google schema it’s show Missing field “itemReviewed”. Sorry for the delay.Thank you for the detailed explanation.
To clarify, my question is actually about the other modules, not the Chatbot. I am integrating via the API with external systems like n8n or custom GPT actions in the browser.
In these scenarios, where there isn’t a specific module interface or a defined system prompt field for the API request, the AI’s inherent goal orientation becomes critical. Without a pre-configured context, the results can be generic.
Could you please advise on the best practice for providing this necessary context? For instance, should a default system prompt be bundled within the API call itself, or is there another method to ensure the AI’s role is properly defined for these external integrations to return optimal results?
Thank you for your guidance.
No, I think you misunderstood me. I meant using existing Google Images directly, not through the API. I want to search for images that match the content of a post using Google search results or the Images tab.
Hi Peter,
I hope you’re doing well. Before reaching out, I made sure to exhaust all possible solutions on my end. I carefully followed the step-by-step guide provided at https://wpghost.com/kb/config-htaccess-in-openlitespeed-a-step-by-step-guide/ and double-checked my configuration multiple times. Unfortunately, I’m still encountering issues with specific WP-JSON endpoints.
Here’s the behavior I’m experiencing:
/apireturns a 200 status code (success).- However,
/api/,/api/wc, and/api/wc/v2all result in 404 errors.
I suspect this might be related to OpenLiteSpeed’s caching mechanism. Initially, after switching configurations, the endpoints might work due to cached responses. However, after waiting 1-2 minutes or performing a hard refresh (Ctrl + F5), the 404 errors reappear.
Could you please take a moment to verify the compatibility of your plugin with OpenLiteSpeed? All other features are functioning perfectly, but the issue seems to persist specifically with the
wp-jsonrewrites.Your assistance in resolving this would be greatly appreciated. Thank you for your time and support!
Best regards,
David JameHi Peter,
Thank you for your help earlier. I’ve tested the setup on InstaWP, and it works perfectly. However, after deploying it on an OpenLiteSpeed server, I encountered a 404 error again. For testing purposes, I only installed two plugins: WooCommerce and WP Hide My Ghost. It seems there might be a compatibility issue or configuration conflict with the OpenLiteSpeed server.
Could you please advise if there’s a known solution or specific server configuration required to resolve this? Your expertise would be greatly appreciated.
Best regards,
David JameHi Peter,
Thank you for your response.
Despite following your tutorial, I’ve tested everything, and it still doesn’t function as expected. Could you try modifying “wp-json” to “api” or a similar endpoint? For instance, navigate to domain/api and then domain/api/wc/v2. You’ll likely encounter the issue I’m referring to.Hi Peter, Thank you for your response.
When I change wp-json to a custom structure like call, I expect the endpoints to work seamlessly with the new URL. For example, /wp-json/wc/v2 normally returns a JSON response with a 200 status. However, when I change it to /call/wc/v2, it returns a 404 error instead of the expected JSON response.It seems that simply replacing wp-json with call doesn’t automatically update the internal routing for the REST API endpoints. The custom URL structure isn’t being recognized, which is why the endpoints aren’t functioning as intended. I assumed that changing wp-json to call would be enough, but it appears the internal endpoints aren’t being affected by this change.
Could you clarify if there’s an additional step or configuration needed to ensure the custom URL structure works correctly with the REST API endpoints? Thanks!
- This reply was modified 1 year, 1 month ago by andi2021.
It seems the feature is not functioning as expected. This functionality is specifically designed to work with classes or IDs.
Thank you so much! For example, if you activate the Flatsome Child theme, it means it will use some CSS or images from the parent theme, Flatsome. Your plugin will change the name of “flatsome-child” to a random name, but it will not change the name of the parent theme, Flatsome.