Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Robinton

    (@robinton)

    Thank you, wfalaa.

    I’ve decided to delete the WordPress installation in the root directory of my primary domain.

    So far I’ve encountered two hosts that put addon domains in the root directory of the primary domain, so that each file and directory in an addon domain is simultaneously in the primary domain, and I’m sure many more hosts do it that way as well. It seems to me a crazy way to structure the hosting space, but as long as it’s being done, I think you may want to consider a solution for that in Wordfence, to avoid this problem that was driving me nuts, and causing problems for my clients too.

    Thanks,

    Robinton

    Robinton

    (@robinton)

    Oops! Just now installed and activated Titan Framework myself, and the message didn’t go away. Anybody know how to make it go away?

    Robinton

    (@robinton)

    I don’t know how you got that message, but I got it after installing and activating “Ultimate Addons for SiteOrigin”, and it disappears when I deactivate that plugin. I don’t know if it’s required for the use of that (or any other) plugin.

    Titan Framework itself seems to be for theme and plugin developers, but it may (I don’t know) be required for the operation of some of the plugins developed with it. Chances are, you’ve got a plugin (or theme) that if you deactivate it, the Titan message will go away.

    While you probably won’t be using Titan yourself, if a plugin you want requires it, having it on your site probably won’t do any harm.

    Thread Starter Robinton

    (@robinton)

    Thanks, Ron. I’ll ask them.

    Thread Starter Robinton

    (@robinton)

    Thank you, RichardWPG.

    I’ve now resolved the issue. Here’s the solution.

    1) I retrieved my first “news” page from trash. The permalink was mysite.com/news

    2) Under Settings / Reading Settings, I chose “A Static Page”

    3) Under “A Static Page”, I left “Front page” at “— Select —“

    4) Also under “A Static Page”, I set “Posts page” to “News”

    5) I discovered that this installation had no .htaccess file in the installation root, so I copied one from another site.

    6) In the .htaccess file, I changed RewriteBase / to RewriteBase /news/

    7) In the .htaccess file, I changed RewriteRule . /index.php [L] to RewriteRule . /news/index.php [L]

    8) Above the other .htaccess commands I put Options +FollowSymlinks

    I don’t know if this last item was needed. I picked it up somewhere. But anyway, this whole package worked.

    May this prove useful to somebody sometime — but may no one else ever have to face this mess!

    Robinton

Viewing 5 replies - 1 through 5 (of 5 total)