J4 Issue ?
avatar richard67
richard67
16 Jun 2019

Steps to reproduce the issue

Happens since PR #25055 has been merged.

  1. Install clean 4.0-dev.
  2. In backend, install some extension which has an update site, e.g. one of the supported languages for 4.0, e.g. German DE.
  3. Try to uninstall the extension.

Expected result

Extension is uninstalled.

Actual result

screen shot 2019-06-16 at 10 43 42

System information (as much as possible)

4.0-dev

Additional comments

The problem comes from PR #25055 having been merged recently, which includes the call to a DB driver function "whereNotIn" which has not been merged yet with any PR into 4.0-dev:

richard@vmkubu01:~/lamp/public_html/joomla-cms-4.0-dev$ find ./ -type f -name "*\.php" -exec grep -il "wherenotin" {} \;
./plugins/extension/joomla/joomla.php
richard@vmkubu01:~/lamp/public_html/joomla-cms-4.0-dev$

Another PR which contains a call to that function is PR #25090 , which has not been merged yet.

The missing function has been added to the database framework with joomla-framework/database#156, but it seems these changes have not been fetched yet.

Running composer update joomla/database locally on my 4.0-dev branch solves the problem.

@alikon Please check and comment.

avatar richard67 richard67 - open - 16 Jun 2019
avatar joomla-cms-bot joomla-cms-bot - labeled - 16 Jun 2019
avatar richard67 richard67 - change - 16 Jun 2019
The description was changed
avatar richard67 richard67 - edited - 16 Jun 2019
avatar richard67 richard67 - change - 16 Jun 2019
The description was changed
avatar richard67 richard67 - edited - 16 Jun 2019
avatar alikon
alikon - comment - 16 Jun 2019

confimed, but joomla-framework/database#156 is merged on the framework database repo, maybe a simple update to the composer can solve it, let's ping @HLeithner

avatar richard67
richard67 - comment - 16 Jun 2019

@alikon Not sure if update via composer will help because there has not been made a new release of the framework database package since that time. Edit: I just see composer should fetch current 2.0-dev branch from the framework database package. But I always do a complete reset of my branch before testing, so a "composer install" seems not to do that. Waiting for what @HLeithner sais.

avatar franz-wohlkoenig franz-wohlkoenig - change - 16 Jun 2019
Labels Added: J4 Issue
avatar franz-wohlkoenig franz-wohlkoenig - labeled - 16 Jun 2019
avatar richard67 richard67 - change - 16 Jun 2019
The description was changed
avatar richard67 richard67 - edited - 16 Jun 2019
avatar richard67 richard67 - change - 16 Jun 2019
The description was changed
avatar richard67 richard67 - edited - 16 Jun 2019
avatar richard67
richard67 - comment - 16 Jun 2019

@alikon @HLeithner Running composer update joomla/database locally on my 4.0-dev branch solves the problem.

avatar richard67 richard67 - change - 16 Jun 2019
The description was changed
avatar richard67 richard67 - edited - 16 Jun 2019
avatar richard67
richard67 - comment - 16 Jun 2019

@alikon @HLeithner It seems I just have to change file composer.lock as follows, right?

Unbenannt

Unbenannt-2

If that is all: Shall I make the PR for that?

avatar richard67
richard67 - comment - 16 Jun 2019

Closing as having PR #25232 .

avatar richard67 richard67 - change - 16 Jun 2019
Status New Closed
Closed_Date 0000-00-00 00:00:00 2019-06-16 12:08:50
Closed_By richard67
avatar richard67 richard67 - close - 16 Jun 2019

Add a Comment

Login with GitHub to post a comment