Skip to content
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

GuildedCommunity Guidelines ‧ not tracked anymore #1426

Open
1 task
OTA-Bot opened this issue Mar 18, 2024 · 0 comments
Open
1 task

GuildedCommunity Guidelines ‧ not tracked anymore #1426

OTA-Bot opened this issue Mar 18, 2024 · 0 comments
Labels
403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA]

Comments

@OTA-Bot
Copy link
Collaborator

OTA-Bot commented Mar 18, 2024

No version of the Community Guidelines of service Guilded is recorded anymore since 18 March 2024 at 18:36:06 UTC

The source document has been recorded in a snapshot, but no version can be extracted.
After correction, it might still be possible to recover the missed versions.

What went wrong

How to resume tracking

First of all, check if the source documents are accessible through a web browser:

If the source documents are accessible through a web browser

Edit the declaration:

  • Try updating the selectors.
  • Try switching client scripts on with expert mode.

If the source documents are not accessible anymore

  • If the source documents have moved, find their new location and update it.
  • If these terms have been removed, move them from the declaration to its history file, using 2024-03-18T18:36:06Z as the validUntil value.
  • If the service has closed, move the entire contents of the declaration to its history file, using 2024-03-18T18:36:06Z as the validUntil value.

If none of the above works

If the source documents are accessible in a browser but fetching them always fails from the Open Terms Archive server, this is most likely because the service provider has blocked the Open Terms Archive robots from accessing its content. In this case, updating the declaration will not enable resuming tracking. Only an agreement with the service provider, an engine upgrade, or some technical workarounds provided by the administrator of this collection’s server might resume tracking.

References

@OTA-Bot OTA-Bot added the 403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA] label Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
403 Fetching fails with a 403 (forbidden) HTTP code [managed by OTA]
Projects
None yet
Development

No branches or pull requests

1 participant