Hello,
After upgrading 2.3.10 to 3.0.0, i get a page saying :
" [
Sorry we could not find that page.
Please press the button below to go to your homepage or press back in your browser"
Using debian stable with apache2 and mariadb,
extracting new archive : OK
chown file extracted : OK
create new folder for cms 3.0: OK
chmod/chown new folder : OK
add settings.php from 2.3.10: OK
editing apache2 conf file (with new folder 3.0.0) : OK
using sphinx command to upgrade bdd : OK
the CMS has work fine this morning, but when i try to connect it few hours later, i got the message “Sorry we could not find that page.”
using config file ./phinx.php
using config parser php
using migration paths
/home/site-web/xibo.info.srv.csm/ht-docs/3.0.0/db/migrations
warning no environment specified, defaulting to: production
using adapter mysql
using database xibo
grep -ri 'Sorry we could not find that page' .
./lib/Middleware/Handlers.php: 'message' => __('Sorry we could not find that page.')
./locale/default.pot:msgid "Sorry we could not find that page."
./views/not-found.twig: <p>{% trans "Sorry we could not find that page." %}</p>
the message is generated due to “Middleware/Handlers.php”
specially by this part :
// Handle 404’s
if ($exception instanceof HttpNotFoundException) {
if ($request->isXhr()) {
return $response->withJson([
‘success’ => false,
‘error’ => 404,
‘message’ => __(‘Sorry we could not find that page.’)
], 404);
} else {
return $twig->render($response, ‘not-found.twig’, $viewParams);
}
after installing xibo on another VM using docker, i reproduct the same error while enable SSL and replacing IP by an internal DNS adresse (was working before that step)