So I ran into this awesome situation. After I have moved and got my server up here with me, I am faced with a temporary ordeal. I have no control over the router and how information is relayed to my server. Nor do I have control over the IP addy in which I am given. It isn’t my networking equipment. So I was forced to change the address, and until I can get any sort of port forwarding or DMZ set up, I’m without access to my domain from my server. So as of the writing of this post I’ve had to figure out a way to update wordpress’ url and home link settings without being able to login to the admin pages.

Anytime you try to go to the site I am forced to be redirected to the domain, however at the time of this writing that ends up hitting the router that I’m behind, which doesn’t point to this server obviously, therefore I’m thrown a 404 error. The only way to allievate this situation is to change the URL’s to point to the local IP. At least that is the only thing I can think of as of right now.

How can you do that if you can’t even get to the admin pages? It’s almost too easy.

Inserting some php functions in the active theme is all it takes.? Here are those functions.

update_option('siteurl','http://example.com/blog');
update_option('home','http://example.com/blog');

These functions needs to be placed directly after the <?php line in the functions.php file of the active theme.

You can discover how I did this from this post here. There are other methods available. That post tells you how to do it.

Just the other day I was offered a job! Soon I will be making the finalizations of the scene which I currently live in now. And soon the next scene will take to the stage! This will bring immence change in my life as I will be making a move to a much larger area. Annapolis Maryland to be exact. I’m currently looking for housing and more so way to excited that I’m starting so soon.

I’m taking the position of a System Administrator at a company called InforMed-LLC. They are a Health Care Solutions provider for many companies. They are a rather small company but growing. This is an awesome oppurtunity for me and if you can see my face expression you can definately tell how ecstatic I am about this change in life.

I’ve been waiting a long time for a job offer. Now I will move on, and ponder the future. Now I shall see where my life takes me.

Yesterday I brought on-line a new server. I took my old laptop and threw Debian Etch on it. The same laptop that used to run windows Server and before that was and Ubuntu Desktop is now once again a server. Running Folding at Home and apache as a web-server, I know intend to do some testing with VPN’s and emails. Something I haven’t done much of in the past, I would like to add to my experience. However right now I wish I could get a job and be able to flex my educational muscle that was being grown all these past years. I still haven’t figured out what I’d like to write for this blog. So more random stuff will be posted. I guess if I have any troubles for my own personal diary. I should use the word journal instead.

If you’ve noticed I have all my old posts that I had on my SQL database. I backed all that up using the BlogXML export function that came with the .NET BlogEngine, then just copied and pasted the info into new posts here on WordPress. Being that it was only a couple of posts it isn’t that hard to do and probably the easiest. I need to build up my list of tags and categories again, however. I’ll work on that eventually. RIght now, I’ve got to get ready for an interview.

In the mean time, enjoy my fresh new looking blog. Have a fantastic rainy day.

So I wanted to post up here my issue I had when I first tried to install BlogEngine and forcing it to use a database instead of the default XML. The reason I wanted to use a database in the first place is the fact that I have Microsoft SQL 2008 installed on this machine and nothing to really use with it. So taking advantage of such products already available, I thought I’d go ahead and start it up. Installation goes just as simple as the README’s take anyone. However when I was first trying to reach the brand new page, it was a no go. I was thrown an error indicating that the user, in my case blogger, was not able to log in. .NET fails to actually tell me exactly what the error was when trying to log in, it’s just nice enough to provide me the numerous exception errors that kept coming as it proceeded to process whatever it does.

Upon learning to figure this out, I scrambled through the log files to figure out why I couldn’t log in. Everything was set up correctly I know that for a fact. But going through the log errors that SQL throws out, it was discovered that apparently you are not able to log in when SQL is configured to use Windows Authentication. During the install of SQL Server, I chose that as a method of logging into the database as it had not occured to me as to how much a difference it would make to use the database system. I thought at first this error was null as I did end up creating a user named blogger on the system. But obviously it did not work properly.

To alleviate the poor situation I was in, I simply reconfigured Microsoft SQL to use Windows Authentication alongside SQL User Authentication. After recreating a user just on my behalf to make sure I was doing everything correctly, I was rolling. Of which can be verified as the post created in the database is right below this post. Yay for fixing problems!

Happy Blogging.