Jump to content


AlexJ

Member Since 12 Oct 2009
Offline Last Active Today, 08:13 AM
*****

Posts I've Made

In Topic: Versioning control per category

02 April 2013 - 01:05 AM

Giving a bump ;)


In Topic: I do not like 3.4

05 March 2013 - 08:30 AM

It sounds easy on the surface, but what if the bug is not confirmed and cannot be reproduced?  What if it is a duplicate and someone else has already reported it, or we already spotted it internally and fixed it?  What if the bug report is regarding a code-level comment block that needs to be updated - does that count?  We don't typically treat such things as "bugs" since it doesn't affect the quality of the software, however it can be helpful for developers and we would generally "fix" the problem.  It would be extremely hard to keep up with and account for the many, many nuances of what does and does not qualify as a bug.

 

If bug can't be reproduced then it's not a bug as simple as that.

 

 Anything wrong spotted by end user which requires change in IPS software anywhere = bug.  That's just my opinion. And off course if comments in code need to be update then it's not a bug ..Just create new status: Comment Update.. so those will never be counted in confirmed bug reports.

 

I thought IP.Content is powerful so please excuse me if this suggestion is not possible since I am not an expert in php/sql. Wouldn't be possible to create a custom script which pulls out number of confirmed bug reported by user in a xx period amount of time? 

 

What you guys are doing right now is.. heavily depending on end users to report most of the bugs and then same old story.. Oh we have released beta .. feel free to test it. No I don't need to test if someone can purchase anything from store or not.. It's basic feature and it should work out of the box for Nexus. 

 

If you are facing a problem with the software, please be sure to submit a ticket so that the issue can be addressed.

 

I do always but it's no fun when user PM's me after each Nexus update that they can't purchase anything. Since last 3 nexus release that's what I am doing. Creating support tickets and that's annoying. Each time same reply and then wait begins when Mark fixes it or tells me patch available in next release.

 

We've reviewed your request and unfortunately, it is going to require further investigation. I've escalated your ticket, and it will be addressed as quickly as possible. Because of the advanced nature of your request, please note that it may take longer than usual to fully address your concern. I apologize for this delay and appreciate your patience.


In Topic: I do not like 3.4

05 March 2013 - 05:01 AM

We've done similar things in the past. Our experience has been we get a flood of people who get the beta for the perks and then never use/report anything. 

 

I believe we will have a program for 4.0, which will undergo extensive testing throughout the process due to the massive overhaul.

 

Why not just give the benefits after/once they have reported 50 confirmed bug reports / period of xx amount of time? Normally QA engineers make at least 30$/hr and above.. so giving out 25$ gift coupon for someone reporting 50 bugs in your software is not big deal and I believe is fair trade. You save on QA's which I believe did horrible job on each Nexus release. Each Nexus release is mess compare to other add-ons. Sometimes front end doesn't work and other time no one can buy products from store. Even in new release i am having issue where users can't buy anything from store. What's the point of store/Nexus where users are unable to buy the things? I believe at least this show stopper bugs should be ironed out before release.


In Topic: Can't download IPboard

26 February 2013 - 07:18 AM

Then renew your license you bum!

 

jk..  Make sure you're logged into the right account (if you have multiple) and try again.  If that fails, submit a ticket to Customer Service.

 

Done for time being :)

 

Will just get new license once IP 4.0 is released for my another planned forum :)


In Topic: Can't download IPboard

26 February 2013 - 07:16 AM

Try a hard refresh on that page.

 

That doesn't fixes it. 

 

Logged out.

Delete browser cache and cookies.

Logged in.

 

Still same issue.