If there's some time left after discussing code signing (yay!)...
1. Friendly reminder: usage stats are still broken
Didn't data get fetched at all (broken parser) or is it a display problem? Only guessing here. But public usage stats shouldn't stay broken too long (now broken since June).
2. This has been briefly discussed in a Zulip thread: When upgrading from Drupal, after file classification (when file entities get their type assigned) all files in file_managed db table have the same timestamp (caused by bulk file_save()). This breaks sorting files by age.
There are ideas how to fix that, but it involves a (possibly dynamic) property on File entities, which might not be desirable.
Does it make any sense to proceed? Core committer feedback highly appreciated.
If there's some time left after discussing code signing (yay!)...
1. Friendly reminder: usage stats are still broken
Didn't data get fetched at all (broken parser) or is it a display...
Sorry - it is the field_group module.
However, last night I switched off proxying to the site and proved to Cloudflare Support that it was NOT a Backdrop issue. After a thorough...
I'm also now getting a 403 when trying to access admin/reports/updates - it seems to be Backdrop generated but there is nothing in the Recent Log messages other than my login as admin...
Since this is still possibly Cloudflare related I'll post here:
I'm now experiencing what I think is caching issue - since installing Bee I've run bee cc all, bee cron, bee mm 1, then,...
Comments
If there's some time left after discussing code signing (yay!)...
1. Friendly reminder: usage stats are still broken
Didn't data get fetched at all (broken parser) or is it a display problem? Only guessing here. But public usage stats shouldn't stay broken too long (now broken since June).
2. This has been briefly discussed in a Zulip thread: When upgrading from Drupal, after file classification (when file entities get their type assigned) all files in file_managed db table have the same timestamp (caused by bulk file_save()). This breaks sorting files by age.
There are ideas how to fix that, but it involves a (possibly dynamic) property on File entities, which might not be desirable.
Does it make any sense to proceed? Core committer feedback highly appreciated.