[TYPO3-english] Uncaught exception in Extension Manager

[François Suter]

Hi all,

I just updated the extension list on some 6.2.6 installation and now the
Extension Manager crashes with the following uncaught exception:

#1342432101: static_info_tables was requested to be downloaded in
different versions.

As far as I could see, only two extensions had a requirement on
"static_info_tables". I have tried toying with the version numbers in
their respective ext_emconf.php, but to no avail.

Does anyone how I can get my Extension Manager out of this fix?

Cheers

[François Suter]

Hi all,

Post by François Suter
As far as I could see, only two extensions had a requirement on
"static_info_tables". I have tried toying with the version numbers in
their respective ext_emconf.php, but to no avail.

I found the culprit.

In my installation's current state_info_tables can be updated from 6.1.0
to 6.1.2. It is thus added to the EM's list of updatable extension.

sr_language_menu is also updatable, from 6.0.5 to 6.0.6. But
sr_language_menu has a dependency on static_info_tables (which it didn't
have before). And its requirement is static_info_tables 6.0.4 to
6.0.99). The EM resolves that requirement by deciding to fetch the
latest fitting version of state_info_tables, i.e. 6.0.10. Since it is
already trying to fetch 6.1.2, it generates the previously mentioned
exception.

If that exception were caught, the EM would still be usable... It is
obviously impossible to catch each and every exception, but I think that
things like BE modules should have a generic try/catch block early in
their structure and channel exceptions to flash messages.

Cheers

[Markus Klein]

Hi, ran into the same problem.

It is even worse. I changed the dependencies locally, such that lang_menu also requires the current version, but the dependency information is fetched from TER!!!

Couldn't get it to work without removing lang_menu

Kind regards
Markus

------------------------------------------------------------
Markus Klein
TYPO3 CMS Active Contributors Team Member

-----Original Message-----
Sent: Friday, October 24, 2014 12:28 PM
Subject: Re: [TYPO3-english] Uncaught exception in Extension Manager
Hi all,

Post by François Suter
As far as I could see, only two extensions had a requirement on
"static_info_tables". I have tried toying with the version numbers in
their respective ext_emconf.php, but to no avail.

I found the culprit.
In my installation's current state_info_tables can be updated from 6.1.0 to
6.1.2. It is thus added to the EM's list of updatable extension.
sr_language_menu is also updatable, from 6.0.5 to 6.0.6. But
sr_language_menu has a dependency on static_info_tables (which it didn't
have before). And its requirement is static_info_tables 6.0.4 to 6.0.99). The
EM resolves that requirement by deciding to fetch the latest fitting version of
state_info_tables, i.e. 6.0.10. Since it is already trying to fetch 6.1.2, it
generates the previously mentioned exception.
If that exception were caught, the EM would still be usable... It is obviously
impossible to catch each and every exception, but I think that things like BE
modules should have a generic try/catch block early in their structure and
channel exceptions to flash messages.
Cheers
--
Francois Suter
Work: Cobweb Development Sarl - http://www.cobweb.ch
TYPO3: Help the project! - http://typo3.org/contribute/
Appreciate my work? Support me -
http://www.monpetitcoin.com/en/francois/support-me/
_______________________________________________
TYPO3-english mailing list
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

[François Suter]

Hi,

Post by Markus Klein
It is even worse. I changed the dependencies locally, such that
lang_menu also requires the current version, but the dependency
information is fetched from TER!!!

Indeed, because the new versions aren't available locally yet.

To work myself out of this conundrum, I downloaded the extension from
typo3.org as a t3x file, added the dependencies again (they are lost by
typo3.org; I opened a ticket about this), modified them to fit and
uploaded this modified version via SSH :-\ That now works (well, I still
have to check my frontend ;-) ).

Cheers

[Markus Klein]

Post by François Suter
Hi,

