Thread

Hello-

First time EE (1.67) user here, and I’m loving it so far. I’ve successfully installed EE on my local computer as well as my own website, and the site I’m developing is 90% done, but I’m having issues with the installation on my client’s server…where the site will finally reside.

Here’s what I’m running into:

When you click on any Weblogs under Publish tab the next page is completely blank, when it should be the standard entry form. I know there’s nothing wrong with EE itself in this case (cause it runs great on my site), so the issue is that the client’s hosting company has certain server settings that are conflicting with EE.

Support guy at the client’s hosting company traced the error to this file:
core/cp/cp.publish.php

At this point in the file:

Current PHP settings for the server are here:
http://pacmeddna.adhostclient.com/phpinfo.php

If there is any additional info you need to help me solve this problem, let me know. I’d obviously like to get this figured out asap, so I can move on to doing cooler things with EE itself. 😊

greetings, and welcome to the forums!

What extensions are you running on the site?  What led the hosting company back to that file?

-greg

Hey Greg, thanks for getting back to me.

Extensions enabled:
- jQuery for the Control Panel
- Tag Submit (I tried disabling this and trying again, but that didn’t help)

All the support guy said was this:
“It appears to be dying somewhere in core/cp/cp.publish.php, at this point in
the code:”
then he pasted the code in my first post.

Beyond that it’s the standard ‘we don’t have any experience with EE to help you further’ response.

Can you please see if you can get the exact php errors that lead them to believe that the code is ‘dying’ at that point?  Or do you have access to apache error logs?

Thanks!

-greg

I asked hosting support for more info, and here is there response:
“Unfortunately, it is not throwing any PHP errors - it simply shows the blank page in question. More than likely, the code is being aborted in the middle as part of the CMS itself.”

They aren’t being very helpful and are wanting to charge $150/hour to investigate the issue further. They’re your typical ‘we won’t give you access to figure it out yourself, so you’ll have to pay us to do it’ kind of hosting company.

BTW- I’m happy to send someone at EE support a temp user/pass to see the issue yourself. There’s no content in the installation in question, so there’d be nothing to mess up.

You need to turn on error reporting explicitly: http://expressionengine.com/wiki/HowTo_Turn_on_Error_Reporting/

Please do so, and make sure it’s also turned on in your PHP environment. The error message should give us something to work with.

Thanks, Ingmar, for the suggestion. I went through the steps, confirmed that php error reporting is turned on, and unfortunately no php error shows. The only thing I’m seeing, for the page after clicking on publish > ‘weblog’, are a few odd characters: 

Okay, I just went through the above steps again with the same result.

Does it help to know it’s a Windows, not Apache, server?

What is your debug preference set to at;  CP Home ›  Admin ›  System Preferences ›  Output and Debugging Preferences

-greg

Debug preference is “1: PHP/SQL error messages shown only to Super Admins”

My client is cracking the whip on the hosting support guys, so hopefully they’ll cough up some useful information on the issue.

okay, please do keep us posted.  Really, they should be giving you php errors if you are getting any.  I’m glad your client is willing to rattle some cages.  😊

-greg

What you can try in addition is adding this to your config.php:

$conf['debug'] = "2";

This would show error messages to every one, not just Superadmins (and thus is clearly only for debugging purposes).

Thanks for the responses. I cleared out everything and reinstalled, making sure to select Windows for the server option during the install…which fixed the issue. So turns out it was my fault for not clarifying with the client what kind of server they are on.

Glad to see you found a working solution. Please post again if you need additional help.