Fix Genesis 2.4.0 Update Redirection Loop

The upgrade to Genesis 2.4.0 causes some sites to enter into a redirection loop that prevents access to the admin pages. There is a simple fix that takes less than 5 minutes to implement.

The Upgrade Problem

After upgrade to Genesis 2.4.0 you find the dashboard is inaccessible because of a redirect loop. The page that tries to load has a URL that looks similar to

https://example.com/wp-admin/admin.php?page=genesis-upgraded

The notable part of that URL is ?page=genesis-upgrade. This query string is set by the Genesis theme upgrade redirection function that loads the changelog page. The site is broken and will load as per normal once the error is fixed.

This Redirection Loop Fix

Log into your web server AKA cPanel and open the File Browser or login to the server with an FTP program like FireFTP.

Browse to wp-content/themes/genesis/

Open functions.php to edit it.

Add the next line to the bottom of functions.php

remove_action( 'genesis_upgrade', 'genesis_upgrade_redirect' );

Make sure there is not an empty line after it.

Save the changed functions.php file.

Reload the WordPress dashboard. You will need to delete the part of the URL that reads ?page=genesis-upgraded e.g. load example.com/wp-admin/

Strange things happened after updation. I am using newspro child theme for the genesis on my blog Examchacha.in. The adsense ads used for the posts have started to visible on Homepage. The loop structure has the issue and I tried to fix but no success yet.

StudioPress released Genesis 2.4.2 today. This release might resolve the issue for you. Two other items to check: 1, have the widget areas moved? Make sure widgets are assigned to the correct widget areas, and, 2, see whether a new version of your child theme is available. Some of the older child themes are incompatible with the new Genesis framework.

Thank you! Funny, I had been delaying the Genesis upgrade out of a vague feeling of dread. I decided to update today after it’s been out there a few weeks. Amazing that I ran into this issue. You’d think it would have been patched by now.