Permalink
Switch branches/tags
Nothing to show
Commits on Sep 9, 2010
  1. Removing the upgrade plugin and removing a bunch of code from sfSympa…

    …lConfig for features that won't be supported, at least for now.
    committed Sep 9, 2010
Commits on Sep 8, 2010
  1. Reworking the content loader class to be more basic but still do what…

    … it needs to do. It's now passing with the given functional test.
    committed Sep 8, 2010
  2. Re-adding logic to sfSympalPluginConfiguration related to whether or …

    …not the current user can edit content.
    committed Sep 8, 2010
Commits on Aug 6, 2010
  1. Remocing lots of excess content - we have record of it, can be put ba…

    …ck at some point if needed
    committed Aug 6, 2010
Commits on Jul 29, 2010
Commits on Jul 26, 2010
  1. Fixing the getUrl() method

    committed Jul 26, 2010
Commits on Jul 23, 2010
  1. Fixing the page content type

    committed Jul 23, 2010
Commits on Jul 13, 2010
Commits on Jul 12, 2010
  1. Removed the hasField() magic method on sfSympalContent as it doesn't …

    …make sense really to ask this now that it and the content record are more disjointed. Added getModuleToRenderWith and getActionToRenderWith and started using the min the toolkit routing. Fixed a bug in the routing that cased custom route paths to be generated incorrectly.
    committed Jul 12, 2010
  2. Renaming sfSympalContentType.key to sfSympalContentType.type_key beca…

    …use mysql didn't like the field name "key" - more changes probably needed.
    committed Jul 12, 2010
  3. Moving away from slug, i18n_slug - this affects the route object in a…

    … special way since the i18n_slug field was getting special treatment.
    committed Jul 12, 2010
  4. Removing the default url pattern if a sfSympalContentType record does…

    … not supply a default_path. The default_path is now a notnull field and we always use it.
    committed Jul 12, 2010
  5. Having the slug and content_slug on sfSympalContent, while everything…

    … else was on the content type model was very awkward. Dealing with the $record->Content and $content->Record relationship in both directions was causing all sorts of problems. This is the first step to remove slug and i18n_slug from sfSympalContent.
    
    The importance of slug is primarily in url creation. Now, you can have the slug on your content type model and choose to have it in your url or not (or make up a different field name that acts like a slug). My hope is that with good awareness of i18n, the i18n_slug functionality can be recreated by having some sort of slug field that is i18n'ed and then included in your route.
    committed Jul 12, 2010
Commits on Jul 11, 2010
  1. Removing old methods.

    committed Jul 11, 2010
  2. Code cleanup

    committed Jul 11, 2010