Viewing posts from pre-Telligent Community

Yes please let us have the old posts back ASAP. For me the old posts is the whole backbone of how I'm supporting my site!

And that Telligent have upgraded to the new site without bringing over the old messages, well I simply cannot understand that. I will not take google more than a few days to remove them from all the indexes if they are really unlucky!

Well, ok, there's status updates, but that lacks the persistence & length possibilities that announcements had.  Blog posting sound reasonable - except that it doesn't appear to be enabled (which makes sense).  Even with blog posts, they would lack the positioning of announcements.

There's also the issue of _prior_ announcements and files - they didn't make the transition.  Which again is understandable, but the stuff is just _gone_ - no warning. 

Not a really big deal in my own case, and these were probably under-utilized features in the first place.  I'm assuming that was checked.

As for previous forum posts, my older ones are still associated with my user id, but some of the more recent ones are not.  It appears that a snapshot of the database was taken at some point before the transition, and then work began on that.  Those recent posts _are_ still in the forums, but the association with user accounts doesn't seem to have made the transition. 

This would seem to have a much greater impact than the user profile changes.

Links: those are pretty much destroyed across the board.  The url structures in the forums appear to have changed in more than just the root, with even the post and thread id's different. 

Is there a mapping for those ?  As in, old = new ?  So that maybe a 404 page (or some other approach) can be created that can recognize an old url and redirect to the new one ?  Just a thought.

There are mappings but the issue is due to changing the root directory of CS (from / to /communities ) , the old urls are never even getting to CS to be redirected.  Post and ThreadIds may have changed upgrading dev.cs.com - because dev.cs.com has been historically upgraded through various alpha / beta / interim releases, upgrades don't always go smoothly and sometimes we have to deviate slightly from the normal upgrade path in order to complete the upgrade.  On a standard upgrade, PostIds and ThreadIds shouldn't change

I would point out that your announcements and files are still arround, but they're just not exposed in the default UI at present.  For proof, take a look at telligent.com/.../files and telligent.com/.../announcements .

Re announcements & files: that's cool.  But until you pointed that out explicitly, I would never had known.  Web navigation for mindreaders ?  Hmm, I didn't get that upgrade; let me check my inbox ;-)

URL redirection: "...  the old urls are never even getting to CS to be redirected ..." - there _are_ ways to do that.  _If_ old CS.com is still running on IIS, but in full redirection mode, there are variables that can be used to reconstruct the destination URL (assuming the thread / post id's survived).  If it's a flat out DNS redirect & CS.com is just plain gone, then the receiving end could sort those out.  It's an admin thing, not an app thing.  Or, y'know, there's a zillion possible solutions.  I don't think there's a business reason for leaving those hanging, is there ?  Just a time issue, right ?  Or an oversight ?

Even if the item id's don't match, the redirects should at least be able to get closer than where they get now.  Yeah, I know - priorities.

Well, there's certainly lots of work to go around - enjoy !

The migration *did* unfortunately change the thread/post IDs because multiple communities and sites were merged into one.  We've been working to see if we can fix the issues, but so far, no dice.