This is a follow-up task that was mentioned in #2074 (where we removed the tag default from all core views).
Now with Views in core and also with admin_views in core, I think that it would make sense to be adding:
- a core tag for all views provided by core
- a custom tag for all views manually added to the site
- a %module name% tag for all views regardless of whether they are core/contrib/custom (we currently have a "Default (module-provided)" indication in the "Storage State" column, which is not very useful, but it would be if the module providing the view was also indicated). If not a tag, this could be a new provided-by property.
As it is now, these tags would have no value, but if we added an instant search filter at the top of the views list (#503), then it would be very useful, because as you must have also experienced yourselves, most sites end up with a few dozens of views.
Anyways, I have previously filed #1897 in which I mention the same issue. Similar/related but different problems.
Recent comments
This was tricky, so i tried to stay minimal and try to snatch the very first procedure after file upload and inject rehashing there. The file is tinymce.pages.inc under the function...
File hashing uploads made through TinyMCE
Bee's great. But if you don't want to install bee, or can't, or you already have a bunch of scripts you're used to using in D7, then the method I posted is quick and easy and all you really...
How to create a command-line (cli) routine or script (bee not required)
Or you can install bee, get the benefit of all the included functions and either include your script using: bee php-script ../my-scripts/scratch.php https://github.com/backdrop-...
How to create a command-line (cli) routine or script (bee not required)