Latest Listings In Category - General Information

Joomla 1.5 Compatibility Statement

62 — Thu, 01 Jan 1970 00:00:00 +0100

Joomla Tags is fully compatible with Joomla 1.5.x

Tags Hangs when selecting it from the components menu

62 — Thu, 01 Jan 1970 00:00:00 +0100

If your server is behind a restrictive firewall that doesnt allow outgoing port 80 traffic from your server to the rest of the internet then all bfFramework components (Joomla Tags included) will stall when selected from the components menu.

The reason for this: bfFramework calls out to an XML file located at http://www.phil-taylor.com/versions.php in order to determine the latest version for the component so that you can be notified of updates available.

version.php is also passed your domain name, this is currently not logged, however in the future, should this feature be abused, we reserve the right to log incoming calls.

To skip the update check, and resolve this issue, simply edit

For Joomla 1.0.13+
/mambots/system/blueflame/bfChecks.php

For Joomla 1.5.x+
/plugins/system/blueflame/bfChecks.php

Near the top of that file there is an obvious line relating to skipping update checks, the default is false - change this to true and safe the file - this will prevent bfFramework from checking for updates.

Permission denied to call method XMLHttpRequest open

62 — Thu, 01 Jan 1970 00:00:00 +0100

Beacause of a browser security policy (called Same Origin Policy) dating back to Netscape days, the complex AJAX and Javascript contained in our Tags and KB components will not work unless you access the website using the exact same domain name as you have configured in configuration.php.

The most common problem is that you have configured www.domain.com and you are accessing now with domain.com. These two are considered by your browser to be totally different sites and thus the browser security stops you running javascript between them.

The solution - easy!

In order to proceed just retype the correct web address into your web browser making sure you access the site with the same url as in configuration.php

Remember that www.domain.com and domain.com are DIFFERENT HOSTS/DOMAINS for the purpose of the "Same Origin Policy"

This is not a bug or an issue with our code !! It is a security feature of all web browsers.

the same origin policy is an important security measure for client-side scripting (mostly JavaScript). The policy dates from Netscape Navigator 2.0, with necessary coverage fixes in Navigator 2.01 and Navigator 2.02. It prevents a document or script loaded from one "origin" from getting or setting properties of a document from a different "origin".