-
Notifications
You must be signed in to change notification settings - Fork 10
ISSUE-510: New embargo (global) options + ADO Argument validator for Views + Refactor embargo service #513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@alliomeria not ready yet. But pretty advanced already. Will let you know when/how to test and to merge. Thanks |
What do you think about these minor wording changes @DiegoPino ?
|
@alliomeria thanks for your edits! The wording looks very good. Really appreciate it. |
Allows ADO embargo to drive Argument validation on a View/Block (10/10!)
We need to statically cache as UUID and NID the results (in a single call) to avoid over processing. The reason we need the NID (and new method for that) is that at the View level, where we have our new Argument Validator, the argument is a NID .... Also. When a View checks/validates the argument and e.g We find it is "FALSE", meaning the user can't bypass an embargo, basically no more processing happens and the View might return FALSE (not an render array). IN that case, no more "hooks" run and i can't longer alter the Cache tags/ max times and context. So the safest option for that is really, simply NOT cache at all. It is one or the other: safety v/s speed. First one wins in the world of Bots/access restrictions.
Why? We need the entity now, not just the UUID. That way we can set 2 static caches, one via UUID and one via NID
|
@alliomeria Ok. This is working and tested on all parts we apply Embargoes. I still need the last pull to add to some viewers the Formatter settings form checkbox to hide in case of embargo. Once that is done (tomorrow 10AM) I will ask you to merge please. Night |
|
@alliomeria I will merge and make another pull for the Formatter settings. My pulls/commit trail is getting too large |
See #510 and #497