Login | Forgot password | Register

X

What is OpenID?

OpenID is an Internet-wide identity system that allows you to sign in to many websites with a single account.

With OpenID, your ID becomes a URL (e.g. http://username.myopenid.com/). You can get a free OpenID for example from myopenid.com.

For more information visit the official OpenID site.

Jump to:

2488 Posts in 731 Topics by 541 members

Customising the CMS

SilverStripe Forums » Customising the CMS » add_extension woes...

Page: 1
Go to End
Author Topic: add_extension woes... 593 Views
  • SmartPlugsDesign
    avatar
    Community Member
    57 posts

    add_extension woes... Link to this post

    I'm trying to put together a USDatetime Module for future release and am using a series of Extensions to get the job done. I've run into a bit of a problem that I'm hoping someone can shed some light on.

    When trying to add an extension to DMYDateField (which is a child of CalendarDateField, which is a child of DateField - both of which have extensions), I'm only getting one confirmed extension ... the DateField extension. If I comment out the DateField extension, then it defaults to the CalendarDateField extension. It's looking like this:

    class A {}
    class B extends A {}
    class C extends B {}

    A::add_extension()   //   no problems
    B::add_extension()   //   A extension only
    C::add_extension()   //   A extension only

    Any ideas on why this is defaulting to the top parent extension? Or better yet, how to implement this sort of behavior?

    Thanks!
    John

  • Ingo
    avatar
    Administrator
    593 posts

    Re: add_extension woes... Link to this post

    First of all, we're planning a rewrite of the formfield API for better localization support, see http://open.silverstripe.com/ticket/2931
    Its good to have extensions like USDateTime as short-term fixes though.

    I'm assuming you're calling Object::add_extension('A','<your-ext-name>') instead of A::add_extension()? Static classes (currently) don't know about their classname, hence the two arguments for the method.
    The static handling in SilverStripe needs some polish, it might well be the cause of this error. An abbreviated code example which we can fire up and debug would be ideal (perhaps even a unit test class?).

    593 Views
Page: 1
Go to Top

Currently Online: aram, Ingo, Sean, eskimo, steve_nyhof

Welcome to our latest member: jasonthkim

Want to know more about the company that brought you SilverStripe? Then check out SilverStripe.com

Comments on this website? Please give feedback.