Important 500 Internal Server Error

I simply performed it by selecting all the files and moved them into public_html and fixed the paths in the config. Everything but posting seems to work fine though.

I am going to do a quick check through my database to see what I can find.

And no. When it was in /test stupidly of me I didn't test posting so I can not be certain if it was working.

I use Joomlapack (now known as Akeeba Backup) to copy my database and site files from one location to another. It also helps to have the "strategic view": always use relative links (not absolute links) when building a website, because you never know if you're going to move the site somewhere else ... possibly to a different server ... possibly to an entirely different domain.

I think I hit a similar problem once (early in my use of Joomla): tried to copy directories across; failed in the task ... 500 server error problem. Used Joomlapack and I've never encountered those issues since.

I have had plenty of HTTP 500 Internal Server Errors (some of them with Kunena) in my experience ... but for the reasons I have explained in this thread.

Okay so you suggestion using the extension but what can I do about the current issue? Sadly the internet doesn't have an undo button

I, personally, don't know what to do specifically about your current issue. If I, personally, were in your shoes, I'd restore my test site from a backup or, if that weren't possible, I'd start again and be very careful next time around. Testing ideas is a pain in the rear-end; it can take hours or days - searching for answers on the internet or using a bit of rat-cunning to work through or work around the technical problems that you encounter along the way.

The KISS principle is the best principle. Keep it simple, stupid!

Start with what you know works: Apache (the right version); PHP (the right version); MySQL (the right version); Joomla (the right version); a simple template (rhuk_milkyway or JA_Purity); the most important component that you absolutely must have and that your entire site is built around ... and make sure it's the right version.

And when you've done all of those things, and when you've exhausted yourself testing them and making sure they work ... that's when you start adding the "bells and whistles", one at a time, and after each one, check that your core platform still performs without any problems. Sometimes you might need more than one pair of hands to test these things. That's the way it goes.

But, you've probably heard all of this before and I could be preaching to the converted, for all I know. For your sake, I hope that someone else might have some better tips than I've given you. It's unfortunate that all we've got to go with is "HTTP 500 Internal Server Error" and nothing else.

Ya it sucks that, that is all we have to work with and nothing to tell us what to do more specifically. Although I really really don't want to have to start over, because I did a lot of work 'behind the scenes' that would take me quite a long time to do again, lol.

Knowing me its probably the simplest error thats causing this especially since it only is posting and nothing else on my website.

Errors are a real pain in the ass lol, not that I am not used to them (I program in C++ all the time making software)

You could try running your website on your own PC (using WAMP or XAMPP software) - this has helped me, in the past, identifying these mystery HTTP 500 Internal Server Errors. :dry: