Check Add-On update [Deleted]

[Deleted member 232995]

Some of my sites have a very large number of addons. Upgrading addons one by one is not doable. To cater to this, I have the following suggestion:

Please consider to add a bulk upgrade function.
Here is how it could work:

1. Display a tickbox for each available upgrade.
2. The admin can check the boxes of the addons that he/she wants to upgrade.
3. Display a Bulk Upgrade button that can be clicked IF boxes have been ticked.
4. If clicked then perform the upgrades in the same way that the 'upgrade from archive' function normally does when multiple files are selected.

Definitely coming... But first I wanted to see how the response is. Also how it goes so.

 

[webbouk]

One small suggestion, when ignoring an add-on update is it possible to exclude the notification that the add-on has an update available, therefore only watched add-ons are noted if an update becomes available.....

admin.php

 

[Deleted member 232995]

One small suggestion, when ignoring an add-on update is it possible to exclude the notification that the add-on has an update available, therefore only watched add-ons are noted if an update becomes available.....

admin.php

View attachment 273402

This is rather a bug should not appear at all!

 

[rdn]

As for this error (although it was posted 2 times it is the same) I can not say anything yet... Since I have to research first.

This addon does request or connect to an external service using TCP on port 443 only, right?
I have blocked all other ports except TCP ports 80 and 443.

 

[Oblivion Knight]

Just submitted a load of "Unsupported" resource URLs.. hope it helps!

However, I think I may have got the one for [XTR] Style Changer incorrect.

 

[Deleted member 232995]

I just saw... Wow thanks a lot... I'll check tomorrow and then go to the update list....

 

[duderuud]

I submitted quite a few too a couple of days back. Did it from my staging server though, hope that will work out.

 

[Deleted member 232995]

I submitted quite a few too a couple of days back. Did it from my staging server though, hope that will work out.

All submissions that were available up to 12 hours ago have been processed.

 

[Deleted member 232995]

Suggestion:
If there are updates, then display an alert or notice to the superadmin. Optimally this would have a setting to turn this on/off.

I would find this really handy, because then I don't even have to log in the admincp to know if there is work to be done. If there is nothing on the front end, I can go check the next. And better yet, if it can be done with alert then I could get a push notification as soon as an update is available for the website.

Has anyone here already had experience of how this works?

 

[Deleted member 232995]

Just submitted a load of "Unsupported" resource URLs.. hope it helps!

However, I think I may have got the one for [XTR] Style Changer incorrect.

I submitted quite a few too a couple of days back. Did it from my staging server though, hope that will work out.

All entries have been published.

 

[Finexes]

Has anyone here already had experience of how this works?

Works great so far! The only thing I noticed is, that I still receive an alert for an add-on I'm currently ignoring. Just as @webbouk reported, the notice for this specific add-on is displayed in the ACP, too.

 

[Deleted member 232995]

Works great so far! The only thing I noticed is, that I still receive an alert for an add-on I'm currently ignoring. Just as @webbouk reported, the notice for this specific add-on is displayed in the ACP, too.

Sorry! There I have worked badly! Is a bug

Will be fixed in the next version! The next one is scheduled for tomorrow or the day after.

 

[Alpha1]

I'm also getting this Guzzle error. Its only on a site running PHP8.1.10 (Centminmod)

GuzzleHttp\Exception\ConnectException: cURL error 35: Peer reports incompatible or unsupported protocol version. (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) in src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php at line 200

