Yet another problem with yet another EE 2.1.0 test installation.

My core site dates back to the pMachine days, back when a “channel’s” CSS template was named weblog_css by default. When my EE 1.6.9 was updated to 2.1.0, the CSS isn’t getting loaded. I noticed that EE 2.1.0 did what appears to be a global search/replace for “weblog” > “channel.”

Yes, I updated all the references in my templates to reflect the change. But the CSS still isn’t getting loaded. Here’s the relevant code snippet.

Pretty straightforward, right? What am I missing?

Hi mfraase,

Just to confirm, you have updated the template name to reflect the change as well as references within your templates? Have you got a URL where we can see this?

Cheers

Greg

I see what the problem is. EE is making an absolute reference to the stylesheet.

Hi mfraase,

Have you got a URL where we can see this? Have you got this working properly?

Cheers

Greg

Like all major EE updates this one is turning out to be a real pain in the ass.

Because EE uses absolute references for everything, it’s impossible to develop on one server and migrate that to a production server. And because Engine Hosting uses an old version of phpMyAdmin, I have to email them the .sql file to import.

Here’s something that would be really nice: If Ellis spent a little more time testing its installer/updater so it would error out gracefully from a failed update process it would make things much easier. Shouldn’t be too hard to add logic on the order of “does this table/column exist? Is it valid? OK, move along to the next one. Don’t just error out, leaving tables and columns behind

Hi mfraase,

What is the status of your upgrade now?

Cheers

Greg

It’s working now. Apologies, I thought I had added that after my rant, but I guess not.

Hi mfraase,

We appreciate the feedback, and I’m glad you got this working. Don’t hesitate with further questions.