Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Installing SilverStripe /

Getting SilverStripe up and running on your computer and on your web server.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

New installation of SS 2.3.7 corrupt CMS and XML Parsing Error


Go to End


4 Posts   1724 Views

Avatar
Angelika

Community Member, 6 Posts

22 April 2010 at 11:26pm

Hello,

I previously had an older version of SS installed. I removed all old components and did a clean installation (with a new DB and DB user).

At the end of the installation, instead of the " Congratulations you have successfully installed SS" message I got the following error:

XML Parsing Error: mismatched tag. Expected: </div>.
Location: http://www.sitename.com//home/successfullyinstalled?flush=1
Line Number 70, Column 17:

It also looks like the CSS is corrupt as the formating of the homepage is as in the below screenshot.

Has this happened to anyone before? Any idea what may have gone wrong?

I appreciate your help!

Many Thanks

Angelika

Attached Files
Avatar
Angelika

Community Member, 6 Posts

23 April 2010 at 8:50am

Hi Again,

as there were no replies, I eventually gave up on the new release and installed a version of the candidate release isntead. The XML parse error did not come up and everything looks fine.

I would still like to know if other people have come accross this issue with v. 2.3.7. If you have then I assume it's a bug.

Angelika

Avatar
Thomashv

Community Member, 35 Posts

30 April 2010 at 1:08am

Hi Angelica,

I got the same error.
But the website seem to work when I go to www.mysite.com and so does the admin...

Seem to be a bug.

- Thomas

Avatar
Sean

Forum Moderator, 922 Posts

4 May 2010 at 12:28pm

Edited: 04/05/2010 12:28pm

Hi all,

This bug was fixed in the 2.3 development branch, but it hasn't been released yet.

Here's the fix so you can manually patch your files for now: http://open.silverstripe.org/changeset/101258/modules/sapphire/branches/2.3

Cheers,
Sean