HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Search
-
Re: After Upgrading to Vanilla 3.2 (HTTP ERROR 500)
-
Re: After Upgrading to Vanilla 3.2 (HTTP ERROR 500)
-
Re: After Upgrading to Vanilla 3.2 (HTTP ERROR 500)
-
Re: After Upgrading to Vanilla 3.2 (HTTP ERROR 500)
-
Re: After Upgrading to Vanilla 3.2 (HTTP ERROR 500)
-
Re: After Upgrading to Vanilla 3.2 (HTTP ERROR 500)
I suspect people are not responding because you are not doing what is suggested. You have been told that a 500 error is an error on your webserver, not a specific Vanilla error. There is no way for anyone else to guess what your issue night be. You were asked to set up a clean install of Vanilla 3.2, which you have not yet… -
Re: After Upgrading to Vanilla 3.2 (HTTP ERROR 500)
Disable all then enable one by one not disable>enable one by one. This is intended to rule out conflicting plugins (either conflicting plugin<>plugin, plugin<>Vanilla or plugin<>server). The suggestion to install a clean version on a secondary test domain is intended to rule out configuration conflict (Vanilla or server).… -
Re: After Upgrading to Vanilla 3.2 (HTTP ERROR 500)
You should not have run utility/update and utility/structure - you now need to do an extra setup. You have seen that a clean Vanilla install and a new database throw no error. You have seen that a clean install works with your database. Issue is in your install, not in a Vanilla Forum as it is delivered - so it is a plugin…
8 results