Sorry that you didn't understand the simplicity of this component. Install with one click. Just put your additional css-files into yours template/css directory. Don't forget to give them filename the prefix template_.
Then go to the components backend and assign the css-files to the menuitems you like.
That's all, easy goin'. You need no luck, but a little bit intelligence.
More then 10.000 Joomla! Websites works with css2switch without any problems. If the component is to strong, you are to weak. Tell the community your problem in a usefull way, or post your problem at our first aid support forum. People like you does'nt think about how much work and sweat developers like us puts into their work.
Thanks and "good luck" to you,
John | mediahof, Germany
If NinjaBoard can add an image gallery tied to the post preview process, then I think they would move ahead of Kunena at that point. Right now, you have simple text and linking abilities.
Keep up the great work Ninja!
Great editor with a full development team behind it with a good set of plugins.
Good plugin architecture for easily creating plugins.
There's no layout editor for moving/removing buttons or a group personality editor like JCE (major problem for us).
Still lacking some direct plugins for other popular components.
Not as configurable as JCE.
That the same support level we provide our clients so, outstanding. I would recommend purchasing this plugin to anyone.
If more payment gateways were added, this would be a rock star.
Link is optional (you can remove it w/o any damage). And free features acceleration is more than other free plugins provide.
Keep up the awesome work on this component.
What would make this even better is if we had an admin template which was K2 aware and would allow you to select K2 functions to replace the core Joomla content functions. That would be way cool!
While this component has great potential, it still lacks greatly when it comes to plugins and community support compared to Community Builder.
For the Intranet project we were hidred to build, we used CB because JommSocial Pro hadn't been battle tested in a corporate environment and LDAP support is sketchy at best. That didn't worry me as much as not having the Lists feature that CB has. Without lists, there is no way to create the equivalent of a company directory like we have done with CB without adding significant costs to the project.
Right now we see CB as the product of choice for internal company sites with heavy requirements and JSP for light weight social sites.
I am confident this outlook (hopeful) will change over the next year and look forward to all products maturing. The cool thing about this space in Joomla is that competition is heating up!
We now have CB, Joomsocial, Joomunity and Jcommunity.. wow..
Let the best product(s) win!