There was a change in Drupal release 8.4.0 that made Libraries module incompatible. As a result, it makes Juicebox incompatible. I;m still not sure if this will be considered a bug in Libraries, or a bug in Drupal 8.4.0 core, but either way, this issues serves to highlight the fact that oneone with Juicebox installed will brick their application when updating code to 8.4.0. Please see the various linked/related issues for more specific details.

Since Libraries is still completely unstable with no official releases of any kind, not even Alpha or Beta, I want to re-raise the concerns I raised in 2770255. Can we just get rid of this dependency? It doesn't look like anyone is pushing it forward or even working on it.

Comments

xeM8VfDh created an issue. See original summary.

xeM8VfDh’s picture

Maybe this is a non-issue. As it turns out, in my case, this might only have been a problem with Libraries release 8.x-3.x-dev (2016-Nov-13), not the current 8.x-3.x-dev release. Testing further now. Either way, Libraries API doesn't seem to be actively maintained and still have no alpha or beta. Would be nice if we could ditch it as a dependency.

xeM8VfDh’s picture

Confirmed this was an issue with the specific 8.x-3.x-dev (2016-Nov-13) Libraries version I was running, and that it is not an issue with the newest version of Libraries 8.x-3.x-dev. If you experience this issue, try updating Libraries and re-running the core update.

My Solution

  1. restore backup
  2. update Libraries Module from 8.x-3.x-dev (2016-Nov-13) to latest 8.x-3.x-dev
  3. Get Pantheon support to restart my webstie container to get around Fatal Error cause by step above (more)
  4. run update.php for good measure
  5. update core to 8.4.0
xeM8VfDh’s picture

Status: Active » Closed (works as designed)
MadSciencePro’s picture

I just noticed that Drupal 8.4.4 appears to have broken my galleries. I updated to the latest Libraries dev and Juicebox dev. Still no luck. I've got Juicebox Pro, so I've placed the folder in the Libraries folder in the docroot. Any suggestions?

UPDATE: The culprit was AdvAgg and Preprocess JS.

xeM8VfDh’s picture

thanks for the info@MadSciencePro