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
A source I use has cloudflare protection, so when I did a global update, the entries in that source ended up in the update errors screen. It can easily be solved by passing a captcha (no need to migrate), and I want to manually update those entries and remove them from the update errors screen. It seems that there is currently no way of doing this. Even when I go into the entry itself and update it, it still stays in the update errors screen. I have now placed the entries for that source in an excluded category, so I have no way of getting rid of those entries from the update errors screen.
It would be great to have a feature to update these entries manually and/or remove these entries from the update errors screen.
Other details
No response
Acknowledgements
I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
I have written a short but informative title.
If this is an issue with an official extension, I should be opening an issue in the extensions repository.
Describe your suggested feature
A source I use has cloudflare protection, so when I did a global update, the entries in that source ended up in the update errors screen. It can easily be solved by passing a captcha (no need to migrate), and I want to manually update those entries and remove them from the update errors screen. It seems that there is currently no way of doing this. Even when I go into the entry itself and update it, it still stays in the update errors screen. I have now placed the entries for that source in an excluded category, so I have no way of getting rid of those entries from the update errors screen.
It would be great to have a feature to update these entries manually and/or remove these entries from the update errors screen.
Other details
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: