Intellectual Property is a full-featured real estate extension for the Joomla! CMS
IPReserve is a reservation extension for IProperty.
Need to keep track of your IProperty stats? Meet IReport - a reporting tool for IProperty!
Work Force is a staff listing extension for the Joomla! CMS. Show off your employees with style!
Report Card is a testimonials extension for the Joomla! CMS. What are people saying about your company or product?
Ultra Transport is a full-featured vehicle listing extension for the Joomla! CMS
Project Log is a project management extension for the Joomla! CMS. The best part is, it's totally free!
Have pre-sales questions or need support for an existing subscription? Look no further - we have active support forums and pride ourselves on friendly and timely response!
Not finding what you're looking for? Don't hesitate to contact us!
Before posting questions in the forums, please be sure to read the FAQs by clicking on the FAQs link in the sidebar product menu. You must be logged in and have a valid subscription to access the SUPPORT FORUMS.
elduderino created the topic: joomla core multi language integration
I believe it would be great if IP had the same multi language concept than the core joomla extensions. This will allow to stop depending on 3rd party extension to achieve that.
This should allow to easily manage translation and have the same "admin views/layout" when translating. Client, and myself included, always found weird to have to go in a complete different extension with a different name to translate property or content.
But more importantly, to be able to display properties according to the language selected by visitors.
I know Joomla is taking the "every thing is content" approach which basically means that extension item will be stored in the "_content" table, and each extension will simply "extend" each "content item" with its properties.
Pretty similar if not the same as what CCK FLEXIcontent is doing. It just extend content items with its own properties allowing to have virtually any type of custom field per "content item/article".
I hope my english is clear enough (it's not my mother language).