Title: Compatibility with 4.3 Last modified: August 30, 2016 --- # Compatibility with 4.3 * [guillaumemolter](https://wordpress.org/support/users/guillaumemolter/) * (@guillaumemolter) * [11 years, 1 month ago](https://wordpress.org/support/topic/compatibility-with-43/) * Hi, * Anyone experiencing troubles with 4.3? * [https://wordpress.org/plugins/wordpress-mu-domain-mapping/](https://wordpress.org/plugins/wordpress-mu-domain-mapping/) Viewing 14 replies - 1 through 14 (of 14 total) * [lynnakvo](https://wordpress.org/support/users/lynnakvo/) * (@lynnakvo) * [11 years, 1 month ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6453765) * It didn’t work for us from 4.2 onwards. * [Tasnimul H. Tauhid](https://wordpress.org/support/users/tht52/) * (@tht52) * [11 years, 1 month ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6453887) * I upgraded to 4.3 and now I see many errors in my Domain mapping page. * [RiseOfLex88](https://wordpress.org/support/users/riseoflex88/) * (@riseoflex88) * [11 years, 1 month ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6453929) * [@lynnakvo](https://wordpress.org/support/users/lynnakvo/), we’ve been running this plugin on 4 separate installs (roughly 300 sites) without problem on 4.2, I don’t think the plugin is at fault on this. * Thread Starter [guillaumemolter](https://wordpress.org/support/users/guillaumemolter/) * (@guillaumemolter) * [11 years, 1 month ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6453930) * Same here no problem on 4 multi-sites installs with 4.2. However a friend warned me of breaking problems with 4.3? Anyone else experiencing problems except : [@tasnimul](https://wordpress.org/support/users/tasnimul/) Hasan Tauhid ? * [Tasnimul H. Tauhid](https://wordpress.org/support/users/tht52/) * (@tht52) * [11 years, 1 month ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6453931) * Actually it was wp_debug (I forgot about it). So no problem here. 🙂 [@guillaumemolter](https://wordpress.org/support/users/guillaumemolter/) * [lynnakvo](https://wordpress.org/support/users/lynnakvo/) * (@lynnakvo) * [11 years, 1 month ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6453938) * [@riseoflex88](https://wordpress.org/support/users/riseoflex88/) not sure what was the cause. The admin pages wouldn’t load at all. It’s as if the sunrise entry int he config file were completely ignored as per below message to the plugin support: “ We have a WP Multisite installation and I am struggling to figure out why the pages dm_domains_admin & dm_admin_page are not loading. This means I cannot setup any domain names. * The plugin shows as network active yet only appears under plugins for the ‘network admin’ (but maybe that’s normal?). The dropin ‘sunrise.php’ is available under wp-content. The wp-config.php file has been updated with the define script. I’ve spent days ‘redoing’ these to make sure they have the correct permissions/added correctly, etc. * The error when going to ‘domain mapping’ is “Please edit your /var/akvo/akvosites/ code/wp-config.php and move the line define( ‘SUNRISE’, ‘on’ ); above the last require_once() in that file or make sure you updated sunrise.php.” * I’ve tried an older version, now using the current version but with no luck. * Below is what the site url looks like: * [http://ourwordpressdir.test.ourdomain.org/](http://ourwordpressdir.test.ourdomain.org/) * Thanks for any help. Lynn * [https://wordpress.org/plugins/wordpress-mu-domain-mapping/](https://wordpress.org/plugins/wordpress-mu-domain-mapping/) * Ron Rennick MultiSite Guru Plugin Author Posted 1 month ago # * Is your define(‘SUNRISE’,’on’); below the line that says that’s all, stop editing? * lynnakvo Member Posted 1 month ago # * No, first I had it directly above ‘stop editing!’ but as it didn’t work I tried a variety of different places. Currently it’s below ‘define(‘WP_DEBUG’, false);’ but has made no difference where I put it in the file.” * Possibly something else caused this not to work on our server, but I couldn’t do anything without the admin page loading so it was useless for us on this install. * Lynn * [George Lerner](https://wordpress.org/support/users/lernerconsult/) * (@lernerconsult) * [11 years, 1 month ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6453980) * The plugin definitely works fine with WordPress 4.2 and 4.3 * lynnakvo says in another of her support posts that she gave up on this plugin for her installation * [Raptor K](https://wordpress.org/support/users/raptorhk/) * (@raptorhk) * [11 years, 1 month ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6454018) * This plugin runs very slowly in WordPress 4.3. It tooks ~20 seconds to load finish loading in Admin section, confirmed by P3 Plugin Profiler. Didn’t notice any errors on screen at all. * p.s. I have around 50 sites configured. * [davinian](https://wordpress.org/support/users/davinian/) * (@davinian) * [11 years ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6454022) * It seems to work on 4.3 but on “domains” page I only see 20 out of my 50+ sites. * [Lidgett](https://wordpress.org/support/users/lidgett/) * (@lidgett) * [11 years ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6454045) * All my existing mappings are working fine but since going to 4.3 i configure new sites and new mappings and they never take effect. * I go to the mapped domain and get hijacked saying registration is disabled so the mapping hasn’t worked. 🙁 * [davinian](https://wordpress.org/support/users/davinian/) * (@davinian) * [11 years ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6454046) * I have updated to 4.3 (not 4.3.1) and mapping is still working for me, but when I go to the domains page, I don’t see all of them – but they are all working. * Is there likely to be an update to this plugin before WordPress 4.4 ? * Plugin Author [Ron Rennick](https://wordpress.org/support/users/wpmuguru/) * (@wpmuguru) * [11 years ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6454048) * > Is there likely to be an update to this plugin before WordPress 4.4 ? * No. WordPress 4.4 is going to support arbitrary URLs. Essentially that should make the DM plugin obsolete. * [davinian](https://wordpress.org/support/users/davinian/) * (@davinian) * [11 years ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6454049) * Thanks Ron, * I knew 4.4 would support arbitrary URLs. Will there be a process to migrate from DM to 4.4? * I’ll try and download 4.4 beta as soon as it’s available and test locally and report any bugs/issues. * Plugin Author [Ron Rennick](https://wordpress.org/support/users/wpmuguru/) * (@wpmuguru) * [11 years ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6454052) * > Will there be a process to migrate from DM to 4.4? * I would assume so. If what you would like to know is whether I’m going to write a script/plugin that does that for you, I haven’t decided anything on that yet. Viewing 14 replies - 1 through 14 (of 14 total) The topic ‘Compatibility with 4.3’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/wordpress-mu-domain-mapping.svg) * [WordPress MU Domain Mapping](https://wordpress.org/plugins/wordpress-mu-domain-mapping/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-mu-domain-mapping/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/) * [Active Topics](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordpress-mu-domain-mapping/reviews/) ## Tags * [update](https://wordpress.org/support/topic-tag/update/) * 14 replies * 9 participants * Last reply from: [Ron Rennick](https://wordpress.org/support/users/wpmuguru/) * Last activity: [11 years ago](https://wordpress.org/support/topic/compatibility-with-43/#post-6454052) * Status: not resolved