Post by Markus Klein
It is even worse. I changed the dependencies locally, such that
lang_menu also requires the current version, but the dependency
information is fetched from TER!!!

Indeed, because the new versions aren't available locally yet.
To work myself out of this conundrum, I downloaded the extension from
typo3.org as a t3x file, added the dependencies again (they are lost by
typo3.org; I opened a ticket about this), modified them to fit and uploaded
this modified version via SSH :-\ That now works (well, I still have to check my
frontend ;-) ).

Frontend is not affected.
How should we handle this problem in EM?

In my case the problem came up, because I uploaded the latest version of static_info_tables manually.
If I downloaded it via EM, the EM should have forbidden to download the new version due to the requirement of language menu ext

Post by François Suter
Cheers
--
Francois Suter
Work: Cobweb Development Sarl - http://www.cobweb.ch
TYPO3: Help the project! - http://typo3.org/contribute/
Appreciate my work? Support me -
http://www.monpetitcoin.com/en/francois/support-me/
_______________________________________________
TYPO3-english mailing list
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

[François Suter]

Hi Markus,

Post by Markus Klein
Frontend is not affected.

Not directly. In this case I was just wondering why sr_language_menu did
support static_info_tables until 6.0.99.

Post by Markus Klein
How should we handle this problem in EM?

I think the EM should show the update icon, but disabled and showing
some error status (like an exclamation mark overlay), with a tooltip
indicating the cause of the problem.

Post by Markus Klein
In my case the problem came up, because I uploaded the latest version of static_info_tables manually.
If I downloaded it via EM, the EM should have forbidden to download the new version due to the requirement of language menu ext

But it doesn't. I encountered the same situation while working only with
the EM. The fact is that it is not downloading anything at that point.
It is just assembling a list of extension that can be updated
(presumably in order to display the update icon).

Cheers

[Markus Klein]

Post by François Suter
Hi Markus,

Post by Markus Klein
Frontend is not affected.

Not directly. In this case I was just wondering why sr_language_menu did
support static_info_tables until 6.0.99.

Post by Markus Klein
How should we handle this problem in EM?

I think the EM should show the update icon, but disabled and showing some
error status (like an exclamation mark overlay), with a tooltip indicating the
cause of the problem.

Post by Markus Klein
In my case the problem came up, because I uploaded the latest version of

static_info_tables manually.

Post by Markus Klein
If I downloaded it via EM, the EM should have forbidden to download
the new version due to the requirement of language menu ext

But it doesn't. I encountered the same situation while working only with the
EM. The fact is that it is not downloading anything at that point.
It is just assembling a list of extension that can be updated (presumably in
order to display the update icon).

Yes it runs the path in the code like it would download the extension.
Debugged that already. Will be another bigger change to EM I fear.

Post by François Suter
Cheers
--
Francois Suter
Work: Cobweb Development Sarl - http://www.cobweb.ch
TYPO3: Help the project! - http://typo3.org/contribute/
Appreciate my work? Support me -
http://www.monpetitcoin.com/en/francois/support-me/
_______________________________________________
TYPO3-english mailing list
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

[Philipp Gampe]

Hi François,

Post by François Suter
If that exception were caught, the EM would still be usable... It is
obviously impossible to catch each and every exception, but I think that
things like BE modules should have a generic try/catch block early in
their structure and channel exceptions to flash messages.

IMHO it must be defined where an exception must be caught (or not) before
introducing the exception.

AFAIK EM exceptions are displayed as flashmessages. This is not the case for
you.

Best regards

[François Suter]

Hi Philipp,

Post by Philipp Gampe
IMHO it must be defined where an exception must be caught (or not) before
introducing the exception.

Yes, that should actually be so.

Post by Philipp Gampe
AFAIK EM exceptions are displayed as flashmessages. This is not the case for
you.

Obviously, this one isn't caught. Of course it's not just a question of
flash message in this case. It should be reflected in a "forbidden"
update icon, for example.

Cheers