| 1 |
Http Request Fail Reset
|
| 2 |
http://drupal.org/project/http_request_fail_reset
|
| 3 |
=================================================
|
| 4 |
|
| 5 |
|
| 6 |
DESCRIPTION
|
| 7 |
------------
|
| 8 |
At Tribute Media we have many sites in various stages of development. Sometimes upon returning to them I have noticed that Update Status has not checked for updates for up to 4 weeks. I then notice that the "drupal_http_request_fails" flag is set.
|
| 9 |
|
| 10 |
It is my understanding that when the variable "drupal_http_request_fails" is set the only way to get Drupal to re-attempt to make a request if to manually reset the variable. Drupal doesn't even check anymore until I reset the flag.
|
| 11 |
|
| 12 |
This module allows the user to configure when to check if the flag is set, and reset the flag. The interval is configurable from 1 minute to days or weeks.
|
| 13 |
|
| 14 |
When the interval times out the module checks "drupal_http_request_fails" to see if it is set to TRUE - meaning that no HTTP requests are being attempted - this module will reset the flag and log to the watchdog table. If the variable is set to FALSE - meaning that there is no problems making HTTP requests - it logs this to the watchdog table as well.
|
| 15 |
|
| 16 |
There are many things that can cause the "drupal_http_request_fails" flag to be set to TRUE, one of these is having the site offline. Drupal tries to make a connection to itself to make sure it can make http requests, if the site is offline it gets the Maintenance page instead of the page it is expecting, so it thinks it cannot make http requests.
|
| 17 |
|
| 18 |
|
| 19 |
REQUIREMENTS
|
| 20 |
------------
|
| 21 |
Drupal 6.x
|
| 22 |
|
| 23 |
|
| 24 |
INSTALLING
|
| 25 |
------------
|
| 26 |
Copy the 'http_request_fail_reset' folder to your sites/all/modules directory.
|
| 27 |
Go to Administer > Site building > Modules. Enable the module.
|
| 28 |
Read more about installing modules at http://drupal.org/node/70151
|
| 29 |
|
| 30 |
|
| 31 |
CONFIGURING AND USING
|
| 32 |
---------------------
|
| 33 |
Go to http://yourdomainnamehere.com/cron.php
|
| 34 |
This will start the automated CRON process.
|
| 35 |
|
| 36 |
If successful Drupal will return a blank page. With the message '$fails = TRUE'.
|
| 37 |
|
| 38 |
Go to http://yourdomainnamehere.com/admin
|
| 39 |
Navigate to ADMINISTER > REPORTS > STATUS REPORT. Error message should be gone.
|
| 40 |
|
| 41 |
|
| 42 |
REPORTING ISSUE. REQUESTING SUPPORT. REQUESTING NEW FEATURE
|
| 43 |
-----------------------------------------------------------
|
| 44 |
1. Go to the module issue queue at http://drupal.org/project/issues/http_request_fail_reset?status=All&categories=All
|
| 45 |
2. Click on CREATE A NEW ISSUE link.
|
| 46 |
3. Fill the form.
|
| 47 |
4. To get a status report on your request go to http://drupal.org/project/issues/user
|
| 48 |
|
| 49 |
|
| 50 |
UPGRADING
|
| 51 |
---------
|
| 52 |
1. One of the most IMPORTANT things to do BEFORE you upgrade, is to backup your site's files and database. More info: http://drupal.org/node/22281
|
| 53 |
2. Disable actual module. To do so go to Administer > Site building > Modules. Disable the module.
|
| 54 |
3. Just overwrite (or replace) the older module folder with the newer version.
|
| 55 |
4. Enable the new module. To do so go to Administer > Site building > Modules. Enable the module.
|
| 56 |
5. Run the update script. To do so go to the following address: www.yourwebsite.com/update.php
|
| 57 |
Follow instructions on screen. You must be log in as an administrator (user #1) to do this step.
|
| 58 |
|
| 59 |
Read more about upgrading modules: http://drupal.org/node/250790
|
Parent Directory
| 
Revision Log
| 
Revision Graph