I'm getting the following error right after a new clean install on Dreamhost
This page contains the following errors:
error on line 45 at column 500: attributes construct error
Below is a rendering of the page up to the first error.
Any Ideas?
This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.
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.
I'm getting the following error right after a new clean install on Dreamhost
This page contains the following errors:
error on line 45 at column 500: attributes construct error
Below is a rendering of the page up to the first error.
Any Ideas?
This looks like the error that Safari gives when it encounters problems with xml parsing of the html returned by a page.
Viewing the same page in firefox, the error shown is "XML Parsing Error: not well-formed", and it also indicates where the problem is in the web page source.
There seems to be some problems with the quoting generated from this file:
sapphire/core/control/ContentController.php:
lines 247, 252, 257
Where the text 'Note: this message won\'t be shown to your visitors' appears.
I found the simplest solution is to replace each instance of "won\'t" with "will not" on these three lines
The quoting of the div title uses single quotes and then has a single quote in the middle.
--
Sean Farrell
Thanks Sean. That fixed the problem. :)
Cheers,
Mike
Made the change and I'm still getting and error, this time in a different spot.
According to to Firefox its
Line Number 22, Column 76:
I think I'll just install the older version
Thanks Sean. That fixed the problem for me too.
Cheers,
J-P
replacing with " works well too...
is there a bug tracker we can file these things against?
There is a bug-tracker @ open.silverstripe.org - but this specific bug has already been fixed in the 2.3 branch, and will be present in the next 2.3 minor release.