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.

Customising the CMS /

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

select form in CMS


Go to End


10 Posts   3663 Views

Avatar
UncleCheese

Forum Moderator, 4102 Posts

19 January 2009 at 6:40am

You're still missing something, here. I'm not sure why you're trying to create a relationship to SiteTree. All Pages are related to SiteTree by virtue of inheritance.

It's working right now because you're only asking for the $Title property, which is part of the SiteTree, but if your SeeAlso field is a TourPage, then you should really set up the relationship as such so you can access the unique properties of the TourPage, as well.

You should never have to set up any relationships to SiteTree. That just.. doesn't make sense.

Avatar
ajshort

Community Member, 244 Posts

19 January 2009 at 11:33am

Setting up a relationship to SiteTree actually makes perfect sense - sometimes you need to provide information about a remote page without hardcoding the URLSegment into the template. Also, thanks to the ORM you can also access any extra fields on subclasses of the relationship (TourPage) without having to specify it manually.

Go to Top