This will not work with Genesis 3.0 or higher. It only works with Genesis 2.10
The most recent Genesis release (2.10) moved the theme settings to the Customizer. If you try accessing the old theme settings page, it redirects you to the customizer with the Theme Settings panel open.
Here are a few reasons why you may want to access the old theme settings page:
- You don’t like the customizer 👋
- You’re using a plugin like Genesis Title Toggle that includes themes settings which are now inaccessible
- You have added your own theme options in your child theme which are now inaccessible
The redirect does not apply to additional settings pages that you have created, or those added by plugins like Genesis Grid and Genesis 404.
These approaches will only work with the 2.x branch of Genesis (ex: Genesis 2.10 and any other 2.x releases that come later). Genesis 3.0 will remove these pages completely, not simply redirect them.
There are two ways you can access the old theme settings page.
Include &noredirect in URL
If you only need to access the settings page once, this is the simplest approach.
Hover over Genesis > Theme Settings, right click and select “Copy Link Address”. Paste that URL in the address bar, then add &noredirect to the end of it. This tells Genesis to bypass the redirect.
The URL will be: https://yoursite.copm/wp-admin/admin.php?page=genesis&noredirect
If you access theme settings often, you might prefer a more permanent solution.
Disable the redirect
It only takes a few lines of code to disable Genesis from ever redirecting to the customizer. You can then access the theme settings the way you always have, by clicking Genesis > Theme Settings.
Install the plugin
I’ve packaged this code into a plugin so you can easily install it without having to edit code. Go to Plugins > Add New > Upload and upload this zip file.
/**
* Disable Genesis Customizer Redirect
* @see https://www.billerickson.net/disable-genesis-customizer-redirect
*/
function be_disable_genesis_customizer_redirect() {
global $_genesis_admin_settings, $_genesis_admin_seo_settings;
$_genesis_admin_settings->redirect_to = '/wp-admin/admin.php?page=genesis&noredirect';
$_genesis_admin_seo_settings->redirect_to = '/wp-admin/admin.php?page=seo-settings&noredirect';
}
add_action( 'genesis_admin_menu', 'be_disable_genesis_customizer_redirect', 11 );
Skylar says
I’m with you on disliking the customizer.
Given that Genesis has explicitly stated they’re removing the settings page in 3.0 (issue #2257), what are your feelings on re-adding it once it’s removed?
Bill Erickson says
Genesis 3.0 is a complete rewrite and is not backwards compatible with Genesis 2.x, so it won’t be easy to add back the settings page. It’s likely most of the current theme settings will be removed anyway.
The particular feature that prompted this post (accessing Genesis Title Toggle settings) won’t be an issue since that functionality is being merged into Genesis core in 3.0.
Selena says
“Genesis 3.0 is a complete rewrite and is not backwards compatible with Genesis 2.x…” As in we should expect things to break? Or just we won’t be able to get back things like the theme customization settings. Should I be worried about the Genesis sites I support?
Bill Erickson says
Recently developed Genesis sites shouldn’t break, but very old ones (those using XHTML rather than HTML5) should remain on the 2.x branch until rebuilt with a newer theme.
Here are some things you can expect in Genesis 3.0:
– All code related to XHTML removed
– Removal of the “blog” and “archive” page templates. There will be some sort of fallback to display recent posts if you were using the blog template, but you shouldn’t be using that template.
– Removal of all functions deprecated prior to 2.8 (full list of removed functions)
– Removal of Theme Settings and SEO Settings pages
– Reorganize and modernize much of the core code (namespaced classes built as modular components)
– AMP Support
Unlike WordPress core, Genesis uses semantic versioning, which is why 2.10 just came out rather than 3.0. The tl;dr summary of semantic versioning is:
x.0.0 = breaking changes (MAJOR)
0.x.0 = feature release (MINOR)
0.0.x = bug fixes (PATCH)
You should definitely test Genesis 3.0 thoroughly on a staging environment before updating your live website.
Selena says
Great – thanks! We still have 2 clients on Thesis 1.x because they refuse to do a new site…I just don’t want to go down that path again! This is super helpful.
Daniel Andersson says
Hi,
Works great in previous versions.
Unfortunately not working in the latest version of Genesis Framework (3.0.0).
Do you have a modification in the loop?
Bill Erickson says
I mentioned this in the article above. Genesis 3.0 removes those pages completely. It doesn’t simply redirect you when trying to access them. This means there’s no way to add back those pages if you’re using Genesis 3.0 or higher.
Toby says
Now that Studiopress have removed the Genesis settings page, does that make this CMB2 code redundant?
https://github.com/CMB2/CMB2-Snippet-Library/blob/master/options-and-settings-pages/genesis-settings-metabox.php
Bill Erickson says
Correct, now that the Genesis settings page is removed, that CMB2 code will no longer function.