I’ve attempted to reproduce this issue in my test environment by changing page setup settings, but it did not modify the .htaccess file. It seems likely that a different plugin is responsible for updating the .htaccess file.
As the next step, I recommend setting up a staging site and testing again after deactivating all other plugins except WooCommerce. Additionally, it would be helpful if you could share a list of your active plugins.
One thing to note is that Nginx does not support .htaccess files, as far as I understand. Could you confirm whether your server is running Nginx or Apache?
For those encountering the issue, could you please share your system status if it’s still active? I’m finding it difficult to replicate the problem with my setup.
This reply was modified 2 years, 2 months ago by moon0326.
If the returned schema doesn’t match its endpoint, it’s not possible to build a tool and “we are returned the schema of our API, enabling others to write client libraries to interpret our data” is false in that case because those tools need to guess the type of endpoints — object or array.
Let’s say I’m building a mock server using schema and I want to provide a mock endpoint for the posts. It’s not possible to build the tool without mapping the endpoint’s type.
posts => collection
post => item
> Since being RESTful is all about resources, I believe defining the resource’s schema and not the response itself is proper.
We can have both, and that’s what other tools such as OpenAPI (aka Swagger) choose to.
Once you define a resource (Post in this case), you can reuse it as if it’s a model.
