Admin posted on June 28, 2008 18:00

If you see this post it means that BlogEngine.NET 1.4.5 is running and the hard part of creating your own blog is done. There is only a few things left to do.

Write Permissions

To be able to log in to the blog and writing posts, you need to enable write permissions on the App_Data folder. If you’re blog is hosted at a hosting provider, you can either log into your account’s admin page or call the support. You need write permissions on the App_Data folder because all posts, comments, and blog attachments are saved as XML files and placed in the App_Data folder. 

If you wish to use a database to to store your blog data, we still encourage you to enable this write access for an images you may wish to store for your blog posts.  If you are interested in using Microsoft SQL Server, MySQL, VistaDB, or other databases, please see the BlogEngine wiki to get started.

Security

When you've got write permissions to the App_Data folder, you need to change the username and password. Find the sign-in link located either at the bottom or top of the page depending on your current theme and click it. Now enter "admin" in both the username and password fields and click the button. You will now see an admin menu appear. It has a link to the "Users" admin page. From there you can change the username and password.  Passwords are hashed by default so if you lose your password, please see the BlogEngine wiki for information on recovery.

Configuration and Profile

Now that you have your blog secured, take a look through the settings and give your new blog a title.  BlogEngine.NET 1.4 is set up to take full advantage of of many semantic formats and technologies such as FOAF, SIOC and APML. It means that the content stored in your BlogEngine.NET installation will be fully portable and auto-discoverable.  Be sure to fill in your author profile to take better advantage of this.

Themes and Widgets

One last thing to consider is customizing the look of your blog.  We have a few themes available right out of the box including two fully setup to use our new widget framework.  The widget framework allows drop and drag placement on your side bar as well as editing and configuration right in the widget while you are logged in.  Be sure to check out our home page for more theme choices and downloadable widgets to add to your blog.

On the web

You can find BlogEngine.NET on the official website. Here you'll find tutorials, documentation, tips and tricks and much more. The ongoing development of BlogEngine.NET can be followed at CodePlex where the daily builds will be published for anyone to download.

Good luck and happy writing.

The BlogEngine.NET team


Posted in: BlogEngine.NET  Tags: ,

What the hell is the "SharePoint Ninja Toolkit" you ask?  It is going to be where I plan to release the countless small little utility apps/features that I've written over my SharePoint development experiences.  Almost every project I've worked on I end up with small little apps or chunks of code that end up sitting around that I reference from time to time.  I figured, I might as well polish these up a tad and release them out there for others to enjoy.  Hopefully it will save someone the headache of having to do it themselves, or if anything, serve as a learning tool.

Check it out over at CodePlex. (Right now its unpublished, but by the end of the week i'll have at least 1 or 2 small utilities up there to start it out.)


Today I ran into a bit of an issue in a SharePoint server farm environment where I added a web part to a page, but for the life of me I couldn't delete it.  I clicked the 'X' button, I tried to edit properties, I tried to delete from the edit pull down menu, but nada!  I tried from the load balanced URL and from the Index Server but no dice.  I did a quick google search and hit this helpful link,

http://www.sharepointblogs.com/nrdev/archive/2007/02/08/tip-easily-get-to-the-webpart-maintenance-page-for-any-sharepoint-site-url.aspx

Basically by adding "Contents=1" as a query string variable to any page, you'll go directly to the web part maintenance page for that page.

Ex. http://{site url}/pagewithproblemwebpart.aspx?contents=1 will take you to the maintenance page.

 

Update 7/7/2008

The url above will actually redirect you to the following url. 

Ex. http://{site url}/_layouts/1033/spcontnt.aspx?&url=pagewithproblemwebpart.aspx

 

Between the two url's I provided you should be able to deal with problem web parts and get back to a working page with little downtime.


Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2017 Tony Testa's World