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

SiteTree Error in ajax


Go to End


6 Posts   2939 Views

Avatar
msantang

Community Member, 41 Posts

16 February 2008 at 12:31pm

Edited: 17/02/2008 2:48am

Hi i just install the windows version of SS 2.21.
it's work ok but in the CMS when the sitetree have more than 3 levels (when use ajax) the tree is broken.

See Screenshots: when i click on Aberturas, the tree start the request and then when this is finished i get the error of the second screenshot

I already try to upgrade to the lastest daily build

Avatar
msantang

Community Member, 41 Posts

18 February 2008 at 11:23pm

Someone know what it's the error?

Avatar
Tim

Community Member, 201 Posts

19 February 2008 at 9:26am

What version of Windows are you running?

Avatar
msantang

Community Member, 41 Posts

20 February 2008 at 11:34pm

I use Windows XP the error happens in IE and Firefox

thanks for reply

Avatar
msantang

Community Member, 41 Posts

26 February 2008 at 2:08am

I discover that if i install SS and in the empty new DB structure (fresh install) i copy my theme and the mysite files and run /db/build it works ok.
But i had to make every page again.

basicaly Update my old site didnt work. I had to rebuild it again.

Sorry for my english

Avatar
Krueme1

Community Member, 1 Post

27 February 2008 at 4:22am

Hi,

I know this problem I get it when url is .../admin/
When I delete the last '/' I dont get this SiteTree Error.

But I have this SiteTree Problem on /admin/assets/ and on this its not to fix with delete the last '/'.