Knowing if an add-on is 2.3 compatible?

[Mouth]

As there is no search or filter functionality available for determining if an add-on you have (or those that you could have) is 2.3 compatible, is the only option to interrogate the updates and discussion tabs of every add-on, and repetitive post(s) asking if/when the dev will update or test the add-on for 2.3 compatibility?

 

[Kirby]

You could to some basic checks:

1. Does it have its own JavaScript files?
   If so it is very likely that iit is not compatible
2. Does it have template edits that don't apply in a XenForo 2.3?
   If so it is very likely that it is not compatble
3. Does it have style properties, options, etc. that use Font Awesome icons?
   If so there is a medium-high chance that it is not compatible

That being said, IMHO the easiest way is to just look at field Compatible XF 2.x versions and assume all Add-ons that do not list 2.3 to be probably incompatible.

 

[woody]

As there is no search or filter functionality available for determining if an add-on you have (or those that you could have) is 2.3 compatible, is the only option to interrogate the updates and discussion tabs of every add-on, and repetitive post(s) asking if/when the dev will update or test the add-on for 2.3 compatibility?

yes.

 

[Mouth]

look at field Compatible XF 2.x versions and assume all Add-ons that do not list 2.3 to be probably incompatible.

Agreed. Was hoping not to have to manually evaluate, and continuously re-evaluate, every add-on currently used separately.
We have this issue with every XF version minor version, was hoping it was solved by now, maybe with another add-on I missed etc.

 

[woody]

Agreed. Was hoping not to have to manually evaluate, and continuously re-evaluate, every add-on currently used separately.
We have this issue with every XF version minor version, was hoping it was solved by now, maybe with another add-on I missed etc.

I mean, print off your current list of add-ons, and take notes. I've done exactly that and then have a download folder already populated with compatible add-ons.

 

[Mr Lucky]

If it's a crucial addon, wait until it says 2.3. If not so crucial I just check if it works by trying it on my test installation. I'm now only waiting for one addon to be "officially" compatible.

 

[bzcomputers]

Not sure the best solution for this, but I know if something doesn't change we'll all be doing this again within about 6 months when 3.0 comes out.

Maybe a request for developers to include a "XFmax" under the requirement section in the addon.json if that addon release is not compatible with a XenForo release that is already out in beta or later.

"require": {
      "XF": [2000010, "XenForo 2.0.0+"],
      "XFmax": [2030010, "XenForo 2.3.0+"]
      "php": ["7.4.0", "PHP 7.4.0+"],
      "php-ext/json": ["*", "JSON extension"]
  }

Then have the XF AdminCP addon list display the min and max XF requirements (if available).



...now that I think about it, it'll never happen
-------------------------------------------------------

Just seems like there must be a better way. Not having something in place to make transitions to a new XF major release easier is very odd for a piece of software in the year 2024.

 

[BassMan]

If it's a crucial addon, wait until it says 2.3. If not so crucial I just check if it works by trying it on my test installation. I'm now only waiting for one addon to be "officially" compatible.

That is exactly what I do.

 

[Kirby]

Maybe a request for developers to include a "XFmax" under the requirement section in the addon.json if that addon release is not compatible with a XenForo release that is already out in beta or later.

"require": {
      "XF": [2000010, "XenForo 2.0.0+"],
      "XFmax": [2030010, "XenForo 2.3.0+"]
      "php": ["7.4.0", "PHP 7.4.0+"],
      "php-ext/json": ["*", "JSON extension"]
  }

The functionality of the version field is indeed pretty limited; I'd appreciate if if would support (a subset of) Composer version constraints.

Versions and constraints - Composer

A Dependency Manager for PHP

getcomposer.org

 

[philmckrackon]

I mean, print off your current list of add-ons, and take notes. I've done exactly that and then have a download folder already populated with compatible add-ons.

Exactly, I created a spread sheet and two directories (2.2x, 2.3) and list / download the current add-ons. Once the spread sheet is populated with both columns showing compatible (and tested on my test backup site) I'll upgrade (or at least know which add-ons I keep.)

 

[Mouth]

I mean, print off your current list of add-ons, and take notes. I've done exactly that and then have a download folder already populated with compatible add-ons.

Yes, of course, doing it manually and repeatably is available, but .....

Not having something in place to make transitions to a new XF major release easier is very odd for a piece of software in the year 2024.