ElasticSearch Essentials [Paid] 3.17.16

[Xon]

These are not fixed after upgrade to 3.17.13
I suspect it didn't really upgrade. What can I do to force it?

Can you try manually uploading the zip and then doing a force-rebuild of the add-on?

This fix was done based on the very latest version of the the PixelExit themes, so if your thing is older it might not be applying the template modifications as expected

 

[Alpha1]

Can you try manually uploading the zip and then doing a force-rebuild of the add-on?

It still lists that the addon has an upgrade.
The issue also persists, while I'm using PixelExit's Nova style version 2.3.7
I am however using a child style. There are no relevant outdated templates.

 

[Xon]

It still lists that the addon has an upgrade.
The issue also persists, while I'm using PixelExit's Nova style version 2.3.7
I am however using a child style. There are no relevant outdated templates.

I've identified some flaws in the 3rd party theme support, which I'll be working on this week. This will fix support for PixelExit's styles and UI.X in various configurations

 

[Xon]

Xon updated ElasticSearch Essentials with a new update entry:

3.17.14 - Bugfix & Maintenance updates

• Only show post-area for a user if they have posts
• Fix unexpected failure for autocomplete for some themes
• Improve compatibility with UI.X and various PixelExit themes (for XF2.2 and XF2.3)

Read the rest of this update entry...

 

[nocte]

2.17.14 - Bugfix & Maintenance updates

Typo in the version number.

 

[Xon]

Numbers are hard! (Should be fixed now, it was just transcribing them to the resource update form)

 

[Xon]

Xon updated ElasticSearch Essentials with a new update entry:

3.17.15 - Bugfix udpate

• Fix possible error with XF2.3.8+ & search

Read the rest of this update entry...

 

[Xon]

Xon updated ElasticSearch Essentials with a new update entry:

3.17.16 - Maintenance update

• Improve support of ReplicationAdapter when using the xf-rebuild:search-bulk CLI command
• Note; if SQL errors occur when bulk-indexing referencing the xf_search_bulk_indexing table, start a new indexing task not just restart the old one. This will regenerate this table.

Read the rest of this update entry...

 

[willl]

When upgrading on XF 2.3.8, it spits out the error:

The following errors must be resolved before continuing:

• ElasticSearch Essentials requires Browser Detection 2.0.0+.
• ElasticSearch Essentials requires Search Improvements v2.9.0+.

However I made sure to grab the latest of both as of writing, and it's still giving the error.

 

[Xon]

You need to update StandardLib to v1.23.0+ first, or update/install each add-on one at a time. The stock admincp updater isn't aware of add-on requirements and sorts alphabetically which can be hilariously wrong.

StandardLib v1.23.0 patches the admincp batch updater to check and sort the add-ons based on requirements so updating multiple add-ons at once works as expected. Sadly you need to install that update first by itself before any other add-ons

 

[willl]

You need to update StandardLib to v1.23.0+ first, or update/install each add-on one at a time. The admincp updater isn't aware of add-on requirements and sorts alphabetically which can be hilariously wrong.

What's interesting is I did upgrade SL, and also ran the upgrade via CLI at the time.. Will double-check when I get a chance, busy afternoon

 

[Xon]

What's interesting is I did upgrade SL, and also ran the upgrade via CLI at the time.. Will double-check when I get a chance, busy afternoon

Check the add-ons aren't disabled, that is another way for the requirements check to fail weirdly

 

[willl]

Check the add-ons aren't disabled, that is another way for the requirements check to fail weirdly

Yeah, they're all enabled; I will note ES essentials was disabled, but attempted to upgrade it after re-enabling it (again, all via CLI) and it's still spitting out the same error..

Just as an FYI, this is upgrading from XF 2.2.16 running ES Essentials 3.4.2, if that's useful at all.

 

[Xon]

Yeah, they're all enabled; I will note ES essentials was disabled, but attempted to upgrade it after re-enabling it (again, all via CLI) and it's still spitting out the same error..

Is $config['enableListeners'] = false; set in src/config.php ? That can cause weirdness sometimes

 

[willl]

Is $config['enableListeners'] = false; set in src/config.php ? That can cause weirdness sometimes

Nope, that was the second thing I checked, in fact.

 

[Xon]

When upgrading on XF 2.3.8, it spits out the error:

The following errors must be resolved before continuing:

• ElasticSearch Essentials requires Browser Detection 2.0.0+.
• ElasticSearch Essentials requires Search Improvements v2.9.0+.

However I made sure to grab the latest of both as of writing, and it's still giving the error.

Reviewing how the addon.json is structured, this could happen is SV/StandardLib was disabled or stuck in an is_processing state as it means the string-version comparisons aren't being done.