Thread

Er… upgrading from EE Core to EE Personal can do that to my webserver?

I didn’t change anything on the server, so IMHO that can’t be it (other sites aren’t affected either). I’m seriously considering a reinstall now… Sigh

Herko

Er… upgrading from EE Core to EE Personal can do that to my webserver?

Definitely no.

Goto Admin > System Preferences > Output and Debugging Preferences

Check if “Generate HTTP Page Headers?” is set to “Yes”. If not, set it to “Yes” and see if that changes something.

Generate page headers was set to Yes…

Herko

Hi, herko—

Having not seen this before I enquired to see if others in our team had.  It is possible for a server to auto-send headers, which in turn prevents PHP from being able to set the headers itself.  It sounds like this may be happening on your host so you would need to enquire with them if that is the case. It can sometimes be disabled via .htaccess but that is definitely something to follow up with at your hosting provider, as they could just turn that off, too.

Keep us updated on how it turns out. =)

A bit more information as well, please make sure you are *not* suppressing errors, and that display_errors in PHP is enabled, so that we can get a real picture of what is going on here in order to fix it.  Thank you =)

I’m going to reinstall from scratch. Backing up my stuff now. Funny thing is that the site worked perfectly fine in EE Core, but the problems started as soon as I upgraded to EE Personal.

Oh well, the support so far has been outstanding, makes me feel that this is a good choice. I haven’t lost that much content, so its not the biggest disaster in the world.

Herko

herko- I’m not sure a reinstall will fix it- only if it’s a corrupted file, which I’m not sure it is.  The first thing I’d do is talk to my host- see if they are forcing the headers.  That’s definitely the issue.  Then, while you’re waiting to hear from them- try renaming your css template from site_css to site_css.css and use that in the link.  See if it makes any difference.

There isn’t anything about EE per se that should be causing this- we’d have seen a lot of it if it were a standard bug.  I’d seriously ask my host about it, see if they know what’s up.

Thing is, I have 55 other sites running on that same host and server. And everything there works fine. It’s a reseller host that I control myself, so I whould know what goes on there. On all the other sites (wordpress, xoops, joomla based) the pages are served fine, it’s only thins site, and only *after* I upgraded in an a-typical way to the 1.6.0 release. So I’m putting my bets on the install for now, and not on the host.

Herko

Herko, did you follow Lisa’s instructions carefully for making sure PHP errors are enabled?  This would easily happen as a result of some whitespace in your path.php, index.php, or config files (or any others for that matter), and if that’s the case, and error reporting were enabled (both in your Site preferences and on the server), you’d see cannot modify header errors telling you precisely which file is causing the problem.

Yes, I know, and the only error feedback I got was the 3 identical notices in a previous post in this thread. I checked the config files and just about any file I had opened for whitespaces after the closing ?>, but no such luck.

Like I said, I’ll try a reinstall and see where that will get me 😊

Herko

Ok, I did not see a clear explanation from you on what you did to get rid of this error:

Notice: Undefined property: Pages_QSTR in /dohduhdah/public_html/system/modules/weblog/mod.weblog.php on line 103

As that would only occur if your files had not been properly updated.  And depending on what you did, they could have been and could still be the source of the problem of EE not being able to set headers.

I’ll give upgrading another try, seeing your reply Derek, and the following message I got:

Sender:
  Joe Muscara
Subject:
  Error after upgrading to 1.6
Date:
  2007-07-16 01:00 PM
Recipients:
  <herko>

Hi Herko,

I can’t post on the forums yet due to getting set up with a client’s EE license and all that.

I just updated a client’s site from 1.5.2 to 1.6, and got the same error you did. When I uploaded the new files, I used Transmit’s Synchronize feature. After reading your thread, I reuploaded the new files, except I just replaced all the old folders with the new ones. I didn’t bother to upload the “update” file and folder, as I had already run those.

Anyway, replacing all the folders as instructed in the update instructions seems to have fixed it for me. Hopefully this will help you too, and you can post it in the thread in case it happens to anyone else.

Joe

:-( I replaced all files and followed all directions, but no change. The notices are gone tho, but the CSS isn’t loading. I’m reinstalling as I type this.

Lets see if this is a server config thing or an upgrade I messed up.

Herko

Reinstalling solved everything, even tho my server backup was corrupt :-( I haven’t lost much tho (a few images), as I backed up the db separately before I removed all files.

So, onwards with my discovery of EE! Thanks for all your support tho, it’s been a great help.

Herko