Check Add-On update

Check Add-On update 1.0.0 Beta 9

No permission to download

Paul

Well-known member
@0815

Silly Q maybe - for those that are hosted outside of XF - why not set an "url" and/or "Login"/"pass" for each site??
I have a few that are (for example) OZZMods for example - those are showing completely blank....

1663342938914.png

If i am honest, even something checking the version of release is a bonus, since half the battle is to KNOW there's a release..
Lots of these are hosted on individual users/teams sites, but each use the same layout... An example on the above..


1663343080392.png

At least i would know there's an update, even if i cant directly download it :)

Anyhow - thank you for something mega-useful - means i can spend less time checking for updates and more time creating stuff :)
 

Mr. Jinx

Well-known member
Silly Q maybe - for those that are hosted outside of XF - why not set an "url" and/or "Login"/"pass" for each site??
I have a few that are (for example) OZZMods for example - those are showing completely blank....
I don't agree with this, that is so hard to maintain. If every add-on is published on XF, everything works fine without adding custom URLs.
Just ask your favorite developer to stay up-to-date on this site.
 

Paul

Well-known member
I don't agree with this, that is so hard to maintain. If every add-on is published on XF, everything works fine without adding custom URLs.
Just ask your favorite developer to stay up-to-date on this site.
You would be surprised how many people have add-ons that arent published on XF. I would say over 50% of mine arent... some are because the developer prefers to support directly on their site, others because they are pre-releases... (and again may never appear on XF.com).

Either way, if the option was there, it would benefit those that take that path... and wouldnt harm those that dont...

Not sure what you mean by " hard to maintain"? A link to the resource, be it on XF.com or off, they all seem to follow a similar format/layout (See the Ozzmods one i posted above) - worst case they only need to parse the release version to be able to show if there has been an update - i do agree that to make it a one-click option would be more of a challenge :)
 

GameNet

Active member
Silly Q maybe - for those that are hosted outside of XF - why not set an "url" and/or "Login"/"pass" for each site??
I have a few that are (for example) OZZMods for example - those are showing completely blank....
Yes I agree unfortunately I have some xf add-ons available on my developer website and I haven’t released them here on xenforo.com as its needed more work!

It’s should be Available only if the developer website doesn’t have any nulled plugin or restrict items on there website (just my suggestion)
 

Alpha1

Well-known member
Not sure what you mean by " hard to maintain"?
The upgrade notification comes from the API that is maintained by the developer. The developer keeps track of all the addons and versions. And needs to be able to find those somewhere. For private addons its impossible. For public addons on hundreds of external websites its not really doable. Especially not on websites that run non-xf software. And then there is the issue of nulled software.

I do hope that some external sites for popular developers will be supported. But a very limited number of highly popular devs so that this great addon will not beccome impossible to maintain. Its really great functionality. IMHO its essential functionality. And free as well.
 

Oblivion Knight

Well-known member
Is there anything that can be done about false positives, aside from ignoring the add-on (either figuratively or literally)?

Perhaps an alternative "ignore" method, where you can ignore the current latest version only? If it gets updated again, the add-on alerts you as normal?

1663396830213.png
1663396873961.png
1663396992603.png
1663397078923.png
1663397142629.png


--EDIT--
I see Beta 7 appears to have gone some way to resolving this - two of these have dropped off the list :)
 
Last edited:

0815

Well-known member
You would be surprised how many people have add-ons that arent published on XF. I would say over 50% of mine arent... some are because the developer prefers to support directly on their site, others because they are pre-releases... (and again may never appear on XF.com).

Either way, if the option was there, it would benefit those that take that path... and wouldnt harm those that dont...

Not sure what you mean by " hard to maintain"? A link to the resource, be it on XF.com or off, they all seem to follow a similar format/layout (See the Ozzmods one i posted above) - worst case they only need to parse the release version to be able to show if there has been an update - i do agree that to make it a one-click option would be more of a challenge :)

I had already written something about this topic in the FAQ.


If I start making this extra sausage for everyone, I will spend my life....

There are other reasons:
I can't know how serious the developer is - does he have an XF license? Does he distribute nulled? I can't check every provider for his seriousness.
Oh yes and Brivi***** would have to record then also! SORRY NO!

But Alpha has made an interesting suggestion:

Establish certain standards, rules that must be met. here I am still thinking. But this is also difficult.
I would say the largest providers.
xon, th, bob, andyB and a few more. Finished


The problem is more technical.
Everybody uses other tools from XF - or no XF. Most of these tools do not provide a version number which I urgently need...

I can only minimally understand why developers do not offer their add-ons on XF. Makes little sense to me - since XF is a one-stop shop and I certainly get the most customers here. At least I think so.
Sure you have double work... No pain, no gain.

