Re: Renaming and moving xoops_lib and xoops_data [Installation Troubleshooting]

1

Renaming and moving xoops_lib and xoops_data

2008/8/5 4:59
Nick_James
Friend of XOOPS
Posts: 359
Since: 2006/10/14

Okay, it is probably already answered somewhere else, but does anyone have more information on this line?

"6. For security considerations, you are encouraged to move directories xoops_lib (for XOOPS libraries) and xoops_data (for XOOPS data) out of document root, or even change the folder names."

What else do we have to change so that XOOPS can find them if we rename and move them?

Nicholas James
President - LaDads
http://www.ladads.info

2

Re: Renaming and moving xoops_lib and xoops_data

2008/8/5 5:52
Nick_James
Friend of XOOPS
Posts: 359
Since: 2006/10/14

Ah, well there it is. A very nice menu once I start the upgrade sequence. It asks me where those two files are.

I. C.

What is a good security practice for moving them out of the root?

If we want to move them later, after the upgrade, what file do we edit? Or can we just run the upgrade again.

Nicholas James
President - LaDads
http://www.ladads.info

3

Re: Renaming and moving xoops_lib and xoops_data

2008/8/5 7:01
anderssk
Quite a regular
Posts: 335
Since: 2006/3/21

You can edit the mainfile.php if you want to move them later.

Moving theme out of web-root is a very secure thing to do.
It's like your home. Things You don't want stolen, You can move to a secure place like the bank

Try read this security guide

4

Re: Renaming and moving xoops_lib and xoops_data

2008/8/5 20:05
Nick_James
Friend of XOOPS
Posts: 359
Since: 2006/10/14

Thanks

Nicholas James
President - LaDads
http://www.ladads.info

5

Re: Renaming and moving xoops_lib and xoops_data

2008/8/5 20:11
Nick_James
Friend of XOOPS
Posts: 359
Since: 2006/10/14

This upgrade is eating my lunch.

The original install went okay and the site is 'running' again.

But...

I am missing a concept somewhere. The installed modules are not showing up on the admin menu...

Nicholas James
President - LaDads
http://www.ladads.info

6

Re: Renaming and moving xoops_lib and xoops_data

2008/8/5 20:29
Nick_James
Friend of XOOPS
Posts: 359
Since: 2006/10/14

Well, my modem got fried by a power surge on Friday, so I switched to using an on-line connection.

And my dreamweaver refuses to make ftp connections to this account for some reason. It used to. So I am learning Filezilla.

Zilla will load the files into the directory you have selected... Ouch. So if you upload the modules to the wrong directory. They don't show.

Sigh. Okay. Lest see if we have it now.

Nicholas James
President - LaDads
http://www.ladads.info

7

Re: Renaming and moving xoops_lib and xoops_data

2008/8/5 21:39
Nick_James
Friend of XOOPS
Posts: 359
Since: 2006/10/14

Okay. For some reason the installed modules are not showing up.

Manual installed TAG and PROTECTOR by copying the code from an other install. Protector seems to be working.

Nicholas James
President - LaDads
http://www.ladads.info

8

Re: Renaming and moving xoops_lib and xoops_data

2008/8/6 6:11
anderssk
Quite a regular
Posts: 335
Since: 2006/3/21

What error are You getting, when turning on debug-mode?

Stats
Goal:	$100.00
Due Date:	Nov 30
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Renaming and moving xoops_lib and xoops_data

Re: Renaming and moving xoops_lib and xoops_data

Re: Renaming and moving xoops_lib and xoops_data

Re: Renaming and moving xoops_lib and xoops_data

Re: Renaming and moving xoops_lib and xoops_data

Re: Renaming and moving xoops_lib and xoops_data

Re: Renaming and moving xoops_lib and xoops_data

Re: Renaming and moving xoops_lib and xoops_data

Login

Search

Recent Posts

Re: Privacy

Privacy

XOOPS MyMenus 1.54.0 Beta 10

Re: XOOPS MyMenus 1.54.0 Beta 7

Re: XOOPS MyMenus 1.54.0 Beta 7

Re: XOOPS MyMenus 1.54.0 Beta 7

Re: XOOPS MyMenus 1.54.0 Beta 7

Re: XOOPS MyMenus 1.54.0 Beta 7

Re: XOOPS MyMenus 1.54.0 Beta 7

Re: XOOPS MyMenus 1.54.0 Beta 7

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}