6172
Quote:
Yes, it is a little bit confusing, so let me explain differently.
And let's forget about XOOPS_TRUST_PATH for right now.
"xoops_lib" and "xoops_data" are directories, which are locations for "XOOPS_PATH" and "XOOPS_VAR_PATH" respectively, and they should be located outside of your "DocumentRoot", which in your case is C:/Program Files/xampp/htdocs/testing'.
You mainfile.php should be:
Quote:
Some modules, especially D3 modules developed by GIJOE, use the variable "XOOPS_TRUST_PATH". In order to make sure that they work, you point "XOOPS_TRUST_PATH" to "XOOPS_PATH":
Quote:
which then points to C:/Program Files/xampp/xoops_lib.
As you can see, "XOOPS_TRUST_PATH" and "XOOPS_PATH" are pointers to the same directory.
Please note: it's always good to change the name of the directory "xoops_lib" and "xoops_data", to something random. So if you change it to "20090128lib" and "01282009data", your mainfile.php would look like this:
Quote:
Hope it helps a little...
this is confusing i thought xoops_lib = xoops_trust_path
Yes, it is a little bit confusing, so let me explain differently.
And let's forget about XOOPS_TRUST_PATH for right now.
"xoops_lib" and "xoops_data" are directories, which are locations for "XOOPS_PATH" and "XOOPS_VAR_PATH" respectively, and they should be located outside of your "DocumentRoot", which in your case is C:/Program Files/xampp/htdocs/testing'.
You mainfile.php should be:
Quote:
// Physical path to the XOOPS documents (served) directory WITHOUT trailing slash
define( 'XOOPS_ROOT_PATH', 'C:/Program Files/xampp/htdocs/testing' );
// For forward compatibility
// Physical path to the XOOPS library directory WITHOUT trailing slash
define( 'XOOPS_PATH', 'C:/Program Files/xampp/xoops_lib' );
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash
define( 'XOOPS_VAR_PATH', 'C:/Program Files/xampp/xoops_data' );
// Alias of XOOPS_PATH, for compatibility, temporary solution
define("XOOPS_TRUST_PATH", XOOPS_PATH);
Some modules, especially D3 modules developed by GIJOE, use the variable "XOOPS_TRUST_PATH". In order to make sure that they work, you point "XOOPS_TRUST_PATH" to "XOOPS_PATH":
Quote:
define("XOOPS_TRUST_PATH", XOOPS_PATH);
which then points to C:/Program Files/xampp/xoops_lib.
As you can see, "XOOPS_TRUST_PATH" and "XOOPS_PATH" are pointers to the same directory.
Please note: it's always good to change the name of the directory "xoops_lib" and "xoops_data", to something random. So if you change it to "20090128lib" and "01282009data", your mainfile.php would look like this:
Quote:
// Physical path to the XOOPS documents (served) directory WITHOUT trailing slash
define( 'XOOPS_ROOT_PATH', 'C:/Program Files/xampp/htdocs/testing' );
// For forward compatibility
// Physical path to the XOOPS library directory WITHOUT trailing slash
define( 'XOOPS_PATH', 'C:/Program Files/xampp/20090128lib' );
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash
define( 'XOOPS_VAR_PATH', 'C:/Program Files/xampp/01282009data' );
// Alias of XOOPS_PATH, for compatibility, temporary solution
define("XOOPS_TRUST_PATH", XOOPS_PATH);
Hope it helps a little...
6173
For a starter, you should read this article: A Guide to Make your XOOPS Installation even more secure
You should invest some time and update your XOOPS Version to 2.3.2b, or if you're not in hurry, wait for the 2.3.3 that should be released soon as RC1 (Release Candidate 1). You might also update the modules, if they have a newer version (e.g. Forum could be updated to CBB 3.08)
Protector is a must! But you should install the new version 3.32
But make sure that you understand how the hacker got into your system, so you can fix it. For example, check if there are new users with Webmaster privileges, and delete them.
You should invest some time and update your XOOPS Version to 2.3.2b, or if you're not in hurry, wait for the 2.3.3 that should be released soon as RC1 (Release Candidate 1). You might also update the modules, if they have a newer version (e.g. Forum could be updated to CBB 3.08)
Protector is a must! But you should install the new version 3.32
But make sure that you understand how the hacker got into your system, so you can fix it. For example, check if there are new users with Webmaster privileges, and delete them.
6176
Quote:
I use it, and didn't have any problems with installing XOOPS. Actually, this is a preferred setup for me, because I can test XOOPS under different versions of PHP and MySQL with a simple right-click switch
I tried WAMPserver 2.0f. But I failed to add smarty support to wamp 2.
I use it, and didn't have any problems with installing XOOPS. Actually, this is a preferred setup for me, because I can test XOOPS under different versions of PHP and MySQL with a simple right-click switch
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|