- This topic has 20 replies, 5 voices, and was last updated 10 years, 1 month ago by
.
-
Posts
-
(Appearance : Weaver Xtreme Admin : Advanced Options : Admin Options : Disable Customizer)
this seemed to fix it. thank you very much. here was another suggestion (below) but i REALLY want to avoid touching code.remove_action( 'admin_init', 'dm_redirect_admin' );
add_action( 'admin_init', 'theme_redirect_admin' );
function theme_redirect_admin() {
// don't redirect admin ajax calls
if ( strpos( $_SERVER, 'wp-admin/admin-ajax.php' ) !== false )
return;
// Added 2016-01-25 by CH - && !is_customize_preview()
if ( get_site_option( 'dm_redirect_admin' ) && !is_customize_preview() ) {
// redirect mapped domain admin page to original url
$url = get_original_url( 'siteurl' );
if ( false === strpos( $url, $_SERVER[ 'HTTP_HOST' ] ) ) {
wp_redirect( untrailingslashit( $url ) . $_SERVER[ 'REQUEST_URI' ] );
exit;
}
} else {
global $current_blog;
// redirect original url to primary domain wp-admin/ - remote login is disabled!
$url = domain_mapping_siteurl( false );
$request_uri = str_replace( $current_blog->path, '/', $_SERVER[ 'REQUEST_URI' ] );
if ( false === strpos( $url, $_SERVER[ 'HTTP_HOST' ] ) ) {
wp_redirect( str_replace( '//wp-admin', '/wp-admin', trailingslashit( $url ) . $request_uri ) );
exit;
}
}
}bruce – what do you think of this code? i got it from here:
Sorry, I didn’t realize you were looking for an opinion.
I really can’t comment on the code. It is probably harmless, may work to fix the issue.
But the real question is if MU Domain Mapper breaks the Customizer in general, or just the Weaver Customizer interface?
There are limited, but important Customizer options that are used by WP by default now, and if the MUDM breaks that, then they are inaccessible, too.
But as I said before, this clearly seems to be an issue with MUDM, and it would seem to me that the plugin developer is 100% responsible for fixing the problem. And I would not really trust anyone else to fix it.
As the support post you referenced, the plugin developer needs to see and add that code. I could be done from a theme functions.php, but is could also be done from a plugins admin interface.
The ‘admin_init’ action probably comes too early in the WP startup sequence, but you also could try entering that code directly into the Weaver Xtreme Plus Filters and Actions code block, and it might work right there, but I kind of think that feature happens too late in the whole admin process.
Or you could create a child theme with that code and see for yourself what happens.
But I really can’t express anything about what the code does. It is fairly technical, and specialized, and I couldn’t understand it without spending a whole lot of time. MUDM authors should fix their code!
If the customizer is not working, and you need to set some WordPress features like header or background that only work in the customizer, you can turn off the advanced customizer of Xtreme in Appearance > Weaver Xtreme Admin > Advanced Options > Admin Options > Disable Xtreme Customizer interface.
This will limit the customizer to the basics WordPress options and should work.
For the Theme Options, they are all available in Appearance > Weaver Xtreme Admin > Main options.
Do make sure you have Installed the Weaver Xtreme Theme Support.
Regardless fixing the customizer, the first thing to do is make sure you PHP memory is set at at least 128. If you do not know where to do that, Ask your Host provider to check / set it for you.
Once that is done, if you still have a problem, deactivate ALL non weaver plugins and see if that fixes the issue. If it does, reactivate one by one to find the Culprit.
Finally also try a different browser, IE and Edge seem to be more sensitive to the full Xtreme Customizer.Thank you for helpful hints. After deactivating all non weaver plugins and subsequently reactivating them one by one I found the culprit – plugin Ninja Announcements https://wordpress.org/plugins/ninja-announcements/ .
Now the customizer works OK.
- You must be logged in to reply to this topic.