Hello Everyone,
I have recently turned my attention to Project Naming Conventions, as a consequence of attempting to locally MIRROR certain parts of the Drupal codebase. For example, the Drupal 7 oriented codebase (from which Backdrop is/was derived) is rather large:
- ~170,000 files
- ~340Gb
My MIRROR effort is being complicated by the inconsistent application of what appears to to me to be at first an emergent, then semi-official Drupal Project Naming Convention:
Project_name-Backdrop_version-Project_version.Extension_A.Extension_B
The inconsistent application of Project Naming Conventions has resulted in an exceptions list of over 7,000 items, mostly due to the inconsistent application of Drupal Project Name separator(s). Some used a dash ("-") instead of using an underscore ("_") in their Project Name, like these entries:
MyDrupal-Tidy-5.x-1.0.tar.gz
MyDrupal-Tidy-5.x-1.0.zip
Others did not use a version number:
CiviCRM-HEAD.tar.gz
...and so on.
My question
Has Backdrop officially adopted a Project Naming Convention?
I assure you, it would make any visitors from the future very grateful :)
The consistent use of underscore ("_") and dash ("-") and period (".") in filenames can really simplify filename processing.
g.
----
Recent comments
I think it’s totally fine to share, especially if it helps others! Just be honest that it was AI-assisted and make sure it works well and doesn’t break anything. Many people would appreciate a...
Thoughts on AI generated code contrib?
Thank you very much for your fast answers and clear explanations ! I understand that the site is not corrupted and that there is no danger in leaving the code and the database in their...
Base table or view not found upgrading to 1.32.0, TRUNCATE {cache_book}
Until the official new release (coming soon), the error will ALSO show up when you clear caches, unless you fix this manually as above.
Base table or view not found upgrading to 1.32.0, TRUNCATE {cache_book}
If you want to try to fix it yourself now, I think you can manually set the schema version for the book module (in the system table) to 7000, and then try running the updates again. Test on a...
Base table or view not found upgrading to 1.32.0, TRUNCATE {cache_book}
This was turned up as an issue with Drupal 6 -> 7 -> Backdrop upgraded sites because the schema version for Book is still from Drupal 6 and Backdrop's upgrade hooks don't fire. There's a...
Base table or view not found upgrading to 1.32.0, TRUNCATE {cache_book}