Fancy Login Block appearing in footer/closure when logged in as admin/user1

Fixed in beta4

Hi there

I am reopening this issue because it is happening to me in version 6.x-1.7. The weird thing is I installed and enabled the module over a month ago and now is behaving oddly, like this footer block for logged-in users.

Let me know if further information is required.

Regards

Hi there,

try to hide it with the css add the following css in your style sheet

#fancy_login_login_box{
	display: none;
}

Regards,
Danish Gillani

ayukko - if it was working, and stopped working, it's something you have changed on your site. If you would like to post a link to your site, I'll take a look at it and see if I can help. In the meantime, I'm closing this issue.

Hi

I am getting the same result using beta5 after upgrading from 1.7. i.e. fancy log-in box appearing in the footer. I've tried running updates, un-installing and re-installing - and adding the css snippet. I've checked my css and template files and I can't see any reason for this to be in the footer. The code itself is in the page after

<div id="footer">

and that's where the block is being rendered.

Is there a current security issue with the 1.7 version which makes it unsafe to install? Should I disable this module on current sites until I can upgrade to version 2?

Many thanks
Jon

Version 6.x-1.x is completely unsupported, as it's old and outdated. Please update to version 6.x-2.x and if you are still seeing this issue, please open a new ticket for that version and I'll provide assistance ASAP.

Thank you.

Hi Jaypan

Sorry, I wasn't clear enough about what the problem is. I've upgraded my dev version to version 6.c-2.x - 6.x-2.0-beta5 to be precise - and this is where I am seeing the problem with the log-in box appearing in the footer.

I was asking about how safe version 1 is because I am still using it on live sites as I can't upgrade with the log-in box appearing in the footer. Do you still want me to open a new ticket?

Thanks for your help ion sorting this out

Jon

Version 1 is no less safe than it was when version 2 was released, so if it has been working fine for you, then you can keep using it.

And yes, please open a new ticket for this.

Ideally, I would like to just carry on using version 1, but it's currently getting flagged as being "Not supported". Is there any way this version can be kept as a supported module but marked as not being developed any more? Drupal flags this as follows:

The installed version of at least one of your modules or themes is no longer supported. Upgrading or disabling is strongly recommended! Please see the project homepage for more details.

Which tends to scare end users!

Hello

Unfortunately there is no way to prevent that message, as I am not supporting this version of the module anymore, and therefore have marked it as unsupported. Any bugs or security fixes that are reported will not receive fixes, and therefore the message you are seeing is actually quite appropriate.

I suggest upgrading to version 6.x-2x in a development environment, opening a new ticket, and I will help you work through the issue with the block showing in the footer. When we have it worked out, if it's a problem with the module I will release a new version with a fix, or if it's an issue on your site I will point you at how to fix the problem on your site.