I won't go into a repeat of the documentation provided in the Wiki so I'll just provide the link. http://www.bestofjoomla.net/wiki/com_fir...elease_1.0/upgrading

As I've just completed an upgrade from 1.0.3 to the latest release I must warn you beforehand that, as of now, your config file will be reset to the Fireboard defaults upon upgrade and you will need to reconfigure it.

Edit:
For those of us that don't like, or simply REFUSE to read through pages in a long post I will TRY to consolidate all issues and their respective fixes/workarounds here. If there are any that I missed or any whose fix/workaround is incorrect PLEASE send me a PM so that I can correct this. DO NOT SPAM THIS THREAD with these notifications & DO NOT PM ME WITH NEW ISSUES.

Config file overwritten.
Fix/Workaround:www.bestofjoomla.com/component/option,co...imitstart,100/#36320
Seyret commenting in Fireboard illegible
Fix/Workaround:www.joomlaholic.com/index.php?option=com...;id=8705&catid=2
Quoted text does is no longer highlighted.
Fix/Workaround:www.bestofjoomla.com/component/option,co...limitstart,60/#35993
Quick Reply box always open.
Fix/Workaround:www.bestofjoomla.com/component/option,co...limitstart,20/#35571
Fix/Workaround:www.bestofjoomla.com/component/option,co...limitstart,60/#36010
Fix/Workaround:www.bestofjoomla.com/component/option,co...limitstart,30/#36142
The "size" option of the tag IMG not work.
Fix/Workaround:www.bestofjoomla.com/component/option,co...limitstart,80/#36171
Image codes in quote box.
Fix/Workaround:www.bestofjoomla.com/component/option,co...limitstart,70/#36037
Problem with tag CODE.
Fix/Workaround:www.bestofjoomla.com/component/option,co...limitstart,70/#36128
Sccroll Bars on posts.
Fix/Workaround:TBD-Cause cannot be duplicated.
Legacy HTML tags.
Fix/Workaround:www.bestofjoomla.com/component/option,co...w/id,36195/catid,79/
No line breaks in post.
Fix/Workaround:Fixed in or before SVN 550
Escaped characters in search results.
Fix/Workaround:TBD
Cannot change font size
Workaround:www.bestofjoomla.com/component/option,co...imitstart,110/#36410

Yes, it true and bad.

FB should keep the configuration in a different file like fb_configuration.php just like Joomla's configuration.php.

Then how can we upgrade it? Can I delete the file administratorcomponentscom_fireboardfireboard_config.php from the official upgrading patch and upload rest files?

Thanks.

I don't know what's different in the NEW config file and the old as I haven't opened them up for comparison. So deleting it may or may not work. I didn't see any difference of added/changed options in the config (yet) so I cannot say.

How's THAT for a definitive answer?

I have a few websites using fireboard and I just upgraded my personal one just to see how its works, and to me this new release is a little bit problematic. People that does not know how to edit or change code manually could have problems. For example the seyret video component in my website was working fine with the comments integration with fireboard 1.0.3 but now its just a bunch of crappy code errors. The solution was to cancel the integration for fireboard comments in seyret. Please try to make full backups before any upgrades just in case. If the forum upgrade goes well it will be no problem with if there is some errors and you dont have a backup you will be stuck a few days or more figuring how to fix it(you will always find a way but the problem is the time), and this could be a major headache for people with forums with lots of traffic. So be safe, make a backup, learn how to use the backup, be sure that you know how to install the backup and then make the jump.

I got big problem after upgrading to 1.0.4.

When I click the 'forums' link on the front end, it says:

Parse error: syntax error, unexpected '}' in public_html/components/com_fireboard/fireboard.php on line 922

When I go to the backend, it is huge mess:

