This project is read-only.

Oxite not running,giving an error No site or redirect was found

Dec 12, 2008 at 4:17 AM
Edited Dec 12, 2008 at 4:20 AM
if (foundRedirect == null)
                    throw new Exception(string.Format("No site or redirect was found for '{0}'", host));
Hi all this line is throwing the exception and saying No site or redirect was found for 'http://localhost'
Can anyone please help me what is the problem
I have created a virtual directory for the Oxite project and running it from IIS
Dec 12, 2008 at 7:27 AM
That means the url being requested wasn't found to be the url your instance of Oxite was setup to accept.

  • What was the url being requested?
  • What is the value on the web.config/oxite/site "host" attribute?
If they don't match then it will throw an error.

I am in the process of making a change to the site element so you can specify other aliases (e.g. your host can be setup for while you can have an alias of that is also accepted) and will probably have that checked in later tonight.

For now though just make sure the two values I asked about above match and you won't get that error.
Dec 12, 2008 at 4:29 PM
Please make sure you allow for blogs not running as the main site.  In other words, almost all my websites will have blogs, but blogging won't be the only thing or even the main thing going on.  So I would want my blog to run as or  I also need to be able to handle this with multiple blogs, so I would want to support:

If this is not already supported, please try and account for it.  One of the things that has turned me off almost all .NET blogging platforms is that they take over the whole world and interfere with my main application.


Dec 12, 2008 at 5:41 PM
You can definitely not have the accumulation of all the blogs on your site as the home page.  You'll have to do a few changes to make that happen at the moment.  In the future, we'll make it easier.  Right now, you'll need to get the latest checked-in code, but it will show up in the next release, and inherit from OxiteRoutes and override what controller and action are called for the homepage, make your own action that gets the data you need (if any) and an appropriate view and register your new routes class in the web.config.  Again, this will get easier down the road.  For now, I'm sure we could do a write up on how to do this if you're interested, but it's definitely possible today.

Today, might not be possible.  We could definitely make it possible without a huge amount of work though.

We built in some plumbing at the last second before publishing the first release to enable different urls for blogs like that, but didn't get to actually implementing all the rest of the plumbing needed to make different names happen.

Thanks for the feedback and we'll keep this all in mind moving forward.