Frequently Asked Questions (FAQ)

…and the frequently answered descriptions to it:

Some Joomla! Module might be a good fit to get used with MooBot content tags, however you may experience that one or more modules output will be left unprocessed by the MooBot.

The reason for that is the way that particular module is written. As per our experience modules that present content items mostly work with MooBot, however modules that generate its own output based on the Joomla! database might not trigger mambots at all. Thus leaving MooBot silent with all other mambots when sending its output.

One suggestion is to contact the Author of that particular module and to suggest to invoke mambots on the modules output as per the Joomla! offered API.

The Frontend Component of Joomla! 1.x is looking for a module parameter called firebots that controls if a module allows to trigger mambots on its output. This parameter requires to be set to 1 or true in the modules parameter .XML-File. That is as much support we are able to give on that.

We know of the following modules that might help to include MooBot effects into a module position:

Module Name Description
Content Item This modules allows for publishing content items or articles in module positions.
Note: Use the Setting “Run Plugins” to let this extension trigger all Content Plugins of Joomla, and with it the MooBot for processing the content before sending it to the page.
Include Content Item Is similar to the Joomla CustomHTML Module, and allows to enter any text. It does also trigger all Content Plugins of Joomla before sending the page, such that the MooBot is triggered as well.

Having MooBot published and your site is generating blank pages, then this may be caused by:

  • Insufficient server resources for PHP processing
  • Some type of error occurring and your server is set to suppress error outputs

When your site template stops loading with having the Extension published, than this may be related to insufficient memory resources configured on your Server for the PHP Scripting Engine. The current resource limits defined for PHP are too tight to support your Joomla installation with your current set of extensions loaded, therefore the PHP Scripting Engine stops processing the current script due to insufficient memory resources.

When having access to your Servers PHP.INI, then the following settings may help:


; Resource Limits ;

max_execution_time = 120     ; Maximum execution time of each script, in seconds
max_input_time = 60     ; Maximum amount of time each script may spend parsing request data
memory_limit = 32M      ; Maximum amount of memory a script may consume

The current or default setting for memory_limit may be too less to support the processing of your current Joomla environment. We suggest to allow at least 32M of memory for script execution.

Check your PHP Error Log for error messages that might prevent full execution of the extension or your Joomla site. All our extensions are thoroughly tested, however errors might occur on individual basis on different systems due to conflicts with other extensions or configuration issues on your server environment.

Your site might be configured to send any PHP error messages to a log file or to suppress it completely. On a Apache HTTPd server create a .htaccess file in your Joomla! root directory. Or use the one that might be already in place. Add the following PHP setting to enable output of all PHP error messages to the browser:

Enable Error Messages in .htaccess

php_flag display_errors on

Check if you see any error message from PHP in your browser. On complex templates these messages might disappear due to your template styling, so open the page as “Page Source” (commonly refered to as “View Page Source”) to see if and what PHP error message is occurring.

Having a blank page on your Joomla installation with using MooBot is mostly related to your Joomla and Server environment. Please understand that support to fix or improve your Joomla! or Server environment is outside of our scope of support.

When your Accordion Sections stay open using one of the Accordion Plugins with Internet Explorer, than that may be related to an template issue with your Joomla! template.

To make Accordions work with Internet Explorer in Version 6 (and maybe also in higher versions of) the site template requires to be of a specific HTML DOCTYPE. Make sure the first line in your Joomla Template specifies this to set the correct Document Type to make Accordions work:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "">

If you receive a Server Error Message, maybe similar to this:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

…then your servers configuration is not allowing our extension to use a server-side script for data exchange.

This is most relevant for all Site Popup Plugins which rely on loading additional content from the server to display in its windows. For that a server side script is accessed, which is located here:

On Joomla 1.0:

On Joomla 1.5:

Ensure that your servers configuration is allowing access and processing of this script. For testing purposes you may also directly access this script via your sites url:

On Joomla 1.0:

On Joomla 1.5:

Following situations may contribute to make your server create such error message:

  • The access privileges for the path of the server side script are incorrect
  • Using a .HTACCESS file (when using Apache HTTPd) in the root of your Joomla installation and another one on a deeper level directory, which settings are concurrent
  • Using some type of SEF extension which is using a .HTACCESS file (when using Apache HTTPd) and its setup is preventing direct access to the server side script (and trying to redirect to a different location)
  • You are using a .HTACCESS file which is in conflict with your general server configuration in HTTPD.CONF (when using Apache HTTPd) or any related global server configuration.
Please understand that any type of support for your server environment is outside of our scope of support on any type of our licenses and the related license fees.

Other components may or may not make use of the Joomla! Plugins, that depends on how the Source Code was written by the creators of such Component. To make a individual component aware of MooBot, some has to modify the Source Code of such component in order to call the MooBot Plugin and pass the data to be processed.

Here we have some example code to show how this might be accomplised:

Joomla 1.5: components/com_content/view/article/view.pdf.php

* Joomla 1.5
* File: components/com_content/view/article/view.pdf.php
* Modification to invoke Header-Footer Plugin for PDF also
class ContentViewArticle extends JView
	function display($tpl = null)
	  // process the new plugins
	  JPluginHelper::importPlugin('content', 'image');
	  // --- Modification to load the MooBot Plugin ---
	  JPluginHelper::importPlugin('content', 'moobot_ce');
	  // --- This triggers the loaded plugins and processes $article with $params ---
	  $dispatcher->trigger('onPrepareContent', array (& $article, & $params, 0));
	  $document = &JFactory::getDocument();

This here is only a example to show how to load the MooBot Plugin and execute it on some data. Particular changes may well be required for the individual component subject to modifications. Best is to have PHP and some Software Development experience for performing such task.