You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I asked my question in the old solved discussion, but then decided to create a new one:
I previously used "payload": "1.6.32" and attempted to replace it with the next "payload": "1.7.0". However, I encountered an issue with access control in one of my collections.
This collections contains upload field asset.
We only return files with permitted extensions for one of the user roles.
I use something like access: accessFunction, in collection
Where accessFunction has this part of code ('en' is default locale,${locale} is current locale from the query)
Do you have any idea which part of this release could potentially affect it?
UPD: another strange thing that when I replace extension with filename without extension - it works, for example:
I have asset with full name myasset.ext1
If I use condition {['asset.en.url']: { contains: '.ext1' }} it returns nothing
But if I write {['asset.en.url']: { contains: 'myasset' }} it returns the correct result
It looks like
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I asked my question in the old solved discussion, but then decided to create a new one:
I previously used
"payload": "1.6.32"
and attempted to replace it with the next"payload": "1.7.0"
. However, I encountered an issue with access control in one of my collections.This collections contains upload field
asset
.We only return files with permitted extensions for one of the user roles.
I use something like
access: accessFunction,
in collectionWhere accessFunction has this part of code ('en' is default locale,
${locale}
is current locale from the query)Do you have any idea which part of this release could potentially affect it?
UPD: another strange thing that when I replace extension with filename without extension - it works, for example:
I have asset with full name
myasset.ext1
If I use condition
{['asset.en.url']: { contains: '.ext1' }}
it returns nothingBut if I write
{['asset.en.url']: { contains: 'myasset' }}
it returns the correct resultIt looks like
Beta Was this translation helpful? Give feedback.
All reactions