|
Upgrade from 1.0.0 to 1.0.3, 1.0.4 Stable 1 Year, 1 Month ago
|
|
|
I have been following the instructions in 'Fireboard Forum_Installation_Upgrade_Manual.pdf' and everything goes fine until you ask me to
If necessary, rename all the “jos_” occurrences to your own database prefix. Hence, if your db prefix it “boj_” then you should rename all “jos_” to “boj_”.
I can see all datatables contain the 'jos_' prefix from myphpadmin. I have a couple of questions:
1) how do I rename them?
2) is it all my tables?
I continued without renaming but ended up with a lot of SQL errors when I ran 'Fireboard_100_to_1.0.3.Stable.sql'
Can anyone help my site is down and I am worried.
|
|
BoJosley (User)
Junior Boarder
Posts: 31
|
Logged
|
|
|
Last Edit: 2008/01/23 19:14 By grumblemarc.
|
|
|
The administrator has disabled public write access.
|
|
|
Re:Upgrade from 1.0.0 to 1.0.3 Stable 1 Year, 1 Month ago
|
|
|
Ok I have found how to rename data tables it was under the operations tab in myphpadmin. I renamed all jos_fb* to boj_* and tried to run the 'Fireboard_100_to_1.0.3.Stable.sql' - I still get SQL errors this time relating to not being able to read data tables called jos_fb*. My site is still down and I am beginning to regret waking this morning.
|
|
BoJosley (User)
Junior Boarder
Posts: 31
|
Logged
|
|
|
The administrator has disabled public write access.
|
|
|
Re:Upgrade from 1.0.0 to 1.0.3 Stable 1 Year, 1 Month ago
|
|
|
It was not neccessary to change your database prefix at all... your site was set up in the most common way (default) using 'jos_' as the SQL prefix..
Change all your 'bos_' amendments back to 'jos_' and all should be fine
|
|
|
Logged
|
|
|
The administrator has disabled public write access.
|
|
|
Re:Upgrade from 1.0.0 to 1.0.3 Stable 1 Year, 1 Month ago
|
|
|
Thanks for your comments freefallnz I had done it already. Now when I look at my forum from the front end it renders ok but I can only see the main categories of the forum and none of the messages at all. I guess this is because I could not get the 'Fireboard_100_to_1.0.3.Stable.sql' to run. Have you any further suggestions?
|
|
BoJosley (User)
Junior Boarder
Posts: 31
|
Logged
|
|
|
The administrator has disabled public write access.
|
|
|
Re:Upgrade from 1.0.0 to 1.0.3 Stable 1 Year, 1 Month ago
|
|
|
Interesting,
I've go that same problem..
I have seen in a couple of other post to run the update statistics.
Sadly in my case update statistics just times out.. and like the forum is lucky if its got 40 posts on it.
|
|
|
Logged
|
|
|
The administrator has disabled public write access.
|
|
|
Re:Upgrade from 1.0.0 to 1.0.3 Stable 1 Year, 1 Month ago
|
|
|
I think that the nub of this problem is that the 'Fireboard_100_to_1.0.3.Stable.sql' has not worked for us. Any suggestions out there?
|
|
BoJosley (User)
Junior Boarder
Posts: 31
|
Logged
|
|
|
The administrator has disabled public write access.
|
|
|
Re:Upgrade from 1.0.0 to 1.0.3 Stable 1 Year, 1 Month ago
|
|
"Could not get it to run". Are you referring to the errors that you get that "prevent" the SQL from running? Easy way to get around them. Here's an example with the 1.0.1 to 1.0.3 script-others are similar. When you get an error delete the code you have run up to that point and run the SQL again. I would run them in sections-noted by the "alter table" at the beginning or each new query.
EDIT*
OR you can try this if the following script editing is not our cup of tea.
Example script.
-- __^__ __^__
--( ___ )------------------------------------------( ___ )
-- | / | SQL Upgrade | |
-- | / | Fireboard 1.0.0 to 1.0.3 Stable | |
-- |___| Rename jos_ to your db prefix |___|
--(_____)------------------------------------------(_____)
-- Don't copy/paste this part.
/* Alter table in Second database */
alter table `jos_fb_attachments`
add KEY `mesid`(`mesid`), COMMENT='';
/* 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`, Error here? Delete everything BEFORE "alter table `jos_fb_categories`" and this point and run SQL again
drop key `catparent`, Error here? Delete everything BEFORE "alter table `jos_fb_categories`" and this point and run SQL again
add KEY `msg_id`(`id_last_msg`),
add KEY `parent`(`parent`),
add PRIMARY KEY(`id`),Error here? Delete everything BEFORE "alter table `jos_fb_categories`" and this point and run SQL again
add KEY `published_pubaccess_id`(`published`,`pub_access`,`id`), COMMENT='';
/* Create table in Second database */
create table `jos_fb_groups`(
`id` int(4) NOT NULL auto_increment ,
`title` varchar(255) NULL ,
PRIMARY KEY (`id`)
);
/* Alter table in Second database */
alter table `jos_fb_messages`
add column `modified_by` int(7) NULL after `moved`,
add column `modified_time` int(11) NULL after `modified_by`,
add column `modified_reason` tinytext NULL after `modified_time`,
add KEY `hold_time`(`hold`,`time`),
drop key `id`,
add KEY `locked`(`locked`),
add KEY `time`(`time`), COMMENT='';
/* Alter table in Second database */
alter table `jos_fb_messages_text`
drop key `mesid`,
add PRIMARY KEY(`mesid`), COMMENT='';
/* Alter table in Second database */
alter table `jos_fb_moderation`
drop key `catid`, COMMENT='';
/* Create table in Second database */
create table `jos_fb_ranks`(
`rank_id` mediumint(8) unsigned NOT NULL auto_increment ,
`rank_title` varchar(255) NOT NULL ,
`rank_min` mediumint(8) unsigned NOT NULL DEFAULT '0' ,
`rank_special` tinyint(1) unsigned NOT NULL DEFAULT '0' ,
`rank_image` varchar(255) NOT NULL ,
PRIMARY KEY (`rank_id`)
);
/* Alter table in Second database */
alter table `jos_fb_users`
add column `group_id` int(4) NULL DEFAULT '1' after `karma_time`,
add column `uhits` int(11) NULL DEFAULT '0' after `group_id`,
add column `personalText` tinytext NULL after `uhits`,
add column `gender` tinyint(4) NOT NULL DEFAULT '0' after `personalText`,
add column `birthdate` date NOT NULL DEFAULT '0000-00-00' after `gender`,
add column `location` varchar(50) NULL after `birthdate`,
add column `ICQ` varchar(50) NULL after `location`,
add column `AIM` varchar(50) NULL after `ICQ`,
add column `YIM` varchar(50) NULL after `AIM`,
add column `MSN` varchar(50) NULL after `YIM`,
add column `SKYPE` varchar(50) NULL after `MSN`,
add column `hideEmail` tinyint(1) NOT NULL DEFAULT '1' after `SKYPE`,
add column `showOnline` tinyint(1) NOT NULL DEFAULT '1' after `hideEmail`,
add column `rank` tinyint(4) NOT NULL DEFAULT '0' after `showOnline`,
add column `GTALK` varchar(50) NULL after `rank`,
add column `websitename` varchar(50) NULL after `GTALK`,
add column `websiteurl` varchar(50) NULL after `websitename`,
add KEY `group_id`(`group_id`), COMMENT='';
/* Alter table in Second database */
alter table `jos_fb_whoisonline`
add KEY `userid`(`userid`), COMMENT='';
INSERT INTO `jos_fb_groups` VALUES ('1', 'Registered User' ;
INSERT INTO `jos_fb_ranks` (`rank_id`, `rank_title`, `rank_min`, `rank_special`, `rank_image`) VALUES
(1, 'Fresh Boarder', 0, 0, 'rank1.gif' ,
(2, 'Junior Boarder', 20, 0, 'rank2.gif' ,
(3, 'Senior Boarder', 40, 0, 'rank3.gif' ,
(4, 'Expert Boarder', 80, 0, 'rank4.gif' ,
(5, 'Gold Boarder', 160, 0, 'rank5.gif' ,
(6, 'Platinum Boarder', 320, 0, 'rank6.gif' ,
(7, 'Administrator', 0, 1, 'rankadmin.gif' ,
(8, 'Moderator', 0, 1, 'rankmod.gif' ,
(9, 'Spammer', 0, 1, 'rankspammer.gif' ;
UPDATE `jos_fb_users` SET `rank`=8 WHERE `moderator`=1 AND `rank`=0;
|
|
|
Logged
|
|
|
Last Edit: 2008/01/24 00:07 By grumblemarc.
|
|
|
The administrator has disabled public write access.
|
|
|
Re:Upgrade from 1.0.0 to 1.0.3 Stable 1 Year, 1 Month ago
|
|
|
I have tried again and run the sql in blocks marked by "/* Alter table" as you suggested. I got quite a few error messages usually associated with not being able to "DROP". When this happened I moved on to the next block and pasted that in. Some blocks ran without errors and some did not. I am not totally sure if you wanted me to delete the offending "Drop" line in the SQL try to re-run it. Is that correct?
Once I had completed the process my fireboard shows but says "There are no forums in this category!" in each category. The good news is that the Recent post show some messages which I can successfully navigate to and read. So it seems I have just lost the connection between categories and forums. Can you help any more?
|
|
BoJosley (User)
Junior Boarder
Posts: 31
|
Logged
|
|
|
The administrator has disabled public write access.
|
|
|
Re:Upgrade from 1.0.0 to 1.0.3 Stable 1 Year, 1 Month ago
|
|
|
I have just installed the EasySQL joomla component and ran the SQL script here. But I still have the same problem "There are no forums in this category!" in all categories.
I guess its the following code that did not run
[code:1]/* 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='';
/* Create table in Second database */[/code:1]
|
|
BoJosley (User)
Junior Boarder
Posts: 31
|
Logged
|
|
|
The administrator has disabled public write access.
|
|
|
Re:Upgrade from 1.0.0 to 1.0.3 Stable 1 Year, 1 Month ago
|
|
|
I guess I am going to have to restore my 1.0.0(Beta) FireBoard. If anyone can tell me why I had this problem I would be very grateful - otherwise I'll be stuck in a 1.0.0(Beta) time warp.
|
|
BoJosley (User)
Junior Boarder
Posts: 31
|
Logged
|
|
|
The administrator has disabled public write access.
|
|
|