31
peterr
Re: Protector 3.0
  • 2007/4/12 9:04

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Quote:

MadFish wrote:
If you extract the files out of the archive you should find the config directory somewhere down around xoops_trust_path/modules/protector etc. If it isn't there, then you have a dud download, grab it again.


For Protector version 3.02 , neither the ZIP or the TAR.GZ files have a folder called 'config'.

I downloaded it again though, there are 4 more files, since 2 days ago, but they are 4 additions for the Russian language.

Message 1.1 on the Peak forums, from GIJOE says to remove the 'configs" folder, so the readme doesn't line up with the version 3.02 maybe ??

Possibly earlier versions had this path called 'configs' ??
NO to the Microsoft Office format as an ISO standard.
Sign the petition

32
irmtfan
Re: Protector 3.0
  • 2007/4/12 9:13

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


its not 'config' but 'configs' located in XOOPS_TRUST_path/modules/protector/configs

33
peterr
Re: Protector 3.0
  • 2007/4/12 9:16

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Quote:

irmtfan wrote:
its not 'config' but 'configs' located in XOOPS_TRUST_path/modules/protector/configs


Unless there is something strange happening with me downloading the module, it just isn't there, in the archive for version 3.02.
NO to the Microsoft Office format as an ISO standard.
Sign the petition

34
irmtfan
Re: Protector 3.0
  • 2007/4/12 9:34

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


its a blank directory so you can create it yourself but i just worried about missing other important files in your downloaded zip

35
peterr
Re: Protector 3.0
  • 2007/4/12 9:54

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Solved the mystery, the archiver I use is Powerachiver, and there are different 'views'. The view I use is 'classic style' which shows the full path name, but doesn't show any paths that have no files in them.

I changed the view to 'explorer' mode, and could see 3 empty paths

* /blocks
* /configs
* /filters_enabled

I'll add those 3 to the website and then update the module.

Thanks !!
NO to the Microsoft Office format as an ISO standard.
Sign the petition

36
MadFish
Re: Protector 3.02 - documentation available
  • 2007/4/13 7:30

  • MadFish

  • Friend of XOOPS

  • Posts: 1056

  • Since: 2003/9/27


Documentation for is now available:

Protector 3.02 - PDF
Protector 3.02 - Open document format
Protector 3.02 - Microsoft Word

If anyone spots any mistakes be sure to let me know. It is complete, but I guess you can call this a 'final draft for public comment'.

If no substantial changes I will send to GIJOE and Rowd for posting on the official docs site tonight (sorry I'm having incredibly bad luck with computers and internet connections at the moment).

37
Anonymous
Re: Protector 3.02 - documentation available
  • 2007/4/13 8:08

  • Anonymous

  • Posts: 0

  • Since:


Great documentation - good job and very helpful

As an aside, I'm running v3.01a. Am I right in thinking that the upgrade to v3.02 is nothing more than a "file upload followed by module update in admin" procedure?

38
xgarb
Re: Protector 3.02 - documentation available
  • 2007/4/22 18:45

  • xgarb

  • Not too shy to talk

  • Posts: 154

  • Since: 2003/3/30


Thanks for that, very useful docs..

Also thanks go to GI for an essential module.

39
vwood
Re: Protector 3.0
  • 2008/5/26 18:52

  • vwood

  • Just popping in

  • Posts: 5

  • Since: 2006/10/25


I had difficulty installing Protector using the instructions at
https://xoops.org/modules/newbb/viewtopic.php?post_id=254269#forumpost254269

I think that what I've done is a close match to the explanation at
https://xoops.org/modules/newbb/viewtopic.php?post_id=252705#forumpost252705


I now have a trust path above the web site path. The trust path had nothing in it but the modules folder (with the protector module folder) from the xoops_trust_path (/xoops_root_path folder didn't exist in the download) in the protector download. And the protector folder under html\modules was copied to the XOOPS modules folder. I added a trust path definition to mainfile.php as described
define('XOOPS_TRUST_PATH', '/home/www/xxxxxxxxx');

But when I went to install the module, the first clue something was wrong was that the Protector module had a blank name (but had the version correct: 3.17). My second clue was when it said it "Unable to install . Error(s): Module already exists". My final verification that something is wrong that XOOPS Info shows protector module with a red light.


I've set the configs path to 777 (was 755), same behavior.

40
peterr
Re: Protector 3.0
  • 2008/5/27 5:15

  • peterr

  • Just can't stay away

  • Posts: 518

  • Since: 2004/8/5 9


Quote:

vwood wrote:
I had difficulty installing Protector using the instructions at
https://xoops.org/modules/newbb/viewtopic.php?post_id=254269#forumpost254269


If you follow the documentation from done by "MadFish", then you won't have any problems..

PDF version
Open document version
Word version

Quote:

vwood wrote:
I now have a trust path above the web site path.


The trust path should be outside the web root path. If your definition for it is ..

define('XOOPS_TRUST_PATH''/home/www/xxxxxxxxx');


then it should be something like ..

define('XOOPS_TRUST_PATH''/home/username/xxxxxxxxx');


HTH
NO to the Microsoft Office format as an ISO standard.
Sign the petition

Login

Who's Online

141 user(s) are online (94 user(s) are browsing Support Forums)


Members: 0


Guests: 141


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits