Jump to:
| Project: | Automated Logout |
| Version: | 6.x-2.3 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
the reason i would like to use this module is for this feature:
"A user can have basic privileges to sensitive data without having to login while inside a local network; however, they will have to login if they are accessing the site from outside a local network."
so this is the solution i've been looking for (http://drupal.org/node/570120)
after installing this module, i went to the admin page, add an IP and assign a user. i'd already make sure that the user is blocked at his account, and set active at ip_authenticator setting.
from any computers that is not logged in to Drupal yet, the site won't be able to be displayed. an error will occur:
Fatal error: Call to undefined function node_get_types() in /home/www/sites/all/modules/og/og.module on line 194
Untick the to set user inactive from ip_authenticator, the site is back to normal.
Other modules that is running on the system that i must mention here is Organic Group, Content Access, CCK, Archive, Messaging, Notifications, Global Redirect, Ubercart.
Anyone having a similar problem?
Thanks in advanced!
Comments
#1
i'd just tried it again, but this time was from my home. the result is weird but true.
With the IP address that I'd set from my office this morning, I was surprised that I did not receive any error though I can't login. It says that the username not been activated or is blocked. Fine, though I'd already make sure that it is set to active at the ip_authenticator settings.
So, I added a new IP and assigned to the SAME username. If I set the new IP to active, now I will get back that error message I got earlier. But I won't get it if it's back to the old one (but still can't login).
This same goes when I create and assign to another new username, will receive the error message.
#2
sorry, it's og.module on line 1941.
and i'd tried both Release version and Dev Snapshots with no success.
when i disabled and uninstalled OG module, i don't see that error anymore. but i am still not able to login, infact, i lost the login block.
#3
any help here? please?
#4
As a stop-gap solution to this problem, change the weight for this module so it loads before OG:
In the {system} database table, look for "ipauth" in the name field. Then set it's weight field to a lighter number, like -1.
This removes the node_get_types() PHP error for me so the site loads again. Not an ideal code-based solution, but it works for now.
#5
I have a similar problem when OG 2.0 is enabled: the site is only accessable anonymously or when logged in as uid=1. When trying to login as any other user, a WSOD appears caused by the error
PHP Fatal error: Call to undefined function node_get_types() in /var/www/drupal/sites/all/modules/og/og.module on line 1941I can ony fix this critical problem by disabling the OG module. No other module seems to make a problem. Any clues how to solve this?
#6
The suggestion from #4 did not work for me. I increased the weight of both the og and og_access modules by 10, cleared the cache - but no luck. Also decreasing the weight of the node module didn't help :-( Only current solution is to disable og at all.
#7
Does anyone here also use Automated Logout on their sites?
Recently my website has this issue after I updated automated logout to 2.3
if i disable automated logout module, it returns to normal.
however, it is very interesting that the error is shown as occurring in og instead of automated logout
#8
Yes - Bingo! I have also updated Automated Logout to 6.x-2.3. Disabling that module makes OG (and the entire site) working again. autologout has a weight of 1000 set! Changing it to -1 also solves the problem!
#9
I also have this problem, beginning after I updated Automated Logout to 6.x-2.3. The solution suggested above (disabling autologout) does not help me, because I am completely locked out of the system. I cannot log in with the first user, and I cannot log in with any other admin user. Therefore I cannot disable any modules. This, for me, is a disastrous and mission critical bug. Please help!
#10
Duplicate of #668192: organic groups incombatibility completely breaks site!
#11
Encountered the same problem with autologout-6.x-2.3 and OG 2.0
User1 can login without the error, but any other user cannot login successfully.
Also, even though user1 can login successfully, prior sessions that are active are not cleared as they were before with 2.2
I did not try changing the weight but simply went back to earlier version as the "vulnerability is mitigated by
the fact that the attacker must have a role with the 'administer autologout' permission."
Not sure if this issue or the duplicate will be kept open.
#12
Yes - I had the same issue come up today, same error message, and after disabling the autologout module my site is functioning as before.
#13
I experienced the same issue after upgrading autologout to 6.x-2.3. I set the weight of the autologout module to -1 and it works.
#14
Same here, running OG 1.4 and having just updated autologout to 2.3.
Setting the weight of autologout to -1 works. Is this going to be fixed soon?
Thanks in advance!!
Jutta