I have multiple installations of xoops. I am planning to move all core XOOPS files to a single location that is going to be linked into from all instances using symlinks. I will of course not be symlinking files such as templates, language files, etc.

I am wondering if anyone has done this or can foresee any pitfalls with this?

If it is possible then it will save space on my server but more importantly I can make updates from a single location .

I have personally never done this and would be interested in your results for future reference.

Good luck, sorry I couldn't have been more of a help to you though.

Catz

Refer to this site- http://jazzz1s.blogspot.com/. You can find the installation guides and tricks.

Hope it helps you:)

BTW - I have successfully implemented XOOPS installations with symlinks - so I am able to answer question should anyone have any.

I've done it successfully for subdomains, but it's complicated:
1.) core installation on same server
2.) symlinks created from each subdomain, excluding cache & uploads folders
3.) separate MySQL database for each subdomain - created from phpmyadmin, not XOOPS installation
4.) requires a few core and module hacks

Advantages:
- Performance isn't affected by symlinks
- only have to update one set of core files & saves server space
- separate database allows completely different settings and templates for each subdomain
- can create separate cpanel admin access to each subdomain

Disadvantages:
- core hacks!!!
- my web host disallows symlinks from separate domains even tho they are on the same server, so I can only use on subdomains

Bottom line is that it can be done, but requires pretty good understanding of XOOPS/PHP code.