racoon wrote:
Did you installed SVN 551 or the javascript workaround for the code tag issue?

I installed SVN551 but donīt work for me. Can you put the link to javascript workaround for the code tag issue?

Thanks!

juanma wrote:
racoon wrote:
Did you installed SVN 551 or the javascript workaround for the code tag issue?

I installed SVN551 but donīt work for me. Can you put the link to javascript workaround for the code tag issue?

Thanks!

Look at this:

www.bestofjoomla.com/images/fbfiles/file...a5be455e3f211756.txt

Some days ago this workaround helps to display lines after the code tag correctly. But this has a side effect: the preview does not work if there is a code tag. If 551 is installed, then change it back. The javascript workaround is no longer needed.

upgrade from 1.0.0 to 1.0.4 using sql script as per instructions failed in this code:

Code: :


/* Alter table in Second database */
alter table `jos_fb_categories`
add column `headerdesc` text NOT NULL after `description`,
add column `class_sfx` varchar(20) NOT NULL after `headerdesc`,
add column `id_last_msg` int(10) NOT NULL DEFAULT '0' after `class_sfx`,
add column `numTopics` mediumint(8) NOT NULL DEFAULT '0' after `id_last_msg`,
add column `numPosts` mediumint(8) NOT NULL DEFAULT '0' after `numTopics`,
add column `time_last_msg` int(11) NULL after `numPosts`,
drop key `catid`,
drop key `catparent`,
add KEY `msg_id`(`id_last_msg`),
add KEY `parent`(`parent`),
add PRIMARY KEY(`id`),
add KEY `published_pubaccess_id`(`published`,`pub_access`,`id`), COMMENT='';




Error message and current file structure:

SQL Error

Can't DROP 'catid'. Check that column/key exists.

Query: /* Alter table in Second database */ alter table `jos_fb_categories` add column `headerdesc` text NOT NULL after `description`, add column `class_sfx` varchar(20) NOT NULL after `headerdesc`, add column `id_last_msg` int(10) NOT NULL DEFAULT '0' after `class_sfx`, add column `numTopics` mediumint(8) NOT NULL DEFAULT '0' after `id_last_msg`, add column `numPosts` mediumint(8) NOT NULL DEFAULT '0' after `numTopics`, add column `time_last_msg` int(11) NULL after `numPosts`, drop key `catid`, drop key `catparent`, add KEY `msg_id`(`id_last_msg`), add KEY `parent`(`parent`), add PRIMARY KEY(`id`), add KEY `published_pubaccess_id`(`published`,`pub_access`,`id`), COMMENT=''


File does not include the fields!!
File

id int(11) PRI
parent int(11) YES
name tinytext YES
cat_emoticon tinyint(4)
locked tinyint(4)
alert_admin tinyint(4)
moderated tinyint(4)
moderators varchar(15) YES
pub_access tinyint(4) YES
pub_recurse tinyint(4) YES
admin_access tinyint(4) YES
admin_recurse tinyint(4) YES
ordering tinyint(4)
future2 int(11) YES
published tinyint(4)
checked_out tinyint(4)
checked_out_time datetime
review tinyint(4)
hits int(11)
description text
image varchar(255)

Did you even read this thread before you posted? The thread you NEEDED to READ was here.
www.bestofjoomla.com/component/option,co...w/id,27233/catid,79/

I did read it, just went through it again... must be missing something or it goes right over my head, as I see a lot of different problems and lots of technospeak but could not match to my problem. What I seem to get from that is that each bit of the SQL script should be run separately, OK, but their still remains the oddness of the missing fields which I saw no mention of.

I was upgrading from 1.0.0 beta and it does not give a specific sql for the beta version... or is 1.0.0 beta the same as 1.0.0 ?

So I am still stuck at the moment. I do need to get this new version up asap as it was buggy. I have another site using 1.0.0 beta that I also want to upgrade

Look at the download list at this link. Does it have a 1.0.0?
www.bestofjoomla.com/component/option,co...1/catid,3/Itemid,67/

The link I gave you and this one

