Forum Replies Created

Viewing 15 replies - 16 through 30 (of 37 total)
  • Thread Starter sachi21

    (@sachi21)

    Thanks Moshu. Just to clarify one thing. When you say the “whole WP install”, you are referring to each and every file and directory found in my root directory. Which I believe is wp-admin, wp-content, wp-include and all the “wp” prefixes to them.
    I just want to make sure of the terminology that you are using and that I’m on the same page.

    Thread Starter sachi21

    (@sachi21)

    >>>The Pages and posts would not become dead – only the old links!

    Confused. when you say old links, aren’t you referring to the old posts?

    Thread Starter sachi21

    (@sachi21)

    >>>I relate to what you are talking about. Don’t feel dumb,

    Nah, I don’t feel dumb 🙂 Just a bit irked at this moment. I forgot all about Filofso plugin until you mentioned it. I installed it. It works just like the Semiologic plugin works so that was fine.

    I tried to customize my permalinks by prepending, “/blog/” to the permalink structure. I had to manually update my .htaccess file for whatever reason with the following code;
    ——————
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /blog/
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /blog/index.php [L]
    </IfModule>
    —————

    but now, I get a 500 internal server error for any page but the homepage.

    Thread Starter sachi21

    (@sachi21)

    I was posting to the Semiologic community forum, but still had issues with their plugin.

    So I sat there and thought about it for a while.

    And when I sit there and think about it, there is one way to get around this w/o using the opt-in plugin because you have to admit that it’s kinda wierd to categorize every entry under “blog.” Just wierd.

    I was thinking of creating a link from the homepage and point it to something like this; /blog/2006 . Like this;
    http://mydomain.com/blog/2006 . Whereby 2006 is the yearly archive.

    In effect, visitors would be looking at the entries for the current year which pretty much replicates what most of us see when we visit a blog- the most recent entries which are all for the given year.

    I thought this might help those who would have future issues.

    Thread Starter sachi21

    (@sachi21)

    >>>Ah, now I got it… well, if that plugin is using the “home.php” mechanism built in WP (see Template Hierarchy in Codex) then you can not have both.

    Wow. I’m surprised. Considering all the wonderful things that WP can do 🙁

    I installed the opt-in plugin but still no go. I’ll have to post on their community forum to see what the issue is.

    Having said that, I guess another option to get around this is to have WP installed twice. Once for the website and then another for the /blog domain. I’d prefer not to do that but a blogger has to do what a blogger has to do….

    Thread Starter sachi21

    (@sachi21)

    >>>No. I mean it depends what you mean by homepage… a non-WP whatever index file? That would be at example.com.

    No- my entire website is based out of WP, including the homepage.

    Thread Starter sachi21

    (@sachi21)

    Honestly, I didn’t know that when I installed this. Having said that, if I installed WP into a subdir, then my homepage would no longer be the top level domain, would it? ie; http://www.mydomain.com

    It would be like http://www.mydomain.com/subdir and then the blog url would
    http://www.mydomain.com/subdir/blog . Right?

    So I guess there is no way to reach both goals– have the blog url and then have a top level domain for my homepage?

    Thread Starter sachi21

    (@sachi21)

    Well, the problem with this is that I once I implemented it, the url takes me back to my homepage and not to my blog. As I mentioned, I am using the Semiologic Frontpage Static Plugin and that is what is preventing the blog url to show up.

    Of course, I can disable the plugin, but then my blog would show up on the homepage and I don’t want that as I want just a normal homepage. Is there a way to get around this?

    Thanks.

    Thread Starter sachi21

    (@sachi21)

    Unfortunately, I was looking under manage > comments.

    Thanks!

    Thread Starter sachi21

    (@sachi21)

    thanks moshu.

    Thread Starter sachi21

    (@sachi21)

    Sorry for the late reply. I’m just now logging back in to the support forum.

    It was sort of a silly oversight that I failed to understand. But aren’t they all?. But basically, in the header section of the template, the code looked like this;

    <h1 id="title"><a>"><?php bloginfo('name'); ?></a></h1>

    It seems that when I activitated the static plugin, the above code found the ‘home’ slug and turned it to the blog tab because of the
    php bloginfo ('home')

    To fix this issue, you have to get ride of the code and have the code look something like this.

    <li class="<?php echo $pg_li; ?>"><a>" title="Blog"><span>Home</span></a>

    I hope this helps others

    Thread Starter sachi21

    (@sachi21)

    Nope- for whatever reason, the htaccess file was never there. I made sure to show hidden files in my ftp client but the file still didn’t show up. It’s ok because I just created a new one anyway.

    But I’m thinking I should keep the WP core files in both directories…just to play it safe?

    Otherwise, thanks for your time, Han

    Thread Starter sachi21

    (@sachi21)

    and one more question. Once I move the WP files to the root directory, should I delete the files in the other directory? ie; delete the files at http://www.domain.com/main but keep the files at http://www.domain.com/ ?

    Thread Starter sachi21

    (@sachi21)

    Very cool. It actually works!

    Question: In step 9, it says;

    Change the following and save the file. Change the line that says:
    require(‘./wp-blog-header.php’);
    to the following, using your directory name for the WordPress core files:
    require(‘./wordpress/wp-blog-header.php’);

    I never did that because the index.php file doesn’t have that command at all. In fact, I looked through a couple other themes I downloaded and none of the index.php file has that command.

    In fact, I can’t even find the .htaccess file at all. It’s usually there. Is this normal?

    Thread Starter sachi21

    (@sachi21)

    Nice article, Handy. This article is showing how to ensure our blog entries exist in the site root. But what if I’m not using the blog at all? I am just using WP as a CMS for regular old pages. Does this article still remain relevant?

Viewing 15 replies - 16 through 30 (of 37 total)