Far as I can tell, posts/threads have been transferred from old YaBB 2.1 directory.

Any problems with missing or can't-read/access posts/threads?

I know about Pleo's thread with Magoo, but any others?

Definitely problems transferring the *bigger* files. Most were small .. 3-to-8 KB. But some were ~100 kb. Had to transferred separately. FTP client (server) choked. Kept spitting them out when I'd try to up 50 files at a time.

Do the math. 50 files/transfer. How many transfers to reach 25,000? Ansr: a *lot*. (My FTP client .)

Thought my archiving prgm (Winzip) was locked up after I tried to execute the tarball (1.2 gig). Was getting ready to terminate. When all these files start extracting. Then, after extracting for a *long* time I (on my laptop) right at the end. Had to burn files and delete to make room for the 32K posts. That's what took so much time.

Gonna work on transferring member's accounts now. Only 500 of them missing. Small potatoes compared to 25K missing posts. Takes forever just to *extract* 35K files from the back-up tarball I downloaded (1.2 gigs compressed). Currently extracting members/ and /boards.

I saw many ugly threads at the YaBB forum when I was researching the upgrade .. so I knew it could easily go south.

Some of the problem files/threads:

1144131251.txt
1131831389.txt
1117736753.txt
1116434248.txt

Another source of problems is two versions of same user_name, with one having a Capital letter (which Linux/Unix allows and recognizes). e.g. Mongo vs mongo. Sometimes they're two different names, and sometimes they're the same. Depends what program you ask. Trouble.

My host says our CPU usage has decreased, but we are still using too much *memory* to be moved off the "stabilization" server. (Where all badboy-sites are banished.)

I am now forwarding the old YaBB 1.4 forum, which we were using as an archive, and cuz search engines knew it better than the new forum (this one). So that should kill a lot of CPU usage, no longer having to service those (archived) posts.

threads andposts. Does that sound right? I shouda looked before starting the upgrade.

Rad wrote on Jan 22^nd, 2008 at 9:36pm:

Not thus far, looks like your hard work has paid off and things seem fine from here; works great in the feed reader and on the google homepage. Nicely done!

Rad

Quote:

The *law of unintended consequences*!!!!

Quote:

Looking back, probably should have retained the same sub-directory structure back when it was v1.4 and you upgraded to v2.1--should not have created that new *yabb2* directory--should have kept it as it was and just did the upgrade to the program files in place!!!!

Reason--now that you are forwarding from the v1.4 address to the v2.x address, all the old links in the threads prior to your upgrade to v2.x are now *dead* links!!!  You get forwarded to the main screen of the *new* forum, and not to the actual referenced thread!

If you had left the directory structure as it was, and upgraded over the old program files, the search engines would still have found the same active links as before--and now this upgrade would also have the same directory linkage--note for future consideration--don't make a new directory for a new version of the forum software when/if upgrading!

Rad

I stand corrected!  I thought there was just a sub-directory name change, but I see now that the way the board references and calls for a thread in the v2.x is a different structure, as you mentioned, than for the v1.4 software!

Here's an example of an old v1.4 style link:

Quote:


and here's the new style:

Quote:


The differences are here:

Old style:  /YaBB.cgi?board=general;action=display;

New style:  /YaBB.pl?


I wonder...that's a pretty radical change--everyone using the v1.4 would be hit by that same issue of loosing their ability to reference all their old links unless they kept their old board active like you did.  Didn't the YaBB folks create some sort of a conversion program (tool) to update all the old style links to the new style?  Seems like they would not want to leave everyone in that bind of incompatible links in old posts after the upgrade!

Seems like a *search and replace* function that can look inside each thread file could accomplish that conversion!?  But, I'm not smart enough to know what the problems with such a tool might be!

RSS feeds are based on a url that points to an XML view of the forum data.  It should be completly independant of any theme you see when you view the actual forum page.  Once you've found the link, it should work no matter what theme you use.  Finding the link might be the hard part for people using the default theme.

NightOwl wrote on Jan 23^rd, 2008 at 9:14am:

I used the blk_gry3d template; although the RSS isn't a regular link on the page itself, it's also embedded as a link rel="Alternate" element in the page header and that's universal. It means that RSS-aware browsers and search engines (Google do indexing of RSS feeds in "Google Blog Search") can snag feeds as a universal feature.

In FireFox, for instance, if a page advertises a feed this way the standard RSS icon appears in the browser address bar. For this forum the RSS feed itself isn't styled, but if you want to make it more browser-aware a good thing to do is separately style the RSS XML using an <?xml-stylesheet> processing instruction, so things that scrape the text can do that and browsers can render it in a more fancy way.

If there are mutiple kinds of feeds for advanced users you can have them advertised with multiple link rel="Alternate" elements and most browsers will turn their RSS feed button into a menu.

Not sure if this is related, but when reading a post, there doesn't seem to be any way to return to the threads of that board.  Only way to go back "up a level" is to go to "home".

I'm pretty sure it was there yesterday, so maybe some change today caused this. ??

Oops.  Now I see it again, the title line "Radified Community Forums > Radified ... "

Must have been an optical illusion.  sorry.

P.S. It would be nice if that title line were also displayed at the BOTTOM of a long list of replies.  That way you don't have to manually scroll up to the top just to "return".