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.
Funnily we launched a new Dutch website this very week, milieucafe.nl
It is not a 'news' website but operates in the context of local government. The layout focuses on content instead of...
The answer is off topic, but I'll add a little.
1. Backend. Why you don't need links to other websites: Since you know the structure of your site and content, you can decide for...
Hi Chrys,
AI isn't always your best friend. A form alter hook is correct, but hiding by CSS isn't ideal.
You could look at how the TinyMCE integration does it, which provides hiding...
Hi zilvervos...,
Welcome back to Backdrop.
I've just started a new "news" website for a client, but it's at the very early stages. I'm hoping to have a soft launch in a couple...
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: