Forums

can't login to front end

tokenring 13 Nov, 2011
SYMPTOMS:

I have my 2 sites. (test and live)

http://test.funkyhousebeats.com
http://www.funkyhousebeats.com


if you login (front end) on the live site, this happens.
http://www.funkyhousebeats.com/ (before click login)
http://www.funkyhousebeats.com/index.php (after click login)


on the test site it does this.
http://test.funkyhousebeats.com/ (before click login)
http://test.funkyhousebeats.com/index.php/component/comprofiler/login.html (after click login)

but the user is NOT logged in. I don't even get presented with a bad user/pass message. The difference between the two sites was that I installed and uninstalled a new shoutbox that I was testing. after the uninstall or mabye when it was installed, the login stopped working.


ENVIRONMENT:

PHP Built on: Linux infong 2.4 #1 SMP Thu Nov 25 01:59:22 UTC 2010 i686 GNU/Linux
Database Version: 5.0.91-log
Database Collation: utf8_general_ci
PHP Version: 5.2.17
Web Server: Apache
Web Server to PHP interface: cgi
Joomla! Version: Joomla! 1.5.23 Stable [ senu takaa ama baji ] 04-March-2011 18:00 GMT
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1


NOTES:

I just noticed that if I supply a bad user/pass combo on the live site, it takes me to a similar structured URL like in test. However, there is also a page that alerts you about the bad user/pass and provides a new input box for user/pass input. This is a different set of input boxes than the other ones the user used to create the error.
Harvey51 13 Apr, 2012
I think the most likely reason is a javascript error.

Can you check for this? if not, post back telling me what browser you use.

If you have installed an extension/add-on that you are now not using and everything was okay before, I would fully uninstall the extension making sure the database tables are removed/deleted. This could fix the issue.

Different input boxes makes me think it might be a difference between a Joomla login module and your templates login module, some templates come pre-installed with modules etc and maybe your site is cross using the different versions of modules. Check this and also check any differences between the two sites.
tokenring 30 Apr, 2012
Hey Harvey51,

Again thanks for helping with this. I installed the IE developer toolbar and tried the login again. Before I paste the error messages, I'll let you know that when I installed this new shoutbox announcer, I was actually instructed to change some html (and add some javascript) in the template or site index files. I thoughth I put it all back after the uninstall, but I guess not because of the error.

Here are the details of what happens when I try and login.

SEC7115: :visited and :link styles can only differ by color. Some styles were not applied to :visited.
login.html

HTML1115: X-UA-Compatible META tag ('IE=9, IE=8, chrome=1') ignored because document mode is already finalized.

fastbutton?url=http%3A%2F%2Ftest.funkyhousebeats.com%2F&size=standard&count=true&hl=en-US&jsh=m%3B%2F_%2Fapps-static%2F_%2Fjs%2Fgapi%2F__features__%2Frt%3Dj%2Fver%3DDzS4TuhaHO8.en_US.%2Fsv%3D1%2Fam%3D!OUkz_Oqk3wyIgzT76w%2Fd%3D1%2Frs%3DAItRSTM1bjCp_59I6fj0gy3Bo7pwJFtn6A

SCRIPT5007: Function.prototype.apply: argument is not an Object
rs=AItRSTM1bjCp_59I6fj0gy3Bo7pwJFtn6A, line 142 character 204


I tried to expand the error bug the debugger says that the source is not available. At least we're on to something. Let me check line 142 ;-)

Aaron
tokenring 04 May, 2012
This was the line of code you had to put in your template index.php file

//<link rel="stylesheet" href="<?php echo $mosConfig_live_site;?>/modules/mod_smo_ajax_shoutbox_css.php" type="text/css" />
<script type="text/javascript" src="<?php echo $mosConfig_live_site;?>/modules/mod_smo_ajax_shoutbox_js.php"></script>//

I took it back out after uninstalling the component and module. The add was SOM shoutbox announcer by steve-o-meter I believe.

;-/
tokenring 04 Jan, 2013
Hey guys,

I think I'm closer, but then it get's more strange. I found the error actually and you (Harvey51) were right. Here is the offending line (js error) in my login page.


Firebug reports error on line 450
<p><script type="text/javascript" src="http://widgets.twimg.com/j/2/widget.js"></script><script type="text/javascript">new TWTR.Widget({version: 2,type: 'profile',rpp: 2,interval: 20000, footer: 'Join the Conversation', width: 'auto',height: 50,theme: {shell: {background: '#333333',color: '#ffffff'},tweets: {background: '#000000',color: '#ffffff',links: '#4aed05'}},features: {scrollbar: true,loop: false,live: true,hashtags: true,timestamp: true,avatars: true,behavior: 'all'}}).render().setUser('funkyhousebeats').start();</script>


Chrome (Web developer) reports the same error in line 450
(Uncaught ReferenceError: TWTR is not defined)
<p><script type="text/javascript" src="http://widgets.twimg.com/j/2/widget.js"></script><script type="text/javascript">new TWTR.Widget({version: 2,type: 'profile',rpp: 2,interval: 20000, footer: 'Join the Conversation', width: 'auto',height: 50,theme: {shell: {background: '#333333',color: '#ffffff'},tweets: {background: '#000000',color: '#ffffff',links: '#4aed05'}},features: {scrollbar: true,loop: false,live: true,hashtags: true,timestamp: true,avatars: true,behavior: 'all'}}).render().setUser('funkyhousebeats').start();</script>


However when I browse the filesystem through 1and1.com control panel, FTP and Unix shell I don't see this file.

http://test.funkyhousebeats.com/index.php/component/comprofiler/login.html

That is the URL that shows in the UI (all browsers) after the error, but I can't find that file. Is it generated during runtime and cleaned up after? I can't figure why I can't find this file.

Aaron
GreyHead 05 Jan, 2013
Hi Aaron,

They are SEF URLs so they are made up as needed. If you turn off the SEF URLs you can probably see the real URL that is being used. These look like Community Builder links to me.

Bob
tokenring 05 Jan, 2013
Wow! I don't get it. Not only did it show me the URL, it fixed the problem. When I turned of "SEF friendly URLs" the login is now successful.

Those script errors I mentioned are now gone too. The only thing is that this option is enabled on my test site and doesn't cause any issues. I'll see what I can figure out. Either way, I'm buying you a beer!

;-)

Aaron
This topic is locked and no more replies can be posted.