Patch 11 also solved the problem for me. Thanks!
Just for tracking purposes, I tried to apply the patch from 27, and it did not apply in composer. Running Drupal 10.3.10, PHP 8.3.6, nginx/1.24.0, and MySQL 8.0.40-0ubuntu0.24.04.1.
It appears that comment #7 solved the problem for us.
My team and I will be looking into this and what it might entail.
tyler.hastain → created an issue.
We realized that this happens because of 2 different ECA models that we have running.
1st Model: We have an ECA model that when an article is moved to draft from published, that it populates the user who moved the article to draft into a "checked out by" field and resaves the article. We use this field to disable all fields while an article is checked out by someone to everyone except the person in that field.
2nd Model: This ECA model disables all the fields on an article if the logged in user is not the user in the checked out by field and the article is in the draft state.
These two models together caused the problem. Model 2 disabled the attachment fields on the initial move from published to draft. Model 1 came in to update the checked out by field and resaved. However, since the attachments field was disabled, it did not save the attachments field correctly on the resave. In other words, it saved the field as empty since it was disabled.
Thank you for getting us headed in the right direction! In trying a fresh reinstall and trying to reproduce the issue, we discovered that it was an ECA model that we have that was causing the problem. We are going to dive into that instead. Thank you for your help!
Hey Jeremy,
Do you know if you or someone can approve my email address for slack? I tried to join and it didnt work. We did create the #utah channel in the Drupal Slack instead. I think maybe we should be working there?
tyler.hastain → created an issue.
It sounds like you are using the Webform module? I know that this process can be fairly easily done in ECA and Views. It might be something that you might want to look into for your organization? If you have specific questions or want to pursue this option, let me know. We have done a lot of things like this in my organization.
We currently use version 3.0.0-beta1 and ran into the same AJAX pagination issue.
Applying Patch #25 resolved the problem for us as well.
I'm also currently using version 3.0.0-beta1 and was having the broken pagination issue when AJAX was turned on.
Applying Patch #25 resolved the problem for me as well.
Added patch 17 for Drupal 10.2.4. It only fixes the issue if the aggregation setting for the moderation state is set to aggregate on the Entity ID instead of the Value. (See attached screenshot for more information.)
My organization would also like to use this option if it ever became available.
Fourthing. This is really needed! In our use case, we want to hide the facet's data that the user does not have permissions to. We believe that this is happening because the index itself is not tied to groups or its permissions.
Example:
-Article is in 2 separate groups.
-User only has access to one of those groups.
-User should be permitted to see the article and see it is in a group they have access to.
-However, they should not see the other group they don't have access to that the article is in within the facet.