Description of the need I have adopted a practice of moving config files from the files directory to a special config directory 1 level below Backdrop CMS root. However, this is not consistent across all my sites. I think it would be great if the status report page showed where Backdrop CMS is actually looking for the config files (as set in the settings.php file)
Proposed solution Add "config directory" path to the status report.
Alternatives that have been considered None
Additional information This seems pretty obvious to me so I expect that there is another ticket somewhere discussing this that I was unable to find.
I am also considering that this MIGHT not be a good idea for security reasons. Maybe there are good reasons to not include the path to these files in the UI. I'm not sure if this would be a problem and look forward to hearing from others.
Recent comments
To confirm that it is ok to be deleted, I would look in the config folder for any config files with the string taxonomyextra in. If you don't find any, then yet it is probably safe to drop...
taxonomyextra table after migration from Drupal 6
Today there was finally time to delve into this issue. First I downloaded the field_data_taxonomyextra table into a spreadsheet. There is a column called Bundle, which in my case included,...
taxonomyextra table after migration from Drupal 6
Hi Enthusiast - there is work in progress on an improvement to core that I think will help this. https://github.com/backdrop/backdrop-issues/issues/4127 I don't fully understand it...
The problem of caching the pages