- Posts: 12
- Thank you received: 0
Blue Eagle (1.5.0) for K5.1 is released (20 Jul 2018)
Please update the Kunena Blue Eagle to 1.5.0 if you use Kunena 5.1.
We made several bug fixes and improvements. Also Blue Eagle has now all the features from Crypsis.
It is important to note that the Kunena team does not have a standard, recommended or supported protocol for these ideas and that posting questions in this category may not receive advice from team members.
Idea phpBB 3 to Kunena 3 Migration Script
CREATE TABLE IF NOT EXISTS `#__users` ( `id` INT(11) NOT NULL AUTO_INCREMENT, `name` VARCHAR(255) NOT NULL DEFAULT '', `username` VARCHAR(150) NOT NULL DEFAULT '', `email` VARCHAR(100) NOT NULL DEFAULT '', `password` VARCHAR(100) NOT NULL DEFAULT '', `block` tinyint(4) NOT NULL DEFAULT 0, `sendEmail` tinyint(4) DEFAULT 0, `registerDate` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `lastvisitDate` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `activation` VARCHAR(100) NOT NULL DEFAULT '', `params` text NOT NULL, `lastResetTime` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT 'Date of last password reset', `resetCount` INT(11) NOT NULL DEFAULT 0 COMMENT 'Count of password resets since lastResetTime', `otpKey` VARCHAR(1000) NOT NULL DEFAULT '' COMMENT 'Two factor authentication encrypted keys', `otep` VARCHAR(1000) NOT NULL DEFAULT '' COMMENT 'One time emergency passwords', PRIMARY KEY (`id`), KEY `idx_name` (`name`), KEY `idx_block` (`block`), KEY `username` (`username`), KEY `email` (`email`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
This means there is no column "requireReset". Could you please exclude that column from insert and check if the rest of script works? I would like to add that into checklist for new users.
requête SQL: Documentation INSERT INTO TESTJOOMLA.testjoom_users( id, name, username, email, PASSWORD , block, sendEmail, registerDate, lastVisitDate, activation, params ) SELECT user_id AS id, username AS name, username, user_email AS email, user_password AS PASSWORD , /*lets not store blank passwords.*/0 AS block, 0 AS sendEmail, FROM_UNIXTIME( user_regdate ) AS registerDate, FROM_UNIXTIME( user_lastvisit ) AS lastVisitDate, 1 AS activation, /*1 as requireReset, /*The phpBB password cannot be converted to joomla password.*/ '' AS params FROM CopieForumSG.phpbb_users WHERE user_posts >0; MySQL a répondu: Documentation #1062 - Duplicate entry '207' FOR KEY 'PRIMARY'
Was expecting cause of my Name/nickname/mail.
I change all of them with one never used on my old PHPBB.
Still the same issue.
This means, you can do:
DELETE FROM joomla_database_name.jos_user_usergroup_map; DELETE FROM joomla_database_name.jos_users;
CREATE TEMPORARY TABLE IF NOT EXISTS joomla_database_name.jos_users_backup AS (SELECT * FROM joomla_database_name.jos_users); DELETE FROM joomla_database_name.jos_user_usergroup_map WHERE user_id NOT IN(SELECT id FROM joomla_database_name.jos_users_backup); DELETE FROM joomla_database_name.jos_users WHERE id NOT IN(SELECT id FROM joomla_database_name.jos_users_backup); DROP TABLE joomla_database_name.jos_users_backup;
Remember, if you do that, you are lost without a joomla administrator access to your backend. But if you could come this far, creating a new joomla administrator or upgrading your forum account (which gets migrated along with) to administrator would not be a big deal though.
I upgrade my PHP.
I'm now on the last joomla, and last kunena.
DELETE FROM joomla_database_name.jos_user_usergroup_map;
DELETE FROM joomla_database_name.jos_users;
requête SQL: Documentation
INSERT INTO TESTJOOMLA.testjoom_kunena_categories ( id, parent_id, name, alias, icon_id, locked, accesstype, access, pub_access, pub_recurse, admin_access, admin_recurse, ordering, published, checked_out, checked_out_time, review, allow_anonymous, post_anonymous, hits, description, headerdesc, class_sfx, allow_polls, topic_ordering, numTopics, numPosts, last_topic_id, last_post_id, last_post_time, params ) SELECT forum_id, parent_id, REPLACE(forum_name, '&', '&'), CopieForumSG.get_forum_alias(forum_id) AS alias, 1 as icon_id, 0 as locked, 'joomla.level' AS accesstype, 1 as access, 1 as pub_access, 1 as pub_recurse, 8 as admin_access, 1 as admin_recurse, left_id as ordering, 1 as published, 0 as checked_out, '0000-00-00 00:00:00' as checked_out_time, 0 as review, 0 as allow_anonymous, 0 as post_anonymous, 0 as hits, forum_desc, '' as[...]
MySQL a répondu: Documentation
#1270 - Illegal mix of collations (latin1_swedish_ci,IMPLICIT), (utf8_general_ci,COERCIBLE), (utf8_general_ci,COERCIBLE) for operation 'concat'
And this as well:
First, I've migrated Snitz to phpBB2, there is a converter somewhere.
Then I migrated phpBB2 to phpBB3 - it did that, but some of the fields were missing. I don't know if that happened on purpose or it was a migration error. The phpBB3 forum worked so I guess if you migrate, that happens.
By modifying some of the statements to point to the phpBB2 database I was able to process all messages! www.i-war2.com/forum lives again for another 15 years (I hope).
I just have to replace all HTML tags with bbcode now. The old Snitz forums were ASP based, horrible stuff - they wrote all HTML stuff directly into the message. And sometimes even the signature.
I had a new test case and added support for missing column today, which is updated to the GitHub repository.
I am surprised by your tone. Sorry, I will not be able to help you.
- Not Allowed: to create new topic.
- Not Allowed: to reply.
- Not Allowed: to add attachements.
- Not Allowed: to edit your message.