Question 1.7.1 to 1.7.2 upgrade 500 error

See HTTP 500 Internal Server Error in the Wiki.

sozzled wrote: See HTTP 500 Internal Server Error in the Wiki.

As I said in my original post I've gone through all of the docs multiple times and have not found a solution. Please help me to diagnose!

What I would do, in your situation, is to do exactly what we've been discussing ... to use Joomla debug mode to attempt to identify exactly where the HTTP 500 error message occurs, to try to actually see the text of the error message and see where it points as the source of the error. Sometimes, however, Joomla debug mode is not smart enough to tell you where the error occurs. In cases like those, you need to look at the web server logs. Sometimes even then nothing seems to work and it can take hours or days of patient "detective work" to identify the problem.

But let's get a few things out of the way here.

You're using K 1.7.1 and you've hacked your configuration report so that we can't really see anything. That's your choice to change the configuration report, if that's what you want to do. In these kinds of circumstances, where people have chosen not to provide certain information - information that is only visible to you and to the forum moderators here on this forum - we can only advise you to read whatever general documentation that we have. On the other hand, if you would like someone to spend a couple of hours trying to figure out what is happening at your website then that's a different proposition.

Would you like someone to spend a few hours looking over your website to try to find out what it is that you've done and what you need to do to correct it? :dry:

sozzled wrote: What I would do, in your situation, is to do exactly what we've been discussing ... to use Joomla debug mode to attempt to identify exactly where the HTTP 500 error message occurs, to try to actually see the text of the error message and see where it points as the source of the error. Sometimes, however, Joomla debug mode is not smart enough to tell you where the error occurs. In cases like those, you need to look at the web server logs. Sometimes even then nothing seems to work and it can take hours or days of patient "detective work" to identify the problem.

I"ve tried that to no avail.

But let's get a few things out of the way here.

You're using K 1.7.1 and you've hacked your configuration report so that we can't really see anything. That's your choice to change the configuration report, if that's what you want to do. In these kinds of circumstances, where people have chosen not to provide certain information - information that is only visible to you and to the forum moderators here on this forum - we can only advise you to read whatever general documentation that we have. On the other hand, if you would like someone to spend a couple of hours trying to figure out what is happening at your website then that's a different proposition.

I've argued this with you a number of times before. Removing my domain name and website name from this report does not affect the data or change the outcome in any way. I wish you would just get over it and stop with the badgering.

Would you like someone to spend a few hours looking over your website to try to find out what it is that you've done and what you need to do to correct it? :dry:

Not someone with your attitude towards 'customer service' or helping people.

Where do I find the documentation to upgrade manually?

No badgering here. Perhaps you could suggest a way for us to help that works better for you?

In all seriousness, HTTP 500 Internal Server Errors can mean just about anything. We need a place to start. I'm sorry, but I can't find a place to start in your case without some assistance from you.

When you say, "upgrade manually", I presume you mean replacing the existing files, one-by-one on your server with new files and (if needs be) making any changes to the database tables? I don't believe that K 1.7.1 -> K 1.7.2 changed the database (apart from updating the version number). What you could do, though, is examine the installation pack's manifest and replace the files one-for-one. I'm sorry, there's no "manual upgrade" documentation; there hasn't been any documentation in the 3+ years since Kunena was first released.