vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)
-   -   iTrader Quarantined? (https://vborg.vbsupport.ru/showthread.php?t=279368)

twista46 03-11-2012 05:47 PM

Pls Release a Comeback from Itrader :):)

meissenation 03-16-2012 12:06 PM

Seriously... still nothing?

cellarius 03-16-2012 12:08 PM

What do you expect to happen? Lynne has pointed out the options.

meissenation 03-16-2012 12:26 PM

So because the coder has lost interest we all just have to give up on ever using iTrader again? What I expected to happen is vBulletin.org staff to go "Hey, this is a pretty popular mod, since we already know what the flaw is, we can just fix it..." Or at the very least another coder to step in and rescue the mod. I already said I'm willing to chip in money to have the mod fixed, I'm sure others would join in if someone would just help us...

cellarius 03-16-2012 12:33 PM

If he can't or won't be contacted: yes. You can pay a coder to fix your installation, bu you can't publish it here. You could post the changes necessary in the thread, though, I guess. Or offer diff-patches. You also can contact the coder of the vB3-Version to get his o.k. to start from there to make a fresh adaption to vB4. You also could be patient. The addon has been quarantined for two weeks now. Please realize that people have lives beside offering addons for free at vb.org. The coder may be temporarily unavailable for a variety of reasons.

Addons on vb.org come for free, and they come without any guarantee whatsoever, especially not with a guarantee that fixes for issues will be provided in short time (or at all). The coder owes you nothing, and much less do the admins or mods of vb.org. You surely were aware of that fact when you downloaded and installed the addon, were you not?

meissenation 03-16-2012 02:49 PM

We can't post the changes in the thread because we can't post in the thread at all -- that was why I created this thread.

Yes I was aware of everything that you said, but the fact that the coder has not been on the site since the beginning of February lends me to think he wasn't concerned with his modification being quarantined. I understand that no one owes us anything which is why I'm offering to pay for someone to fix it. It's just surprising when we're talking about such a popular modification like iTrader. When IbpArcade was quarantined recently, it was fixed within a few days.

Again, the frustration is that there are people who know what the problem is and how to fix it but won't.

cellarius 03-16-2012 05:49 PM

Quote:

Originally Posted by meissenation (Post 2310082)
Yes I was aware of everything that you said, but the fact that the coder has not been on the site since the beginning of February lends me to think he wasn't concerned with his modification being quarantined.

You should not be so quick and harsh in your judgement if you lack any information. There are many causes I can think of why I would not be able to visit this site for a long time, or not anymore at all. Several of them not very pleasant or of the choosing of the coder.

Rushyman 03-16-2012 05:58 PM

I am guessing the previous version before the last update also had the same security issue?

Moving to Xenforo is not an option really.

meissenation 03-16-2012 05:59 PM

My "harshness" is not directed at the coder. It would be nice if he could pop in and let us know he got the e-mail and plans to fix it or not, but again my main frustration is that vB.org staff found the flaw and I know they have competent coders on their team that could fix it in a handful of minutes if they wanted to.

In other modifications on this site, you will routinely see people other than the developer offering file edits to slightly modify or enhance a product. Fixing the security flaw in this product should be no different. I know we don't want to "give away" what the security risk is to allow the modification be exploited even more easily, but can't the vb.org staff that know what the flaw is just fix the bad line(s) of code and then attach the updated file so we can all move on? It's just frustrating that there are people on this site that know what the flaw is, know how to fix it, and yet just sit back saying "Well, too bad - it's the developer's problem to fix, not mine..."

Andyrew 03-16-2012 06:09 PM

I contacted vbenhancer last week and asked if he could give us a fix, he said he would look in to it.


All times are GMT. The time now is 06:47 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01251 seconds
  • Memory Usage 1,740KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete