PEAK XOOPS - Protector block in 2.40 
Protector block in 2.40
- You cannot open a new topic into this forum
- Guests cannot post into this forum
Previous post
-
Next post
|
Parent
-
Children.1
|
Posted on 2005/4/3 13:50
Dave_L
From: Virginia, USA
Posts: 35
From: Virginia, USA
Posts: 35
After upgrading from 2.38 to 2.40, the Protector block is still in the database, and shows up on the Blocks Management page, although I guess it's not really used.
What's the best way of getting rid of that block?
What's the best way of getting rid of that block?
Votes:0
Average:0.00
GIJOE
Posts: 4110
Posts: 4110
hi Dave.
I'll check it.
Perhaps, I will make some codes to delete the record from newblocks table on update.
I'll check it.
Perhaps, I will make some codes to delete the record from newblocks table on update.
Votes:2
Average:5.00
Dave_L
From: Virginia, USA
Posts: 35
From: Virginia, USA
Posts: 35
Thanks, the block was deleted correctly in 2.40RC2.
A minor documentation issue - the module description still refers to the block:
language/-/modinfo.php
define("_MI_PROTECTOR_DESC","This module protects your xoops site from various attacks like DoS , SQL Injection , and Variables contaminations.<br />\nYou should put this block in top of left blocks and edit all groups can access this block.");
A minor documentation issue - the module description still refers to the block:
language/-/modinfo.php
define("_MI_PROTECTOR_DESC","This module protects your xoops site from various attacks like DoS , SQL Injection , and Variables contaminations.<br />\nYou should put this block in top of left blocks and edit all groups can access this block.");
Votes:0
Average:0.00
Previous post
-
Next post
|
Parent
-
No child
|
Posted on 2005/4/11 18:48
GIJOE
Posts: 4110
Posts: 4110
hi Dave.
Thank you for the suggestion.
I'll fix it.
-------------
There are non-sense language files in 2.4 ...
Thank you for the suggestion.
I'll fix it.
-------------
There are non-sense language files in 2.4 ...
Votes:0
Average:0.00
Login