GIJOE:
It would be great if there were some kind of patch files for people upgrading from previous versions. It is not a big task un-installing and re-installing, but a patch would definitely help in upgrading the module. Thanks.
tl

hi tl.

It is not necessary to uninstall and reinstall Protector.

Just update the module via module manager in system admin after overwriting /modules/protector/.

That's all.

Thanks, GIJOE.
I tried the upgrade on one of my sites by uploading the files directly over the exisiting files and I ended up with duplicated blocks after having updated the modules. I believe the reason is that I hadn't upgrade Xoops to 2.0.9.2. In the end, I had to go through the whole routine again, uninstall and reinstall.

hi tl.

As you know, 2.0.9 & 2.0.9.1 has a bug in modulesadmin.

I heard from onokazu that the unfortunately duplicated blocks are eliminated by overwriting these recent files int 2.0.10-CVS.

class/xoopsblock.php
http://cvs.sourceforge.net/viewcvs.py/*checkout*/xoops/xoops2/class/xoopsblock.php?rev=1.19.20.2

/modules/system/admin/blocksadmin/blocksadmin.php
http://cvs.sourceforge.net/viewcvs.py/*checkout*/xoops/xoops2/modules/system/admin/blocksadmin/bl...

a problem find while i upgrade protector to 2.21

"Notice: Undefined index: REQUEST_URI in g:\inetpub\wwwroot\modules\protector\class\protector.php on line 451 "

plateform: Xoops 2.092

Please help ^^ thx

Do you use IIS?

Anyway, I've fixed the IIS specific problem in Protector 2.22.

Hi GIJOE

In my site is Protetor version 2.1, question...
is Necessary update for version 2.2 ?

My xoops is 2.0.7.3 ok ?

Giba
www.xoopstotal.com.br

hi Giba.

Protector 2.1 is not enough.
Another holes of the core was found since 2.1 released.

Upgrading Protector is quite easy.
Update the module after overwriting it.

If you feel difficult "overwrite", newly uploading after entirely deleting modules/protector/ is ok.

Quote:
Yes, I look in xoops.org...

Quote:
Ok Thanks

Problem Fixed. ^3^/

Thanks.