Administration page 404 error after upgrading from 3.2.1-4 to 3.3.0-10

I was finally able to upgrade one of our 3.0.0 journals all the way to 3.3.0-10 (3.0.0 → 3.1.2-4 → 3.2.1-4 → 3.3.0-10), but after the 3.3.0-10 upgrade, the Administration page links in both the Dashboard left side menu (“https://journaldomain/index/admin”) and right-hand top menu from the main screen (“https://journaldomain/index/admin/index”) throw 404 errors. With error display turned on in config.inc.php, the trace is:

404 Not Found

Stack Trace:

File: /opt/www/bollerreview_upgrade.tcu.edu/current/lib/pkp/classes/core/PKPPageRouter.inc.php line 228
Function: Dispatcher->handle404()

File: /opt/www/bollerreview_upgrade.tcu.edu/current/lib/pkp/classes/core/Dispatcher.inc.php line 144
Function: PKPPageRouter->route(Object(Request))

File: /opt/www/bollerreview_upgrade.tcu.edu/current/lib/pkp/classes/core/PKPApplication.inc.php line 362
Function: Dispatcher->dispatch(Object(Request))

File: /opt/www/bollerreview_upgrade.tcu.edu/current/index.php line 68
Function: PKPApplication->execute()

I’ve reviewed several support posts relating to the same basic error, but I’m not finding anything that solves the problem, and some of the solutions seem to refer to problems in 3.1.x or 3.2.x that are fixed in 3.3.x, but 3.3.x is where I’m seeing the problem. And unlike several of those posts, I can’t tell if the problem is the URLs that are being constructed in the navigation menus, or if the page is simply inaccessible, since I can’t find any URL that works for the Administration page.

Thanks for any help, Kerry

Did you check the Apache .htaccess rules ? The rules that worked for 3.0.0 may not work anymore for 3.3

Thanks. We’re using NGINX instead of Apache; below are the rewrite rules and path statements from our NGINX .conf file:

location / {
    rewrite ^/$ /index.php/boller last;
    try_files $uri $uri/ @boller;
}

location @boller {
    rewrite ^(.*)$ /index.php/boller$1 last;
}

location ~ index\.php/boller(/|$) {
    fastcgi_split_path_info ^(.*?\.php)(/boller.*)$;
    fastcgi_pass unix:/var/opt/remi/php74/run/php-fpm/php-fpm.sock;
    include fastcgi_params;
    fastcgi_index  index.php;
    fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
    fastcgi_param  PATH_INFO $fastcgi_path_info;
    fastcgi_buffers 16 16k;
    fastcgi_buffer_size 32k;
}

location ~ [^/]\.php(/|$) {
    fastcgi_split_path_info ^(.*?\.php)(/.*)$;
    fastcgi_pass unix:/var/opt/remi/php74/run/php-fpm/php-fpm.sock;
    include fastcgi_params;
    fastcgi_index  index.php;
    fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
    fastcgi_param  PATH_INFO $fastcgi_path_info;
    fastcgi_buffers 16 16k;
    fastcgi_buffer_size 32k;
}

The base URL’s in the config.inc.php file for the testbed copy of the journal I’ve been using to work through upgrade issues are:

base_url[index] = https://bollerreview_upgrade.tcu.edu/index
base_url[boller] = https://bollerreview_upgrade.tcu.edu

I have no idea what problems to look for in the rewrite/path rules because I don’t know what makes the OJS Administration page different from all the other OJS pages.

Thanks, Kerry