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
This function relies on _elgg_get_access_where_sql() which relies on get_access_array(). Both rely on the global access state. The former can be altered to pass an explicit "ignore_access" option it, but get_access_array() is called by get_access_list(), and there's a nested cache, making it practically impossible to pass the ignore flag into it directly.
So I'm recommending just turning on the access system when building the query in has_access_to_entity().
Long term solution is to allow creating a temporary use query builder that relies on a directly-injected access bit. I.e. no functions that reach out to global access.
The text was updated successfully, but these errors were encountered:
This function relies on a nested stack of functions which all depend
on the global "ignore access" state. This pragmatic workaround ensures
the access system is always enabled while all these functions are called.
FixesElgg#7159
…o be ignored
This function relies on a nested stack of functions which all depend
on the global "ignore access" state. This pragmatic workaround ensures
the access system is always enabled while all these functions are called.
FixesElgg#7159
This function relies on _elgg_get_access_where_sql() which relies on get_access_array(). Both rely on the global access state. The former can be altered to pass an explicit "ignore_access" option it, but get_access_array() is called by get_access_list(), and there's a nested cache, making it practically impossible to pass the ignore flag into it directly.
So I'm recommending just turning on the access system when building the query in has_access_to_entity().
Long term solution is to allow creating a temporary use query builder that relies on a directly-injected access bit. I.e. no functions that reach out to global access.
The text was updated successfully, but these errors were encountered: