As I spent a number of months comparing CMS tools, I initially set up my directory for Drupal as a sub-directory. I did this, in fact, with each of the CMS tools we explored.
i.e.,
<root>/dru <root>/pmachine [1] <root>/spip <root>/geeklog
Before I go about the process of moving my primary site content from "/dru", up to the site root:
1. What pitfalls might I encounter? 2. What should I be on the look-out for? 3. What databases replaces should I perform? (just URL paths in appropriate table columns?) 4. What am I not asking?
I can handle re-directing incoming pre-linked traffic to back up to the root, using Apache's tools to do so, so this doesn't worry me very much.
If there are other considerations that you would recommend or caution, please share them with me before I make a mess of things (which might happen anyway. ;)
I do have some "path-sensitive" modules installed, such as:
Image Assist + FileManager
Attach
Image
Project [* I note that the Project help says that changing the location of directories can cause problems, but I believe I can solve this in the DB itself, if so.]
These are not all of the modules I've installed, of course, just the ones that seem very path-centric.
I appreciate your time, in advance.
-- Gary
[1] As a side-note, I'd like to let others know (I read a few online user questions about whether this would work):
pMachine blends very nicely with Drupal. This is especially useful if:
one has legacy content, one prefers the very clean interface of pMachine entries (I do), one has a large number of images already in well-known directories, (because pM's FileBrowser system is excellent and easy, and works much better than any Drupal module I've found) one has a preference for pMachine's 'bookmarklet' tool
Just FYI...it works very well and we will continue to use this combo.
You may find this thread of use:
In general, though, if you're just moving up a level, turn everything off, move the files, tweak settings.php and .htacess, and turn it back on. The database shouldn't need to know the difference.
On Thursday 27 April 2006 09:56, Gary (Lists) wrote:
As I spent a number of months comparing CMS tools, I initially set up my directory for Drupal as a sub-directory. I did this, in fact, with each of the CMS tools we explored.
i.e.,
<root>/dru <root>/pmachine [1] <root>/spip <root>/geeklogBefore I go about the process of moving my primary site content from "/dru", up to the site root:
1. What pitfalls might I encounter? 2. What should I be on the look-out for? 3. What databases replaces should I perform? (just URL paths in appropriate table columns?) 4. What am I not asking?I can handle re-directing incoming pre-linked traffic to back up to the root, using Apache's tools to do so, so this doesn't worry me very much.
If there are other considerations that you would recommend or caution, please share them with me before I make a mess of things (which might happen anyway. ;)
I do have some "path-sensitive" modules installed, such as:
Image Assist + FileManager Attach Image Project [* I note that the Project help says that changing the location of directories can cause problems, but I believe I can solve this in the DB itself, if so.]These are not all of the modules I've installed, of course, just the ones that seem very path-centric.
I appreciate your time, in advance.
-- Gary
[1] As a side-note, I'd like to let others know (I read a few online user questions about whether this would work):
pMachine blends very nicely with Drupal. This is especially useful if:
one has legacy content, one prefers the very clean interface of pMachine entries (I do), one has a large number of images already in well-known directories, (because pM's FileBrowser system is excellent and easy, and works much better than any Drupal module I've found) one has a preference for pMachine's 'bookmarklet' toolJust FYI...it works very well and we will continue to use this combo.
-
Gary (Lists) -
Larry Garfield