migrating database to new joomla installation

12 years 6 months ago #174566 by wolverton
I find the quickest way is using notepad++ from sourceforge.

Please Log in to join the conversation.

12 years 6 months ago #174567 by jackibar
I'm on a Mac :)

I know I could use any text editor or code editor... I guess my question is what exactly do I edit within the dump file?! For example, it begins with the following:


-- phpMyAdmin SQL Dump
-- version 3.3.9.2
-- www.phpmyadmin.net
--
-- Host: localhost
-- Generation Time: Aug 29, 2011 at 05:30 PM
-- Server version: 5.5.9
-- PHP Version: 5.3.5

SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO";


/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;

--
-- Database: `worship_jmla1`
--

--



--
-- Table structure for table `rpt_assets`
--

CREATE TABLE `rpt_assets` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT COMMENT 'Primary Key',
`parent_id` int(11) NOT NULL DEFAULT '0' COMMENT 'Nested set parent.',
`lft` int(11) NOT NULL DEFAULT '0' COMMENT 'Nested set lft.',
`rgt` int(11) NOT NULL DEFAULT '0' COMMENT 'Nested set rgt.',
`level` int(10) unsigned NOT NULL COMMENT 'The cached level in the nested tree.',
`name` varchar(50) NOT NULL COMMENT 'The unique name for the asset.\n',
`title` varchar(100) NOT NULL COMMENT 'The descriptive title for the asset.',
`rules` varchar(5120) NOT NULL COMMENT 'JSON encoded access control.',
PRIMARY KEY (`id`),
UNIQUE KEY `idx_asset_name` (`name`),
KEY `idx_lft_rgt` (`lft`,`rgt`),
KEY `idx_parent_id` (`parent_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=123 ;

--
-- Dumping data for table `rpt_assets`
--

INSERT INTO `rpt_assets` VALUES(1, 0, 1, 416, 0, 'root.1', 'Root Asset', '{"core.login.site":{"6":1,"2":1},"core.login.admin":{"6":1},"core.login.offline":{"6":1},"core.admin":{"8":1},"core.manage":{"7":1},"core.create":{"6":1,"3":1},"core.delete":{"6":1},"core.edit":{"6":1,"4":1},"core.edit.state":{"6":1,"5":1},"core.edit.own":{"6":1,"3":1}}');
INSERT INTO `rpt_assets` VALUES(2, 1, 1, 2, 1, 'com_admin', 'com_admin', '{}');


Is this the file I edit?! And do I change every single instance of the new prefix into the old jos_ prefix manually? Or do I need to export a different way?

Please Log in to join the conversation.

12 years 6 months ago #174568 by jciconsult
Replied by jciconsult on topic Re: migrating database to new joomla installation
theoretically, you could edit rpt_ to jos_ but there is no real requirement to do so. Just when you do your non-upgrade installation, make sure that the prefix is set to rpt_ in the configuration file. I like to use the standard jos_ until the system is stable and then edit the file to something else to enhance security.

Please Log in to join the conversation.

12 years 6 months ago #174569 by jackibar
So to make sure I understand(!) - are you saying that I don't even have to change the rpt to jos - as long as I set the new install to rpt as the prefix?

Please Log in to join the conversation.

12 years 6 months ago #174579 by jackibar
UPDATE: I've gone ahead and made an attempt to just use rpt_ instead of jos_.

When I finished all the steps above, my database now only has 44 tables instead of the 92 I started with - is this correct?! Here's the ones I ended up with:

rpt_assets
rpt_associations
rpt_banner_clients
rpt_banner_tracks
rpt_banners
rpt_categories
rpt_comprofiler
rpt_comprofiler_field_values
rpt_comprofiler_fields
rpt_comprofiler_lists
rpt_comprofiler_members
rpt_comprofiler_plugin
rpt_comprofiler_sessions
rpt_comprofiler_tabs
rpt_comprofiler_userreports
rpt_comprofiler_views
rpt_contact_details
rpt_content
rpt_content_frontpage
rpt_content_rating
rpt_core_log_searches
rpt_extensions
rpt_languages
rpt_menu
rpt_menu_types
rpt_messages
rpt_messages_cfg
rpt_modules
rpt_modules_menu
rpt_newsfeeds
rpt_redirect_links
rpt_schemas
rpt_session
rpt_template_styles
rpt_update_categories
rpt_update_sites
rpt_update_sites_extensions
rpt_updates
rpt_user_profiles
rpt_user_usergroup_map
rpt_usergroups
rpt_users
rpt_viewlevels
rpt_weblinks
rpt_wf_profiles


The step that said to delete all tables in the database of course left me with 0. Then the next import had me import just the j17 tables from an earlier step (which in my case was rpt_ tables) - which left me with only the above tables... I'm missing things like my polls, etc.

Please Log in to join the conversation.

12 years 6 months ago #174580 by jciconsult
Replied by jciconsult on topic Re: migrating database to new joomla installation
There is no native POL component in Joomla 1.7. The jupgrade only moves the core tables. For example, we had to use a separate upgrade process for the Jevents and docman tables in our sites. In the church site which is my next upgrade target, I am going to have to write some code to move all the sermons.

Please Log in to join the conversation.

Moderators: beatnantkrileon
Time to create page: 0.253 seconds

Facebook Twitter LinkedIn