11
LucaNet
Re: Protector 3.02 question
  • 2007/4/19 10:57

  • LucaNet

  • Friend of XOOPS

  • Posts: 90

  • Since: 2006/5/25


Hi folks,

I don't understand how to upgrade from 3.x version.

Should I do a fresh install?

12
Ronaldus
Re: Protector 3.02 question
  • 2007/4/19 11:01

  • Ronaldus

  • Friend of XOOPS

  • Posts: 389

  • Since: 2004/5/8 1


If I read the doc, that should not be a problem. Just uninstall and delete, and upload the new version.

But I'm no expert
(see above.... )

Grtz,

13
MadFish
Re: Protector 3.02 question
  • 2007/4/19 11:03

  • MadFish

  • Friend of XOOPS

  • Posts: 1056

  • Since: 2003/9/27


You might as well do a fresh install. Note that you will need to adjust the pre/post check lines in your mainfile. They are a bit different in the new module (just replace them!).

14
LucaNet
Re: Protector 3.02 question
  • 2007/4/19 11:12

  • LucaNet

  • Friend of XOOPS

  • Posts: 90

  • Since: 2006/5/25


OK, I'll do a fresh install.

Thanks a lot for your replies

15
goodwrench1
Re: Protector 3.02 question

I just upgraded from 3.01 to 3.02 and I simply FTP'd the files (overwrote) in the respective folders, then went to the modules page and performed an upgrade. Everything seemed to work out.

16
Anonymous
Re: Protector 3.02 question
  • 2007/4/22 7:09

  • Anonymous

  • Posts: 0

  • Since:


Quote:
goodwrench1 wrote:

I just upgraded from 3.01 to 3.02 and I simply FTP'd the files (overwrote) in the respective folders, then went to the modules page and performed an upgrade. Everything seemed to work out.


A slight variation for me.......

For a v3.0x to v3.0x upgrade I delete the existing files and upload the new ones before updating the module in admin.

I do the "delete and upload" rather than "overwrite" procedure because I read somewhere that are being gradually moved from the "website path" to the "trust path" and I don't want any duplication. I could be wrong about this, though

[Ronaldus: Check your email from about 10mins after this post. Sorry for the delay.]

17
Dave_L
Re: Protector 3.02 question
  • 2007/4/22 9:57

  • Dave_L

  • XOOPS is my life!

  • Posts: 2277

  • Since: 2003/11/7


Quote:
JAVesey wrote:

I do the "delete and upload" rather than "overwrite" procedure because I read somewhere that are being gradually moved from the "website path" to the "trust path" and I don't want any duplication.


That's a good point.

A lot of files were removed from the web document tree in Protector 3.

One potential security vulnerability in web applications is the presence of old or unneeded files, which could have uncorrected security issues or could otherwise be exploited by abusers.

18
Ronaldus
Re: Protector 3.02 question
  • 2007/4/22 18:04

  • Ronaldus

  • Friend of XOOPS

  • Posts: 389

  • Since: 2004/5/8 1


I guess you're right Dave_L, but isn't this something module developers should include in the update procedure:

1) instructions to delete certain/all files
2) a delete schript in the update procedure (if possible at all...)

But sure something I'll try to remember.

Cheers,

19
omyasuda
Re: Protector 3.02 question
  • 2007/4/22 18:09

  • omyasuda

  • Just popping in

  • Posts: 3

  • Since: 2004/10/5


Thank you for the link.

20
davidl2
Re: Protector 3.02 question
  • 2007/4/22 21:01

  • davidl2

  • XOOPS is my life!

  • Posts: 4843

  • Since: 2003/5/26


Quote:

Dave_L wrote:
One potential security vulnerability in web applications is the presence of old or unneeded files, which could have uncorrected security issues or could otherwise be exploited by abusers.


This is a very good point that would be worth all module devs including...

Login

Who's Online

57 user(s) are online (46 user(s) are browsing Support Forums)


Members: 0


Guests: 57


more...

Donat-O-Meter

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

Latest GitHub Commits