Running wordpress from blog.html

I know this is backwards, but only because I can’t think of a solution going the other way. Why not redirect blog.html to the /blog directory?

No … I need to run the blog from https://www.mydomain.com/blog.html while wp is installed in https://www.mydomain.com/blog/ folder

If you are currently using /blog/ how do the post URLs look? Like /blog/?p=123 or /blog/2008/12/16/post-slug-here/ ?

And if /blog.html could be made to work, what do you expect the post URLs to look like then? /blog.html?p=123 or /blog.html/2008/12/16/post-slug-here/ …?

Post URLs are of the form /blog/2008/12/16/post-slug-here.html

I expect post URLs to look like /blog.html/2008/12/16/post-slug-here.html
OR
/blog/2008/12/16/post-slug-here.html

No … I need to run the blog from https://www.mydomain.com/blog.html while wp is installed in https://www.mydomain.com/blog/ folder

Why? If it’s to avoid broken links or lost search engine ranking, then a 301 redirect from mydomain.com/blog.html to mydomain.com/blog/ would take care of that.

A redirect is not what is required. Does anybody know how to do this?

I don’t see how you can possibly run WP from a single HTML file when all the required files to run WP are in the /blog/ directory. The WP file referencing system greatly depends on that fact that there is a common root folder.

/blog.html/2008/12/16/post-slug-here.html

The server will still read /blog.html/ as a directory, which will be empty. I imagine you would have to do something along the lines of /blog.html?year=2008&month=12&day=16, but why do that (assuming you could get it to work) when WP does that all of that for you?

/blog/2008/12/16/post-slug-here.html

This is correct because WP is in fact in your /blog/ directory.

A redirect is not what is required. Does anybody know how to do this?

Not really. As mentioned above by reflexionstudios, it would be technically incorrect. The url /blog.html could be a file that does a redirect but you don’t want that. You could rename /blog/ to /blog.html/ but it looks like you don’t want that either.

Also unclear is what are you trying to accomplish and why.

If you have old URLs that are in that format and you want to migrate them, then that is something we can help you with. That is not an unusual scenario and many of us have done this when migrating from a blog to WordPress (from MT for example). But it will use 301 redirects.

One of my clients requires that the blog be run from https://www.mydomain.com/blog.html while wp is installed in https://www.mydomain.com/blog/ folder

I’m afraid you’ll have to tell your client it can’t be done, unless you build your own blogging system with all necessary files in the root and all output is sent to blog.html.

I don’t see anything wrong with having someone go to https://www.yourdomain.com/blog — it’s actually much easier to type, remember, more organized, and cleaner (and subsequent URLs will be equally as clean).

I suppose you could use frames and have the blog called inside a frame in blog.html but … Yick. Why?