Jump to:
| Project: | Toggle WWW |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | Toggle www |
Issue Summary
I believe this module would provide great effect if it were fully functional. I'd like to contribute towards a fix, but I'm still learning the right techniques for programming for Drupal.
I like this module because it's perfect for preventing double site listings. http://www.example.com and http://example.com do reduce page rank, and a lot of web masters prefer their page rank stay grouped instead of having 2.
Here's two bugs I've encountered when applying this module. Sometimes it will not appear until several hours later, and sometimes it will start instantly. Maybe it has something to do with actions that occur on a Drupal site?
When you attempt to use autocomplete functions
- It will give you an http 0 error
- I think it has something to do with directories. it's looking for the http://www.example.com directory, when the http://example.com is the one it's supposed to be using.
When you attempt to go to example.com/update.php
- An unrecoverable error has occurred. You can find the error message below. It is advised to copy it to the clipboard for reference.
Please continue to the error page
An HTTP error 0 occurred. http://example.com/update.php?id=34&op=do
Note: I haven't tested the module in http://example.com format, only with the redirecting to the www.jname.com format. Maybe the issue won't occur if you keep everything in the http://example.com format, but then again isn't everyone so used to the www.example.com format?
This is my first bug report, I hope the Drupal community finds this information useful. Do not use this module yet! :)
Comments
#1
This problem is maybe caused by a wrong configuration of $base_url and should be prevented by inserting a warning message to the requirements system. Therefore I created a new issue #1046682: Install/Update process fails if $base_url is set to a wrong URL. Please close this bug as a duplicate, if this solves your issue. Thanks!