Wordpress to Prosepoint
Sat, 30/05/2009 - 23:02
I've been experimenting with Prosepoint for a few weeks. Now I want to start the real thing, but I need to convert everything from a Wordpress site. I've been examining the tables for both and think I can handle most of it. There is also a Wordpress-to-Drupal module that might work.
I know I'll have to manually set up some things that don't exist in Wordpress. What are some of the extra things I need to consider or do for Prosepoint?
Thanks,
Mon, 01/06/2009 - 23:18
#2
I guess I should've been more
I guess I should've been more specific. I was most interested in what tables I had to modify.
I am in the middle of it. Here's a run-down on what I've done so far...(after running wp2drupal)
Created source nodes for users in node and node_revisions
Assigned sources to stories in content_field_source
Converted categories into channels in term_data (vid?)
Change workflow (sid) to Public (4)
In the sql insert file I just search/replaced the img src to point to the new server/file location.
Those were simple SQL statements. What I still have to do is...
convert captions to prosepoint
create galleries
Import images from posts (gallery based on channel) into nodes
I think I'll have to do this with the sql insert file. It looks like all I have to do is add the images to the files table, node, node_revisions and link them in the content_type_ifimage. If the file is specified in the post itself, what is this table used for? Is this just for the gallery? I'll look at your /filter/tips before I begin.
In the conversion process, I apparently used the wrong character set because the punctuation is corrupted, so I still have to convert quotes, apostrophes. Plus, it appears that wp formats on the fly, so I'll have to replace cr and lf with breaks and paragraphs, and add divs.
It appears that content_field_headlines, content_field_stories, and content_field_edition all have to do with editions. Is that right?
Thanks!
Tue, 02/06/2009 - 17:34
#3
...
As an aside, you might also be interested in the Node Import module http://drupal.org/project/node_import. It's not part of ProsePoint, but it still could be useful.
node and node_revisions are the base tables for content. These are joined on nid. All other content-related tables join to one of these two, sometimes on nid, sometimes on vid (node revision number). If you have a new installation, and while no one has created any nodes with multiple revisions, then nid == vid so nid and vid are interchangeable.
Your guesses are generally right. Instead of me trying to write out every single case (and then accidentally forgetting some), I'd like to point you to look in the file .../prosepoint/profiles/prosepoint/includes/prosepoint.content.inc at the function prosepoint_config_nodes_complex() - presuming you know how to read PHP. That will tell you how most (or all) of the content_... tables store content.
You might also want to run the functions pp_ch_update_channel_editions() and pp_update_edition_story_references_all() at the end of your import to initialise some pointers.
Channel settings are stored in the tables term_data and term_channels. Vid is the vocabulary number (not revision number), whilst tid is the term number (aka channel number). Channels are just a thin layer built on Drupal's taxonomy terms.
Node assignments to channels/terms are stored in term_node.
Node body text is stored as html (with ProsePoint specific pp_img tags). You should try to use <p> instead of <br> whenever possible.
Hmmm... I think I've covered most of the main points - It's a big topic, so if I try to cover everything I'll be here forever :)
If you have further questions, please ask (but please try to be specific). Good luck.
Fri, 12/06/2009 - 12:13
#4
converting images
I'm nearing completion of the conversion from Wordpress to Prosepoint, but I'm having trouble getting the images to show in galleries.
What I'm doing is scanning the stories for images referred to in posts, creating a pp_img tag and building SQL commands to execute later. The following are the SQL commands that I'm generating for each image.
INSERT INTO node values (343, 349, 'ifimage', '', 'temple', 1, 1, 1244572586, 1244572586, 2, 0, 0, 0, 0, 0);
INSERT INTO node_revisions values (343, 349, 1, 'temple', 'temple', 'temple', 1, 1244572586, 0);
INSERT INTO node_access values (343, 0, 'all', 1, 0, 0);
INSERT INTO term_node values (343, 349, 294);
INSERT INTO files values (16, 1, 'temple-300x200.jpg', '/wp-content/uploads/2008/07/temple-300x200.jpg', 'image/jpeg', 12780, 1, 1244572586);
INSERT INTO content_type_ifimage values (349, 343, 16, 1, 'a:3:{s:11:"description";s:0:"";s:3:"alt";s:0:"";s:5:"title";s:0:"";};
My question is how to make the images show in the image gallery. Am I missing a necessary table entry? Is a url_alias required?
The images are all still in the Wordpress wp-content folders on the same site. Do the images have to be in the sites/default/files/ folder?
Sat, 13/06/2009 - 00:46
#5
After some more study, it
After some more study, it appears that images must be processed by imagecache before they are available for use. I'll have to look around the source to see just what I need to do.I've also read that imagecache creates the images automatically, but it doesn't for me, so I must be missing something.
I wanted to have the images in all past stories to link to the gallery it is in. I may have to settle for a simple img tag in the story, without galleries.
Sat, 13/06/2009 - 12:46
#6
Some background information ...
Hi,
Some background information ...
The inbuilt gallery only displays nodes of type Image (ifimage being the machine-readable name). If you want any images to appear in the gallery, you'll have to create them as nodes.
Embedded insertion of images into stories uses the special <pp_img> tag, and it works in two modes. In one mode, it inserts an Image node. In another mode, it inserts a general img like a html <img> tag. See .../filter/tips on your site (about halfway down the page) for the syntax.
So, to insert images, you can directly reference your existing images by using <pp_img> in the second mode.
Or, you can create your images as nodes, and then insert using <pp_img> in the first mode.
There's probably more than one way to create image nodes in an automated way.
If you're interested, ProsePoint does this in the file .../profiles/prosepoint/includes/prosepoint.content.inc, function prosepoint_config_nodes_complex(). Function _prosepoint_insert_file() of .../profiles/prosepoint/prosepoint.profile is also interesting.
Fri, 19/06/2009 - 00:19
#7
Got it
I got all of that. The problem I was having was the imagecache wasn't generating the images. At first I thought it was because they had to be in system/default/files. Later, I discovered that the problem was the size of the original images; many of them were over 1M. I resized them all to fit into 1024 x 768 and that worked. I haven't checked, but maybe it doesn't matter where the files are stored.
Anyway, I wrote a C++ program to edit an export of the node_revision table, and create INSERT entries for related tables.
In short, the conversion is mostly successful. There's a few minor issues and I still have a lot of touchup to do, but it's more work than mystery. The temporary site URL is www.ptalon.info.
BTW, I first didn't find /filter/tips so I did a search. As a result of searching for that and pp_img, I found several other websites that use Prosepoint that aren't mentioned here anywhere. That'll come in handy when I go to make the case for Prosepoint.
Fri, 19/06/2009 - 09:54
#8
You can change the 1M limit.
You can change the 1M limit. Have a look at .../admin/content/node-type/ifimage/fields/field_image on your site and see what it reports as the limit under File size restrictions. You may have to change your PHP settings.
Yes, there are many ProsePoint sites out there. The majority of them I never hear from (at least, until there's an issue). A large proportion of them, I expect, are just test or evaluation sites.
Sun, 21/06/2009 - 23:17
#9
Yes, I knew I could change
Yes, I knew I could change the 1M limit, but I put the files there through FTP, so that wasn't an issue. In fact, one of the 6M images was "eventually" processed. :)
Actually, I think the default upload size was 2M. Anyway, 1M is a reasonable enough limit. I resized all of the photos to fit in 1024x768, Jpeg high quality, and they were all less than 1M.
Hi,
Gosh, that's a really open ended question.
I think, in terms of core ProsePoint content, you have:
Stories
Editions
Channels
Images
I expect your Wordpress site doesn't have an equivalent of editions, so that leaves stories, channels and images.
If you import all your stories, make sure they are assigned to the correct channels.
Not sure how you want to do the images migration (if there is a need for one).
I expect you'll need to manually (or via scripting) insert images into stories yourself (see the information for the <pp_img> tag in the formatting tips at .../filter/tips) or just omit associating images with stories altogether.
That should cover ProsePoint core content.
However, as you do the import/migration process, you may come across other things to consider. It's very hard for me to predict ahead of time without actually doing it myself.