Project

General

Profile

Actions

Bug #63601

closed

EM shows two entries if composer.json is added to ext_emconf.php

Added by Daniel Wagner almost 10 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Extension Manager
Target version:
-
Start date:
2014-12-05
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
5.5
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

The entries in the EM are a bit confusing.
There should be only one entry per extension.

The key shown is different:
1. one is the extension key from emconf
2. the other is the name from composer ("/" replaced by ".")

One entry (1) is installed and cannot be deleted,
the other (2) is not installed and could be deleted (not tried).

Actions #1

Updated by Markus Klein almost 10 years ago

Please post your emconf and composer.json here, so we can take a look.

Actions #2

Updated by Xavier Perseguers almost 10 years ago

Yes, we lack a concrete example of such a "doubled" extension to be able to reproduce. Thanks

Actions #3

Updated by Daniel Wagner almost 10 years ago

haven't published this experimental extension yet. running this composer file from shell works fine.
could you please give a link to a documentation of the capabilities of the new packagemanager?

important part from composer.json:
"config": {
"vendor-dir": "Resources/Public"
},
"require": {
"Scottjehl/picturefill": "dev-master"
},
"repositories": [ {
"type": "package",
"package": {
"name": "Scottjehl/picturefill",
"version": "dev-master",
"source": {
"url": "https://github.com/scottjehl/picturefill.git",
"type": "git",
"reference": "origin/master"
}
}
}
]

important part from emconf:
$EM_CONF[$_EXTKEY] = array(
'title' => 'picturefill',
'description' => 'picturefill',
'category' => 'fe',
'state' => 'experimental',
'internal' => '',
'uploadfolder' => '0',
'createDirs' => '',
'clearCacheOnLoad' => 0,
'version' => '0.0.3',
'constraints' => array(
'depends' => array(
'php' => '5.3.0-5.5.999',
'typo3' => '6.2.0-7.0.999',
'css_styled_content' => '6.2.0-7.0.999'
),
),
);

Actions #4

Updated by Daniel Wagner almost 10 years ago

PackageStates.php contains both:

'picturefill' => 
array (
'state' => 'active',
'packagePath' => 'typo3conf/ext/picturefill/',
'classesPath' => 'Classes/',
'suggestions' =>
array (
),
),
'responsiveimages.picturefill' =>
array (
'manifestPath' => '',
'composerName' => 'responsiveimages/picturefill',
'state' => 'inactive',
'packagePath' => 'typo3conf/ext/picturefill/',
'classesPath' => 'Classes/',
'suggestions' =>
array (
),
),

I removed both entries from PackageStates and installed the extension again.
This time there exists only one entry "picturefill".

Good and bad news: I cannot reproduce this error.

Actions #5

Updated by Xavier Perseguers almost 10 years ago

Where does this "responsiveimages" (.picturefill) prefix comes from? Your composer states "Scottjehl" as vendor name.

Here is the entries in PackageStates.php I have with https://git.typo3.org/TYPO3CMS/Extensions/sphinx.git/blob/HEAD:/composer.json:

    'sphinx' => 
    array (
      'state' => 'active',
      'packagePath' => 'typo3conf/ext/sphinx/',
      'classesPath' => 'Classes/',
      'suggestions' => 
      array (
      ),
      'manifestPath' => '',
      'composerName' => 'causal/sphinx',
    ),

Entry is not doubled, composerName is referenced.

Actions #6

Updated by Mathias Brodala almost 10 years ago

AFAIR you have to add "type": "typo3-cms-extension" to your extension's composer manifest to avoid the doubled entry.

Actions #7

Updated by Nicole Cordes over 9 years ago

  • Target version set to 7.3 (Packages)
  • Sprint Focus set to On Location Sprint
Actions #8

Updated by Markus Klein over 9 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (7.3 (Packages))
  • Sprint Focus deleted (On Location Sprint)

Is this reproducable?

Actions #9

Updated by Helmut Hummel over 9 years ago

Here is a minimal composer.json required for the package management to work properly:

{
    "name": "vendor/extention-key",
    "type": "typo3-cms-extension",

    "version": "1.0.0",

    "require": {
        "typo3/cms-core": ">=6.2.6,<8.0" 
    },

    "autoload": {
        "psr-4": {
            "Vendor\\ExtensionKey\\": "Classes" 
        }
    },

    "replace": {
        "extention_key": "self.version",
        "typo3-ter/extention-key": "self.version" 
    }
}
Actions #10

Updated by Daniel Goerz about 9 years ago

  • Status changed from Needs Feedback to Closed

With a proper composer.json this issue is not reproducable. I close this issue for now. If anything new comes up feel free to reopen and comment.

Actions

Also available in: Atom PDF