erick_paper

Well, this is why a number of WP installs get hacked. Because script kiddies can easily find out where the wp-admin is, and then use the Admin account. I see the WP community dismissing this as “not WP’s fault, stupidity of blog owner” but both EE and MT give me huge messages in red suggesting that I should change these simple things.

You’re right. In WP’s case, the content is in the DB. Which makes separation of the path much simpler (mod_rewrite rules only).

Anyway, with whatever kludge is advocated by the WP codex, my site is working. (Until I get to running several blogs, but I can live with that).

Thanks.

Ok, sorry I stand corrected. I did follow the step 7 of the instructions. I have the vault folder and I have the index.php as follows:

<?php
/* Short and sweet */
define(‘WP_USE_THEMES’, true);
require(‘./cms/wp-blog-header.php’);
?>

The Codex is for putting the “blog directory” in the root, so that dot in front of cms makes sense. In my case, I’m in a vault directory, so I made that two dots, and it works now.

I still think this need not be manual at all, it’s a simple mod_rewrite issue for those who have it enabled (and most of us do these days, to use permalinks).

Ideally, the design of a CMS should make sure that the CMS itself is separated from the content. Easy for MT to do as it generates physical HTML files. WP should have a nicer way of doing it without having manual index.phps in physical folders.

Thx a bunch for your help.

Thanks for the tip about creating the vault directory. But since WP does not generate any actual content, why is it essential to have a physical folder called “vault”? I checked the mod_rewrite rules and they seem to be pointing just fine (vault –> /cms/..).

The Codex instructions never mention creating index.php for the “blog URL” (vault in my case), only for the “wordpress URL” (cms in my case). Am I missing something? Again, why does WP need a physical vault folder?

As for MT, yes the MT install would remain in /cms/ for example, but my actual generated files have nothing to do with that folder. I can have MT create html/php files into pretty much any place in my system, and this value is entered in the MT web interface. Which was superlative, but that’s besides the point here.

MT and EE allow me to setup paths with zero manual labor. It’s the way an application is designed.

If copying a file to a location and modifying a line in it is required, then it surely does not need manual intervention. Many WP plugins themselves do this all the time.

Anyway, yes the file exists. I can see the wp-admin now but the https://domain.com/vault still does not work. I have changed the permalinks to reflect the vault etc. What else should I check for errors? There is no “error_log” file being generated.

Thanks for any pointers!

Thanks. Yes I did read that page, but it doesn’t work. As per the instructions, I wanted to move my https://domain.com/wp/ to the following:

WP INSTALL: https://domain.com/cms
BLOG: https://domain.com/vault

So I made these changes in the Options, and then saved them. This came back with a 404, because the “wp” directory is not “cms” yet. So I quickly changed the folder name of “wp” to the new “cms”, as per step 6 in that instruction list.

I still see a 404 at https://domain.com/cms/wp-admin. Any thoughts?

(I don’t mean to denigrate WP in comparison to others, but something like this should be basic functionality and REALLY not require the manual copying of files and editing a line in index.php!)

I think masking stuff is a VERY critical step in security. Of course, that shouldn’t be all.

With Movable Type or Expression Engine, I can have the software installed here:

https://domain.com/mt/mt.cgi
https://domain.com/ee/index.php

But my blog can be anywhere. E.g.,

https://domain.com
https://domain.com/blog/

Etc. With WP, it seems everything I do, the blog runs from the same place WP itself is installed!

WP install:
https://domain.com/wp/wp-admin/

WP blog:
https://domain.com/wp/ !!

Thanks for your response, and for the link to the forums. I think I will try that out for sure. I want to use one WP installation for many domains. Not subdomains of one domain. So, site1.com, site2.com, etc.

I would love to use MU but I am not sure if:

1. It will support all the plugins I want to use. I just about 10 or so for simple themes but even they don’t work from my trial so far. For simple stuff like photo galleries.

2. Allow me to design VERY different blogs on a per domain basis.

3. Which brings me to the main one: will it work across entire *domains*. I want ONE install of WP and want to work it across many domains. And I want to use WP-Cache across all of them where possible.

Thanks!

Btw, SuperCache’s recognition of my mod_rewrite was wrong. I have it enabled server wide. If SuperCache expects .htaccess to be writable, that’s a pretty silly expectation. Maybe I’m spoilt by the easy functionality of WP plugins that “just work”, but this was one painful beast.

Not sure what you guys are doing right and I’m doing wrong, but installing broke pretty much everything in my caching solution, which prior to installing SuperCache, was only WP-Cache! Now I’ve deactivated SuperCache and only have WP-Cache going, but that doesn’t work either! Comes up with a blank page in its Options page.

Why are you using WP-SuperCache instead of WP-Cache? I mean, what is the benefit? WP-Cache is more mature, innit?

This looks interesting. Could you explain what “Featured Page” and “News Page” tabs are on the top? They don’t look like categories, and they are from the same blog, so what are they exactly? (I’m confused about the nomenclature).

Is it that you have three “sections” of this magazine type site, called NEWS, FEATURES, and SAMPLES? Why would NEWS not be a blog post for example and instead a page?

If these are “Page” sections, my question would be: what if I started three four other sections tomorrow, would they automatically show up in the theme?

Thanks for any ideas and apologies for sounding like a newbie on WP, which I am!

Hi, I want to do the same. Is there a plugin that allows this? When we have to upload many images at once, it’s very painful to upload one by one! Thanks for any pointers.