Top 13 Reasons why your post wasn't answered.

[wizardsandwars]

Are you getting frustrated because your call for help seems to be going unheeded? Are you wondering, "Where have all the experts gone?"

 

Well, read no further, friend, here's a brief list of reasons why your post my have gone unanswered.

 

 

13.) You didn't read the Sticky thread at the top of the forum, and therefore disregard form rules.

 

12.) You posted in the wrong forum.

 

11.) You posted the same exact post in more than one forum (see #9).

 

10.) You Posted either in all caps, or in one long run on sentence, making your post very difficult to read.

 

9.) You posted more than a couple of questions in a single post.

 

8.) You posted a question that was answered in another thread on the first page of the forum you are in.

 

7.) You posted asking for the documentation site.

http://wiki.oscommerce.com/Top

 

6.) You posted a question that is listed in the FAQs.

http://wiki.oscommerce.com/helpHowtoTextGeneral

 

5.) You posted a question about features of OSC.

http://www.oscommerce.com/about/features

 

4.) You posted a question that has been asked more than 100 times in the previous 30 days (estimated).

 

3.) You did not provide enough detail for anyone to be able to troubleshoot your problem. (OSC Version, Contributions added, last changed script...etc)

 

2.) You asked, "Is it possible". Of course it is.

 

And the number one reason why your post wasn't answered.....

 

1.) You proclaim that you have "successfully installed" a contribution, but you include an error that you receive that indicates that this was obviously not the case.

 

I hope this helps.

[Rumble]

lol wizard, you wake up on the wrong side of the bed this morning?

 

But i feel for ya man, i come on here trying to help people and end up shuffling through the same queries that I might have answered previously or seen only moments ago. You're over 1500 posts, you got any hair left?

 

The search engine is a powerful tool if people would only try variations of their problem.

 

Heres some more hints to take note.

 

Parse error = you tampered with something and forgot to cross your T's and dot you I's. Check the syntax of what you've edite, make sure all open brackets have a corresponding closing bracket etc etc

 

Try undoing what you did last by using the back up you should have made before you messed things up. Backup backup backup!

 

If you get some good advice that has worked, take some time out by saying so on the form post so other looking at it in the future know its a valid solution!

 

:)

[wizardsandwars]

Nah, actually, I was just trying to be a little humorous and provide some usefull information at the same time.

[wizardsandwars]

Here's a couple more....

 

 

You posted a title saying, "URGENT" or "EMERGENCY" and then you state in your post that your site isn't even live yet.

 

You post asking about how to write rudimentary HTML or PHP stating that "your client" need this functionality.