Does Domain Mapping 4.3.0.4 Resolve These Issues?

There were a number of mapping issues introduced by version 4.3.0. None of the changelogs for versions released since then (including 4.3.0.4) indicate that they've addressed the specific issue described in threads like these:

https://premium.wpmudev.org/forums/topic/domain-mapping-bug-temporary-solution
https://premium.wpmudev.org/forums/topic/image-broken-after-recent-updates
https://premium.wpmudev.org/forums/topic/urgent-updated-domain-mapping-plugin

In fact, the changelog for 4.3.0.4 doesn't say anything was fixed.

The issue at hand is a major bug that effectively broke every mapped site in our networks and forced us to roll back to 4.2.06. I'm reluctant to update to any of the new versions for fear of reintroducing the bug.

Please let us know.

Owen

PS - The changelog shows a release date of February 2, 2015 for every version of Domain Mapping since version 4.3.0. This is inaccurate and should be corrected.

  • Ivan

    Hey there NYCWW,

    Hope you are well and thanks for the question.

    In the thread about the images problem you linked here/ the member already said in the last reposnse this is fixed in the last version.
    The first thread is essentially about the same images problem.

    I just spoke with the developer and he said the bug in the third thread you linked is fixed too, as well as the images bug.

    So you should be able to update to the latest version without problems, but make a backup before that - just in case.
    It is always good idea to have backups. :slight_smile:

    PS - The changelog shows a release date of February 2, 2015 for every version of Domain Mapping since version 4.3.0. This is inaccurate and should be corrected.

    Thanks for this, we noticed that and should be fixed soon.
    Meanwhile you can find changelog in the plugin zip archive if you download it manually.

    Thanks for being WPMU DEV Member,
    Ivan

  • NYCWW

    It wasn't clear to me which version the member was referring to (since the dates are missing from the changelog and he didn't specify), but I know for a fact that 4.3.0.2 did NOT solve the problem.

    I didn't want to assume that he was talking about version 4.3.0.3 or 4.3.0.4. Even if I did, the changelog for those versions don't make any mention of the permalinks, which seems odd.

    Better to hear it from the proverbial "horse's mouth" than to assume and be wrong.

    Thanks for the confirmation.

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.