Central marketplaces are - from my point of view - essential. (apple, Android etc.)


So one thing I can state 100% now.
If I should also be active outside of XF. Then only with very very strict rules. The next hurdle, the developers have to play along and provide me with the information I need. There I see another big hurdle.


Because many do not even manage to specify the same version string in the "addon.json" as here in the RM.
Examples
RM = 1.0.0 b1
addon.json = 1.0.0 beta 1

or

RM = 2022-05-04
addon.json = 1.0.0

I can't make a comparison with this.
Therefore, false reports will occur from time to time.
 

Joeychgo

Well-known member
This from this addon?

Code:
GuzzleHttp\Exception\ConnectException: cURL error 28: Connection timed out after 10000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:200

Code:
#0 src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(155): GuzzleHttp\Handler\CurlFactory::createRejection(Object(GuzzleHttp\Handler\EasyHandle), Array)
#1 src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(105): GuzzleHttp\Handler\CurlFactory::finishError(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object(GuzzleHttp\Handler\CurlFactory))
#2 src/vendor/guzzlehttp/guzzle/src/Handler/CurlHandler.php(43): GuzzleHttp\Handler\CurlFactory::finish(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object(GuzzleHttp\Handler\CurlFactory))
#3 src/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php(28): GuzzleHttp\Handler\CurlHandler->__invoke(Object(GuzzleHttp\Psr7\Request), Array)
#4 src/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php(51): GuzzleHttp\Handler\Proxy::GuzzleHttp\Handler\{closure}(Object(GuzzleHttp\Psr7\Request), Array)
#5 src/vendor/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php(66): GuzzleHttp\Handler\Proxy::GuzzleHttp\Handler\{closure}(Object(GuzzleHttp\Psr7\Request), Array)
#6 src/vendor/guzzlehttp/guzzle/src/Middleware.php(29): GuzzleHttp\PrepareBodyMiddleware->__invoke(Object(GuzzleHttp\Psr7\Request), Array)
#7 src/vendor/guzzlehttp/guzzle/src/RedirectMiddleware.php(70): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Request), Array)
#8 src/vendor/guzzlehttp/guzzle/src/Middleware.php(59): GuzzleHttp\RedirectMiddleware->__invoke(Object(GuzzleHttp\Psr7\Request), Array)
#9 src/vendor/guzzlehttp/guzzle/src/HandlerStack.php(71): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Request), Array)
#10 src/vendor/guzzlehttp/guzzle/src/Client.php(351): GuzzleHttp\HandlerStack->__invoke(Object(GuzzleHttp\Psr7\Request), Array)
#11 src/vendor/guzzlehttp/guzzle/src/Client.php(162): GuzzleHttp\Client->transfer(Object(GuzzleHttp\Psr7\Request), Array)
#12 src/vendor/guzzlehttp/guzzle/src/Client.php(182): GuzzleHttp\Client->requestAsync('post', Object(GuzzleHttp\Psr7\Uri), Array)
#13 src/vendor/guzzlehttp/guzzle/src/Client.php(95): GuzzleHttp\Client->request('post', 'https://addons....', Array)
#14 src/addons/X0815/ChkAddOnUpdate/Repository/Update.php(18): GuzzleHttp\Client->__call('post', Array)
#15 src/addons/X0815/ChkAddOnUpdate/Repository/Update.php(32): X0815\ChkAddOnUpdate\Repository\Update->getCacheData()
#16 src/addons/X0815/ChkAddOnUpdate/Cron/Updater.php(11): X0815\ChkAddOnUpdate\Repository\Update->rebuildCache()
#17 src/XF/Job/Cron.php(37): X0815\ChkAddOnUpdate\Cron\Updater::runUpdater(Object(XF\Entity\CronEntry))
#18 src/XF/Job/Manager.php(260): XF\Job\Cron->run(8)
#19 src/XF/Job/Manager.php(202): XF\Job\Manager->runJobInternal(Array, 8)
#20 src/XF/Job/Manager.php(86): XF\Job\Manager->runJobEntry(Array, 8)
#21 job.php(43): XF\Job\Manager->runQueue(false, 8)
#22 {main}
 

0815

Well-known member
This from this addon?
According to "Stack trace" yes.
An hour ago the server had timed out. According to my hoster because of a ddos.
Currently everything seems to be running again.

Whether your error message fell in that time period or was from the day before yesterday when there was a move or or or.... Unfortunately, I cannot tell you.

Can only tell you: YES - it results from the Add_on... and says that your server could not connect to my server...
 

Hoffi

Well-known member
It would be good, that you built an own AddOn Overview page.

I just needed to disable the listeners in my config.php - and then the AddOn List is not working. So its a lot of harder to search for issues.
For me it was easy with CLI deactivation of this AddOn, but not everyone has this option.
 

