Straw poll - addon + theme compatibility with v9

Of the 12 add-ons we have in the marketplace which I’ve updated for V9:

  1. = 1 addon (a very simple one)
  2. = 4 addons
  3. = 6 addons
  4. = 1 addon
  5. = 0
  6. = 0
  7. = 0
  8. = 0

Beyond the marketplace, I’ve updated maybe another 6 or 7 private add-ons.
Some are quite simple and just work, whereas others have taken a lot of time, mostly on dashboard and editing cosmetics. I’ve not actually tested any of our custom themes at this point, but I’m not expecting issues.

But the main thing I’ve tackled was updating Community Store, which is effectively V9 compatible now in the master branch. There might be a few remaining details to address (in obscure features), hence why I haven’t put out a release yet, but it’s mostly done. There are some new dashboard components, like how to handle search fields, so I’ve been trying to implement those as well.

For Community Store I really didn’t hit any structural issues, it was 95% cosmetic problems. I have been able to adjust the codebase to simultaneously support V8 and V9.

The main things I encountered were:

  • tabs not working. These are currently not backwards compatible, and I’d urge the core team to work on this. It feels like an oversight that tabs on block editing needed a bit of a hack to get working on both V8 and V9 with the same codebase - I’d be surprised if it couldn’t be addressed before release.

  • bootstrap issues with dashboard pages, mostly to do with pull-left and pull-right now being float-start and float-end respectively. Some bootstrap columns needed adjusting as well. Some dashboard pages looked a complete mess, but didn’t take overly long to fix. It might be worth to add a few very commonly used classes to the dashboard css, so there’s a bit of compatibility with BS3. This might fix quite a lot of broken dashboard pages (or at least clean them up a lot), and having those classes there really wouldn’t harm anything.

  • things like select2 no longer being available and replacements having to be pulled in. I can sort of accept this for outdated libraries, but something like a select multi-picker is a very common user interface element, so I’ve had to update this in multiple add-ons.

I’m really liking V9 (and I rambled about this here), and we’re really looking forward to using it. But I’d be lying if I thought it was going to be a seamless transition in terms of add-ons and themes - without all marketplace developers reviewing and updating their add-ons I’m concerned it’s going to be pretty messy… we’ll not be updating client sites with lots of marketplace add-ons for quite some time because of this concern.