Support

Admin Tools

#10205 WAF give me 500 Error

Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a

Latest post by nicholas on Saturday, 07 January 2012 08:59 CST

Baldur2630
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? yes
Have I searched the forum before posting? yes
Have I read the documentation before posting (which pages?)? yes
Joomla! version: (1.5.25)
PHP version: (5.3.8)
MySQL version: (5.5.19)
Host: (Own CentOS 6.2 server)
Admin Tools version: (unknown)


Description of my issue:
I bought a new Server, installed the latest Version of CentOS 6.2 on it and moved my 3 websites from the old server (VMWare ESX 4 not changed), CentOS 5.5 to the new one using Akeeba Backup and KickStart.
When I try to avves WAF on Admin Tools I get : -
500 - An error has occurred
Layout "form" not found

Directory permissions are OK.

Can you please advise?

nicholas
Akeeba Staff
Manager
Please read this: https://www.akeebabackup.com/support/forum/admin-tools-support/500-error-accessing-waf-after-udate/55317.html#p55317

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Baldur2630
Nope, didn't work. It says I have the latest version.

I even tried downloading the Alpha 2.2.a1 and installing that, but I get a message
"It was not possible to copy the selected file".

WAF has the same error.

nicholas
Akeeba Staff
Manager
Well, actually, you did the opposite of the instructions I pointed you at. Let me try again, in more detail.

Version 2.0.a1 is an alpha release, not meant to be installed on live sites. As such, it can contain sever bugs. And yes, it actually does. No big surprise here, it's an alpha release.

You have the following options:
- Roll back to 2.1.14
- Install the latest dev release (as the instructions I pointed you at read) and do not upgrade until I release 2.0.a2
- Wait for me to release 2.0.a2, in about 2 hours from now

What you did was to stick with 2.0.a1 which I already KNOW that has some bugs and that's exactly why I have told everybody else to upgrade to the latest dev release (which, of course, fixes those bugs).

Note: After installing a dev release, it will always tell you that there is an update available and point to the latest official release. This is by design. It doesn't necessarily mean that the official release is newer than the dev release.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Baldur2630
Not really, It was already on 2.0.a1, because the previos time I logged it, it said there was an upgrade, so I installed it and it installed the a1 version on my live site. This was done via the upgrade system, I didn't download it. So it was the Admin Pro that put the Alpha ontomy live site, not me.

What I did when I read your fist email was to actually download a copy of 2.0.1a, and try to install it, because I thought that there may have been an error in the Update, because we had some server problems with hacking attempts (firewall got constipated) over the Christmas period.

I'll wait until tomorrow and then try updating again.

Thanks for your assistance, but you can't blame me for this one!

nicholas
Akeeba Staff
Manager
Just wait 6 hours. Go back to your site. Install 2.0.a2.

The automatic update emails, like the one you received, state the stability very clearly in the email message. Also note that I never sent you an email; it was your site sending you the email, because you enabled that feature when you installed Admin Tools Professional. Should you install a release with an "Alpha" status on a live site? Nope. Alpha means unstable. This stability tagging scheme is used worldwide for the last 40 years, that's why I also use it.

Finally, I will reiterate that the instructions I pointed you to did state that 2.2.a1 is broken (they also explained why) and you must install the latest dev release as a quick fix. Logical assumption: if the software subsequently asks you to reinstall 2.2.a1 you should not re-install it, exactly because it is the broken release you were trying to work around in the first place. Doesn't that make sense?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!