annotate documentation/DEBUG.txt @ 2:e5584a19768b ad

maj module ad
author sly
date Wed, 15 Apr 2009 07:58:32 +0000
parents d8a3998dac8e
children
rev   line source
pierre@0 1 If you are having problems installing or configuring the ad module, please be
pierre@0 2 sure to carefully follow the instructions in INSTALL.txt, and to read through
pierre@0 3 README.txt.
pierre@0 4
sly@2 5 If after reviewing those files you are still having problems with the ad
pierre@0 6 module, please review the project's issue queue to see if you are experiencing
pierre@0 7 a known bug:
pierre@0 8 http://drupal.org/project/issues/ad
pierre@0 9
pierre@0 10 If you're still unable to find the information you need, you can submit a new
pierre@0 11 issue by following the above link. When doing so, it is important that you
pierre@0 12 offer details on how to duplicate the bug that you are experiencing. If you
pierre@0 13 are unable to get ads to appear, be sure to explain what method you are using
pierre@0 14 to try and display ads: blocks, views, ad_embed, etc...
pierre@0 15
pierre@0 16 In the event that ads are not displaying, it is helpful if you collect the
pierre@0 17 following debug information and inculde it in your bug report. Using your
sly@2 18 web browser, view the html source of the page on which you expect
sly@2 19 advertisements to show up. Search for the string "serve.php", then copy and
sly@2 20 paste that entire URL directly into your web browser. It will look something
pierre@0 21 like:
pierre@0 22 http://sample.com/modules/ad/serve.php?q=1&t=23
pierre@0 23
pierre@0 24 Load that URL and see if there are any indications as to why ads are not
pierre@0 25 displaying. If not, add "&debug=2" at the end of the URL:
pierre@0 26 http://sample.com/modules/ad/serve.php?q=1&t=23&debug=2
pierre@0 27
pierre@0 28 (NOTE: you will need to convert "&" to "&" in the url when you cut and
pierre@0 29 paste it from your html source. If you do not do this conversion, most of
pierre@0 30 the URL will be ignored resulting in invalid output.)
pierre@0 31
pierre@0 32 You can then submit the resulting debug output in your bug report.
sly@2 33
sly@2 34 If you are seeing errors, please explain where you are seeing the errors, and
sly@2 35 include the _full_ error message (including any line numbers and file names).
sly@2 36 It is also very helpful to provide detailed instructions on how to duplicate
sly@2 37 these errors.