There is an option in Global Forum Settings that allows the admin to disable the quick reply if they wanted so why not an option to disable the quick login?

it work great for those with custom logins or those people that only want the main login used. Also it works great when working alone side with API, using the API as a login source. Also in some cases if just looks tacky to the design.

Best done with a code in my opinion. I think the table probably has an ID, some CSS would cure. and it'd be 3 lines at the most. And not slow the forum down at all.

k, currently i've been using js because the css leave the head and base images behind. But the js lags the load time just a bit

Edit: wow ok then the css did work

If you need, throw a thread in the Code Requests, and we'll get something thrown up!

lol i already a code I'm not best with JS but I do know what great style.display "none"; works the objuect was to remove the JS from my header and footers cause it was causing the load slower when seen by a guest, but removing it via css removed the lag

Actually this could be a good feature, some don't like to have the QL, and some don't want to mess with coding to do that. If the QR is available to disable at any time through admin panel, then I think the QL should too.

yea i was going to use that was my argument, its the game amount out code to remove either. To be honestly this would rather be easy to implement, all ross would have to do is copy and paste a few code fragment and change the id's from the quick reply to the quick login, shouldn't take more then 10 minutes depending on if the code wants to work right

10 minutes indeed, but I don't know if there'd be that much for this. But then you have the question of should it be skin specific, or not?

Well i can see how this can be setup to be skin specific. The quick reply doesn't always go along great with all the skins, especially those that really get into designing their skins.

Posted By dog199200 on 20th Jan 10 at 12:29pm

 

Well i can see how this can be setup to be skin specific. The quick reply doesn't always go along great with all the skins, especially those that really get into designing their skins.

True.

I'm with Michael on this one - i think having a code to disable it would be the easiest option. I can see the occasional need for it to be removed, but i dont think it's currently a common enough occourance to need it hard coded.

Still, i'm not the one that has to code it

the things is its really annoying how JS codes lag the pages load time. Especially when moving objects that take up a bulk area my main argument on this is it be no different then removing the quick reply, its just a different ID. The reasons for removing the quick login are almost the same as that for removing the quick reply, and anything hard coded or in a template system loads so much better then something that is ran via JS.

The idea of this is about performance as well as design. I'm not saying coding it wouldn't be easier, but the problems with the JS codes is they can be disabled and show things that don't need to be there, causing a lot of complications. I know for how my site setup, the login is designed on the main website and the main website alone.

Posted By dog199200 on 21st Jan 10 at 12:32am

 

the things is its really annoying how JS codes lag the pages load time. Especially when moving objects that take up a bulk area my main argument on this is it be no different then removing the quick reply, its just a different ID. The reasons for removing the quick login are almost the same as that for removing the quick reply, and anything hard coded or in a template system loads so much better then something that is ran via JS.

The idea of this is about performance as well as design. I'm not saying coding it wouldn't be easier, but the problems with the JS codes is they can be disabled and show things that don't need to be there, causing a lot of complications. I know for how my site setup, the login is designed on the main website and the main website alone.

I'm sure CSS can be used!

I tired, I thought it worked, but I forgot i had the JS code in place. The problem is that people who are using head and base images, the css leaves the head and base images and just removed the table.

Simplest thing would be for Ross to give the head/base & quick login all a class of "quick_login"
Much like the welcome table has.

well this is what i use to remove it via JS:

Code:

Select All

 

<script type="text/javascript">
<!--
if(get('loginForm','name')[0]) {
    get('loginForm','name')[0].firstChild.style.display = 'none';
    get('loginForm','name')[0].parentNode.previousSibling.style.display = 'none';
    get('loginForm','name')[0].parentNode.nextSibling.style.display = 'none';
}
//-->
</script>

<script type="text/javascript"> {BR}<!-- {BR}if(get('loginForm','name')[0]) { {BR} get('loginForm','name')[0].firstChild.style.display = 'none'; {BR} get('loginForm','name')[0].parentNode.previousSibling.style.display = 'none'; {BR} get('loginForm','name')[0].parentNode.nextSibling.style.display = 'none'; {BR}} {BR}//--> {BR}</script>

 

i think the id for it all is loginform