Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Error seems only for non-logged in users, as this shows up in another (Opera) browser that not is logged in, while my logged in admin browser has no problem at all.
I just had activated the module, so its not sure if this is related to the new release, or just a unknown error because of interaction with one of my (really high amount of) other modules
Comments
Comment #1
ClearXS CreditAttribution: ClearXS commentedI also have more javascript modules that work for the admin (like admin modules and other modules that anonymous doesn't have permission for yet), than for anonymous. More probably this has nothing to do with it; if so the extra modules would correct an error in-spite of causing...
Comment #2
Jaypan CreditAttribution: Jaypan commentedI will fix this in the next release of the module, as it just requires an additional conditional to be added to the code. However, this must be the result of a conflict with one of your other modules, as no one else has had this problem until now. Can I ask you to try to track down the module conflict? Disable your modules one at a time (start with any other modules that have anything to do with registration) until you find the module that causes the conflict. If I know which module it is, I can look specifically at why this is happening in order to work with it instead of around it (which is what I will be doing by adding a conditional).
Comment #3
HumanTex CreditAttribution: HumanTex commentedI just had the same error. I was logged in as admin (user1), then loaded/enabled Fancy, then refreshed the modules page to add another new one and got the error. I temporarily renamed the directory to get a page to display, and was promptly told I didn't have permissions to view the page and was required to log back in to get anything to show at all. Are there permission settings for Fancy that are required for the user1 admin... or, is the module designed to log out any user when enabled for the first time?
I have nothing else that would directly effect registrations or force logouts, or any un-set permissions for anything else. LoginTobogin and iTweak login are both enabled but I've made no changes yet with either one since they've been installed. There are quite a number of other modules enabled, and unfortunately there are far too many to be practical for me to dis/enable them one by one to pin down conflicts.
Comment #4
Jaypan CreditAttribution: Jaypan commentedI believe this error is fixed in version 1.7. Please re-open the issue if you find that it is still occuring.
Comment #6
jmary CreditAttribution: jmary commentedFatal error: Cannot access empty property in /var/www/cebase/sites/all/modules/fancy_login/fancy_login.module on line 165
Comment #7
Jaypan CreditAttribution: Jaypan commentedThis has been fixed in 6.x-1.7. Please upgrade to that.
Comment #8
Jaypan CreditAttribution: Jaypan commentedSorry, I just realized that you are having this problem in 1.7. Please don't change the thread title, it gets confusing as to what you are referring to.
Comment #9
WideGlide94 CreditAttribution: WideGlide94 commentedI just installed the module and received the same error:
Fatal error: Cannot access empty property in [MyPath]\sites\all\modules\fancy_login\fancy_login.module on line 165
I was logged in as User-1 downloaded and enabled the module, logged out and BOOM! ugly message on white screen. I renamed the directory, logged back in, disabled LoginTobogin and iTweak one-at-a-time re-enabled Fancy Login each time but still getting the same message.
In addition, I disabled the Account Menu module still with no luck.
Environment:
Fancy Login: 6.x=1.7
Drupal Version: 6.20
PHP: 5.3.5
MySQL 5.1.5
Apache 2.2
Comment #10
Jaypan CreditAttribution: Jaypan commentedThe module has been mostly re-written in version 6.x-2.x, so this issue should have been fixed. If it still persists with the new version, please open a new ticket for that version with the appropriate details.
Comment #11
Jaypan CreditAttribution: Jaypan commented