www.bestofjoomla.com/component/option,co...w/id,20600/catid,79/

deal with every possible upgrade error you could deal with. Read those AND the Upgrading info found in the Wiki at this link.
www.bestofjoomla.net/wiki/com_fireboard/release_1.0/upgrading.

This link will help you if you do not know what to do with the SQL upgrades.
www.bestofjoomla.com/component/option,co...w/id,26252/catid,79/

The 1.0.0 without beta on the end was the title to the instructions I followed here www.bestofjoomla.net/wiki/com_fireboard/release_1.0/upgrading

So I then downloaded 1.0.4 patch files and uploaded them over the old files.

The I used the SQL Upgrades/Fireboard_100_to_1.0.3.Stable.sql.

I understand I can bypass any SQL that does not work, but surely the files will then not be correct for 1.0.4. Sorry if I seem dense searching on 'missing field' finds nothing relevant and I have ploughed through lots of threads - I understand the basics of sql but not in any depth, I can follow what the commands are trying to do. In theory I could just run the part of the command that adds the extra fields, is that is what is being said? So for example

instead of
alter table `jos_fb_categories`
add column `headerdesc` text NOT NULL after `description`,
add column `class_sfx` varchar(20) NOT NULL after `headerdesc`,
add column `id_last_msg` int(10) NOT NULL DEFAULT '0' after `class_sfx`,
add column `numTopics` mediumint(8) NOT NULL DEFAULT '0' after `id_last_msg`,
add column `numPosts` mediumint(8) NOT NULL DEFAULT '0' after `numTopics`,
add column `time_last_msg` int(11) NULL after `numPosts`,
drop key `catid`,
drop key `catparent`,
add KEY `msg_id`(`id_last_msg`),
add KEY `parent`(`parent`),
add PRIMARY KEY(`id`),
add KEY `published_pubaccess_id`(`published`,`pub_access`,`id`), COMMENT='';
say
alter table `jos_fb_categories`
add column `headerdesc` text NOT NULL after `description`,
add column `class_sfx` varchar(20) NOT NULL after `headerdesc`,
add column `id_last_msg` int(10) NOT NULL DEFAULT '0' after `class_sfx`,
add column `numTopics` mediumint(8) NOT NULL DEFAULT '0' after `id_last_msg`,
add column `numPosts` mediumint(8) NOT NULL DEFAULT '0' after `numTopics`,
add column `time_last_msg` int(11) NULL after `numPosts`,
deleted lines
add KEY `msg_id`(`id_last_msg`),
add KEY `parent`(`parent`),
add PRIMARY KEY(`id`),
add KEY `published_pubaccess_id`(`published`,`pub_access`,`id`), COMMENT='';

Sorry for saying this but you also have a problem with not reading EVERYTHING before posting. The LAST link will run the SQL scripts REGARDLESS of errors.

www.bestofjoomla.com/component/option,co...w/id,26252/catid,79/

Install EasySQL and run the scripts.

Seems to have got there in the end. Almost, the forums up and mostly running 1.0.4. Smiley prob in back end and front and board just crashes with a serious SQL error if I try and post anything ... so back to rooting through here for those problems. Thanks

hello grumblemarc,
i am sorry to bother you but i just want to make sure i understand because i am a little hesitant to even upgrade right now reading all the posts i see and i am not sure if i am capable of fixing any problems and 1.0.3 has problems but it at least is working and that is most important to me at this point.

if i read your post here correctly, this is what i understand.
1) I am running the 1.0.3 - first stable release...
2) I want to install the new 1.0.4 upgrade
3) was going to do so with the patch till i read so many problems
4) what you are saying here is: uninstall 1.0.3 and install 1.0.4 clean (not messing with any data tables, and things should be OK????)
5) If i save my customized css file of a standard gray theme of 1.0.3, will it work on 1.0.4?

sorry, i just have been hesitant to upgrade till i saw this post, so i just want to double check i understand before attempting the upgrade.

thanks in advance for help.
i know that list of numbers doesn't make sense, but it is just to keep things to the point.
thanks...