Hi Georgia,

Your site is in a frame. Some one did that, not the B2evo engine. The actual blog can be found here: http://localecology.org/blogs/index.php?blog=2 B2evo has tricks to make the blog appear in another folder.

Good luck

Your site *is* generated by php code using information stored in a MySQL database. http://localecology.org/blogs/index.php?blog=2 The link you provided points to, as you already know, a frame with your blog in it.

http://localecology.org/index.htm is a regular old fashioned HTML page. Are you trying to replace the entire web with b2evolution, or just get out of the frame? If the former we can help you do that. If the latter you will have to do that on your own.

I use b2evo to write the posts you see on http://localecology.org/localecologist. Is it possible that the content at http://localecology.org/blogs/index.php?blog=2 can be seen if someone goes to the URL http://localecology.org/localecologist?

As to your question
Are you trying to replace the entire web with b2evolution the answer is yes, I think.

Thank you.
-ecology

ecology wrote:

I use b2evo to write the posts you see on http://localecology.org/localecologist. Is it possible that the content at http://localecology.org/blogs/index.php?blog=2 can be seen if someone goes to the URL http://localecology.org/localecologist ?

Yes, but what you really mean, I THINK, is how do you get rid of the frame the blog is currently in. To do that you absolutely must get rid of the frame file. PROBABLY it is at localecologist.index.htm but I don't know and can't say for sure. Anyway moving your blog up to the root will probably end up wiping it out so let's move on.

ecology wrote:

As to your question
Are you trying to replace the entire web with b2evolution the answer is yes, I think.

Cool. So let's talk about file structures and stuff. Currently on your server your blog is in a path that goes something like /public_html/blogs/ meaning inside the "blogs" folder is where you have all the b2evolution files and folders. Stuff like "conf" and "htsrv" yah?

So what you want to do is 2 things followed eventually by a third thing. FIRST, before we get to the two things, make sure you have a backup of ALL your files from your server. If something goes wrong and you want to back up it might be impossible without having your files backed up.
SECOND, before we get to the two things, make sure you have a backup of your database. I do not believe the following procedure will risk your database at all, but if you do not have a database backup then you will absolutely need it. Funny how that happens, but it almost always does.

Now finally for the two things before the third thing. Aw crap it's gonna be like 5 things. Oh well!

Edit blogs/conf/_basic_config.php and find a bit called $baseurl. There you will see your domain name ending with /blogs/ - change it by removing the /blogs bit. Note that it will now be your actual domain name ending with a "/".

Now the easy part: delete all the files from your server.

Now another easy part: upload to your server's root level all the files that were in the "blogs" folder. The ones you backed up a few minutes ago. By "server root" I refer to the level that "blogs" was at a few minutes ago. So the path for your conf folder would end up something like /public_html/conf/ instead of /public_html/blogs/conf/

Now visit your root domain name and you will see your blog without the nasty frame and without the /blogs part in the URL.

Thanks. I will try this. It will take a while as I am unfamiliar with sort of procedure.

-ecology

Most people are treading in unfamiliar ground when they do this sort of thing. That's why I encourage backup backup backup.

Also, when you attempt it please give it a fair amount of time ... and possibly take some paper notes to make sure you are comfortable with what you are about to do.

In summation: all the stuff in your server's "blogs" folder needs to move UP one level to your server's "root" level. Frequently it has 'public_html' in it, but not always. In no case do you want to put stuff AT the 'public_html' level - rather you want your stuff IN that level.

For Example:

public_html
--blogs
----conf
----htsrv
----many other folders
----a file.php
----another file.php
----many files.php
--cgi_bin

Would Become:

public_html
--conf
--htsrv
--many other folders
--a file.php
--another file.php
--many files.php
--cgi_bin

The part where you edit your conf/_basic_config.php file is how you tell b2evolution where to look to find the files, so it needs to know the files are at the root instead of in the "root/blogs" folder.

Hope that helps!