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
When changing the push rules on a remote server the change does not get applied.
We wanted to change the rules from a local tag to a tag of the Workflow taxonomy.
After performing the change at first it looks successful but it then seems to get reversed to the old filtering.
Tags involved were:
Old tag (local): workflow:state="released"
New tag (from Workflow taxonomy): workflow:state="release"
We checked that the tag we wanted to apply is enabled on the remote server with a call to /servers/getAvailableSyncFilteringRules and this is the case.
All changes were performed as a user with the 'admin' role.
We could not find anything in the error logs relating to this.
For now we solved it by manipulating the related server entry directly in the db but this is clearly not future proof.
Expected behavior
Change in push rules, or any other rules, in the 'Remote Servers' should be applied or at least have a log entry indicating what would be wrong (like a used tag not being present or enabled on the remote server).
Steps to reproduce
Make a change to the push rules on a 'Remote Server'.
After a browser refresh we see that it is reverted to the previous situation (the old tag was previously deleted, that's why you see the id of the old tag)
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Actual behavior
When changing the push rules on a remote server the change does not get applied.
We wanted to change the rules from a local tag to a tag of the Workflow taxonomy.
After performing the change at first it looks successful but it then seems to get reversed to the old filtering.
Tags involved were:
We checked that the tag we wanted to apply is enabled on the remote server with a call to /servers/getAvailableSyncFilteringRules and this is the case.
All changes were performed as a user with the 'admin' role.
We could not find anything in the error logs relating to this.
For now we solved it by manipulating the related server entry directly in the db but this is clearly not future proof.
Expected behavior
Change in push rules, or any other rules, in the 'Remote Servers' should be applied or at least have a log entry indicating what would be wrong (like a used tag not being present or enabled on the remote server).
Steps to reproduce
Make a change to the push rules on a 'Remote Server'.
Version
v2.4.188 (8ac96cc)
Operating System
Ubuntu
Operating System version
22.04
PHP version
7.4.33
Browser
No response
Browser version
No response
Relevant log output
Extra attachments
Right after the update it seems to be applied.
After a browser refresh we see that it is reverted to the previous situation (the old tag was previously deleted, that's why you see the id of the old tag)
Code of Conduct
The text was updated successfully, but these errors were encountered: