Posts Grrrr... Community Server
Post
Cancel

Grrrr... Community Server

Community Server migration is still kicking me in the ***...

I guess I'm going to have to bite the bullet and push the CS files to the root folder so that I can take advantage of some of the other features of the product while also allowing me to maintain my search engine indexing.

In the process of removing one database, I forgot (due to being pulled away for real work) that I was in the process of migrating from one database instance to another to have the database name match the site... and wouldn't you know I had only completely it half way.  Community Server has two connection strings in the web.config and I only updated one of them.  And wouldn't you know that Community Server apparently doesn't care that you have two different ones in there... so I was still posting to the "old" instance thinking it was on the new.  I suppose that's what I get for trying to do this amongst juggling everything else.

Anyway, I lost the last couple of posts and used search engine caching to recover some of the slightly older ones.

So, if your a CS expert, maybe you can answer this...

I would like to do the following:

1) Maintain all the existing URLs that are mapped to search engines and translate those to their (assuming there is) new location accordingly.

2) Take advantage of the files, gallery, home page/article blocks and future enhancements to CS instead of being "stuck" with a "single blog" setup.

3) Cause the "search" mechanism to re-index content.  The .TEXT blog entries were migrated over but they don't show up in the search.

4) "Repair" the ASP.NET profile stuff.  I'm guessing that something was done out of order during the migration (I followed the instructions provided, but people are unable to create new user accounts.)

It's starting to look like I need to drop the base installation to the root of the site in order to take advantage of an add-in to handle #1; which looks like it will allow me to take advantage of #2.  However, #3 and #4 are still a problem.

You'd think after 30 years or so that computers/software would be easier to use. ;-)

This post is licensed under CC BY 4.0 by the author.