A user said his original post didn't work - and it doesn't.
He subsequently created a second new post which worked fine.
Nobody can actually access the post - most get a http500 error, while some just get a blank page.
If you go the section (General / Bike Chat), http://gsx1400owners.org/forum/index.php?board=19.0
then click on the post Oil Pan re assembly by Red Biker
http://gsx1400owners.org/forum/index.php?topic=2269.0
it generates the error (as you can tell yourselves, and I've attached copy below)
Thoughts?
Check your forum's error log to see if anything is there if not. Then check your webservers error log
if no forum error then these tend to be critical PHP errors; i write them out to a seperate log.
if you can't find either then review your php.ini error reporting settings, make the changes, restart your webserver and reproduce it.
Quotethese tend to be critical PHP errors; i write them out to a seperate log.
how?
Quote
review your php.ini error reporting settings, make the changes, restart your webserver and reproduce it.
Not sure what you mean by restart my webserver?
Sorry but this is not clear to me (my fault, not yours)
your environment may be different from mine.
Your webserver will load PHP when it starts and it reads in a config file (php.ini) and you have to read it to understand it.
SMF uses this API to build the pages that are displayed in your browser.
don't worry about a seperate log file, just review your error capturing options and know how to access log data.
i run a VPS and don't know about other hosted environments so bear with me.
whenever i make changes to php.ini, after reSEARCHing the various options (there is no more abundant information than that of computer related data on the internet), i then restart Apache. You may use another form of webserving software.
As you know, SMF is written in PHP (the Hypertext PreProcessor) so it is quite important to know how PHP is handling certain types of errors.
I don't want to get caught up in the fundamentals but understanding the role of PHP is paramount when dealing with such errors.
Good luck, persistence always pays off.
install https://custom.simplemachines.org/mods/index.php?mod=4111 and you should be able to view that topic/post again.
Illori - I already have that installed.
aegersz - ta, sounds daunting but I'll have a look.
in the users profile under show posts -> attachments does it list an attachment for that topic?
A HTTP 500 error should always leave an entry in the server error log, and you should have access to it through your hosting control panel. Can you check to see what the entry in there says exactly?
usually it creates a fille called error.log errorlog. or some variation of that...
Don't worry about what aegersz said... he tends to getoverly complicated when things are actually pretty simple. :P
wait, isnt this www.overly-compilcated-and-overly-longwinded-machines.org ?
whoops, i got it wrong.
POINT TAKEN ! sorry for any discouragement - i'm only trying to help ::)
Help is good. :) What I think was Kindred's point, was that it's often best to start out with the simple and obvious things. Like errorlogs. ;)
Sorry been offline - will def have a look in next day or so, thanks.
try to scan the server logs for the 'fatal' (case insensitive is best) keyword if you are in doubt about where it might be exactly.
Did you find the logs? :)
not yet...
Well, when you do - Let us know :) We'll be waiting.