Latest Listings In Category - How Do I - Questions Answered

How do I backup my tags?

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

At the moment the only way of backing up is to use phpMyAdmin to backup all database tables that have the prefix jos_tag_ (Assuming that your joomla prefix is jos_ )

You could add a feature request in the forum so that we consider a backup system in a later version if you wish.

What to do if all you see is loading screen

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

The Loading messages that appears when you first enter the admin console of Joomla Tags should only appear for a maximum of 15 seconds, if they appear for longer then you have a problem.

Make sure you are running at least Joomla 1.0.13 - Joomla added new code in that version to power mambots in administrator.
Make sure that if you are using a custom administrator template that the code for that template fires mambots in admin console, - or simply switch back to the default Joomla admin template to test if this is your problem.
Use Firefox, and install the Firebug extension for Firefox
Once firebug is installed click F12 to show the debug console - there should be an error message in there - that will help us if you can tell us what that is. If the message is something like bfHandler not defined then check the following page loads on your site (replace joomla-tags.com with your domain - you should see a page of javascript: http://www.joomla-tags.com/mambots/system/blueflame/bfCombine.php?type=js&c=kb&f=mootools,jquery,jquery.tabs,jquery.thickbox_js,bfadmin_js,admin_js,jquery.accordion
Check that the cache folders are writeable, they are: /mambots/system/blueflame/cache

Upgrading between versions

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

We have simplified the process of upgrading to as easy as it can be.

Follow these steps:

BACKUP BACKUP BACKUP - Your mysql database and site.
VERIFY YOUR BACKUPS!
Download the latest version zip from https://secure.myjoomla.com
Uninstall the component from your website, dont worry all your data will be safe,we never delete it!
Install the new zip file as a component using the Joomla installer
Select the newly installed component from the components menu in Joomla
Follow any wizard prompts about upgrade tasks.
Using the addons menu item in the newly installed component, uninstall and then install all addons one by one.
Verify that your site is online.

Thats it! Easy eh?! :-)

How do I upgrade to the newer version

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

The upgrade for all our components is always:

* BACKUP your sites files and database
* and BACKUP your sites files and database again!
* Download the latest version from myJoomla.com
* Make sure your backups are useable!
* uninstall all related mambots/modules/core patches that the component provides
* uninstall component
* install component - got ot the component in the Components Menu - follow the onscreen prompts.
* reinstall and patches/mambots/modules using built in installer in the component.

We are different to many component developers because our installs are full versions and upgrades all in one. Especially the newer components (JoomlaTags and JoomlaKB) as the bfFramework they are bult upon handles the complete database schema updates as well.

Also we are different in so much as when you uinstall our components we NEVER delete/drop/dump your database tables for that component! This means the data is safe in the database and when you install a newer version of our products the data can still be got to and used using the newer components interface.

Overcome conflict with JPromoter Mambot

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

We are aware of a conflict that happens with the bfFramework and JPromoter Mambot.

This is caused because both want to start the PHP Session for administrator. Now this could be argued that this is our problem or theirs as our framework calls system mambots on the admin side which is not a "normal" feature of Joomla (We always push the boundries!!) - and it could be a JPromoter issue because they blindly start a PHP session without regard for other components, namespaces or the fact that by loading system mambots in admin, their code has been run in admin when it never was intended/required.

The fix is simple.

In our framework we define a constant, and you will need to make a small change to the /mambots/system/jp.metaedit.php file to ensure their code is not run when it is not needed.

The change is to wrap the following code:

@session_start();
$_MAMBOTS->registerFunction( 'jpMetaEdit', 'jpmetaedit' );
global $mosConfig_absolute_path, $mosConfig_live_site;
require_once( $mosConfig_absolute_path.'/administrator/components/com_jp/joomlaequipment.config.php');
$_SESSION['REQ_URI'] = $_SERVER['REQUEST_URI'];

with a check - like this:

if (!defined('__BFADMINENTRY__')){
@session_start();
$_MAMBOTS->registerFunction( 'jpMetaEdit', 'jpmetaedit' );
global $mosConfig_absolute_path, $mosConfig_live_site;
require_once( $mosConfig_absolute_path.'/administrator/components/com_jp/joomlaequipment.config.php');
$_SESSION['REQ_URI'] = $_SERVER['REQUEST_URI'];
}

This will ensure that the jp.metaedit.php file doesnt corrupt the admin session when used through bfFramework

JCE Conflict Causes Tabs in Preferences Screen Not To Load

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

We are aware that JCE Editor Mambot currently ijects jQuery into the DOM, sometimes this happens after our own jQuery and this wipes out our jQuery extensions for the Tabs that display on the preferences screen.

The quick solution is to stop JCE including the outdatedjQuery 1.2.1

This can be done by adding one line of code to:

/mambots/system/jceutillities.php

Look for the line 79 (Thats the line with "/mambots/system/jceutilities/js/jquery-121.js" in it.

Place the following code IMMEDIATLY BEFORE that line (Create a new line before it and then paste it in - so its after the line that talks about pngFix)

if (!$mainframe->isAdmin() && ($option!='com_tag' || $option!='com_kb'))

Job Done! - It should nowork!

JCE Editor Javascript Issue

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

We are aware of an issue with the JCE Editor that can cause javascript errors in the admin console of Joomla Tags/Knowledgebase.

We have investigated this and found it to be a problem in the JCE tiny_mce.js file, basically it doesnt check if a var is an object before attempting its methods.

To over come this problem simply download the attachment below and overwrite using file contained in the zip file, the following JCE core file:

/mambots/editors/jce/jscripts/tiny_mce/tiny_mce.js

JoomFish Conflict JRegistryFormatINI

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

It has come to our attention that more and more developers are back porting Joomla 1.5 code into Joomla 1.0.x components :-)

While this is good for code reuse, it can made compatibility a nightmare.

An example is with Tags/KB and JoomFish

If you are getting the error:

Fatal error: Cannot redeclare class JRegistryFormatINI in /home/domain/public_html/new/administrator/components/com_joomfish/libraries/joomla/format/ini.php on line 23

Then you have fallen foul of this :- )

The easy fix is to edit the file:

/administrator/components/com_joomfish/libraries/joomla/format/ini.php

and before the class declaration (thats the line that starts "class JRegistryFormatINI extends JRegistryFormat") add the following code:

if (!class_exists('JRegistryFormatINI')) {

then right at the bottom of the file before the closing ?> add another } brace like this:

} ?>

Save the file and upload it again and the conflict is resolved.

JReviews and Joomla Tags Compatibility

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

The good news is that you can use JReviews and Joomla Tags on the same site - as long as you are running the latest versions of each component.

YOU MUST install JReviews first

Then rename /mambots/system/xajax.system.php to xajax.system.php.saved

Then rename /mambots/system/xajax.system-mambo.php to xajax.system-mambo.php.saved

Then install joomla Tags/Joomla Knowedgebase and follow through the admin screens in that component (This will install the bfFramework version of xajax)

Then both components will work :-)

How do I disable the Live Chat in the component?

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

You need to edit the following file:

/mambots/system/blueflame/bfTweaks.php

/plugins/system/blueflame/bfTweaks.php

And toggle the true/false on the following lines:

/* Live Chat Integration */
define('_BF_CHAT', false); //default: true
define('_BF_CHATMONITOR', false); //default: true