WeBidz Auction Manager, related files

[awevtrading]

Hello Folks,
I have found it easy to find a link to download WeBidz Auction Manager (WAM), yet not the supporting information, such as how to download my current listings, and create a template from it. Since it isn't a sticky here in the community forums, nor an entry in the Help/FAQ area, I though I would provide a link here.

Download and tutor (http://www.webidz.com/auctionmanager.php) for WeBidz Auction Manager

I hope this helps other people, and reduce the frustration.

[Lanascountry]

Hi Awevtrading, and a warm welcome to webidz!!
The Admin regularly gives users helps and updates in the
WAM threads..Glad you are here and Thank you!!
http://www.webidz.com/auctionmanager.php

[admin]

Thank you for posting this. We should probably develop better methods to find downloads and supporting info for this program... I know things are kind of scattered around at this time. Been so busy trying to resolve bugs or assist members in getting this running for them, that sometimes the basics are overlooked.

[awevtrading]

Maybe just sticky this message?

If it helps any I can submit a question in the Help/FAQ area, and at least that will get it posted. The only question would be what category. I think Selling would be proper, yet if you have any suggestions, I am willing to listen and help out as I can.

Thanks for the welcome Lanascountry. I'm just flying below the radar, unless I am busy stiring up trouble ;)

[admin]

A sticky is a great idea. We have created a sticky in the general questions and discussions section of the WAM forum, which is titled "Download and Instructions for the Auction Manager". We have closed the thread so there are not any posts made by members, as we don't want this thread to get too cluttered up. We want to use this thread to post frequent questions/issues that members have with the program, and resolutions for these questions/issues.

http://community.webidz.com/showthread.php?t=906

[awevtrading]

Thank you Admin.
I think I will try editing the title of my first post here and mark it resolved so people won't confuse it with the officall message.

Maybe you can lock/close this discausion as well.

I do understand wanting to keep things tidy, and easy to navigate, yet I have one concern. Yes, problems and bugs should all be contained in one forum/topic, yet we don't want to loose a history of how WAM has progressed over time. Short of a Feature Request/Bug Tracking log, or software that helps manage that, maybe we should just see about adding a final comment to a bug report, marking the title of the discausion resolved, and locking the thread?

Just my two cents on the matter before taxes, inflation, and the service fees ;)

[admin]

There is no need for this thread to be locked or closed. Forums are not going to always be tidy, and I do not expect everything to be in a specific place, or locked when not applicable anymore... I just wanted to keep that particular thread tidy, so members can hopefully find resolution for their issues easily. Without having to see the same questions or answers over and over again. If a question or answer that is listed there is discussed in other threads, that is fine... We are not going to post every question or answer there, just the ones that occur frequently.

Possibly creating a similar locked (sticky) thread for bugs, resolutions and updates? So we find a bug and list the details there. Then edit the post when resolution has been provided. We can also list the bigger updates.

[awevtrading]

Sound like a good idea, the dedicated topic/thread. Now, the only thing to consider is how to you track the bug?

Myself, I don't work on large projects, I just throw something together for my own use, maybe just a small script in php to test something, so I just make a note on a scrap of paper, and get back to the problem when the headache leaves. I don't think that a post-it note that I put on my keyboard is going to be tracked that well by other people, so that is not practicle here.

Just an idea that I am throwing out. When someone post a problem it gets a topic id and post id, like my first post in this thread is post 2400. If it is just a minor problem, like a slow connection, then that would not get tracked or a number. While the connection problem may be considerd a bug (more like a safety feature, and a convenice issue), it could be assigned a number like B2400-011308, being compised of B for bug (S for suggestion), the original post number where the bug or suggestion is posted, and the date posted. This way if more than one person starts a new tread with the same problem or suggestion everything can be referred to the first post, and be tracked. And no elaberate bug tracking software is needed.

Just an idea. May be one of my better ones, so if it stinks don't throw rotten eggs at me, just let me down gentle :D

[admin]

Bug tracking systems are great, and we have one between ourselves and our programmers... But I don't see an easy implementaion of such a program with the vBulletin script, without compromising security. Although this is a good idea, I do not think the manhours and security risks involved would merit such change.

The program is fairly new, so bugs are going to be more prevalent starting off, but will disipate over time.

We have actually been talking about a bug tracking system site wide, which would also include the auction manager program. This would not be a system that would be integrated with our vBulliten application though.