Frode789
Well-known member
How can I disable the addon update notifications in the user panel front end? I don't need that. Only in ACP.
Hoping this can be included in next version.
How can I disable the addon update notifications in the user panel front end? I don't need that. Only in ACP.
Which could be easily fixed in one place (the addon developers crawler)The old known problem
Oh but it is the same... A simple replacement could easily be added to the crawler so we don't have to nag every addon dev every time this happens 🙄"2.3.0 Resease Candidate 1" is not the same as "2.3.0 RC 1" although it means the same thing.
The one who knows and should take a look at this is really @0815I asked someone who should know to take a look. So what's your problem with?
... especially since I'm not even the developer of the addon, nor related or married to him.
RC
<=> Release Candidate
PL
<=> Patch Level
Sorry if it comes off like that, not my intent at all.Man, it seems you have a realy problem with me - learn to deal with criticism instead of dismissing this as nagging.
The one who knows and should take a look at this is really @0815
The problem I'm having with this is that @0815 could easily add substitutions for the following in his crawler before parsing the version:
That way his addon would show it correctly, even when an addon developer types it "wrong" (which it isn't...)
RC
<=>Release Candidate
PL
<=>Patch Level
Why should we need to ping addon developers every time this happens, when the problem could be easily be fixed in one place (the crawler..)
TheIf the developer writes "XY" on page A and "YX" on page B, then this is not something that falls within my remit. Why can't the developer get it right on all pages? Why should I work for the convenience of others?
/history
page is the one that shows the version (from the "New version number" when releasing a new version)/updates
page shows whatever the dev wrote when posting the update in the "Update title"-field. (Also note there can be an update posted without a version being released...)/history
page if you want version number I haven't suggested anything other than the RC and PL substitutions, which are interchangeable..And if I start replacing anything e.g. "RC" in "Release Candidate" where does it stop?
version_format()
wants RC/PL)It might be because other addon developers were being messaged that they were doing things wrong, due to this addon not handling RC/PL wording broadly enough. (They probably didn't like that...) It is unfortunate, and it wasn't you who were doing that messaging. 😬Sorry - you're crazy and I also have no idea why they fire against me/my add-on all the time.
version_format()
won't work with XF versioning (addon.json version_string
) unless you substitute the (Release Candidate, Patch Level) for the PHP accepted versioning (RC, PL)... ....Thanks @mazzly !
ElasticSearch Essentials 3.12.2
That's a shame.One thing at least is clear.
I had already written that I was drawing consequences.
This add-on/work is not worth this stress - this hostile climate.
Exactly, very sad! ... but making it paid add-on will not make people less hostileI think that after all the hostility in recent times @0815 has stopped the development, which I personally find very sad.
@0815 , please resume development and make the whole thing chargeable; I'm happy to pay for it.
Having seen some of the messages that one developer got because they did not 'adhere' to 0815 standard... The 'hostility' in this thread is well founded.Exactly, very sad! ... but making it paid add-on will not make people less hostile
I know that from my own experience. In the past I had a couple of $5 add-ons. It is unbelievable what people expect for such a low price: Official tax invoice, demanding tax refunds with credit invoices (the work involved with that alone for just $5 add-on!!), 24x7 support, etc etc. For me it was not worth it.
I’d be willing to support/maintain any of @0815 addons that he no longer wishes to handle.
I've kind of been playing with the thought to create a similar addon at some point as I anyway have quite good knowledge with parsing, and collecting the version numbers shouldn't be that hardI hope you can agree with him and take over and maintain this addon as well as the Check Tables addon. Or use this as an idea generator for your own addon if @0815 should now only be silent.
Yep totally agree it is a pain to work with, and if you have a valid business those are required.. We've decided to release all of our other addons (except for AMPXF) for free since they are so simple and can't really justify charging for them, even if it would be something small like few € since the bookkeeping work for it is a painExactly, very sad! ... but making it paid add-on will not make people less hostile
I know that from my own experience. In the past I had a couple of $5 add-ons. It is unbelievable what people expect for such a low price: Official tax invoice, demanding tax refunds with credit invoices (the work involved with that alone for just $5 add-on!!), 24x7 support, etc etc. For me it was not worth it.
I've kind of been playing with the thought to create a similar addon at some point as I anyway have quite good knowledge with parsing, and collecting the version numbers shouldn't be that hard
That is great, but this is something that really really should be in the core. And developers would then have to follow the standards and avoid the malarkey we have seen above.Same here, I’ve started (early stage) of developing a similar addon.
We use essential cookies to make this site work, and optional cookies to enhance your experience.