Backend works fine but the login page for the users is blank.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. When I go to the place where there used to be a login form...now there isn't 
anything, it's blank. 
2.
3.

What is the expected output? What do you see instead?

I should see a login form for the username and password. 

I see a blank page

What version of the product are you using? On what operating system?

Not sure on the version to be honest, I just tried a brand new installation and 
the same thing happens as well. 

Please provide any additional information below.

I tried it in Chrome, Firefox and iPhone on 2 different computers (and one 
phone obviously :)

Everything used to work great until this happened. Not sure how to fix it, what 
I tried by now is looking into the index.html and making sure that all the 
javascript, css and other stuff are where they should be and they are. 

Please any help with this would be very appreciated, it's kinda urgent for me. 

Best Regards
Antonio

Original issue reported on code.google.com by antony.m...@gmail.com on 22 Jun 2012 at 6:12

[GoogleCodeExporter]

Sounds like there is either client or backend error. So first check your PHP 
error log, if there is anything. Otherwise, check the chrome web inspector if 
there are any browser errors.

Original comment by samuli.j...@gmail.com on 22 Jun 2012 at 7:12

[GoogleCodeExporter]

Thanks a lot for the fast reply

It seems that there were some files missing, I didn't have that version of 
Mollify and when I tried to replace the missing files with the same files from 
the newest version it didn't help. 

Having wasted my whole day trying to repair the old thing I decided to cut my 
losses and just try to update to the newest version. I installed the newest 
version and it was working fine, this is where things get complicated. 

I have a lot of users in my database and of course I want to transfer them to 
the new version. I have tried everything that came to my mind to do this. First 
I followed the step by step instructions from the read me about a dozen times. 
While when I go to the /backend/update link in the old version it says that 
there is nothing to update, when I try to do the same in the new version it 
just shows a blank page. 

Once I couldn't think of any other way to interpret the pretty straightforward 
instructions I tried to do things semi-manually. I exported the old database 
via phpmyadmin and tried importing it into the installation/database. While it 
worked properly for the folders for some reason it didn't accept the users, my 
guess would be that the database or rather table structure is different in the 
new version so it won't accept the old users. 

I'm somewhat desperate at this point so any help would be deeply appreciated

Eagerly awaiting your reply.
Antonio

Original comment by antony.m...@gmail.com on 22 Jun 2012 at 9:39

[GoogleCodeExporter]

OK, I figured out that you have to be logged in as admin to access the /update 
tool. The problem for me was that I couldn't login as admin with the old 
database in the new version of Mollify because I would get some strange error 
in the backend. 

After a bit of brainstorming I figured it out. I deleted everything, cleared 
out the database and started from scratch. I first installed Mollify from 
scratch, created the new admin during installation and made sure that I login. 
Then I dropped all the tables from the new database and imported the old 
database and just used the /update tool and sure enough...there was the magic 
green button: UPDATE. 

I click Update and it says: Mollify updated to 1.8.8. FANTASTIC!

But of course...there's a rub. None of the old accounts work...when I try to 
login into the backend with my admin I get Authentication failed. When I try to 
login as a user I click on login but nothing happens. 

I am guessing that this has something to do with the hashes, that is just a bit 
out my league so I'm hoping that you will provide some help. 

Thanks in advance
Antonio

Original comment by antony.m...@gmail.com on 22 Jun 2012 at 10:20

[GoogleCodeExporter]

Could you check the PHP error log to see why does it reject the authentication?

Hashes shouldn't be a problem unless it's really old version which upgraded 
from.

Original comment by samuli.j...@gmail.com on 23 Jun 2012 at 7:41

[GoogleCodeExporter]

Uhm, I checked all the instructions I could find and don't really know how to 
check the php error log, sorry. 

Could you please explain ?

On a different note when I added an account directly through phpmyadmin with a 
MD5 hash I created it worked. 

Thanks a lot for your help, you've been fantastic!

Original comment by antony.m...@gmail.com on 23 Jun 2012 at 7:44

