1
Quest
Xoops 2.3.3 xoops_data and xoops_lib
  • 2009/8/19 13:14

  • Quest

  • Friend of XOOPS

  • Posts: 1034

  • Since: 2005/11/19


For sanity sakes could you tell me what purpose these two files serve and how they are relevant to the installation if I have renamed them and moved them from the xoops_root as instructed. I presume they are a viable part of the installation but how does the installation find them if I have renamed and moved them???

DOH! NEVER MIND. Thanks

2
sailjapan
Re: Xoops 2.3.3 xoops_data and xoops_lib

These two directories store files that could be exploited by someone who cared to wreck your site. By moving them out of root, you are making it more difficult for anyone inclined to mess with your site.
The instructions in the read-me are fairly clear about how to make sure XOOPS can still find them once they have been moved (hint: XOOPS_TRUST_PATH defined in mainfile.php). There's a good explanation (translated) here.

3
stgeorge
Re: Xoops 2.3.3 xoops_data and xoops_lib
  • 2009/8/23 14:11

  • stgeorge

  • Just popping in

  • Posts: 13

  • Since: 2009/7/21


I would like to know if moving them to another directory in XOOPS installation root, i.e. domain root/xoops installation directory (root)/folder for data & lib/xoops_data & xoops_lib

The reason I ask is that I still get a warning that these folders should be moved even though I have a new directory and also have renamed the xoops_data & lib directories.

The installation was working as above, however when I tried to move the folders into domain root below the XOOPS installation directory and altered mainfile.php I got white screened and could not access admin.
The site was up though.

Why should I have got a warning when I have done the aforesaid renaming and creating a new directory?

Tried to reverse the process now my whole installation is messed up.

Cannot get to admin.

4
tititou36
Re: Xoops 2.3.3 xoops_data and xoops_lib
  • 2009/8/24 11:40

  • tititou36

  • Just popping in

  • Posts: 16

  • Since: 2009/8/15


Moving outside the XOOPS directory is not enough.
Xoops performs also a test to see if the 2 directories are readable under the DocumentRoot from apache.

So they should be placed outside XOOPS root AND outside Apache htdocs and sub folders.

In fact, the main idea is : these directories should not be visible from the user, where ever they are.


To have your site work again, you only have, IMO, to have mainfile.php point to the right directories.

Could you post here your mainfile.php in order to see if you missed something when you "messed up" your installation ?

5
Mamba
Re: Xoops 2.3.3 xoops_data and xoops_lib
  • 2009/8/24 11:44

  • Mamba

  • Moderator

  • Posts: 11409

  • Since: 2004/4/23


But if you post your mainfile here, please remove any info that could be used by hackers to gain entry to your Website.

6
rayisms
Re: Xoops 2.3.3 xoops_data and xoops_lib
  • 2009/8/24 18:31

  • rayisms

  • Just popping in

  • Posts: 2

  • Since: 2009/8/24


Greetings and thanks for any help in advance,

I have changed the paths in mainfile, now I get this error!
""Error: Smarty error: the $compile_dir '/home/content/dog/xoops_MYSITE/xoops_data/caches/smarty_compile' does not exist, or is not a directory.""
The directory is there and has the right CHMOD.
below is the path section of mainfile..
=========================================================
// XOOPS Physical Paths

// Physical path to the XOOPS documents (served) directory WITHOUT trailing slash
define( 'XOOPS_ROOT_PATH', '/home/content/dog/html/ro/xoops' );

// For forward compatibility
// Physical path to the XOOPS library directory WITHOUT trailing slash
define( 'XOOPS_PATH', '/home/content/dog/xoops_ro/xoops_lib' );
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash
define( 'XOOPS_VAR_PATH', '/home/content/dog/xoops_ro/xoops_data' );
// Alias of XOOPS_PATH, for compatibility, temporary solution
define("XOOPS_TRUST_PATH", '/home/content/dog/xoops_ro/XOOPS-TRUST-PATH');

// XOOPS Virtual Path (URL)
// Virtual path to your main XOOPS directory WITHOUT trailing slash
// Example: define( 'XOOPS_URL', 'http://xoops.rockthepipe.com' );
define( 'XOOPS_URL', 'http://xoops.rockthepipe.com' );

7
rayisms
Re: Xoops 2.3.3 xoops_data and xoops_lib
  • 2009/8/24 18:43

  • rayisms

  • Just popping in

  • Posts: 2

  • Since: 2009/8/24




My bad,
I must allways check my speelling..

best regards
rayisms

8
tititou36
Re: Xoops 2.3.3 xoops_data and xoops_lib
  • 2009/8/24 19:48

  • tititou36

  • Just popping in

  • Posts: 16

  • Since: 2009/8/15


This means, your issue is solved ?

Login

Who's Online

213 user(s) are online (143 user(s) are browsing Support Forums)


Members: 0


Guests: 213


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits