I FIXED MY foreach problem after much searching, de-installing, re-installing and even getting grief from someone here who said "you don't deserve help". How rude.

Here's what I did.

I tried to install from FB 1.0-1.04. The problem was, crucial SQL commands which where in a folder called "upgrades" were not in my zip file which I downloaded. These were mistakenly left out. As a matter of fact, the entire "upgrades" folder was not there. This caused much confusion.

After finding these files in the 1.03 upgrade I executed them in sequence but still had problems.

What worked

I heard someone mention they skipped some lines (with the errors) in the SQL commands. So I started executing the SQL commands and when they'd error out, I'd continue executing them PAST the lines of SQL code which caused the errors. This finally solved the problem.

If this doesn't make sense I can try to explain again to anyone who is having the same problem.

mediaguru I'm attempting to do the same thing, this is a pretty absurd upgrade procedure. It pisses me off a good bit actually.

So mediaguru you used the 1.00 - 1.03 upgrade sql changes?

Do you need to run all of those upgrades from the 1.0.3 distribution? I thought it was just run the relevant one.

MoveTwice wrote:
mediaguru I'm attempting to do the same thing, this is a pretty absurd upgrade procedure. It pisses me off a good bit actually.

So mediaguru you used the 1.00 - 1.03 upgrade sql changes?

I ran each one of the three and deleted the commands which resulted in errors in phpmyadmin until the script finished. Then I moved on to the next one.

It is all very vague, so now I will have a go at that. Should be a warning in that this component is not suited to non-programmers... It was a lot easier doing the upgrade from the original Joomlaboard

Frank A wrote:
It is all very vague, so now I will have a go at that. Should be a warning in that this component is not suited to non-programmers... It was a lot easier doing the upgrade from the original Joomlaboard

I agree. And the fact that they "forgot" to put in the SQL commands in the .zip file also caused me all sorts of problems. They should take an example from joomla or community builder on upgrading and the extremely important documentation which should accompany it, rather then telling people like me who had problems since there were missing files that we "don't deserve support."

grumblemarc wrote:
Skip all missing and duplicate errors.

Hi again,

I've held off my upgrade to see how the 1.0.4 release went.

As per my post on page three of this thread, I get the following when I try and upgrade from 1.0 to 1.0.4:

Code:

mysql> describe jos_fb_messages; +-----------------+-------------+------+-----+---------+----------------+ | Field           | Type        | Null | Key | Default | Extra          | +-----------------+-------------+------+-----+---------+----------------+ | id              | int(11)     | NO   | PRI | NULL    | auto_increment | (snip)

What should this look like on a clean install?

The upgrade instructions say to drop the key, but it is a primary key in my current database, so this drop key syntax would be wrong. I can't do a drop primary key, because the current field is an auto-increment, and an auto-increment field must be a key.

As you can see, this problem is a little different than a missing or duplicate field.

Should I just ignore this error, and leave the field as described above, or should I also remove the auto-increment type, in addition to dropping it as a primary key?

ie:

Code:

/* Stop being an auto_increment */ alter table `jos_fb_messages`    modify column `id` int(11) NOT NULL; /* Stop being a primary key */ alter table `jos_fb_messages`    drop PRIMARY KEY ('id');

Will removing the auto_increment cause issues for fireboard?

Thank you for any help.

Cheers,
Jag

PS: Where can I find the clean install database layout in the 1.0.4 CompletePackage install? It's not in the xml file, and I've not found it in the code so far.

I've figured this out myself, posting here in case someone else finds it useful.

re: my previous post the id field jos_fb_messages is fine.

I installed a clean installation of fireboard 1.0.4 on a test system, and compared it to my upgraded tables. I was surprised to see several differences, I'm not sure if this is missing stuff from Fireboard 1.0 -> 1.0.4 upgrade, or if this is hangover stuff from the Joomlaboard to Fireboard migration.

For each table I've listed the differences I've found, and the SQL to bring the upgraded table in line with the clean install table schema.

Table: jos_fb_attachments

• clean install table has a default value of '0', upgraded table has no default.

Code:

ALTER TABLE `jos_fb_attachments` MODIFY `mesid` int(11) NOT NULL default '0';