Joeychgo

Well-known member
According to "Stack trace" yes.
An hour ago the server had timed out. According to my hoster because of a ddos.
Currently everything seems to be running again.

Whether your error message fell in that time period or was from the day before yesterday when there was a move or or or.... Unfortunately, I cannot tell you.

Can only tell you: YES - it results from the Add_on... and says that your server could not connect to my server...

just to make you aware - I had another error this morning at 1.03am
 

mcatze

Well-known member
Hi @0815 i got this error after a fresh installation when i tried directly after the installation process reload the addon page.

Code:
GuzzleHttp\Exception\ConnectException: cURL error 28: Connection timed out after 10000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) in src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php at line 200
GuzzleHttp\Handler\CurlFactory::createRejection() in src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php at line 155
GuzzleHttp\Handler\CurlFactory::finishError() in src/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php at line 105
GuzzleHttp\Handler\CurlFactory::finish() in src/vendor/guzzlehttp/guzzle/src/Handler/CurlHandler.php at line 43
GuzzleHttp\Handler\CurlHandler->__invoke() in src/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php at line 28
GuzzleHttp\Handler\Proxy::GuzzleHttp\Handler\{closure}() in src/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php at line 51
GuzzleHttp\Handler\Proxy::GuzzleHttp\Handler\{closure}() in src/vendor/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php at line 66
GuzzleHttp\PrepareBodyMiddleware->__invoke() in src/vendor/guzzlehttp/guzzle/src/Middleware.php at line 29
GuzzleHttp\Middleware::GuzzleHttp\{closure}() in src/vendor/guzzlehttp/guzzle/src/RedirectMiddleware.php at line 70
GuzzleHttp\RedirectMiddleware->__invoke() in src/vendor/guzzlehttp/guzzle/src/Middleware.php at line 59
GuzzleHttp\Middleware::GuzzleHttp\{closure}() in src/vendor/guzzlehttp/guzzle/src/HandlerStack.php at line 71
GuzzleHttp\HandlerStack->__invoke() in src/vendor/guzzlehttp/guzzle/src/Client.php at line 351
GuzzleHttp\Client->transfer() in src/vendor/guzzlehttp/guzzle/src/Client.php at line 162
GuzzleHttp\Client->requestAsync() in src/vendor/guzzlehttp/guzzle/src/Client.php at line 182
GuzzleHttp\Client->request() in src/vendor/guzzlehttp/guzzle/src/Client.php at line 95
GuzzleHttp\Client->__call() in src/addons/X0815/ChkAddOnUpdate/Repository/Update.php at line 18
X0815\ChkAddOnUpdate\Repository\Update->getCacheData() in src/addons/X0815/ChkAddOnUpdate/Repository/Update.php at line 32
X0815\ChkAddOnUpdate\Repository\Update->rebuildCache() in src/addons/X0815/ChkAddOnUpdate/Listener.php at line 21
X0815\ChkAddOnUpdate\Listener::X0815\ChkAddOnUpdate\{closure}() in src/XF/App.php at line 1802
XF\App->XF\{closure}() in src/XF/Container.php at line 31
XF\Container->offsetGet() in src/XF/App.php at line 2374
XF\App->get() in src/addons/X0815/ChkAddOnUpdate/XF/Entity/AddOn.php at line 11
X0815\ChkAddOnUpdate\XF\Entity\AddOn->getUpdateAddon() in src/addons/X0815/ChkAddOnUpdate/XF/Entity/AddOn.php at line 60
X0815\ChkAddOnUpdate\XF\Entity\AddOn->isNewVersion() in src/addons/X0815/ChkAddOnUpdate/XF/Admin/Controller/Index.php at line 16
X0815\ChkAddOnUpdate\XF\Admin\Controller\Index->actionIndex() in src/addons/SV/RedisCache/XF/Admin/Controller/Index.php at line 14
SV\RedisCache\XF\Admin\Controller\Index->actionIndex() in src/addons/SV/SearchImprovements/XF/Admin/Controller/Index.php at line 18
SV\SearchImprovements\XF\Admin\Controller\Index->actionIndex() in src/addons/SV/DailyStatistics/XF/Admin/Controller/Index.php at line 21
SV\DailyStatistics\XF\Admin\Controller\Index->actionIndex() in src/XF/Mvc/Dispatcher.php at line 352
XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 259
XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 115
XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 57
XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2353
XF\App->run() in src/XF.php at line 524
XF::runApp() in admin.php at line 13
 

0815

Well-known member
I just asked my hoster again.... According to them, the IP (I have sharedhost) is subject to a DDOS... Therefore, it comes again and again to disturbances :(
 
Top