Closed panosru closed 8 months ago
Will do a test tomorow to see what is causing this and fix it if I can replicate it thanks for the report.
wow mate, your response time! You live here? haha
Thanks a ton! If you need anything else from me to provide as additional data let me know
Just figured out the issue I forgot to add the local key to the UI. update will be out in a hour or so to fix this.
@panosru Just publised a new version this should fix your issue if it does not fix it please feel free to reopen the issue. this adds locale to the options in the plugin interface after updating the plugin and rebuilding the admin
Thanks a lot mate!
One final note locale needs to be enabled for everyting where you want to use ?locale
Hi, I believe my issue is related to issue #14, I will try to be as detailed as possible.
Here is my setup:
When I access
/api/books/1
I get:When I access
/api/books/1?locale=ru
I get the same result as above.If I remove the setting from
protected-populate
* and access either/api/books/1
or/api/books/1?locale=ru
I get:If I access
/api/books/1?populate=*
I get:What I want to get is:
But, I don't see any option in the configuration to include the
locale
attribute in the result.Protected Populate
in the main menu instead ofprotected-populate
it kind of triggers my OCD hahaHey, really appreciate your work on this, it is very good and indeed, like you, I too got sick of those query strings to get to the needed result and avoid unnecessary data in responses.