Great ewel, this will go in next build for sure, as fixes problems with templates like JA ones using special menus.

Thanks

ewel wrote:
So far RC2 works like a charm!

While uninstalling RC1 and installing RC2 I was reminded that in each new version I make a small modification to avoid conflicts between javascript libraries. I use a module called FunkySlide which does not appear on FB pages without my modification, due to such a conflict, and I think others may have the same issue with other modules.

The modification I do is very small and simple. In RC2, in components/ com_fireboard/ fireboard.php, in line 231, I inserted:

Code:

jQuery.noConflict();

So, as modified lines 320-326 are as follows:

Code:

$mainframe->addCustomHeadTag('<script type="text/javascript"> jQuery.noConflict(); //1: show, 0 : hide jr_expandImg_url = "' . JB_URLIMAGESPATH . '";</script>');

Perhaps it would be good to include this in the next downloadable files.

When I do a clean install I get this error:
(installation is ok.. I get this when going to FB admin)

Mackelito wrote:
When I do a clean install I get this error:
(installation is ok.. I get this when going to FB admin)

Code:

/** * $Id: editor_plugin_src.js 201 2007-02-12 15:56:56Z spocke $ * * @author Moxiecode * @copyright Copyright © 2004-2007, Moxiecode Systems AB, All rights reserved. */ /* Import plugin specific language pack */ tinyMCE.importPluginLanguagePack('emotions'); // Plucin static class var TinyMCE_EmotionsPlugin = { getInfo : function() { return { longname : 'Emotions', author : 'Moxiecode Systems AB', authorurl : 'http://tinymce.moxiecode.com', infourl : 'http://wiki.moxiecode.com/index.php/TinyMCE:Plugins/emotions', version : tinyMCE.majorVersion + "." + tinyMCE.minorVersion }; }, /** * Returns the HTML contents of the emotions control. */ getControlHTML : function(cn) { switch (cn) { case "emotions": return tinyMCE.getButtonHTML(cn, 'lang_emotions_desc', '{$pluginurl}/images/emotions.gif', 'mceEmotion'); } return ""; }, /** * Executes the mceEmotion command. */ execCommand : function(editor_id, element, command, user_interface, value) { // Handle commands switch (command) { case "mceEmotion": var template = new Array(); template['file'] = '../../plugins/emotions/emotions.htm'; // Relative to theme template['width'] = 250; template['height'] = 160; // Language specific width and height addons template['width'] += tinyMCE.getLang('lang_emotions_delta_width', 0); template['height'] += tinyMCE.getLang('lang_emotions_delta_height', 0); tinyMCE.openWindow(template, {editor_id : editor_id, inline : "yes"}); return true; } // Pass to next handler in chain return false; } }; // Register plugin tinyMCE.addPlugin('emotions', TinyMCE_EmotionsPlugin); Fatal error: Class 'mosMenuBar' not found in /home/wombat/domains/joomlarefinery.com/public_html/administrator/components/com_fireboard/toolbar.fireboard.html.php on line 136

This does not look like an FB error. The error mosMenuBar no found, points to a Joomla setup problem. This particular part of the code in FB has been unchanged for about a year. It has been in 1.0.4 and all 1.0.5 builds.
In case you are on J1.5.x: Do you still have the legacy plugin enabled?

Hello,

the French translation and the template "defaut_ex" modified for the French are available.

Great job for this new version, thank you very much from the French community.

Yepp I´m running 1.5 and leagacy on... I had the same problem with AEC but fixed it by editing "toolbar.acctexp.html.php":

for more info:
www.theartofjoomla.com/magazine/article/...-legacy--part-3.html


When trying the same thing on FB I can go to the admin but cannot create new categories etc etc...

Mackelito wrote:
Yepp I´m running 1.5 and leagacy on... I had the same problem with AEC but fixed it by editing "toolbar.acctexp.html.php":

for more info:
www.theartofjoomla.com/magazine/article/...-legacy--part-3.html


When trying the same thing on FB I can go to the admin but cannot create new categories etc etc...

You should not try to convert FB to a native application. It cannot be done by a few edits here and there. It is a Joomla 1.0.x native application and requires the legacy plugin enabled. As long as you do this error will not come up.

Believe me, if it was that easy to convert FireBoard 1.0.5 into a native J1.5.x application we would have done it. That's why we are working on FB2.0.

Well I only did it cuz I was desperate

It wont work for me if I´m installing the normal way and using legacy plugin enabled... any Ideas?

Mackelito wrote:
Well I only did it cuz I was desperate

It wont work for me if I´m installing the normal way and using legacy plugin enabled... any Ideas?

What files of you install did you edit by hand? It looks like your legacy plugin is either not enabled or portions of it are missing.

At this point I have not edited any thing... I just get the error after a clean install.

Mackelito wrote:
At this point I have not edited any thing... I just get the error after a clean install.

I am not referring to the FB install. Your Joomla install has been modified and does not seem to provide the legacy support require. You yourself stated that you had to edit another component as well. That should not be required for any component unless Joomla itself got modified.
The Joomla legacy support of your site does not seem to be what comes with Joomla. It is really hard to guess these things with little to no info of the underlying system.
I have visited your site and it is a great looking but highly custom Joomla install. I suggest you check your setup against a clean Joomla 1.5.x install. Something has been modified and you might not be aware of it, or are just not communicating it.