Ryangel's vB3 Journal -> vBJournal 1.0.0 Importer

Introducing.. Jim Port!


[high]Who is Jim Port?[/high]
Jim Port is the name that I gave to the import script..
Journal Import -> admincp/jimport.php -> Jim Port


[high]What can Jim Port do for me?[/high]
He will automatically do the following:

• Backup Ryangel's Journal database tables
• Revert database changes made by Ryangel's Journal
• Remove Ryangel's Journal templates
• Remove Ryangel's Journal phrases
• Install vBJournal database tables
• Alter database tables for vBJournal compatability
• Transfer data from Ryangel's Journal to vBJournal
• Install vBJournal phrases
• Install vBJournal templates

[high]Are there any known issues to using Jim Port?[/high]
Obviously, the database tables aren't 100% compatible with each other.. Jim Port cannot identify which of the journal entries is the journal's latest, and therefore no data is inserted in to the latest entry title or date fields. This was a worthy sacrifice as the majority of users will update their journals on a common basis anyway, and once a new entry is posted the latest entries will continue to function as intended.

Jim Port currently cannot strip the slashes from entry or comment titles and text. As such, journal.php must be modified slightly in order to display these correctly and the edits have been documented in the readme. These edits will not have any side-effects on any new comments or entries made beyond this point.

Also, during the beta testing phase it was reported that any deleted journals (ie. if a user had deleted all of their entries) would still show up as empty, but the comments from these deleted entries would continue to be displayed in the Recent Comments section of the journal. There is no easy fix for this other than manual deletion..


[high]What versions of Ryangel's Journal is Jim Port compatible with?[/high]
To cut a long story short, I don't know 100%. However, as long as you are running a ported vB3 version of Ryangel's Journal and not the original vB2 version, then this should work as it was intended.. I tested it on version 1.1d and at least one of the beta testers tried it on version 1.2 and both appeared to import flawlessly.


[high]What versions of vBulletin is Jim Port compatible with?[/high]
It should work on ANY version of 3.0.0..


[high]Jim Port looks similar to the v3arcade Installer, are they twins?[/high]
Yup, the journal import script is heavily based on the v3arcade Installer by John. I've tried to get in touch with him on numerous occasions about making sure it was ok with him, but currently remain unsuccessful. Should he wish me to cease using it, the zip will be removed and I will attempt to try and write this in some other way.

I feel that I have learnt a lot from his work, and would like to thank him for this.


[high]Miscellaneous notes about Jim Port[/high]
Lines of code in admincp/jimport.php: 1816
Days to write: 4
Private beta testers: tmhall, DanielP (vb.nl)

The backed up Ryangel's Journal database tables *ARE NOT* removed automatically. This was intentional in case admins wanted something to fall back on should anything go wrong, and can be deleted manually if you are satisfied with the import process.


[high]I'd like to buy Jim Port a beer![/high]
Well, you can't buy him one as he's nothing but code, however, if you'd like to buy me a beer my Paypal address is [high]obk395@yahoo.co.uk[/high]. All donations will be drunk with thanks!

[Cloud-Warrior]

Yep the RSS export is somewhere in the original vBJournal thread, link from here:

http://www.johnbreslin.com/blog/2004...ournal-module/

[Ghostsuit]

Ok jsut done this on a test board and I'm having a little problem.

The main page for a users journal takes over a minute to load

Page generated in 82.32792211 seconds (0.36% PHP - 99.64% MySQL) with 18 queries

Any idea what might be causing that?

[Ghostsuit]

Ok done a bit of digging and getting

Query:

SELECT journal_entries.entry_id, journal_entries.entrytitle,
journal_entries.entrytext, journal_entries.mood, journal_entries.allowbuddies,journal_entries.entry date,
journal_entries.entry_totalvotes, journal_moods.mood_name, journal_entries.ipaddress,journal_moods.mood_image , journal_entries.entry_totalrating,
journal_entries.private, journal_entries.whocanview,
COUNT(journal_comments.comment_text) AS comments
FROM journal_entries AS journal_entries
LEFT JOIN journal_comments AS journal_comments ON (journal_entries.entry_id=journal_comments.entry_i d)
LEFT JOIN journal_moods AS journal_moods ON (journal_moods.mood_id=journal_entries.mood)
WHERE journal_entries.journal_id='3'
AND entry_active='1'
GROUP BY journal_entries.entry_id
ORDER BY entrydate ASC
LIMIT 0,10

Time before: 1.1279599666595
Time after: 15.869854927063
Time taken: 14.741894960403

table type possible_keys key key_len ref rows Extra
journal_entries ALL 16789 Using where; Using temporary; Using filesort
journal_comments ALL 13251
journal_moods eq_ref PRIMARY PRIMARY 4 journal_entries.mood 1

Should it really take that long for that process? I'm thinking not and I jsut found if I click one of the members with 900 entrys the time taken seems to be about 250 seconds at that point so I think somethign definitely up with that querie :S.

[Ghostsuit]

Paul M found the solution to my problem it's to do with Indexes on Journal we have over 16,000 entries so required indexes anyway this problem was nothing to do with the rygel transfer but a actual problem with the original Journal script. You can find my fix over in the journal thread around post 1095

[Oblivion Knight]

Thanks for the follow-up Ghostsuit.!

[Kaelon]

Originally Posted by Ghostsuit

Paul M found the solution to my problem it's to do with Indexes on Journal we have over 16,000 entries so required indexes anyway this problem was nothing to do with the rygel transfer but a actual problem with the original Journal script. You can find my fix over in the journal thread around post 1095

And an excellent fix that they are. Added the three indexes, and performance has gotten so much better.

[Kaelon]

Is there any way we can use this script with an already up-and-running vB3.5 version of AN-Net's vBJournal?

[Reeve of shinra]

You probably could but just be careful since this script will drop any existing tables (so backup! backup! backup!).

edit:

If you already have a running journal on 3.5 and your looking to import these older journals...

- backup your current db
- restore it somewhere else
- do a table dump of the 3.5 joural tables
- rename those tables to get them out of the way for a few min
- run the converter to import the old journals
- dump those tables
- in excel or whatever the open office spreadsheet program is, copy the newly imported journals into the 3.5 journal tables you downloaded.
- fix the autoincrement ids
- save as csv and reimport that to your db.

[Oblivion Knight]

Originally Posted by Kaelon

Is there any way we can use this script with an already up-and-running vB3.5 version of AN-Net's vBJournal?

Untested, unsupported and unlikely.. :speechless:

Originally Posted by Reeve of shinra

You probably could but just be careful since this script will drop any existing tables (so backup! backup! backup!).

Eh? No it doesn't..

[kgirl]

I've just tried running this, and got the following error

Database error in vBulletin 3.0.6:

Invalid SQL:
INSERT INTO journals (journal_id, journalist_id, journaldate, journalviews, entrycount, active)
SELECT journalid, userid, timestamp, views, entries, enabled
FROM bjournal
ORDER BY userid ASC

mysql error: Duplicate entry '3' for key 1

mysql error number: 1062

Not being an expert, I've no idea what to do. I've searched here and couldn't find anything.

Can anyone help PLEASE!! :cry: