I have inherited a website that has third-party modules installed into the modules folder at the root level with the core modules, not sites/all/modules folder. Initially, I tried to move the directories one at at a time into the appropriate folder and the site broke. The core is 6.19. Would it be best to upgrade the core first? Should I disable the module, followed by downloading and installing the same module in the correct folder and then re-enabling it? Should I download and install all of the third party modules in the correct folder first, delete the other inappropriately located folders, and then run update first? Do I need to recreate the entire site from scratch?
Just moving them should work. You have something else wrong.
On Sat, Jan 29, 2011 at 1:53 PM, James R Stone fndtn357@gmail.com wrote:
I have inherited a website that has third-party modules installed into the modules folder at the root level with the core modules, not sites/all/modules folder. Initially, I tried to move the directories one at at a time into the appropriate folder and the site broke. The core is 6.19. Would it be best to upgrade the core first? Should I disable the module, followed by downloading and installing the same module in the correct folder and then re-enabling it? Should I download and install all of the third party modules in the correct folder first, delete the other inappropriately located folders, and then run update first? Do I need to recreate the entire site from scratch?
-- Best Regards, James R Stone fndtn357@gmail.com
"The skill of coding is to create a context in which other people can contribute."
-- [ Drupal support list | http://lists.drupal.org/ ]
http://drupleh.com/did-you-try-clearing-the-cache
On Sat, Jan 29, 2011 at 4:02 PM, Walt Daniels wdlists@gmail.com wrote:
Just moving them should work. You have something else wrong.
On Sat, Jan 29, 2011 at 1:53 PM, James R Stone fndtn357@gmail.com wrote:
I have inherited a website that has third-party modules installed into the modules folder at the root level with the core modules, not sites/all/modules folder. Initially, I tried to move the directories one at at a time into the appropriate folder and the site broke. The core is 6.19. Would it be best to upgrade the core first? Should I disable the module, followed by downloading and installing the same module in the correct folder and then re-enabling it? Should I download and install all of the third party modules in the correct folder first, delete the other inappropriately located folders, and then run update first? Do I need to recreate the entire site from scratch?
-- Best Regards, James R Stone fndtn357@gmail.com
"The skill of coding is to create a context in which other people can contribute."
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
FYI I downloaded the Acquia Mac stack last week and noticed they put their included contrib modules into a folder in /modules/acquia instead of in /sites/all/modules. I am sure they had a good reason, but when I need to update those I have a decision to make. Also if I use this stack to develop locally I will have to decide whether to copy that arrangement to a live server or not. Someone from the outside looking in might say I was doing it wrong. *
Ryan LeTulle,* Web Developer
personal: bayousoft.com http://www.bayousoft.com twitter: @bayousoft http://twitter.com/bayousoft
http://twitter.com/bayousoft*"Be the change you want to see in the world." * Mahatma Gandhi
On Sat, Jan 29, 2011 at 1:11 PM, Victor Kane victorkane@gmail.com wrote:
http://drupleh.com/did-you-try-clearing-the-cache
On Sat, Jan 29, 2011 at 4:02 PM, Walt Daniels wdlists@gmail.com wrote:
Just moving them should work. You have something else wrong.
On Sat, Jan 29, 2011 at 1:53 PM, James R Stone fndtn357@gmail.comwrote:
I have inherited a website that has third-party modules installed into the modules folder at the root level with the core modules, not sites/all/modules folder. Initially, I tried to move the directories one at at a time into the appropriate folder and the site broke. The core is 6.19. Would it be best to upgrade the core first? Should I disable the module, followed by downloading and installing the same module in the correct folder and then re-enabling it? Should I download and install all of the third party modules in the correct folder first, delete the other inappropriately located folders, and then run update first? Do I need to recreate the entire site from scratch?
-- Best Regards, James R Stone fndtn357@gmail.com
"The skill of coding is to create a context in which other people can contribute."
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
Ryan LeTulle wrote:
FYI I downloaded the Acquia Mac stack last week and noticed they put their included contrib modules into a folder in /modules/acquia instead of in /sites/all/modules. I am sure they had a good reason, but when I need to update those I have a decision to make. Also if I use this stack to develop locally I will have to decide whether to copy that arrangement to a live server or not. Someone from the outside looking in might say I was doing it wrong.
You should move the /modules/acquia to /sites/all/modules/acquia, then go to the admin/modules page and click the Save configuration button. If your site is in production put it in maintenance mode first and if the development site is used by more than 1 or 2 people also put it in maintenance mode.
It's just a local dev stack, but by default Acquia put the contrib modules in that location. I was just making an observation. *
Ryan LeTulle,* Web Developer
personal: bayousoft.com http://www.bayousoft.com twitter: @bayousoft http://twitter.com/bayousoft
http://twitter.com/bayousoft*"Be the change you want to see in the world." * Mahatma Gandhi
On Sat, Jan 29, 2011 at 2:10 PM, Earnie Boyd earnie@users.sourceforge.netwrote:
Ryan LeTulle wrote:
FYI I downloaded the Acquia Mac stack last week and noticed they put their included contrib modules into a folder in /modules/acquia instead of in /sites/all/modules. I am sure they had a good reason, but when I need to update those I have a decision to make. Also if I use this stack to
develop
locally I will have to decide whether to copy that arrangement to a live server or not. Someone from the outside looking in might say I was doing
it
wrong.
You should move the /modules/acquia to /sites/all/modules/acquia, then go to the admin/modules page and click the Save configuration button. If your site is in production put it in maintenance mode first and if the development site is used by more than 1 or 2 people also put it in maintenance mode.
-- Earnie -- http://progw.com
-- http://www.for-my-kids.com
[ Drupal support list | http://lists.drupal.org/ ]
You may have to go into the system table and adjust the paths to the modules. That's set when modules are enabled. I don't know if unsetting and setting will clear those entries, but uninstalling would remove custom database tables.
-Don-
On 1/29/2011 2:02 PM, Walt Daniels wrote:
Just moving them should work. You have something else wrong.
On Sat, Jan 29, 2011 at 1:53 PM, James R Stone <fndtn357@gmail.com mailto:fndtn357@gmail.com> wrote:
I have inherited a website that has third-party modules installed into the modules folder at the root level with the core modules, not sites/all/modules folder. Initially, I tried to move the directories one at at a time into the appropriate folder and the site broke. The core is 6.19. Would it be best to upgrade the core first? Should I disable the module, followed by downloading and installing the same module in the correct folder and then re-enabling it? Should I download and install all of the third party modules in the correct folder first, delete the other inappropriately located folders, and then run update first? Do I need to recreate the entire site from scratch? -- Best Regards, James R Stone fndtn357@gmail.com <mailto:fndtn357@gmail.com> "The skill of coding is to create a context in which other people can contribute." -- [ Drupal support list | http://lists.drupal.org/ ]
Don wrote:
You may have to go into the system table and adjust the paths to the modules. That's set when modules are enabled. I don't know if unsetting and setting will clear those entries, but uninstalling would remove custom database tables.
From my experience moving a module to another directory then going to
admin/modules and clicking the Save configuration button will reset the system table.
-
Don -
Earnie Boyd -
James R Stone -
Ryan LeTulle -
Victor Kane -
Walt Daniels