Problem/Motivation

As of #3374434 and release 2.0.2 Focal point no longer uses jquery_ui_draggable. However the dependency still exists in the composer.json file, so it is still being installed on the system even when it is not required.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

gordon created an issue. See original summary.

gordon’s picture

Assigned: Unassigned » gordon
Status: Active » Needs review

Ive created a MR to fix this issue.

keshavv’s picture

Status: Needs review » Reviewed & tested by the community

I have reviewed the parent issue as mentioned in the description,
We need to remove it.
Moving to RTBC

Nuuou made their first commit to this issue’s fork.

damienmckenna’s picture

Assigned: gordon » Unassigned

Thanks for this fix.

As a reminder, please set the "Assigned" field to "Unassigned" when you're finished with your work, that lets others know that you're finished and that they can then take it from there.

Rajeshreeputra made their first commit to this issue’s fork.

rajeshreeputra’s picture

Status: Reviewed & tested by the community » Fixed

Merged, release to follow shortly! Thank you for working on it.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

dbrowncode’s picture

@Rajeshreeputra any update on a release for this? Thanks

yobottehg’s picture

This caught me totally unguarded and will potentially also catch others offguard.

As we only had these libraries installed because of focal_point we could not run config import or install from existing config anymore as these were not downloaded anymore.

So if anyone else sees this:
Unable to install the jquery_ui module since it does not exist. or
Unable to install the jquery_ui_draggable module since it does not exist.

You need to either add these to your composer json see here :
https://www.drupal.org/docs/upgrading-drupal/upgrading-from-drupal-8-or-...

Or remove them from you staging config in core.extension.yml.

bsnodgrass’s picture

It seems a related new issue should be posted about the issue notes in #12
We have experienced exactly this same thing doing updates on a number of sites.

rajeshreeputra’s picture

Ohh... I think this need to be fixed then before release.

Will take a look at it on how to overcome problem statement provided in #12.