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.
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again.
Then...
Posted3 days 22 hours ago by Francis Greaves (themetman) on:
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Posted1 week 2 days ago by Francis Greaves (themetman) on:
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.
I fixed the usage statistics again today and filed an issue against Project module to fix it permanently: https://github.com/backdrop-contrib/project/issues/66
The short explanation is that the shell script was not executable.
If there is time, carried over from last week as we didn't have time to look at it then, I would welcome feedback on the approach I've taken to: