No input file specified.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Attempting to access the admin backend
2. [mollify_installation_directory]/backend/admin

What is the expected output? What do you see instead?
Some sort of home page, instead I see "No input specified." This happens 
immediately after the installation when I click the link to go to the admin 
backend.

What version of the product are you using? On what operating system?
1.8.4.4, Linux (most likely CentOS)

Please provide any additional information below.
The installation is running on GoDaddy shared hosting using MySQL 5.0 and PHP 
5.2
I ran the configuration file check and it said OK.

Original issue reported on code.google.com by njbentl...@gmail.com on 8 Nov 2011 at 2:01

[GoogleCodeExporter]

Update:
I installed mollify on XAMPP on my pc and it seems to work fine. So I can only 
assume that it's GoDaddy's servers at fault. Still, any help you could provide 
would be greatly appreciated.
Thanks,
Nick

Original comment by njbentl...@gmail.com on 8 Nov 2011 at 2:55

[GoogleCodeExporter]

Hard to say what is the reason for this error, I'd need server debug log to see 
if it gives any clues.

Original comment by samuli.j...@gmail.com on 8 Nov 2011 at 6:32

[GoogleCodeExporter]

By googling this error, it seems that quite many scripts fail on the same error 
under GoDaddy. However, the suggestions are very different, and as I don't have 
experience on the service provider, I really can't help you on this one.

Original comment by samuli.j...@gmail.com on 22 Nov 2011 at 5:00

• Changed state: Invalid

[GoogleCodeExporter]

I am also able to get mollify running on local XAMPP, but when uploaded to 
GoDaddy Host account, get the protocol error.  Tried fresh install also, and 
get a blank screen when clicking continue button. See a lot of people having 
similar issues with GoDaddy and Mollify, and seeing that GoDaddy has to be one 
of the largest hosting providers in the world, I wonder if anyone has ever 
successfully run mollify on a GoDaddy server.  I suppose I will have to just 
move all the site files and the Mollify installation to a new host, and hope 
that it will all work there.

Original comment by cf_is_h...@hotmail.com on 6 Jan 2012 at 2:26

[GoogleCodeExporter]

On a shared lamp server (Aruba) with Apache 2.2 and PHP 5.3 as CGI, I solved by 
adding

cgi.fix_pathinfo = 1

in the php.ini (into /path/to/mollify/backend/php.ini);

ps: tested with mollify 1.8.6.1;

Original comment by moikanowebreality@gmail.com on 6 Jan 2012 at 8:33

[GoogleCodeExporter]

Really can't help you with GoDaddy since I don't have any experience on it, but 
by what I've read I've got the impression that they don't have all the things 
as they should. Googling "godaddy no input file specified" will give you a long 
list of users having the same issue, caused by some GoDaddy setting.

But this gives you a concrete tip: 
http://www.cesgeekbook.com/2010/07/php-no-input-file-specified-godaddy.html

 I hope it helps, but really I doubt there's nothing I can do about this.

Original comment by samuli.j...@gmail.com on 6 Jan 2012 at 9:04

[GoogleCodeExporter]

Thanks.  Actually this caused a different error to troubleshoot, which is 
perhaps an improvement.  I changed the .php extension from PHP5.2-FastCGI to 
just plain PHP5.2 using the tip you've kindly provided.  Here is the new error, 
which may be resolvable (?):

Protocol error

Got malformed JSON response 

Parse error: syntax error, unexpected T_VARIABLE in [PATH TO MY MOLLIFY INSTALL 
DIR]/backend/configuration.php on line 4

Then my config file looks like so:

<?php
    $CONFIGURATION_TYPE = "mysql";
    $DB_HOST = "my hidden nonlocal url to the database - not using an IP here" 
    $DB_DATABASE = "my hidden db name";
    $DB_USER = "my hidden db username";
    $DB_PASSWORD = "my hidden password";
    $DB_PORT = "3306";
    //NonLocal DB - Commented Out > $DB_SOCKET =  "/var/run/mysql/5.sock"
    $DB_TABLE_PREFIX = "mollify_";  

?>

Any insight given this information?  Thanks.

Chris

Original comment by cf_is_h...@hotmail.com on 7 Jan 2012 at 6:08

[GoogleCodeExporter]

Sorry.  I did notice that I was missing some terminating semi-colons in the 
config file, which cleared all the JSON notices.  Now going to 
files.premierlivinghomes.com (root of Mollify) I get a blank page, no errors.  
If I go to backend/admin I get a blank page, except for the in-page title 
"Administration".  I feel like these are steps toward success.

Original comment by cf_is_h...@hotmail.com on 7 Jan 2012 at 6:17

[GoogleCodeExporter]

Great news.  Mollify does work on GODADDY hosting (Client pages, but not the 
admin pages).  

FRONTEND (CLIENT) FIX
I followed your tip to change the settings on the hosted account for .php FROM 
"PHP5.2-FastCGI" to just plain "PHP5.2" in GoDaddy's hosting control panel.