[code:1]; // no negatives! if($since // finding the biggest chunk (if the chunk fits, break) if (($count = floor($since / $seconds)) != 0) { break; } } // set output var $output = ($count == 1) ? '1 '.$name : $count.' '.$names ; // step two: the second chunk if ($i + 1 FINE('_MESSAGE', 'Message'); DEFINE('_NO_SMILIE', 'no'); DEFINE('_FORUM_UNAUTHORIZIED', 'This forum is open only to registered and logged in users.'); DEFINE('_FORUM_UNAUTHORIZIED2', 'If you are already registered, please log in first.'); DEFINE('_MESSAGE_ADMINISTRATION', 'Moderation'); DEFINE('_MOD_APPROVE', 'Approve'); DEFINE('_MOD_DELETE', 'Delete'); //NEW in RC1 DEFINE('_SHOW_LAST', 'Show most recent message'); DEFINE('_POST_WROTE', 'wrote'); DEFINE('_COM_A_EMAIL', 'Board Email Address'); DEFINE('_COM_A_EMAIL_DESC', 'This is the Boards email address. Make this a valid email address'); DEFINE('_COM_A_WRAP', 'Wrap Words Longer Than'); DEFINE('_COM_A_WRAP_DESC', 'Enter the maximum number of characters a single word may have. This feature allows you to tune the output of FireBoard Posts to your template.
70 characters is probably the maximum for fixed width templates but you might need to experiment a bit.
URLs, no matter how long, are not affected by the wordwrap'); DEFINE('_COM_A_SIGNATURE', 'Max. Signature Length'); DEFINE('_COM_A_SIGNATURE_DESC', 'Maximum number of characters allowed for the user signature.'); DEFINE('_SHOWCAT_NOPENDING', 'No pending message(s)'); DEFINE('_COM_A_BOARD_OFSET', 'Board Time Offset'); DEFINE('_COM_A_BOARD_OFSET_DESC', 'Some boards are located on servers in a different timezone than the users are. Set the Time Offset FireBoard must use in the post time in hours. Positive and negative numbers can be used'); //New in RC2 DEFINE('_COM_A_BASICS', 'Basics'); DEFINE('_COM_A_FRONTEND', 'Frontend'); DEFINE('_COM_A_SECURITY', 'Security'); DEFINE('_COM_A_AVATARS', 'Avatars'); DEFINE('_COM_A_INTEGRATION', 'Integration'); DEFINE('_COM_A_PMS', 'Enable private messaging'); DEFINE('_COM_A_PMS_DESC', 'Select the appropriate private messaging component if you have installed any. Selecting Clexus PM will also enable ClexusPM user profile related options (like ICQ, AIM, Yahoo, MSN and profile links if supported by the FireBoard template used'); DEFINE('_VIEW_PMS', 'Click here to send a Private Message to this user'); //new in RC3 DEFINE('_POST_RE', 'Re:'); DEFINE('_BBCODE_BOLD', 'Bold text: [b]text[/b] '); DEFINE('_BBCODE_ITALIC', 'Italic text: [i]text[/i]'); DEFINE('_BBCODE_UNDERL', 'Underline text: [u]text[/u]'); DEFINE('_BBCODE_QUOTE', 'Quote text: [quote]text[/quote]'); DEFINE('_BBCODE_CODE', 'Code display: [code]code[/code]'); DEFINE('_BBCODE_ULIST', 'Unordered List: [ul] [li]text[/li] [/ul] - Hint: a list must contain List Items'); DEFINE('_BBCODE_OLIST', 'Ordered List: [ol] [li]text[/li] [/ol] - Hint: a list must contain List Items'); DEFINE('_BBCODE_IMAGE', 'Image: [img size=(01-499)]http://www.google.com/images/web_logo_left.gif[/img]'); DEFINE('_BBCODE_LINK', 'Link: [url=http://www.zzz.com/]This is a link[/url]'); DEFINE('_BBCODE_CLOSA', 'Close all tags'); DEFINE('_BBCODE_CLOSE', 'Close all open bbCode tags'); DEFINE('_BBCODE_COLOR', 'Color: [color=#FF6600]text[/color]'); DEFINE('_BBCODE_SIZE', 'Size: [size=1]text size[/size] - Hint: sizes range from 1 to 5'); DEFINE('_BBCODE_LITEM', 'List Item: [li] list item [/li]'); DEFINE('_BBCODE_HINT', 'bbCode Help - Hint: bbCode can be used on selected text!'); DEFINE('_COM_A_TAWIDTH', 'Textarea Width'); DEFINE('_COM_A_TAWIDTH_DESC', 'Adjust the width of the reply/post text entry area to match your template.
The Topic Emoticon Toolbar will be wrapped accross two lines if width [/code:1]

What can I do??? downgrade to 1.0.3??? help pls!!

Upgraded and now my forum is a mess. Text unreadable and this code is under members and guest:

Warning: Invalid argument supplied for foreach() in /usr/local/4admin/apache/vhosts/ohioinspectionsgroup.com/addon/pacificnorthwestinspections.com/components/com_fireboard/template/default/plugin/who/whoisonline.php on line 75

Warning: Invalid argument supplied for foreach() in /usr/local/4admin/apache/vhosts/ohioinspectionsgroup.com/addon/pacificnorthwestinspections.com/components/com_fireboard/template/default/plugin/who/whoisonline.php on line 102


Whats wrong here?

Thanks

People please always make backups, its common sense everytime we use a new version of anything we should make backups. I can edit and check for errors manually but I always make a backup. Fireboard interracts with other things in joomla so you will have to check CB, Seyret or any other thing related to fireboard that you could have installed. I make an upgrade from 1.0.3 to 1.0.4 and knowing what I was doing the new version turned my Seyret video component in crap, so I left seyret not integrated to fireboard till any of the two companies resolve the software conflict, i have a few websites with both components installed and I will not upgrade to fireboard 1.0.4 until I can test in my personal website that there will be no problems. So anyone who does not have programer skills or know how to check the code manually I recommend to stay away of upgrades without full backups.

Joomlaholic just relesed a fix for their fireboard comments pluging for the seyret video component

You can download the file here:

www.joomlaholic.com/index.php?option=com...;id=8705&catid=2

you have to put in your website joomla components in:

/public_html/components/com_seyret/plugins/comment/

iosoft wrote:
Yes, it true and bad.

FB should keep the configuration in a different file like fb_configuration.php just like Joomla's configuration.php.

We will do just that and more, once the new bugs are taken care of.

Thx!