TYPO3 Core

Is your issue something "different" than #38406? If not, why would we need another issue? If its the same, we should close this one and give the original one the required attention. Thanks!

Hi Ernesto, the described problem in 38406 is a different one but the the area where it points to is the same. thus if you take a short look into it and do what I suggest there, you may well close this one. Just didn't know how to raise attention otherwise. BR!

For us to understand the problem it would be good to have "steps to reproduce" in your report, which means: what should I do (for example in the extension manager) to see the bug happening? First we need to understand what's wrong then we can concentrate on the solution.

And we appreciate that you already jumped in with a potential solution.

Thanks for your help!

The problem is that with the current SQL statement you will never find any hint telling you that there is an extension update available - even if there is one in your local cache_extension table because the flag "is latest version" is not set for any extension. So the first step would be to check for one or two sample extension in this table if the lastersion is set correctly. I get a timeout before these updates happens because due to the nature of the current script each version for each extension is tried to be updates with lastextension =1 and this is done not in one statement but in 29k separate statements. hope that helps!

Since I've successfully updated tons of extensions already using the new EM, I would be glad if you give us more information on "where to click" and "what you expect" and "what you see otherwise". This is what I meant with "steps to reproduce". What exactly (for the user) is broken because of this bug?

For example in the EM, I go to

• Import Extensions
• Update the extension list
• Go to "Available Extensions"
• Filter by "Only display updateable extensions"
• I get a list of local extensions that require update
• Hovering over the icon to update I see which is the current and the new versions

So for me it looks like it is working correctly? Or is some specific update "hidden" because of the bug? Do you have an example?

See my point?

Hi Ernesto,

I think I owe you a beer for your time (would it reach you at the cron-it address?). My problem still exists according to your description I never see any result if I filter "Only display updateable extensions". I just checked it again and the "version" in the described lines is not the reason why this check fails on my environment (although it is data never used within the function insertLastVersion nor is it returned. so you can close this issue and I try to find the reason for the timeout that prevents my environment from completing this function.

So you are using DBAL and any "exotic" database (postgreSQL or oracle)? Or just plain MySQL?

We have plenty of beer in stock here at cron it, thanks! :)

no, for me it is pure mysql.