In today's development meeting we started a discussion about priorities for Backdrop CMS v. 1.14.0, scheduled for release on September 15th. We thought it would be helpful to ask the community, beyond those already deeply involved in the Github issue queue, what issues or feature that you think should be prioritized?

Here is your chance. Based upon your experiences with Backdrop CMS, what kinds of features or changes to Backdrop CMS core do you think ought to be prioritized for version 1.14.0?

Here is a list of items that have been currently flagged for possible inclusion in the next minor release. 

 

Most helpful answers

I like the idea of an "Editor Experience" release (as I think someone else floated at one point). Examples:

  • Save draft
  • Improved ability to rearrange fields on the admin content creation pages, ideally using Layouts
  • Maybe an "editor" role out of the box
  • Media improvements (see below)

If "Media improvements" is too large as a sub-point it may need a separate release focus on its own:

  • Ability to upload files independently
  • Better filtering/controls in WYSIWYG image library (e.g. filter by filename, sort by date or name)
  • Add image library to core image fields
  • Ability to manage/edit images directly from the image library
  • Multiupload file and image fields

Another focal area could be "Multilingual":

  • Translating config
  • Upgrade paths/testing from Drupal 7 (e.g. menu translation, etc.)
  • localization server

Hi Jen, thank you for tackling this, and thank you for your awesome work with Backdrop over the years. I really like the software.

To be honest, I am not a big search expert, I have similar settings for the Search API for each site. I used to rent a dedicated service in Germany (https://hosted-solr.com/), but the experience was not very impressive speed-wise, canceled it a few months ago. I use the Virtual Hosting Server here, it's a quite well-known company in Switzerland, but not a dedicated Drupal provider: https://www.nine.ch/en/home

The plan is to rent Nine's SOLR option (again) and make some tests... because right now I use Database Search for all sites, including sites with automplete like this one (try e.g. "Hamilton" in search field) https://zeitshop.ch/

I would be pretty happy to have the current state of Search API  in Backdrop CMS, including the comprehensive settings on a field level, e.g. Regular Expressions on a per-field base. Just one example: this search here showed ALL results with two "1" in there https://binderrehab.ch/de/skusearch?search=01-1001 (hundreds of results). The problem could be solved with RegEx... it's an SMB client, but search becomes quickly "enterprisey" in every project.

Regards from DrupalCamp Spain (and I hope to make it to Minneapolis next spring)
Matthias

Comments

Thank you for raising the issue:-) I have one topic that prevents me migrating many sites to Backdrop CMS: the lack of powerful search functions. In D7 I use Search API a lot, often combined with Autocomplete, Facets, and I really like the module(s), although Autocomplete is quite slow.

For me, it would definitely be an Autoban-equivalent feature. (I know we've been chatting about this on both Twitter and Github but I thought I'd put it here, too, for the sake of consistency and visibility--I know things are being discussed to get a baseline IP block functionality added into BD before something like Autoban.)

With the never-ending bot farms that keep scanning and attempting to inject exploits, this is an absolute MUST before I can move over into BD. I specifically mention Autoban due to it's unique ruleset features where you can define what request rules trigger either a single IP or entire range ban--in my D7 site this has proven to be a mission critical aspect of my site as it not only helps with general day-to-day security but also acts as a means of buying me time to apply any and all security updates or upgrades during times when I might not be at a workstation to install them.

Also, the offer still stands if you guys need someone to test any related functionality. :.)

jenlampton's picture

Thanks for the feedback!

@mazze Search is definitely a weak spot with Backdrop/Drupal core. If you are using SearchAPI with Drupal 7, what are you using for the actual search engine? Are you using Solar, Lucene, or something else?  I'm also curious about where are you hosting, if you'd be willing to share that with us.

Hi Jen, thank you for tackling this, and thank you for your awesome work with Backdrop over the years. I really like the software.

To be honest, I am not a big search expert, I have similar settings for the Search API for each site. I used to rent a dedicated service in Germany (https://hosted-solr.com/), but the experience was not very impressive speed-wise, canceled it a few months ago. I use the Virtual Hosting Server here, it's a quite well-known company in Switzerland, but not a dedicated Drupal provider: https://www.nine.ch/en/home

The plan is to rent Nine's SOLR option (again) and make some tests... because right now I use Database Search for all sites, including sites with automplete like this one (try e.g. "Hamilton" in search field) https://zeitshop.ch/

I would be pretty happy to have the current state of Search API  in Backdrop CMS, including the comprehensive settings on a field level, e.g. Regular Expressions on a per-field base. Just one example: this search here showed ALL results with two "1" in there https://binderrehab.ch/de/skusearch?search=01-1001 (hundreds of results). The problem could be solved with RegEx... it's an SMB client, but search becomes quickly "enterprisey" in every project.

Regards from DrupalCamp Spain (and I hope to make it to Minneapolis next spring)
Matthias

I like the idea of an "Editor Experience" release (as I think someone else floated at one point). Examples:

  • Save draft
  • Improved ability to rearrange fields on the admin content creation pages, ideally using Layouts
  • Maybe an "editor" role out of the box
  • Media improvements (see below)

If "Media improvements" is too large as a sub-point it may need a separate release focus on its own:

  • Ability to upload files independently
  • Better filtering/controls in WYSIWYG image library (e.g. filter by filename, sort by date or name)
  • Add image library to core image fields
  • Ability to manage/edit images directly from the image library
  • Multiupload file and image fields

Another focal area could be "Multilingual":

  • Translating config
  • Upgrade paths/testing from Drupal 7 (e.g. menu translation, etc.)
  • localization server

When I see it right, then it's possible to schedule publishing for later. 

I would also love to have the possibility for scheduled unpublishing

This is for me in many cases an important feature and I used it in most Drupal 7 or 8 installations. 

I agree with mazze: Search API would be nice. 

And also with laryn:

  • Save as Draft
  • Editor role out of the box
  • Media improvements are always welcome.