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