That may have been enough to correct the "Protocol Error", and get everything 
working.  Not sure, because I had some other changes I made before to the index 
and configuration files in my efforts to get it to work.

I also added into the index.html file:

  <script type="text/javascript">
                mollify.init({
            "service-path": "backend/",
                        "limited-http-methods": true,
                });
        </script>   

CONTINUING PROBLEM ON ADMIN BACKEND PAGES

Still just getting the blank page, with a non-working (ghosted out) "LOGOUT" 
text, and the page title "ADMINISTRATOR".

No errors showing.  

LINK

files.premierlivinghomes.com/backend/admin/ (this is a subdomain "files")

Current Configuration:

<?php
    $CONFIGURATION_TYPE = "mysql";
    $DB_HOST = "**hidden**"; 
    $DB_DATABASE = "**hidden**";
    $DB_USER = "**hidden**";
    $DB_PASSWORD = "**hidden**";
    $DB_PORT = "3306";
    //$DB_SOCKET =  "/var/run/mysql/5.sock";   
    $DB_TABLE_PREFIX = "mollify_";
    $SETTINGS = array(
                "enable_limited_http_methods" => TRUE,
        "enable_file_upload" => TRUE,
                "enable_zip_download" => TRUE,
                "debug" => TRUE
        );  

?>

Index file:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd">

<!--
  Copyright (c) 2008- Samuli Järvelä

  All rights reserved. This program and the accompanying materials
  are made available under the terms of the Eclipse Public License v1.0
  which accompanies this distribution, and is available at
  http://www.eclipse.org/legal/epl-v10.html. If redistributing this code,
  this entire header must remain intact.
 -->

<html>
    <head>
        <title>Premier Living Homes - File Management Repository</title>        
        <meta http-equiv="content-type" content="text/html; charset=UTF-8">

        <link rel="stylesheet" href="client/themes/basic/style.css">

        <script type="text/javascript" language="javascript" src="client/include/jquery.js"></script>
        <script type="text/javascript" language="javascript" src="client/include/jquery.tmpl.min.js"></script>
        <script type="text/javascript" language="javascript" src="client/init.js"></script>
        <script type="text/javascript" language="javascript" src="client/localization/texts_en.js"></script>
        <script type="text/javascript" language="javascript" src="client/org.sjarvela.Mollify.nocache.js"></script>

        <script type="text/javascript">
                mollify.init({
                             "service-path": "backend/",
                        "limited-http-methods": true,
                });
        </script>       

    </head>

    <body>
        <div id="mollify"></div>
    </body>
</html>

Original comment by cf_is_h...@hotmail.com on 7 Jan 2012 at 7:58

[GoogleCodeExporter]

Well, I tried the url you gave for the admin util, and the reason why it does 
not work is that none of the resources are loaded. Don't know why, but server 
just gives error 500 (internal server error).

For example, it tries to load this script: 
http://files.premierlivinghomes.com/backend/resources/md5.js

You just need to resolve this, and it should be fine. Maybe the host is not set 
properly, can't help you with that.

Original comment by samuli.j...@gmail.com on 8 Jan 2012 at 11:49

[GoogleCodeExporter]

I did get the admin area to work now.  So everything is now working.  Seems 
like there was an ftp failure, so the entire backend was not uploaded to the 
remote host.  Works, but I am using the old version 1.8.3.  I am going to try 
to upgrade to the newest version to see if that also works.

Original comment by cf_is_h...@hotmail.com on 9 Jan 2012 at 2:00

[GoogleCodeExporter]

Now that both the backend and client sides work perfectly, I upgraded to 
1.8.6.1 and it works perfectly.  ALL operations in backend/client work in both 
the old and newest versions of Mollify on GoDaddy.  

Original comment by cf_is_h...@hotmail.com on 9 Jan 2012 at 3:30

[GoogleCodeExporter]

That's great news!

Original comment by samuli.j...@gmail.com on 9 Jan 2012 at 3:50

[GoogleCodeExporter]

I tried to install Mollify yesterday on Godaddy and run into the same problem.
Then fortunately I found this thread, and now it is working fine.
Thank you!
Please pardon me if I add some verbose instructions for those - like me - not 
so familiar with Goddady Control Center: 
1) enter the Godaddy Hosting Control Center
2) choose settings-file extensions management-default extensions
3) in the table that is presented edit ".php" Runs under "PHP 5.2.x" (instead 
of "PHP 5.2.x FastCGI")

Original comment by patr...@gmail.com on 9 Mar 2012 at 9:06

[GoogleCodeExporter]

For #14, thanks for this, I'll add FAQ item with your instructions.

Original comment by samuli.j...@gmail.com on 10 Mar 2012 at 2:05

[GoogleCodeExporter]

Thanks for being so persistent on this guys!

Original comment by njbentl...@gmail.com on 12 Mar 2012 at 2:13