Chronicle and reorder extensions are not compatible

[Pascal Naef]

Hallo

I installed latest versions of the reorder- and the chronicle-
extension. Thus reorder-extension doesn't work anymore. I found out
that both extensions overwrite methode "children_find_options" with
"alias_methode_chain".

Chronicle:
alias_method_chain :children_find_options, :draft_versioning
Reorder: alias_method_chain :children_find_options, :reorder

The only solution I know is to fork chronicle-extension and integrate
reorder logic in it. Is that the right way or can this error be solved
directly in the extensions.


Thx
Pascal

[Jason Garber]

Hi, Pascal. Yes, the two are incompatible. I wanted to use the
reorder extension too, but didn't have the time to integrate the two.
If you find a way to make the two work together (it's very complex at
this point), please do so in a fork of Chronicle with some logic so
that having the reorder extension is optional.

I'm working on finding a way to plug Chronicle and Multi-site into
some hooks in core so that they cause fewer compatibility problems.
At the rate I'm going, though, it will be a few months.

Best,
Jason

> --
> Radiant CMS Dev Mailing List
> Post: radiant...@googlegroups.com
> Unsubscribe: radiantcms-de...@googlegroups.com
> Group Site: http://groups.google.com/group/radiantcms-dev/

[Jonathan Kinney]

Regarding the incompatibilities mentioned in this email from a while
ago: I wonder if it would be possible to have some sort of matrix of
incompatibilities amongst extensions? It seems like it would be a
massive undertaking but would help save implementers / developers
hours of struggling to figure out incompatibilities.

Or maybe we could have some community maintained launch point versions
of Radiant... like a git repo that has the default Radiant with a
certain subset of extensions installed that is guaranteed to work out
of the box... like a blog edition, or a product catalog edition?

It would help people get going and still maintain the separation
between the core of Radiant and the extensions from 3rd party
developers.

Just a few thoughts for us all to ponder, let me know if anyone thinks
this is a bad idea.

Thanks,
-Jon

[Sarah Allen]

I really like the idea of a variant of Radiant or something based on
Radiant that bundles a number of extensions that are tested to work
together (and maybe where the UI is tweaked to be consistent and make
sense together). It would be great to have such a thing for blogging.

Sarah

http://www.ultrasaurus.com

[Jason Garber]

Sean, John and others have kicked around the idea of a "radiant-more" package that would have some of the most popular extensions. It's a great idea. I haven't made much progress on getting chronicle more compatible with the likes of reorder just because of time. Hope to soon, though!

[John W. Long]

Yes I'm very excited about this idea. Ultimately I'd like for people
to be able to do something like this:

radiant --with extension-set-name path/of/new/radiant/install

Extension sets would be a new part of the extension registry. Someone
could create an extension set on the registry website and then others
could use radiant command to fetch the information from the website
and install the appropriate extensions. This would make it easy to do
something like this:

radiant --with blogging path/of/new/radiant/install

To get a Radiant install with blogging support baked in. Of course
this doesn't directly address the idea of installing specific
versions, but gem support with dependencies could address that.
Perhaps a new flag could be added if you wanted to run on the latest
versions of everything (knowing that they may not work well together):

radiant --edge --with blogging path/of/new/radiant/install

--
John Long
http://wiseheartdesign.com
http://recursivecreative.com