Since Pods 2.9.4: Restricted Access within Templates defaults to Yes

[danmaby]

Description

When creating a new template or editing an existing one in 2.9.4, the Restricted Access settings all default to Yes. When unchecking these settings and updating, they default to Yes.

Version

2.9.4

Testing Instructions

1. Publish a new Template with no Restricted Access
2. Review Template
3. See restrictions applied
4. Remove restrictions
5. Update
6. See restrictions applied again

Screenshots / Screencast

Possible Workaround

Temporarily downgrading to 2.9.3 restores expected behaviour.

Site Health Information

No response

Pods Package

No response

[oldrup]

Mmm, as this obviously only really affects people without access rights, it goes unseen by me, the admin, until some non-admin user complains:

I've spend some time creating a screencast, somewhat redundant to the fine testing instructions by @danmaby but here it is:
https://www.loom.com/share/09931098c9e048f5b33f097a4079d06c

Workaround: disabling the restrictions actually seems to work, even though they still look enabled in the backend.

Is this related to "Fixed: Pod/Group/Field configurations being saved now get their checkbox boolean options properly enforced as 0/1 and sent so they are not reverted to the default value on next load. #6485 (@sc0ttkclark)" ?

Bjarne

[sc0ttkclark]

@oldrup it was unrelated to that it appears

Fixed this in the end by just making this into a legitimate pod object (since it was an internal pod but fields were not defined the same way).

960d4e4