Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUGFIX] Fix extension installation with fixed key #59

Closed
wants to merge 1 commit into from

Conversation

mbrodala
Copy link
Member

The download location for extension packages can be something like ".../vendor/composer/a205122c/" which does not match the extension key, thus use the first item within $EM_CONF instead and be independent from $_EXTKEY.

The download location for extension packages can be something like ".../vendor/composer/a205122c/" which does not match the extension key, thus use the first item within $EM_CONF instead and be independent from $_EXTKEY.
@helhum
Copy link
Contributor

helhum commented Jan 13, 2017

There is only one chance to get this in from my PoV and that is changing the parsing code in every location it exists to do exactly what you propose here. until this happens, I'm closing the PR here.

@helhum helhum closed this Jan 13, 2017
@mbrodala
Copy link
Member Author

OK, totally get that, this needs to be changed in TYPO3 itself first.

@mbrodala mbrodala deleted the patch-1 branch January 13, 2017 09:47
mbrodala added a commit to pagemachine/hairu that referenced this pull request Jan 13, 2017
@helhum
Copy link
Contributor

helhum commented Jan 13, 2017

OK, totally get that, this needs to be changed in TYPO3 itself first.

The only way to more or less reliably change that is to create a lib that parses ext_emconf and use it everywhere.

On top, we must start throwing exception (disallowing TER upload) on parsing errors of this lib.

This is a lot of effort for changing a format that is dated and for the reason people started ignoring a pretty strict requirement of that format.

@mbrodala
Copy link
Member Author

See #60 for more descriptive errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants