Wedge
Public area => Bug reports => The Pub => Archived fixes => Topic started by: havok on January 29th, 2014, 09:31 AM
-
i was just playing around with the settings and when iclick on forum profile it results in internal server error
-
You should give more info.. webserver, php version, environment (local, win, unix)...
-
Yup, because this is exactly the kind of bug that would be found out immediately if it was reproducible everywhere...
-
You should give more info.. webserver, php version, environment (local, win, unix)...
i couldnt log in to reply earlier, i was on night shift and the IT dept has only ugraded pcs to ie7, you cant access most sites, on that.
webhosting on go daddy, running php5.5, windows environment
-
I had a similar error when playing with the "pretty urls", then went back un check them and all was good, May need to investigate more on this..
Not sure if this is the same but may want check those settings?
regards,
Masx
-
Most errors 500 are triggered by a problem with the htaccess file. Most of the file is devoted to making Pretty URLs work everywhere.
So, well... It's unlikely, but possible.
-
i have disabled pretty urls but i am still getting the 500 error as admin and as guest as well.
wedge is installed in a folder and not in a subdomain i do not know if that makes a difference. i have tried googling for the solution and i am stumped.
webhosting o, running php5.5, windows environment errors with ie11 and firefox 26
-
And I suppose your error log is empty...?
Anyway, it's midnight here, meaning I'm off duty! :P
-
yes the error log is empty.
-
Have you tried to purge the cache?
-
Which is the Wedge equivalent of, "Have you tried turning off and on again..?" :geek:
-
i have just tried purging the cache and i am still getting the same error.
-
yeah solved, i am not sure if this would have caused it
go daddyPHP 5.3 is our default version. PHP version 5.4 is available and meets our stability and security requirements. Version 5.2 isn’t actively supported
i changed it to php 5.4 as it was set at 5.3 and it worked.
-
lol....
Well, good to know! Means it was a config error...
Would love to be able to play with your 5.3 install!