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've added a new recipe. The recipe has no PHP code. It has two module dependencies (one of those depends on another contrib module and both depend on core modules that are normally enabled)...
The Future of Configuration Recipes for Backdrop CMS
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...
My Webform Worksheets have disappeared
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...
My Webform Worksheets have disappeared
@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...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists