Deep Six isn't the right word but I thought there was almost a rhyme there... Anyway - my 360 is trying to die - that's the point I'm trying to make. No, I don't have the extended warranty.
When I put in a 360 game, I get a screen that says, please put this disk in a 360 game console - I'm assuming this is the DVD video content that is getting played because the XBOX doesn't realize it's a game and assumes it's a DVD.
When I watch DVDs on my 360, from time-to-time, I get an "Unplayable Disk" message.
Purusing the Community Server powered XBOX360 forums, it seems like the console is just not real reliable...
In reading the Community Server forums, I saw some questions about using forums at the root. I thought that was a great question. I am running my site with a blog at the root and I've seen several sites where they have deployed a forum at the root. Dan documented how to blog at the root for CS2.0 but I don't believe there's quite as much information on running other applications at the root.
To use forums at the root in Community Server 2007, you'll want to do the following things (but don't, yet):
In your SiteURLs.config, find the following setting:
<location name="forums" path="/forums/" themeDir="forums">
You would change your path to "/" and add an attribute for physicalPath. The resulting line would be:
<location name="forums" path="/" physicalPath="/forums/" themeDir="forums">
Now, before you go changing your SiteURLs file, note that Community Server 2007 introduces config override files. Scott Watermasysk provided the override files for blogging at the root which also disables many unnecessary modules and jobs - extremely convenient - thanks, Scott!
The reason you want to use the _override.config files is that you can easily maintain your custom config changes through upgrades/updates/service packs, etc. Your custom config changes will always exist in the _override files.
The logic in the siteurls_override.config file is:
<?xmlversion="1.0"encoding="utf-8" ?>
<Overrides>
<Overridexpath = "/SiteUrls/locations/location[@name='forums']"mode = "change"name = "path"value = "/" />
<Overridexpath = "/SiteUrls/locations/location[@name='forums']"mode = "new"name = "physicalPath"value = "/forums/" />
</Overrides>
I've attached a file containing Scott Watermasysk's blog at the root files and the forums at the root file discussed here. In the next few days I'll try to get a galleries at the root and add those to the collection.
One note - Scott's files were designed for a single-blog CS implementation and therefore remove a number of components that don't need to run if you aren't using anything but a blog. It's easy enough to see what has been removed in the override so take a look at those files if you may use a gallery or something elsewhere on your site and delete the "remove" lines if you want to keep some of those components.
I've been asked by several clients to help them claim their blogs on Technorati. Clients don't want the obnoxious javascript on their site that Technorati tries to inject with their embedded claim and they really don't want to add a "Technorati Claim" link to a post on their enterprise system; it just looks cheap.
For these clients, I've started putting their claim in their top post on their site inside a hidden div. It seems to work nicely and you don't expose the link to your readers while still getting the benefits of the Technorati claim.
I've tried a hidden paragraph and hidden div and the paragraph didn't seem to work but I can't think of a reason why it wouldn't...
Here's how to do it - find your latest post in the control panel under my blogs->all posts. Edit that post and flip over to the HTML editor so you can paste HTML rather than rich text with encoded HTML characters. Add <div style='display:none'></div> to the bottom of your post then paste the <a href='http://technorati.com/claim/xxxxxxxxx" rel="me">Technorati Profile</a> inside the <div> tag and you should be good to go!
For those of you who are really cautious (like me), start a new post, add your hidden div and claim link then "Save, but don't Publish" and view the post to make sure you've got a hidden claim then go back and update the published post, wait for cache to update and claim your blog.