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
The File (Field) Paths module should be able to move existing files. I've not tested it, but the module description says: Retroactive updates - rename and/or move...
Moving from /files into subdirectories
Yes indeed. We are exploring a few other more costly options, but as we are a low-resource start-up, we could save a lot of money by integrating Backdrop, CiviCRM and Ubercart for our membership...
UberPOS for Backdrop?
Hello Chrys.., It looks like it was for Drupal 6, with a Dev release for D7... Never seen it before, but it looks like an interesting module... Do you have an immediate need...
UberPOS for Backdrop?
I do have the apache status page set up ... I will look in to this really fast. BRB.
Status Report Page throws : Forbidden You don't have permission to access this resource.
Hi TallElfin, that sounds like a webserver misconfiguration. It has nothing to do with the CMS itself. So... other paths work just fine, also admin paths, only the path "admin/...
Status Report Page throws : Forbidden You don't have permission to access this resource.