[GoogleCodeExporter]

Your web server creates logs to some location, in linux servers this is usually 
/var/log/apache. There you can find PHP error log, where all PHP errors are 
logged. Also, if you enable debug logging in Mollify, this is where you can 
find the debug log as well.

Original comment by samuli.j...@gmail.com on 23 Jun 2012 at 7:51

[GoogleCodeExporter]

Unfortunately I use web hosting so I don't have access to root and therefore 
don't have access to those files. 

Do you have any recommendations on what I could do now ?

Does the fact that when I add a manually created MD5 hashed password via 
phpmyadmin help in any way in finding the problem ?

Sorry to be such an annoyance, trying my best here :)

Original comment by antony.m...@gmail.com on 23 Jun 2012 at 7:57

[GoogleCodeExporter]

Usually web hosting providers do give access to own site logs, at least mine 
does.

But if not, you could try that debug logging to different file under your site 
where you can access it, see 
http://code.google.com/p/mollify/wiki/Troubleshooting

Original comment by samuli.j...@gmail.com on 23 Jun 2012 at 8:04

[GoogleCodeExporter]

Ah, just went through cpanel and found an error log option :)

The errors I get don't seem to be related to the login thing, at least as far 
as I can tell. 

[Sat Jun 23 21:06:29 2012] [error]  File does not exist: 
home/xxx/public_html/xxx.com/404.shtml
[Sat Jun 23 21:06:29 2012] [error] File does not exist: 
/home/xxx/public_html/xxx.com/favicon.ico

What I just noticed right now is that when I try to use one of the old 
accounts, I don't get any kind of error when I try to login with them. 

When I enter some random stuff on the other hand I get a Authentication failed. 

Any idea what this could mean ?

Thanks again!

Original comment by antony.m...@gmail.com on 23 Jun 2012 at 8:11

[GoogleCodeExporter]

Well, using random stuff naturally _should_ cause authentication failure error. 
But if real accounts don't show any error (and fail to log in), that's another 
story. Hard to say why...

Can you give/create me a test account so I can try? And put the debug logging 
on so there will be some more info.

Original comment by samuli.j...@gmail.com on 23 Jun 2012 at 8:20

[GoogleCodeExporter]

Yea, random stuff shows error, imported accounts from previous version just 
stand there, no error and no login. 

Sure I can create an account, just tell me how can I send you the info over and 
I'll do it (don't wanna be sharing it publicly) 

Regarding the debug logging, I just tried enabling it but when I try to I get 
an error. 

This is the code in my config file:

    $SETTINGS = array(
        "timezone" => "Europe/Helsinki" // change this to match your timezone
        "debug" => TRUE,
        "debug_log" => "/mollify/debug.log", //CHANGE THIS  
    );

and this is the error I get:

Protocol error

Got malformed JSON response: 
Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING, expecting ')' 
in /home/xxx/public_html/xxx.com/mollify/backend/configuration.php on line 23

Line 23 is: 

        "debug" => TRUE,

Thanks
Antonio

Original comment by antony.m...@gmail.com on 23 Jun 2012 at 8:38

[GoogleCodeExporter]

You are missing a colon after the timezone line.

But you really should not copy all the examples exactly as they are given, the 
comment "change this" really means that you should change the value when you 
use it. I mean, unless you really live in Finnish timezone, change it, and I'm 
pretty sure your script cannot write into "/mollify/debug.log". Besides, if you 
can access your PHP log, you don't need this "debug_log" setting at all.

I have no doubt you will run into many problems unless you give some thought on 
the values you put in the configuration.

Original comment by samuli.j...@gmail.com on 24 Jun 2012 at 11:36

[GoogleCodeExporter]

I assume this is solved

Original comment by samuli.j...@gmail.com on 6 Jul 2012 at 7:03

• Changed state: Invalid

[GoogleCodeExporter]

Yes, user switched to a different system so now it's out of my hands. 

Thank you for your time and support though, 

Original comment by antony.m...@gmail.com on 7 Jul 2012 at 8:13