No templates are included with any of our products. This is normal for any Joomla sales-- templates are a totally different type of product than components, modules, etc-- and are not covered under the same licensing rules.

You can apply virtually any standard Joomla template with our products; however, some template designers use non-standard libraries which may affect the way our extensions behave. We recommend first applying a default template to see if problems persist BEFORE posting on the support forums.

We use Rocket Theme templates extensively in our work. The template used in our Joomla 3 IProperty demo site is RT Lumiere. The template used on the Joomla 2.5 IProperty demo site is RT Modulus. The template on the Joomla 1.5 IProperty demo site is RT Affinity. Visit RocketTheme to see other available templates.

Absolutely not! We support open-source developers, and we would not undermine their business by distributing their products. Our plugins for products (sh404SEF, Joom!Fish, Falang, JomComment, etc) are meant to extend the functionality of IProperty to work with these fine products.

You must purchase or install the third-party products from their developers, then enable/install the IP plugin for that particular product.

We're sorry, but due to the dangers inherent in offering unencrypted, open source software, we cannot provide demo copies of our software. UNDER NO CIRCUMSTANCES CAN WE PROVIDE REFUNDS OR RETURNS ON OUR PRODUCTS!

PLEASE-- use the demo sites and our forums to ask questions if you're not sure that the product will do what you need. If you still have questions, email us at info@thethinkery.net and we'll do our best to help you.

While a support subscription is only valid for a single domain, this does not include testing/development. You are welcome to install on a testing domain while you are developing, then move the site and license to another domain for production use.

We unfortunately can't take the time to help you customize every aspect of your site, though we're happy to help with issues or errors in our products.

Our support is limited to fixing actual issues with our products. All of our products are unencrypted and open source-- you are welcome to make modifications as you need to make the products fit your template, layout, color scheme and needs.

Please be aware that modifications to the product may break future upgrades-- we cannot support customized versions of our products.

If you need a customized version of the product, please contact us for a quote.

Editing language text in Joomla 2.5

Instead of editing the language files as explained below, J2.5 has a language override feature which may save you time and trouble. By using overrides, your language file changes will not be lost when upgrading from one version to the next. Go to your admin panel 'Extensions->Language Manager->Overrides' and create new overrides for the language file text that you want to change!

Editing language text in Joomla 1.5

To change any of the text you see throughout the component, you can edit the language files. There is one language file for the administrator panel and one for the front-end. To edit the language files, you may either use a translation component (for example, Translation Manager) or edit the language files in a text editor.

The translation manager component will allow you to edit and create new language files via the Joomla! admin panel. Editing the files with a text editor will require downloading the language file, making your changes and uploading the file to it's original location. Either way is fairly straight forward and easy to do.

Changing the language files is useful in many cases; from changing a popup alert box to say something different to changing a form field name. The language files, if used correctly, could save a lot of time in custom development and will also keep the component files untouched - making your future upgrade process less of a hassle. Below are the locations of the language files (in this case, for com_iproperty English). Each language should have a seperate folder - you may need to install the language packs from Joomla if you don't see your language files.

Location of Language Files:

Admin Language File Location: administrator/language/en-GB/en-GB.com_iproperty.ini

Site Language File Location: language/en-GB/en-GB.com_iproperty.ini

How to edit language files in a text editor:

When editing the language files you will see the language variable and it's definition in the following format:

If you would like to modify the 'Definition' to say something different, you would simply edit like:

After changing all of the language variables to your new definitions, save and upload the language file back to it's original location.

For more information please read this tutorial. This tutorial deals with template translation but same basic idea applies for component text translations.

There may be occasions where you would like to change the way a Joomla! Extension (such as a Component or Module, whether from the Joomla! core or produced by a third party) is displayed on your site. Of course, you could recode the Extension from scratch, but that may be a bit ambitious for you! Thankfully, there is another way.

The standard output from any Joomla! Module or Component can be overridden by adding code to the html directory of your template. It is also possible to override two aspects of core functionality: Module chrome, and pagination.

Learn More: Understanding Output Overrides How to override output in Joomla Layout Overrides

As of this writing, Google will only charge for over 25,000 map loads per DAY. The vast majority of our users will not hit that limit in a month.

If you have more than 25,000 unique property views in a day, you can sign up for the Google Maps Premier license or pay for overages individually.

If you get a message that looks like:

please read this page: http://www.php.net/manual/en/errorfunc.configuration.php#ini.error-reporting

The important things to notice are:

1. Notices and warnings are not errors-- they are typically used to help during development to point out possible sloppy bits of code, or to help developers ensure that they've set variables correctly etc.
2. You probably do not want to be displaying errors/warnings/notices on a production website. Best practice is to set error_reporting to OFF and your log level to Warnings and above.

Please ensure that your error reporting is turned off on your production site. And on a development site, if you know what you're doing and have your error reporting a bit sensitive so you can find errors in your site, don't be overly concerned about Notices and Warnings.

If you get Fatal Errors, then we're happy to help you find a fix. Notices are not really a problem and as of Joomla 3, should be non-existent in Thinkery products.

If you've submitted a payment, but don't obtain access to the appropriate downloads or support immediately, your payment may be on hold.

PayPal or other payment gateways may flag payments if account information is different than their records -- different email address, etc.

We apologize for any inconvenience, and payment holds are typically released after a day or two. Once the payment has been approved, your subscription and access will be activated.