096 RC2 (official release) public support

Please use this thread to discuss the 096 RC2 public release which will be (or already has been) posted soon.

Does the Ajax Message checker work? All I got were question marks in the top right in FF2... I have a fix that I’ll post to the 095dev branch tomorrow, but someone who knows Javascript better may want to check my work and make sure it’s good

UPDATE: @Ryan: What number is it? Because I can post more info and even close it when I commit my patch

UPDATE: Fixed in latest 095dev branch. More info over here: 095 RC2

I don’t think it does sirlancelot and that’d be a handy fix to have fixed indeed (I just commented on that in the bugtracker yesterday in fact!).

As far as updating is concerned, it couldn’t find my database details, but doing the advanced update where you enter the DB details manually worked fine from 0.9.5 to 0.96RC2.

My only problem now is that I can’t figure out how to switch to v2.1.0 of the editor.

EDIT: Changed the settings to math, and had to switch the editor interface to Content Editor in the config settings and it works again

All looking fantastic to me!

What are the Scriptaculous and Prototype links still doing in the template though? Are they safe to remove now we’re Moo powered?

I upgraded from 0.9.5 to 0.9.6 RC2 locally on a Mac. I have <base href="[(base_url)]" /> set in my template and all my snippets worked fine prior to upgrading but now...

Ditto and Breadcrumbs still work fine and still output links like this...
http://127.0.0.1/~someuser/index.php?q=somepage

But MaxiGallery and Wayfinder now incorrectly output like this...
http://127.0.0.1/index.php?q=somepage

Strange. Anyone else have base URL problems after upgrading?

EDIT -- SOLVED: UPGRADING TO RC3 FIXED EVERYTHING! THANKS.

Try switching from base_url to site_url.

Yeah, site_url is actually what I had used previous to the upgrade -- but after upgrading, my css was not being found at all. So I tried switching to base_url and that brought back my css.

Quote from: bullrat at Apr 16, 2007, 03:20 PM

Yeah, site_url is actually what I had used previous to the upgrade -- but after upgrading, my css was not being found at all. So I tried switching to base_url and that brought back my css.

This sounds like a virtual hosting issue with your Apache/PHP config. What are the values of your SERVER variables? base_url should not be used for base href value; it should definitely be site_url. What is the value being rendered in the base href when using site_url?

Quote from: OpenGeek at Apr 16, 2007, 04:13 PM

Quote from: bullrat at Apr 16, 2007, 03:20 PM

Yeah, site_url is actually what I had used previous to the upgrade -- but after upgrading, my css was not being found at all. So I tried switching to base_url and that brought back my css.

This sounds like a virtual hosting issue with your Apache/PHP config. What are the values of your SERVER variables? base_url should not be used for base href value; it should definitely be site_url. What is the value being rendered in the base href when using site_url?

Something I found out by accident:

If <link> occurs BEFORE you set <base href=""/> (HTML source order), you will need to use the absolute URL for <link>.
If <link> is AFTER <base href=""/>, you can either use the relative URL or absolute URL for <link>.

Not sure if this is relevant to the issue, but thought I’d throw it out there.

Right, the base tag must come before any other element with a src or href attribute in order for those elements to respect the path. Also note that with some javascripts, IE 6 crashes if you do not use a full closing tag, i.e. <base href="[(site_url)]"></base>