TomCat & Manager folder issues

Hello

I tried a couple of items to get around the ’manager’ folder & tomcat issue, has anyone had any success with this?

’manager’ folder being a reserved keyword for tomcat

I am able to access manager via the IP route ... http://123.123.123.123/manager/etc ..., but it leave the IP as the base URL, not good for SEO friendly URLs ?!?4

I’ve also tried renaming all occurrences of ’manager’ to something else, not quite finished on that one ...

Anyone have any suggestions on this?

.htaccess redirection or something?

thx

Would love to have your changes to the manager directory submitted as a patch in Jira at http://svn.modxcms.com/jira/

Revo takes care of this but we still need to do it for Evo/096x

Wouldn’t it make more sense to create a variable, constant or value for the manager folder name in the config.inc.php that is selected on install? Could this even be possible? This would mean a replacement for the whole installer/upgrader.

This would be a pain but worth it to have the manager directory as user selectable from the installer.

Quote from: smashingred at Oct 26, 2008, 11:19 AM

Wouldn’t it make more sense to create a variable, constant or value for the manager folder name in the config.inc.php that is selected on install? Could this even be possible? This would mean a replacement for the whole installer/upgrader.

There is a constant that can be used for the manager folder, MODX_MANAGER_PATH. The first step is to make sure that that constant is used throughout the manager code in place of the hard-coded manager folder references. Once that’s done, I don’t think it would be too much work to include it as an option in the install process.

The only bugbear with this is that there are likely several third-party components that would need to be updated as well to make it a seamless upgrade process.

Third-party scripts would need to be updated as needed indeed. I think that we distribute one with 096x that’s dependent on it: AjaxSearch for the mootools bits, and QuickEdit too I think. But that’s a small price to pay...

Using the constant should be indicated as the best in the development documents. I forgot there was one.

I think there are a number of reasons to go through this process, not the least of which is conflicts with tomcat. Making the manager folder user selectable would allow people added security as well as creating a manager folder name with a non english word.

Yes this would mean the included addons would all need replacements done but I love the idea for the added flexibility.

To be fair, this process has already been done; making the folder name configurable is anything but trivial in the current MODx architecture, especially when it comes to distribution and installation, and a lot of work has already gone in to making all of the file locations in Revolution configurable to avoid any number of potential conflicts like this one with Tomcat’s default manager location.

IMHO, though it would be wonderful if the existing code could do this, I do not believe the effort involved in trying to reproduce these significant changes in that code base is practical at this point in its life-cycle.