Domain mapping 1.0.2

Sorry I got to this late, I’ve been stuck with a very slow internet access.

The new version of the domain mapping plugin is now up and available as no doubt you have spotted.

The changes in this version are:

1. Domain redirects. In the front end of the mapped blog, any request for the old domain will now 301 redirect to the new mapped domain. This works for both sub-domain AND sub-directory installs: e.g. myplace.com/userblog/2009/10/fredspost will redirect to myuserblogplace.com/2009/10/fredspost

2. The bug with the My blogs list in the admin system is now fixed.

3. Problems people had with MU installs in subdirectories should no longer be an issue. e.g. user.myplace.com/wpmu/ will map to myuserplace.com/wpmu/ (note the directory still needs to be in the url).

IF you don’t want the front end redirecting, but would like to use the new version then commenting out line 57 (add_action(‘template_redirect ) will disable that feature.

Thanks for your patience everyone.

Rgds

Barry

  • drmike
    • DEV MAN’s Mascot

    The backend for the mapped blog doesn’t redirect to the new domain.

    That may be done on purpose actually. wp.com has their’s setup that way as well. The reason, when I asked about it, being in case something goes wrong with the mapping or if the domain expires, the site is still accessible.

    Gotta admit I would rather see it that way myself.

  • Andrew
    • Champion of Loops

    Yep, that’s intentional. The plugin also integrates with the supporter plugin which means a mapping could be disabled for not only domain issues but lack of supporter privileges. So it’s really best to have the user use the admin panel via an url that won’t change.

    Thanks,

    Andrew

  • Christopher Price
    • The Incredible Code Injector

    I might have found a small bug: When looking at Site Admin > Blogs, if you click on ‘Custom Domain’ as if to sort — "No blogs found" is the result.

    Also, I’ll mention that I upgraded from from Donncha’s v0.3 Domain Mapping Plugin with a few domains already mapped, I only had one problem:

    A single mapped blog domain would not come up properly ultimately presenting me with an error about endless redirects. I noticed in Tools > Domain Mapping for the blog that the custom domain had CAPS in it (e.g. TwoWords.com) so I deleted it and added the domain again without caps. It worked fine after that. I can’t say whether the caps were the problem or not, but it works fine now.

  • Barry
    • DEV MAN’s Mascot

    Hi

    Yeah the sorting by mapped domain doesn’t work. I couldn’t find a quick and easy way of adding the column without the "sortable" title link being enabled, as soon as I work it out I’ll remove it but for now if we want the column there we are stuck with it I’m afraid.

    The Caps issue I’m not sure about. I don’t seem to have an issue regardless of capitalisation on my test server, but I’ll continue testing.

    Out of interest, what web-server are you using?

    Rgds

    Barry

  • Barry
    • DEV MAN’s Mascot

    Me too. If there was a way to be able to filter the SQL for the blog list based on the extra columns it would be fantastic :slight_smile: Seems you can add the column with an enforced linked heading, but then not do anything if they are clicked on.

    I’ll work it out though, I love a challenge.

  • Andrew
    • Champion of Loops

    Seems you can add the column with an enforced linked heading, but then not do anything if they are clicked on.

    Yeh, that’s been a problem for quite a while now. You can add a column but you there’s not a filter in place to let you do anything as far as sorting by that column.

    Thanks,

    Andrew

  • e.yatsik
    • WPMU DEV Initiate

    Where can I find "Make this functionality only available to Supporters" option? I search everything but didn’t find this. My WPMU version is 2.7.1 and I upgraded from Donncha’s Domain Mapping Plugin. It seem this doesn’t work for me:

    add_action( 'wpmu_options', array(&$this, 'handle_domain_options'));

  • e.yatsik
    • WPMU DEV Initiate

    I found the error! It was an eAccelerator issue. When I turned if off by adding php_value eaccelerator.enable 0 in .htaccess file, all works OK. But what is the really matter? I need eAccelerator because of performance.

  • e.yatsik
    • WPMU DEV Initiate

    You *really* need to upgrade to 2.8.4.

    But there isn’t correct Russian localization yet for 2.8.4 :slight_frown: So, my WMPU looks ugly after upgrade.

    But this is not 2.7.1 issue but eAccelerator one.

    Do you know why eAccelerator doesn’t load a full page (when I see source code for the page, it looks uncomplete)?