6402
Quote:
Glad that it's working now!
Quote:
We use CBB here, which is the best for us. Some people use newbbx. There is also X-Forum
Test it and see what's best for your needs.
ya it was the xoops_data/caches
Glad that it's working now!
Quote:
What forum is XOOPS using that it has it featured on the front page? also what are the better forums in general?
We use CBB here, which is the best for us. Some people use newbbx. There is also X-Forum
Test it and see what's best for your needs.
6405
My guess is that if the only files changed by Dugris' hack were Core files, that would be overwritten by the 2.3 files, then it shouldn't be a problem.
However, if you modified any other files (e.g. modules), that depend on Dugris' hack, then it could be a problem. You would probably have to reinstall the modules in their original form.
However, if you modified any other files (e.g. modules), that depend on Dugris' hack, then it could be a problem. You would probably have to reinstall the modules in their original form.
6407
Quote:
Somehow you're ending with two times /xoops_data
It should be only once, but I don't have an answer now why is it happening.
Error: Smarty error: the $compile_dir '/xoops_data/xoops_data/caches/smarty_compile' does not exist, or is not a directory.
Somehow you're ending with two times /xoops_data
It should be only once, but I don't have an answer now why is it happening.
6408
Quote:
This could be exactly the problem. The XOOPS_VAR_PATH should NOT point to your XOOPS directory, but to /xoops_data directory.
Assuming that your physical location of XOOPS is at /home/xoops, The correct paths should be in your mainfile.php defined as:
Quote:
Please note: the paths in green, can be changed for security purposes to other location outside of your XOOPS path (if your server allows that). But at least you should change the names of your subdirectories, which are in orange
Example:
Quote:
XOOPS 2.3 gives you more flexibility in making XOOPS more secure. For more info about security in 2.3, read this tutorial
My path appeared to be right. It was pointing to my XOOPS directory.
This could be exactly the problem. The XOOPS_VAR_PATH should NOT point to your XOOPS directory, but to /xoops_data directory.
Assuming that your physical location of XOOPS is at /home/xoops, The correct paths should be in your mainfile.php defined as:
Quote:
// Physical path to the XOOPS documents (served) directory WITHOUT trailing slash
define( 'XOOPS_ROOT_PATH', '/home/xoops' );
// Physical path to the XOOPS library directory WITHOUT trailing slash
define( 'XOOPS_PATH', '/home/xoops/xoops_lib' );
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash
define( 'XOOPS_VAR_PATH', '/home/xoops/xoops_data' );
// Alias of XOOPS_PATH, for compatibility, temporary solution
define("XOOPS_TRUST_PATH", XOOPS_PATH);
Please note: the paths in green, can be changed for security purposes to other location outside of your XOOPS path (if your server allows that). But at least you should change the names of your subdirectories, which are in orange
Example:
Quote:
define( 'XOOPS_PATH', '/home/myvault/xoopsROCKS_895lib' );
XOOPS 2.3 gives you more flexibility in making XOOPS more secure. For more info about security in 2.3, read this tutorial
6409
Welcome to XOOPS! 
XOOPS doesn't ship with modules, because of the problems with overwriting existing modules on users Website, if they use customized versions with hacks. Plus some users don't want to download huge files.
Try the Module Packs
And don't hesitate to ask, if you need help.
XOOPS doesn't ship with modules, because of the problems with overwriting existing modules on users Website, if they use customized versions with hacks. Plus some users don't want to download huge files.
Try the Module Packs
And don't hesitate to ask, if you need help.
6410
Quote:
Could the users who had the original problems check in their mainfile.php, if they had the correct definition of "XOOPS_VAR_PATH"?
As restrada said, there should be a relative path in the mainfile.php, and you shouldn't have to use a "hard coded path" in the template.php
The correct fix is to define in mainfile.php the path to the data files:
define("XOOPS_VAR_PATH", "path");
Could the users who had the original problems check in their mainfile.php, if they had the correct definition of "XOOPS_VAR_PATH"?
As restrada said, there should be a relative path in the mainfile.php, and you shouldn't have to use a "hard coded path" in the template.php
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 |
 |
|