custom admincp and modcp url's

[BowlingTracker]

When upgrading to vb5, it asked me what I wanted as my admincp and modcp urls. i put adm1n and m0dcp. (note the 1 and 0 instead of i and o).

Somehow it's not working correctly.

In core/includes/config.php they are defined as adm1ncp and m0dcp.

The folders in forums/core are named "admincp" and "modcp". The url's "forum/admincp" and "forums/modcp" work, but "forums/adm1ncp" and "forums/m0dcp" doesn't. They give "Invalid Page URL".

The admincp and modcp links in the bottom footer work. They don't have the 0 and 1 in the links. The admincp link at the top left (site editor) points to adm1ncp and does not work.

If I rename the folders in core to adm1ncp and m0dcp, then I can't get to them at all.

I'm unsure how to resolve this to make it work with the custom urls..

Thanks.

[BowlingTracker]

Also, in the database table "routenew" there are two routes for admincp (identical except for routeid) and 1 for modcp. The actions are "admincp" and "modcp" respectively.

[Zachery]

There isn't an overly good reason to rename folders, you're better off password protecting, or or IP restricting their access.

[BowlingTracker]

I wasn't sure if the folders were supposed to be named differently due to choosing custom urls for those folders.

I guess i can install a test instance specifying the custom url's and see how it all gets configured.

those are good ideas too.

[cellarius]

Of course you would have to rename the folders accordingly if you set the software to use custom names.

What Zachery means is more general: It does not make a lot of sense to use that option at all. There is not much security through obscurity, especially if you just replace i by 1 and o by 0, which has to be the oldest "encryption" trick there is.

You're much better off doing what he proposed: Create a .htaccess-file and protect your admincp folder with an additional password, and if you have a static IP, you can set it up so you don't even have to enter that password if you're working from your own computer. Protecting modcp in this way is not that important - there's not much harm that can be done from there.

[Zachery]

It was one of those things, that we did, and it wasn't a bad thing. But in today's world renaming the folders is just kind of silly.

--------------- Added [DATE]1403126478[/DATE] at [TIME]1403126478[/TIME] ---------------

I'm guessing this will get merged, either way, make sure (for vB5) that you protect both the AdminCP, and core/AdminCP folders.

[BowlingTracker]

Makes sense.. I'll do that.. everything is working fine now with the normal admincp/modcp folder names.... except, the link in the sitebuilder (upper left corner) points to adm1ncp instead of admincp and I can't figure out where it's coming from. I can't find any referecne to adm1ncp in the files or database.

I already changed the core/includes/config.php to set them correctly there.

--------------- Added [DATE]1403139833[/DATE] at [TIME]1403139833[/TIME] ---------------

nevermind.. i found it.. config.php in the forum root.. lol

--------------- Added [DATE]1403141728[/DATE] at [TIME]1403141728[/TIME] ---------------

got the .htaccess password working right too.. both admincp and core/admincp are protected.

Thanks guys!