phpBB • Free and Open Source Forum Software

Great Then the work was worth it and I can keep this as an official new feature.

That means that the version check took 85 seconds for you, so a total of 6 passes were required. Since each pass always costs an extra second because of the automatic refresh of the page, the bottom line is 79 seconds. That also means that my previous estimate/calculation was far too optimistic and phpBB can actually determine far less than 66% of the versions. Purely mathematically only ~38% in your case. But as I said, these are all just estimates and always depend on the 3 factors mentioned.

In the meantime, I have already started with b3, which has fixes and improvements for the new version check of b2. In addition, extensions from the CDB are now clearly marked as such in ExtMgr and the corresponding CDB page can now be called up directly on the "Details" page for each extension. As soon as I have published b3, I will announce it here in this topic.

Beta 3 is now available in the 2.1.0 branch. It took longer because I still had to deal with some very annoying details.

When installing Beta 3, the same applies as I already wrote about Beta 2. Please test it and give me feedback. There is also a detailed beta log, but only in German. But with today's translation options, that shouldn't be a problem.

https://github.com/LukeWCS/ext-mgr-plus ... angelog.md

Hi

dimassamid wrote: The checking time was halved

Interesting, but that's not my achievement because I have no influence on the duration of the version check, as this depends on the external factors that I have already mentioned. Also remember that the runtime is given in net terms, i.e. the pure PHP time. The time for automatically reloading the page is not included.

But 36 errors? Are these really all servers that are no longer accessible?

Okay, then the cause is clear, I was just surprised by the large number of errors.

Beta 4 online.

As for the SSL problem, there will be a fix for it in phpBB 3.3.14, which aims to ensure that HTTP>HTTPS redirects are tracked on the respective version server during the version check instead of simply aborting with an error. This affects many CDB extensions, but other extensions that do not come from the CDB can also benefit from it. This change actually comes from phpBB 4.0 and is now also applied to 3.3.

https://github.com/phpbb/phpbb/pull/6715

I have also attached test results from EMP there.

You could also try this phpBB fix in advance and see how many errors are left.