By paultanner on

going from 6.6 to 6.13 and changing servers
disabled non-core modules before dumping the database
relevant files locaated in sites/all/modules and sites/all themes
installed and upgraded
in admin/build/modules only core modules listed
double-checked directory permissions (755)

On an earlier attempt I could install new modules but not get the original non-core ones to show.
Now I can't get any to display other than core.

Thx. Paul

⋅ Categories: Drupal 6.x

Comments

redpuma’s picture

redpuma commented

Right now you have this problem and it is unclear which change has caused the problem, have you done the upgrade and server move as one operation?

Is it possible to view your website on the old server still?
How do access your files on the server SSH or FTP?
I'd approach it slightly differently depending upon how you have things setup and the answers to the above.

I would try and get the original 6.6 installation working if possible. Make complete file and DB backups. Then try the upgrade. If all is well it would indicate the upgrade is not the cause. If it is then solve that issue before the server migration.

paultanner’s picture

paultanner commented

OK thx redpuma, I did upgrade the old site.
It wasn't my preference as I could have ended up with that broken too.
However, that went OK so I was looking for an issue with the server move.

In the end I happened to notice an issue with file ownership.
Somehow any tarball created on the old site would untar with bizarre file ownership. Downloaded tarballs were OK however.

So all I needed was chown -R on the transferred tarballs and drupal now sees these themes and modules.
This was all rather empirical. I need to find out more about how tarballs should be made so that they transfer OK without chowning them.
(I was fortunate to have full root access so I could do this.)

Paul

redpuma’s picture

redpuma commented

Great news, good to hear you solved it.