Thread

Here’s the thing. I didn’t read the upgrade steps carefully enough and I think I made a mistake somewhere. I’m not asking you to solve it for me, but maybe you can help me get things right.

First of all, I’m pretty familiar with the technology, so it’s not *that* what’s been going wrong. It’s me being too sure about the general way things go that I thought I didn’t *really* had to read through all the upgrade steps before I actually uploaded all the new files to the server :-D

So, here’s what I’ve done:
1. set up a EE core site, made a few posts, changed my theme a lot. This was my initiation into EE, and I’m impressed.
2. Got myself a personal license (and after 9 years of using open source CMS’ for my site, paying for a system means I’m really impressed).
3. Got the 1.5.2 with the new licese, uploaded *all* files to the server.

Oops. Overwrote my config file. The backend works (I can access all admin pages just fine, see my posts there etc.). But, the site itself tells me that there’s nothing installed…

4. Go on vacation thinking I’ll fix all this when I get back. Sunbathed on the shores of Italy’s gorgeous lakes…
5. Got back, saw that 1.6.0 was released, uploaded the files (this time I left config.php out), but its still the same.

Now, there must be another file somewhere that I need to ‘restore’ to get the front side back up again. Is it path.php? ANd if so, what should be in it exactly?

Please give me a hand to sort this out 😊

Thanks in advance!

Herko

Wait, back up.

4.  I’m very, very jealous.

Ok we can continue.

Alright - you need two files, config.php and path.php.  Did you overwrite both without a backup?

Instead of reminding you to backup *coughs* you can find a config.php in the wiki - you will need to fill out the values manually, but it will, in fact, get you up and running.

You may also need path.php - again you’ll need to correct that manually.

That should get you sorted out. =)

Yay! The config.php file I had backed up, bu tthe path.php file was empty. Now the site sems to work again! Thanks a million!

Except for one (tiny) thing: at the top of the page I get 3 identical notices:

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

They look ugly. Is there something I can do about the notices? Or are they only shown to webmasters?

Herko

Nevermind.

Found it 😊 Should learn to look before asking :-D

Herko

Notices should never be ignored - that’s a pet peeve of mine; ignoring a warning (or suppressing it) doesn’t mean it’s fixed…

So did you suppress it, or fix it? 😉

Supress - I think. Although, when I set the debug info to off, my site’s CSS doesn’t work :-\ So I’m digging deeper. I’m no coder tho, so fixing the notice is beyond my abilities. (Notices are just messages stating that there’s some sloppy coding somewhere in the parsed code tho. It’s warnings you need to mind 😉)

Herko

Can you head to Admin -> System Preferences -> General Config and check the URL to your theme directory?

Both the URL and the physical path are correct. Strange thing is, it only happens when I turn the error reporting off. When it’s set to show for super admins only, the page is displayed fine (haven’t checked if it shows badly for non admins yet tho).

Herko

Were you running Mark Huot’s pages module at all?

Nope. I was running the COre version up untill -well, since you helped fix the site.

Herko

Well that’s a third party module.  Hrm - since you were on Core, I need you to download the full version again and upload everything in the system directory EXCEPT

config.php
config_bak.php
cache

Got it? Do not overwrite those files - and make a backup first.  But lets see a full scale re-upload fixes the error and your issue.

full scale re-upload didn’t fix it. I’ll re-download the package and try again later today.

Herko

Re-dowload of the package, re-upload of the files you mentioned, but no change. Still get the notices on top and the CSS less pages when trying to view my site without the debug info.

The URL is http://www.herkocoomans.net, by the way.

Herko

Could it be something to do with the naming of the site? That the path to the CSS file isn’t correct? default_site vs. site as weblog path name perhaps?

Herko

Ok, did you double check the path to your themes folder in the General Config?  The other option is to try moving the themes folder inside of /system/

That error I haven’t seen before, so I’ll need to follow up with that.  Are you running any extensions at all?