I think there is no problem of checking subdomain from sfUser. I think for checking subdomain you only need to have a request object - I think it has a host attribute.
Something about subdomains is here http://www.symfony-project.org/blog/2009/03/02/call-the-expert-adding-subdomain-requirements-to-routing-yml But maybe this isn't exactly what you need. On 9 dub, 17:00, Tom Haskins-Vaughan <t...@templestreetmedia.com> wrote: > Thanks, Tom! > > One of the main reasons to do it with subdomains, is to give the > affiliates "ownership" of the way the site looks. > > If I do do it with subdomains, and then store the affiliate in for in > sfUser, am I ok to do the subdomain analysis in in the sfUser class? > > I mean, can I just check the subdomain in sfUser or *should* I use a > filter for this? I'm looking for the *best* way. > > Tom > > > > On Fri, Apr 9, 2010 at 6:16 AM, Tom Ptacnik <to...@tomor.cz> wrote: > > I think the classic way of doing this is to store a cookie when the > > user comes (from some link with id which idetify the affiliate). Then > > you can identify him by this cookie, or you can use session - if you > > don't need to identify him after he leaves your website and comes > > later by just typing your website url (not comming over the affiliate > > link again). > > > You have to think about advantages and disadvantages of both > > solutions. > > - If you have subdomain based affliate identification you dont need to > > store the cookies or remeber the affiliate in the session. But you > > will have maybe more difficulties with routing. And what if the user > > comes later to your web to another affiliate subdomain or without > > affiliate subdomain? > > > On 8 dub, 03:35, Tom Haskins-Vaughan <t...@templestreetmedia.com> > > wrote: > >> Hi there, > > >> I'm working on an ecommerce site that will eventually have an > >> affiliates programme that will work like so: > > >> * There will be several affiliates. > > >> * Each affiliate will be able to 'skin' the site by adding their own > >> css stylsheet. > > >> * For each purchase on the website the affiliate will be recorded to > >> allow us to pay a commission to the affiliate > > >> * The affiliates will direct traffic to the site be giving out his > >> subdomain: exampleaffiliate.maindomain.com > > >> I started by following the advanced routing chapter in the more with > >> symfony book. I have created a route class and I am setting a request > >> parameter in a custom filter. But before I go any further I'm > >> wondering if it wouldn't be better to store this information in the > >> User classes and just bypass the routing all together. Does anyone > >> have any suggestions? > > >> TIA, > > >> Tom > > > -- > > If you want to report a vulnerability issue on symfony, please send it to > > security at symfony-project.com > > > You received this message because you are subscribed to the Google > > Groups "symfony users" group. > > To post to this group, send email to symfony-users@googlegroups.com > > To unsubscribe from this group, send email to > > symfony-users+unsubscr...@googlegroups.com > > For more options, visit this group at > >http://groups.google.com/group/symfony-users?hl=en > > > To unsubscribe, reply using "remove me" as the subject. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
