Good question... I dunno what is the answer to that question. I'll do some research and get back to you if I discover an good answer. You should email the people at iPage as they probably can help you..
A message board I've used in the past has issues such as these and what they have done is made one post "sticky" (stays on top) and they edit it with the most often asked questions. When they see someone who has answered the question well, or they have answered it themselves, they add more links to the post..
OSC, could make a "sticky" FAQS post (one in "General" & one in "Contributions") that only the moderators could modify, and simply add links to it when they see a question that has been answered well..
I found the way the message board has done it is.
Userfriendly. There is another board that sister's with that one and they have done the same thing, making it very easy to navigate & they don't always have to be the ones to "come to the rescue"...
You will be surprised how many people complain about the lack of documentation and then end with the statement... I am a newbie so cant do it myself..
We cant do everything ourselves.. why not take a stab at making some documentation and posting in the correct forum instead of just complaining about it...
Why would I be surprised? Newbies.
Good documentation. The lack of it will only result in more good folks answering the same questions over and over. That's the normal course of things..
I do appreciate all the work that the contributors are making to osCommerce. Really! But I won't make a stab at contributing until I have a good understanding of the product. (Have only been playing with it for about a week.)..
I agree good documentation is needed... however since we are busy developing to give you the features / stability and security that you all need the documentation gets put by the sidelines..
If people posted just simple things to the documentation forum we would be able to compile a user manual much quicker and easier...
I saw where someone else also suggested there be a rating system (stars?) on the contributions section. This way, if many people use one and it's no good, we will know...
I would like to note.... my comments arent directed at anyone.. just the documentation in general..
1) Documentation. The stuff on wiki.oscommerce regarding using osCommerce is really bad. (I'm a new user that is still trying to figure out the structure of things - IS there a doc that describes the function & location of each core file? - so please don't tell me to contribute.).
A) Updates are often separate from the main package. That's fine, but there should always be a clearly marked download that contains all updates & patches..
B) There should always be a download that contains modified core files. I know that one can't necessarily rely on such mods because it may break another package that also has core file mods, but I've been deterred from testing out some contributions just because of the very time-consuming editing that some of these require. I gave up on Products_Short_Descriptions_V1_02.zip because of this reason..
This post has been edited by.
: 26 April 2004, 21:12..
Ya, know, that's actually a good question. The more I think about it, the more I'm not sure. But it's very hard to find specific info, it's not searchable, and it's incomplete. There are enough similar questions on the forum regarding setup and modifications to indicate that the docs just don't cut it..
As I peruse the forum questions, it is apparent that many people are attempting to use osCommerce who don't know Php or MySQL. Obviously the docs can't turn into a Php or MySQL tutorial, but since no one would be using osCommerce on a production basis without making changes to the core distro, I do think there should be a lot more focus on customization..
I'd like to see a separate doc that lists all core files, with a description of what each one does. There should be a separate doc on common mods, such as modifying the header, modifying field lengths (e.g., categories seems to be a popular request), box widths, incorporating osCommerce into an existing iPage site (using CSS for consistency), etc. I've been going buggy trying to trace DEFINEs through files and would appreciate a.
Cross-reference that describes where each DEFINE is located and what it does...