New user login error: must be greater than zero
Fuzzytek - July 1, 2008 - 07:58
| Project: | WeatherFacti -- from a weather.com xml feed |
| Version: | 6.x-1.9 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I have a critical problem on my site www.RealDivaTv.com
When a new login request is made the following error message is shown....
Must be greater than zero
I'm not sure where to look for the conditions generating the error message. I've looked inside the logs of the site, and the Watchdog table on the database and can't pin this down.
#1
#2
This is not a Drupal Core string.
Look for contribution modules (especially those that can interact with the user login or register form).
#3
Fuzzytek, I've got the same problem on almost all user related forms. So, after a lot module unchecking and form submiting, the error stopped as soon as I disabled the XML Sitemap module, that's still in a dev version.
People must wait or work on it.
#4
I can confirm this bug. It is an addon related bug. With mine, it was due to the Weather Facti module. A good rule I guess is to check the known issues of modules you install before installing and check your add-user functionality after adding too many modules.
#5
It's not even a message error XML Sitemap would print out.
Why do you think it's a bug of this project?
#6
monsterweb reports that he had the problem using the Weather Facti module.
As XML Sitemap doesn't output an error like Must be greater than zero, maybe it's that module to cause the problem.
#7
#8
I can confirm this is the module which raises the error.
At line 255 of weatherfacti.module there is the following code:
<?phpif ($edit['weatherfacti_days'] == "0" || $edit["weatherfacti_days"] == "") {
form_set_error("weatherfacti_days", "Must be greater than zero.");
}
?>
The error is caused by a wrong implementation of
hook_user()(see #360211: Wrong implementation of hook_user()). In short: the module doesn't add its own fields in the user form, but it then checks the value contained in a form field that it didn't even add.I would suggest to investigate more before to report a bug. Who reports the bug should be sure of which module causes the bug; I would rather think twice before to say that the problem is causes by XML Sitemap just because the problem vanished when I disabled xmlsitemap. As it has been proved, that was not the case.