odai atieh → created an issue.
Re-rolled patch #10
Odai Atieh → made their first commit to this issue’s fork.
Odai Atieh → created an issue.
Rerolled patch
I've updated the description of the available token for the email body field. Also, I added the user tokens to the tokens tree.
The idea is to add additional tokens, such as the user's information, to enhance the template with supportive details, but only if the email was related to an existing user. If these tokens are not available, they will not impact the template's functionality.
This approach can be useful for incorporating more personalized information about the recipient in the template, such as "Dear [recipient's first name]."
Odai Atieh → created an issue.
+1 to RTBC
If no value is provided for the Location field or the Department field it won’t assign any policy and it will be accessible to everyone.
Did you mean that if the location field or the department field is empty in the node or the user profile? because I'm talking about case if the fields were empty in the node not in the user profile.
and I'll try the suggested polices.
Break up your access rules across two access policies and group them into a Selection set. This allows you to assign two policies at the same time using OR logic. This will have the same effect and should resolve the issue.
I've tried the above suggestion, but didn't work. E.g. in case I selected department x and the location field was empty for a node, and the user was not in department x, then the node will be accessible. I think this is happened because the location field in the node was empty and the location rule was set to ignore empty values. which will add the user's locations to the query and allow empty value. So, the location policy will allow the user to access the node.
Did you take a look at your entity reference fields to make sure they had the same bundles selected?
Yes, but for the node fields I used "filter by an entity reference view" to apply some restrictions so I think this breaks the rules in the access policy.
You can create your own AccessRuleQueryHandler and modify the query.
I've tried to add some changes to queryIgnoreEmpty to add or group to get all entities that have the rules field empty, but it didn't work. I'll check AccessRuleQueryHandler as you recommended.
Also, I checked your commit here https://git.drupalcode.org/project/access_policy/-/commit/4685b80fe83f3b... but it didn't work.
Hi Joshua,
I've upgraded the module to dev, but I'm facing another issue, now I can't see all needed rules for all fields. I just can find 2 of them.
Is there any change should I do before adding them?
Odai Atieh → created an issue.
It was required to either delete them or do some actions like flagging, send notifications...etc. I agree with you making this optional, so the admin can change it from the settings according to the needs.
Odai Atieh → created an issue.
Odai Atieh → created an issue.
+1 to RTBC
Odai Atieh → created an issue.
Odai Atieh → created an issue.
Rerolled patch for 10.1.5
Thank you partdigital for your quick response. I tested the MR 5 and it fixed the issue.
Odai Atieh → created an issue.
Patch #2 works
I needed to display only the timezone to follow the design and requirements for a project.
Odai Atieh → created an issue.
Just created a patch for the MR
Please ignore better_exposed_filters_allow_the_date_format-2858610-23_2.patch
A warning appeared as below, so I've updated the latest patch to check if the filter is set or not before checking if datepicker is selected.
Warning: Undefined array key "filter" in Drupal\better_exposed_filters\Plugin\views\exposed_form\BetterExposedFilters->exposedFormAlter() (line 797 of modules/contrib/better_exposed_filters/src/Plugin/views/exposed_form/BetterExposedFilters.php).
I can't log out (/user/logout) from the website, and I believe this issue is related.
I applied patch #21, which solved the issue, but I don't know if it will affect the module functionality. or we can ignore the user entity from hook_entity_access().
This is a patch to exclude the file and user entities from the query alter hook, but I'm still testing it.
Odai Atieh → created an issue.
Odai Atieh → created an issue.
Rerolled the patch