1. GuzzleHttp\Handler\CurlFactory::createRejection() in src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php at line 155
2. GuzzleHttp\Handler\CurlFactory::finishError() in src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php at line 105
3. GuzzleHttp\Handler\CurlFactory::finish() in src/vendor/guzzlehttp/guzzle/src/Handler/CurlHandler.php at line 43
4. GuzzleHttp\Handler\CurlHandler->__invoke() in src/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php at line 28
5. GuzzleHttp\Handler\Proxy::GuzzleHttp\Handler\{closure}() in src/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php at line 51
6. GuzzleHttp\Handler\Proxy::GuzzleHttp\Handler\{closure}() in src/vendor/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php at line 66
7. GuzzleHttp\PrepareBodyMiddleware->__invoke() in src/vendor/guzzlehttp/guzzle/src/Middleware.php at line 29
8. GuzzleHttp\Middleware::GuzzleHttp\{closure}() in src/vendor/guzzlehttp/guzzle/src/RedirectMiddleware.php at line 70
9. GuzzleHttp\RedirectMiddleware->__invoke() in src/vendor/guzzlehttp/guzzle/src/Middleware.php at line 59
10. GuzzleHttp\Middleware::GuzzleHttp\{closure}() in src/vendor/guzzlehttp/guzzle/src/HandlerStack.php at line 71
11. GuzzleHttp\HandlerStack->__invoke() in src/vendor/guzzlehttp/guzzle/src/Client.php at line 351
12. GuzzleHttp\Client->transfer() in src/vendor/guzzlehttp/guzzle/src/Client.php at line 162
13. GuzzleHttp\Client->requestAsync() in src/vendor/guzzlehttp/guzzle/src/Client.php at line 182
14. GuzzleHttp\Client->request() in src/vendor/guzzlehttp/guzzle/src/Client.php at line 95
15. GuzzleHttp\Client->__call() in src/addons/X0815/ChkAddOnUpdate/Repository/Update.php at line 18
16. X0815\ChkAddOnUpdate\Repository\Update->getCacheData() in src/addons/X0815/ChkAddOnUpdate/Repository/Update.php at line 32
17. X0815\ChkAddOnUpdate\Repository\Update->rebuildCache() in src/addons/X0815/ChkAddOnUpdate/Listener.php at line 22
18. X0815\ChkAddOnUpdate\Listener::X0815\ChkAddOnUpdate\{closure}() in src/XF/App.php at line 1802
19. XF\App->XF\{closure}() in src/XF/Container.php at line 31
20. XF\Container->offsetGet() in src/XF/App.php at line 2374
21. XF\App->get() in src/addons/X0815/ChkAddOnUpdate/XF/Entity/AddOn.php at line 11
22. X0815\ChkAddOnUpdate\XF\Entity\AddOn->getUpdateAddon() in src/addons/X0815/ChkAddOnUpdate/XF/Entity/AddOn.php at line 60
23. X0815\ChkAddOnUpdate\XF\Entity\AddOn->isNewVersion() in src/addons/X0815/ChkAddOnUpdate/XF/Admin/Controller/Index.php at line 16
24. X0815\ChkAddOnUpdate\XF\Admin\Controller\Index->actionIndex() in src/XF/Mvc/Dispatcher.php at line 352
25. XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 259
26. XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 115
27. XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 57
28. XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2353
29. XF\App->run() in src/XF.php at line 524
30. XF::runApp() in admin.php at line 13

 

[Deleted member 232995]

Server error log
GuzzleHttp\Exception\ConnectException: Macro admin:addon_list_macros :: addon_list_item_menu() error: cURL error 35: Peer reports incompatible or unsupported protocol version. (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:200
Generated by: Admin Sep 15, 2022 at 12:53 AM

I'm also getting this Guzzle error. Its only on a site running PHP8.1.10 (Centminmod)

GuzzleHttp\Exception\ConnectException: cURL error 35: Peer reports incompatible or unsupported protocol version. (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) in src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php at line 200

Do you use Cloudflare?

 

[Alpha1]

Yes, I do.

 

[Deleted member 232995]

Ja, ich will.

I almost thought so! Because the other who posted the same error also uses it. Therefore - with reservation - I see parallels there.

Unfortunately, I have not found a solution to this. Except this link (At bottom): https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:cloudflare-ssl-require-sni

Also my Hoster could do little with this error message.

 

[mcatze]

GuzzleHttp\Exception\ConnectException: cURL error 35:

The cURL error35 says always the same.

CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.

This is sometimes a big problem with Cloudflare. If i am right, there're are two certs if you are using cloudflare. First one between visitor and CF, and the second one between CF and the website/server. There is an option to use the same cert with cloudflare. But i am not a pro, it might be the issue.

 

[mcatze]

@Alpha1 you said that you use cloudflare. Can you say something about your SSL/TSL options at CF? Like these are mine and this add-on works fine.

 

[mcatze]

@Alpha1 could you please check your website, like described here: https://stackoverflow.com/a/55654778

This is the interesting part...

 

[MattW]

Could it be Cloudflare's Firewall that is blocking something? If I use CURL to connect to his site, I'm getting a 403 denied by the firewall and the Managed Challenge. I don't know what this addon is doing or trying to connect to though.