Yireo - Extensions, tutorials and blog for Magento and Joomla!

Introducing FLEXIcontent labs

For some time already, our improved Yireo site is live and kicking. Since some major changes, it is now based upon FLEXIcontent - a wonderful CCK-extension for Joomla! that allows you to flexibly built your content. Because we would like to share with you what we build, we decided to open up a special Yireo Labs section for FLEXIcontent: Here it is.

FLEXIcontent plugins for Yireo extensions

First of all, we have made various of our own Yireo extensions compatible with FLEXIcontent. This allows you to build a site with these extensions based upon FLEXIcontent:

• SimpleLists is able to point a small piece of text (item) to an external link: This external link can be a Joomla! article-page, but with this FLEXIcontent plugin it can also be a FLEXIcontent item.
• Dynamic404 catches all 404-errors when they occur, and is able to suggest the right page to the visitor by searching the Joomla! database. With this FLEXIcontent plugin, you can also search for FLEXIcontent items. Add to this the fact that Dynamic404 allows for automatic redirection to these FLEXIcontent items, and you have found the ideal tool to migrate from Joomla! articles to FLEXIcontent, without having to deal with numerous 404 Not Found hits.
• Not FLEXIcontent, but actually FLEXIaccess: MageBridge is able to add a customer X to a specific FLEXIaccess user-group when that customer X buys a specific product. You can use this to sell downloadable products the Joomla! way.

JFinder plugin for FLEXIcontent

Besides our own extensions, we have also worked with other extensions in relation with FLEXIcontent: For instance, we wanted to replace the core Joomla! search-functionality with JFinder. But there was no JFinder plugin yet available for FLEXIcontent. Instead we created it and are now able to share the result with you. The plugin can be found for free in the labs.

More stuff for FLEXIcontent?

While our own Yireo site contains more stuff we did with FLEXIcontent, we don't share this yet. Part of this is that, when you release something to the public, it should work under multiple configurations and not just for your own. One example of this, is the router-file: We found the default router-file of FLEXIcontent lacking (because various types of content were supported but not needed by us, while others caused numerous 301-redirects which we did not want), so we created our own. But the resulting router-file is probably giving you headaches when you try to implement it, so we keep it ours. But we hope to share more results with you in the neat future.