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.

Archive /

Our old forums are still available as a read-only archive.

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

mootools/getElementByTagName


Go to End


2 Posts   6139 Views

Avatar
dashiel

Community Member, 13 Posts

26 April 2008 at 4:53am

Edited: 26/04/2008 4:57am

i had a static site that i'm porting to silverstripe that made heavy use of the mootools framework. for some reason something in silverstripe seems to be conflicting with the $$ function in mootools.

i have a completely clean silverstripe template (e.g. i've done nothing, but replace my standard php include directives with the silverstripe method for including files). there is as far as i can tell no javascript what-so-ever being added to the rendered page.

i copy/pasted the rendered html in to a static page in the silverstripe architecture and everything worked fine (once i removed the xml heading at the top).

any thoughts/work arounds?

--- edit

as usual i hit upon an "aha" moment minutes after posting this. it seems removing the xml declaration, not the doctype, from the top of the document "fixes" mootools. will this have any adverse affect on sliverstripe?

Avatar
Blackdog

Community Member, 156 Posts

26 April 2008 at 6:49pm

perhaps it is the prototype js framework which is used throuhgout SS.