PEAK XOOPS - Protector 3.34 gives problems in englishin japanese

Protector 3.34 gives problems

  • You cannot open a new topic into this forum
  • Guests cannot post into this forum
Previous post - Next post | Parent - Children.1 .2 .3 .4 .5 .6 | Posted on 2009/8/5 17:40
DonCurioso  企霹始   Posts: 5
Hi,

I have this config in one of my sites:

Version XOOPS - XOOPS 2.3.3
Version PHP - 5.2.6
Version MySQL - 5.0.81-community
Version Server API - apache2handler
Version OS - Linux
Version Protector - 3.34
safe_mode - Off
register_globals - Off
magic_quotes_gpc - On
allow_url_fopen - Off
fsockopen - On
allow_call_time_pass_reference - On

Of course, i have my lib&data folders out of root.
I can
Votes:9 Average:10.00
Previous post - Next post | Parent - No child | Posted on 2009/8/7 17:33 | Last modified
onasre  惧霹始   Posts: 38
i had the same error , with my old Hosting , i used to get the error 500 but after clik refresh the error disaperaed. i do know exactly wht cuz it but Now i'm with new hosting and i dont have the error anymore..

if you updating protector from 2.3.3 try remove all old files and upload fresh .. it might help if you try first on local machine and see if u get the error.

Good luck
Votes:11 Average:10.00
Previous post - Next post | Parent - No child | Posted on 2009/8/7 19:51
DonCurioso  企霹始   Posts: 5
onasre,

thanks for reply. I have more xoopsites with same hosting & none of them have got this problem...

I did a fresh upload & doesn
Votes:11 Average:10.00
Previous post - Next post | Parent - Children.1 | Posted on 2009/8/8 4:35
onasre  惧霹始   Posts: 38
For Sure you Not the first One that Happend to him . Like i said it did happen to me , and i used to solve it by click refresh to the page .... and By the way i used to Embty the Session Tabel too .. Just do wht i do if you get the 500 error again just click refresh or f5 and see wht happens.
Votes:10 Average:9.00
Previous post - Next post | Parent - Children.1 | Posted on 2009/8/11 2:16 | Last modified
DonCurioso  企霹始   Posts: 5
onasre,

you can kick me because i caused the error 500.

A .htacess archive was uploaded into modules folder & causes this error. I remove from it& works fine again. Maybe i did double-click over it or move from root & no idea about it. Today, when i was update other module, i see this file... i think: "strange... what are this file doing here?". Of course, Protector 3.34 it
Votes:10 Average:10.00
Previous post - Next post | Parent - No child | Posted on 2009/8/11 10:54
onasre  惧霹始   Posts: 38
i dont know if you Mean the htaccess that inside the protector trusted Folder or not ..

because there htaccess file at the trusted folder been placed for security reasons and u shouldt remove it.
Votes:15 Average:7.33
Previous post - Next post | Parent - No child | Posted on 2009/8/13 12:53
GIJOE  黎扦烦菱   Posts: 4110
Onasre is right.

The file xoops_trust_path/.htaccess never harm your site like 500 errors.

Perhaps, you've confused the paths between XOOPS_ROOT_PATH and XOOPS_TRUST_PATH.
Votes:11 Average:9.09
Previous post - Next post | Parent - No child | Posted on 2009/8/15 3:06 | Last modified
DonCurioso  企霹始   Posts: 5
hi,

both didn't read me

Quote:
A .htacess archive was uploaded into modules folder & causes this error.

I never wrote other like modules folder

It was a mistake. Maybe i did double click over .htaccess on my computer on Filezilla & it upload it to modules folder, that's all

Regards & don't worry
Votes:11 Average:9.09
Previous post - Next post | Parent - No child | Posted on 2010/6/25 16:02
larryp7639  企霹始   Posts: 1
Quote:

onasre wrotes:
For Sure you Not the first One that Happend to him . Like i said it did happen to me , and i used to solve it by click refresh to the page .... and By the way i used to Embty the Session Tabel too .. Just do wht i do if you get the 500 error again just click refresh or f5 and see wht happens.

Thanks you for the post.

__________________
Watch Grown Ups Online Free
Votes:6 Average:10.00

  Advanced search


Login
Username or e-mail:

Password:

Remember Me

Lost Password?

Register now!