12
Hi,
I am very annoyed by some forumers who used CAPS throughout the forum title.
Is there a hack where I can force it to be uppercase letters to lowercase?
I am very annoyed by some forumers who used CAPS throughout the forum title.
Is there a hack where I can force it to be uppercase letters to lowercase?
14
still unable to login to admin with protector.
i download XOOPS full package and replace the necessary files. checksum verified all the files are correct.
can XOOPS 2.4.3 run without protector? if so, can i remove protector clean from the site? and make a fresh install of protector?
how do i do that?
i download XOOPS full package and replace the necessary files. checksum verified all the files are correct.
can XOOPS 2.4.3 run without protector? if so, can i remove protector clean from the site? and make a fresh install of protector?
how do i do that?
15
already had the trusted path defined in mainfile.php.
now i can access the admin with the protector turned on.
but the module pages in admin still turn out weird and protector is no where to be seen.
I think i willl try to reinstall the upgrade.
Can i delete the stuff in the xoops_cache, smarty_complile and smart_cache? in the trusted path?
I see alot of forum uploads files from inside XOOPS cache. are those just cache files?
now i can access the admin with the protector turned on.
but the module pages in admin still turn out weird and protector is no where to be seen.
I think i willl try to reinstall the upgrade.
Can i delete the stuff in the xoops_cache, smarty_complile and smart_cache? in the trusted path?
I see alot of forum uploads files from inside XOOPS cache. are those just cache files?
16
i redo my mainfile.php by using the mainfile.dist.php from 2.4.3 but still doesn't work either.
// Physical path to the XOOPS documents (served) directory WITHOUT trailing slash
define("XOOPS_ROOT_PATH", "/home/xxx/domains/xxxdomain.com/public_html");
// For forward compatibility
// Physical path to the XOOPS library directory WITHOUT trailing slash
define("XOOPS_PATH", "/home/xxx/domains/xxxdomain/xoops_lib");
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash
define("XOOPS_VAR_PATH", "/home/xxx/domains/xxxdomain/xoops_data");
what else can i do?
// Physical path to the XOOPS documents (served) directory WITHOUT trailing slash
define("XOOPS_ROOT_PATH", "/home/xxx/domains/xxxdomain.com/public_html");
// For forward compatibility
// Physical path to the XOOPS library directory WITHOUT trailing slash
define("XOOPS_PATH", "/home/xxx/domains/xxxdomain/xoops_lib");
// Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash
define("XOOPS_VAR_PATH", "/home/xxx/domains/xxxdomain/xoops_data");
what else can i do?
18
i still can't get into admin when enabled the protector from the database.
any pointers on what i should do now?
any pointers on what i should do now?
19
after all the upgrade which i was notified successful,
tried login to the site it was all ok.
but when login to the admin.php.
the site went blank.
tried to troubleshoot, I disable the protector module through the database directly and it then I can login to my admin.
and I can't see the protector module at all from my admin. it also gives a weird and uncompleted load looks of the admin when I load the admin page like the image below
what do I do now? how should I uninstall / reinstall a installed protector which is not visible from the admin?
*update* after some module update.
i enabled the protector from the database again. and tried to login to admin.php. it showed
"Registry not found"
just extra information. i have 2 protector folder. one in the module section and another one in the trusted path side. is that correct?
Other Question:
do i need to include these 2 lines back into mainfile.php after the upgrade ?
include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php' ;
include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php' ;
tried login to the site it was all ok.
but when login to the admin.php.
the site went blank.
tried to troubleshoot, I disable the protector module through the database directly and it then I can login to my admin.
and I can't see the protector module at all from my admin. it also gives a weird and uncompleted load looks of the admin when I load the admin page like the image below
what do I do now? how should I uninstall / reinstall a installed protector which is not visible from the admin?
*update* after some module update.
i enabled the protector from the database again. and tried to login to admin.php. it showed
"Registry not found"
just extra information. i have 2 protector folder. one in the module section and another one in the trusted path side. is that correct?
Other Question:
do i need to include these 2 lines back into mainfile.php after the upgrade ?
include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php' ;
include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php' ;
20
this could be integrated into the user account where the username can be click and msg instantly !
need to start learning php and sql now.
need to start learning php and sql now.
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 |
 |
|