Closed kaho88 closed 4 years ago
So as mentioned in seat-slack please have a look through the troubleshooting guide
https://eveseat.github.io/docs/troubleshooting/
As 500 error can happen for many reasons.
I suggest you also ensure that migrations have been run.
I am having the same error.
Hey @Crypta-Eve Sorry... Not on the Slack Server at the moment. But here the Logs:
The "Solution to run migration" didnt work.
`Illuminate\Database\QueryException
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'corporation_id' in 'field list' (SQL: select `corporation_id` from `character_infos` where `character_id` in (93361068, 96715891, 2112723126, 2112833017, 2115460998))
https://auth.braindead-zombies.org/fitting`
`Illuminate\Database\Connection::runQueryCallback
vendor/laravel/framework/src/Illuminate/Database/Connection.php:669
* @throws \Illuminate\Database\QueryException
*/
protected function runQueryCallback($query, $bindings, Closure $callback)
{
// To execute the statement, we'll simply call the callback, which will actually
// run the SQL against the PDO connection. Then we can calculate the time it
// took to execute and log the query SQL, bindings and time in our memory.
try {
$result = $callback($query, $bindings);
}
// If an exception occurs when attempting to run a query, we'll format the error
// message to include the bindings with SQL, which will make this exception a
// lot more helpful to the developer instead of just the database's errors.
catch (Exception $e) {
throw new QueryException(
$query, $this->prepareBindings($bindings), $e
);
}
return $result;
}
/**
* Log a query in the connection's query log.
*
* @param string $query
* @param array $bindings
* @param float|null $time
* @return void
*/
`
The "Solution to run migration" didnt work.
That would be because you have partially run migrations. You are essentially trying to run the same migration twice which wont work. Can you explain what you have done up until reaching this point? Is this an update from seat3 to seat4 or a fresh seat4 install? Are you using docker or blade install?
We did an Update to V4 and used blade install :)
I am running fresh install of seat4 on blade install.
@bradleyshelley just confmirming that you also see the error of
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'corporation_id' in 'field list' (SQL: select `corporation_id` from `character_infos` where `character_id` in (93361068, 96715891, 2112723126, 2112833017, 2115460998))
Exactly the error.
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'corporation_id' in 'field list' (SQL: select corporation_id
from character_infos
where character_id
in (90537376, 90657388))
Cheers, thanks for that. I am closing this issue as this is a duplicate of #59. Also this is fixed in a patch that is getting pushed later today
Hi,
after Updating to the new SeAT Version we re-Installed the Fitting Plugin. Superadmins can point the "Fitting" side without a Problem. Normal Members cant.... They always get a 500 Error.
Logs Show: Request to fitting was denied. The permission required is global.superuser
Doctrine side work fine for all members.