Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest sNews - sNews 1.7 - with its own forums - for discussion and user mods.

Author Topic: [READ FIRST] Guidelines for posting in Bug Report  (Read 3542 times)

Patric Ahlqvist

  • Nobodys perfect, but Im pretty effing close
  • ULTIMATE member
  • ******
  • Karma: 65
  • Posts: 4867
  • I'm a self-made man and worships my creator.
    • p-ahlqvist.com
[READ FIRST] Guidelines for posting in Bug Report
« on: May 23, 2007, 09:01:02 AM »

Here's a little what's and whatnot's on posting inside this section. Only BUGS  found in 1.6 should go here. That is:

What is a Bug?
1) default snews.php, .htaccess or index.php fails to produce intended  result.
2) default coding produces or is prone to a security situation.

What is NOT a Bug?
1) You think it could/should be coded differently to produce the same result.
2) Where coding needs to alter to suit your mod/addon
3) where a mod prevents proper/expected snews operation

So after found something. consider the above before posting.
Logged
"It's only dead fish that goes with the flow... "
Updated

philmoz

  • High flyer
  • ULTIMATE member
  • ******
  • Karma: 161
  • Posts: 1988
    • fiddle 'n fly
[READ FIRST] Guidelines for posting in Bug Report
« Reply #1 on: May 24, 2007, 01:39:45 PM »

Please note.
It is preferable that you post something that you believe fits the above criteria for a bug.
If it is otherwise, please don't be offended if it is moved.

If what you are intending to post fits
What is NOT a Bug?
1) You think it could/should be coded differently to produce the same result.
the best place to put it is in the suggestions forum.

Also, if you have found a bug in the default snews, and have developed a fix for it, please post it along with the bug report. Moderators will see that it is placed in the patch/fix forum.
Logged
Of all the things I have lost, it is my mind that I miss the most.