update_extension function called twice?
Development and Programming
I am aware of that, but my code does prevent the double database entry which was the real problem. Would preventing that second call require an update to EE or are you thinking of some other way to tackle this?
What I am going to do is update core.extensions.php to have a new class array called $version_numbers. This will be the master array of version numbers for extensions. Whenever an update occurs, whether in core.extension.php or cp.utilities.php, this array will be updated. Prior to doing an update, this is what will be checked. That way, we should be able to make sure we always have the current version number prior to do an update.
OK, I have tested the changes and committed them, so if you want a copy send me an email (not PM) and I might just answer it.
Good to hear you fixed it already!
Unfortunately the extension has to work correctly with older versions so I’ll need to use that extra check anyway.
Cheers, Elwin