Table: jos_fb_categories

• Extra field "image" in upgraded table, doesn't exist in clean install


• Default value for moderated is "0", it is "1" on a clean install.

Code:

ALTER TABLE `jos_fb_categories` MODIFY `moderated` tinyint(4) NOT NULL default '1', DROP `image`;

Table: jos_fb_messages

• Upgraded table is missing several keys. The clean install has the following extra fields defined as keys:
  parent, thread, catid, userid, ip

Code:

ALTER TABLE `jos_fb_messages`   ADD KEY `thread` (`thread`),   ADD KEY `parent` (`parent`),   ADD KEY `catid` (`catid`),   ADD KEY `ip` (`ip`),   ADD KEY `userid` (`userid`);

Table: jos_fb_moderation

• catid and userid are primary keys on the clean install, but not the upgraded table

Code:

ALTER TABLE `jos_fb_moderation` ADD PRIMARY KEY  (`catid`,`userid`);

Table: jos_fb_sessions

• userid is a primary key on the clean install, but not the upgraded table

Code:

ALTER TABLE `jos_fb_sessions` ADD PRIMARY KEY  (`userid`);

Table: jos_fb_subscriptions

• thread and userid are keys on the clean install, but not the upgraded table

Code:

ALTER TABLE `jos_fb_subscriptions`    ADD KEY `thread` (`thread`),   ADD KEY `userid` (`userid`);

Table: jos_fb_users

• userid is a primary key on clean install, but not the upgraded table


• birthdate default value is 0001-01-01 on clean install, but 0000-00-00 on the upgraded table

Code:

ALTER TABLE `jos_fb_users`    MODIFY `birthdate` date NOT NULL default '0001-01-01',   ADD PRIMARY KEY  (`userid`);

This work has been somewhat complicated for me due to our site being moved to a new hosting company and domain name.

We had a problem with image and file attachments not showing up in the forums. This was caused by two issues:

1. The absolute path for our base Joomla! directory has changed.


2. The domain name for our website has changed

NB: We moved site, then upgraded Fireboard, only then was the attachment problems noticed, so note the new and old style fireboard locations for files and images, as these fixes were applied after the 1.0.4 upgrade.

The first problem (Moving Joomla base directory) was fixed with the below:

Code:

UPDATE jos_fb_attachments SET filelocation=(REPLACE(filelocation, 'old_joomla_base_path/components/com_fireboard/uploaded', 'new_joomla_base_path/images/fbfiles'));

The second problem (Moving site to a new URL) was fixed with the below:

Code:

UPDATE jos_fb_messages_text SET message=(REPLACE(message, 'http://oldurl.example.com/components/com_joomlaboard/uploaded', 'http://newurl.example.com/images/fbfiles')); UPDATE jos_fb_messages_text SET message=(REPLACE(message, 'http://oldurl.example.com/components/com_fireboard/uploaded', 'http://newurl.example.com/images/fbfiles'));

We had several instances of attached image urls referring to com_joomlaboard, hence why it is included above, if you only ever had fireboard installed, you can ignore the line mentioning joomlaboard.

Cheers,

Jag

I am having the same problem. "There are no forums in this category!" I'm sure the answer is here but I am not programmer so all the db stuff is over my head. I now have a forum offline while 1500 members have nothing to do? I'm at a loss. I've ran every script here and still the same results? "There are no forums in this category!". I would be willing to pay someone to help. I just need to get this taken care of. I've never had this much trouble upgrading a component and I've been using Mambo/Joomla for years. Please help..

Jeremy

BoJosley wrote:
I am pleased to report that I finally made the upgrade from 1.0.0(Beta) to 1.0.3 thanks to the efforts of grumblemarc who generously offered to look at my backend (not everyday I allow people to look at my backend but I was grateful he did). I believe that he ran the sql and had the same problem as me with the "No Forum In this Category". He then ran the sql upgrade script for 1.0.1 and that seemed to do the trick. I think this was more or less advised by bpowers84 too. Anyway I am up to date and very pleased with both the upgraded component and with all the help I received through this forum. Thank you.

This is from the second page in this very thread. Have you tried this?