Import rss-0.3 -->0.7.1-Shared Install-Extended Entry lin

[steve]

Since we're under a comment-spam attack, we've decided to bite the bullet and make the upgrade from 0.30 to 0.7.1 (see http://www.s9y.org/forums/viewtopic.php?t=784) -

This is where we run into 'Extended Article' problems.

We're importing from blog to blog1, a single category at a time. The problem is the extended entry url hyperlinks back to the original blog address (even after mv).

We've tried:
scenario (a)
s1. Setup shared install w/ link as per http://www.s9y.org/41.html
s2. [old blog=domain.com/blog; new blog=domain.com/blog1]
s3. import via 0.3 domain.com/blog/RSS&all=1 to 0.7.1 by category
s4. mv domain.com/blog domain.com/blogbak
s5. mv domain.com/blog1 domain.com/blog
Extended entries now hyperlink to domain.com/blogbak/xyz-entry#extended

scenario (b)
s1. Setup shared install w/ link as per http://www.s9y.org/41.html
s1.5 mv domain.com/blog domain.com/blogbak
s2. [old blog=domain.com/blogbak; new blog=domain.com/blog]
s3. import via 0.3 domain.com/blogbak/RSS&all=1 to 0.7.1 by category
s3.5 Search & Replace w/text editor rss(xyz).xml replacing all occurences of 'blogbak' to 'blog'
Extended entries now hyperlink to domain.com/blogbak/xyz-entry#extended

and kinda every scenario inbetween. This includes editing the relevant htaccess files and the table_config entries to match.

Our goal is to import all the entries from the old 0.3 to the 0.7.1 version, and kill-off the old installation. The import should produce blog_entries with extented entry hyperlinks to the new blog, not the old blog.

I have a feeling there is something I'm missing in the rewrite area (seehttp://www.s9y.org/forums/viewtopic.php?t=784).

We are running about half a dozen shared installation units now so we know it works.

[garvinhicking]

You should not use the RSS import. You can do a clean migration of Serendipity 0.3 by:

1. Copy over the 0.7.1 release files to the new directory
2. DO NOT YET OPEN YOUR BLOG URL!
3. Backup your blog database
4. Execute the files from sql/db_update_XXX with phpMyAdmin or mysql console until you've patched your database layout up to version 0.5
5. Edit your serendipity_config_local.inc.php file. Insert the variable

Code: Select all

$serendipity['versionInstalled'] = '0.5';

6. As soon as you have done that, the automatic Serendipity version upgrade recognizes you're using Version 0.5 of Serendipity.
7. Now you can open your Blog URL and follow the automatic upgrader. It will patch up your serendipity up to version 0.7.1. automatically.

Then you should be settled with all the database files and do not have to fix and old entry links.

As you can see you shouldn't need to make a backup copy of your "blog" URL anywhere in between. Everything will work off from the "old" directory structure.

And after having done all those steps, you can turn your "blog" installation into a shared installation by just removing all files except .htaccess and serendipity_config_local.inc.php (and your templates and uploads directories, maybe). Then you copy the deployment/ fake files into this directory, and it should use your include_path to work as a shared install.

Hope that helps,
Garvin.

[steve]

The migration went off, with only a few deviations. The upgrader didn't detect - so never launched.

If your upgrade script doesn't detect your install, execute EACH mysql.sql file in sequence!

Thanks Garvin for your help.