If anyone has used any of these CCK's
FlexiContent
and
K2
could you please write your impression pros and cons, I know I can test it myself but I thought if anyone has used it can write a few line, thank you.
I migrated over from MyBlog and think K2 is far superior in many ways. The only cons I have are:
1.) Content is stored outside com_content, so when J1.6 drops, we'll need to do some fancy SQL to port over the K2 content.
2.) Calls about 30K in js/css on EVERY page, not just the page that needs it (i.e., the blog page).
I just started using it and worked around the css loading on every page by setting the 'load k2 css?' to "no", creating a copy of my master template and assigning it to the blog, then taking the k2 css I need and adding it to my template copy assigned to the blog. This way, the css loads only on the blog page now and not on every page. I am still working on the k2 js from being called on everypage, but not a big issue...
It has everything that MyBlog and others lacked...permissions can be set at the category level, nested categories, clean code, simple editor for users, lots of bells and whistles in the 'item view', etc, etc, etc...a bazillion settings to customize it how you like.
I tested K2 when is was first released v1.0 it was buggy and since I didn't had any project I didn't bother, now I need to setup a site that requires CCK functionality I am looking at
FlexiContent
,
K2
and
Resources
, I could test all myself which I am doing but was looking to have an input from live site users, thanks for your input.
One thing about FlexiContent that I just read is that it does allow for forward and backwards compatibility with com_content. So, whether you revert to a previous version of Joomla or 1.6 you will be good to go.
At the same time, I have a HIGH RESPECT for Fotis and the Joomlaworks crew. They produce some awesome extensions. What they've done with K2 is phenomenal so far.
Just by a quick first use of both components, I like K2 better so far. Plus, I know they are working on implementing many new features, one I'm sure will be forward/backwards compatibility. It only makes sense. This could make or break CCK extensions my opinion. It's essential.
But, if you don't plan on converting from a CCK platform and aren't worried about compatibility at the moment, my vote would be K2. But again, that's just with a quick "play" with both.
I also like the fact that Joomlaworks is heavily involved in the Joomla Community. That usually shows promise of continued support and innovation of a component.
I also like that the k2 module (singular) does everything that the half dozen modules MyBlog takes to give it that blog-like feel...calendar, categories, most read, highest rated, archieves, bloggers, etc, etc. That way, you don't have a half dozen plugins all firing and calling a bunch of js files and the like....one module produces all of these toys just by running different queries.
And I now favor jcomments over Jomcomment, too...supplanted 2 commercial extensions for two open source extensions that are arguably superior.
I have not fully used FlexiContent, but it does look amazing. Looks like it can do what k2 can.
Flexicontent
- back end template editing is great, k2 does not have this. This is okay for people who do not know how to edit a php file.
- Nested categories: can't go wrong with that. I also love that an article can be in multiple categories. K2 does not have that
- Supports Jcomments & Jomcomment
Overall k2 out of the box seems to be favoring blogging. I still have not used Flexicontent, only messed with the back-end as well. It is still in beta, and has no modules. Flexicontent also uses Joomla's default permissions. K2 wins in user groups and permissions, because Flexicontent does not have this to the public.
www.flexicontent.org/forum/index.php?f=3...&rb_v=viewtopic#p889
Flexicontent also has no style at all.
It would be great
And I would be glad to provide my help (if needed).
Emmanuel.
PS: I'm the lead developer from FLEXIcontent
Welcome! I've been impressed with what i've seen with FLEXIcontent so far, we are considering supporting it in the future so please keep us in your development loop.