#5118 - Privacy policy: last modified considerations

  • By
  • Added
  • 16 views
Identifier #5118
Issue type Trivial issue (does not break functionality)
Title Privacy policy: last modified considerations
Status Completed
Handling member Chris Graham
Addon General / Uncategorised
Description We need to consider the "last revised" date on the Privacy Policy page. Currently, it pulls from either the modified or created metadata, but this only tracks manual edits to the privacy page.

However, by default, the privacy page uses the auto-generating main_privacy_policy_auto block to create a privacy policy. If the information in this block changes, realistically the revised date should also change. But we should maintain the ability for the revised date to also change if the page is manually edited.
Steps to reproduce

Additional information Perhaps:
a) When main_privacy_policy_auto is generated, hash all its data and store in a database value.
b) If the hash changes, update the hash in the database and update the modified metadata for whichever Comcode page is using the block.

Another idea (since the above could get tricky messing with Comcode page meta)... since we can reasonably assume main_privacy_policy_auto will never contain more than one privacy policy (it does not use a param):
a) When main_privacy_policy_auto is generated, hash all its data and store in a database value.
b) If the hash changes, update the hash in the database and also maintain a revised timestamp for the block
c) Create a new Tempcode symbol that outputs either the Comcode page creation date, the Comcode page modified date, or the main_privacy_policy_auto modified date... whichever is most recent. Use this on the default Privacy Policy page.
Funded? No
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated