I upgraded today to all the dev builds of -core, netherportals etc and since then the netherportals do not work anymore.

The commands work fine, this is my config:

worlds:
darklands:
portalgoesto: {}
nether:
portalgoesto:
NETHER: darklands

so when you are in the nether, you should warp to the darklands, but not the other way around.
When I step into a nether portal in the world "Nether", nothing happens though.

I can also confirm Nether portals are not working since 1.4.2 ;)

Aight, I'll have a look. I need to do some re-working in NPs to reduce confusion regardless.

Same here, nether portals not doing anything. Got a 'Vanilla' map and the nether being 'Vanilla_nether'. Definitely a 1.4.2 bug.

Thank god I'm not the only one. Just added this part of the plugin when we added a new world for 1.4. And matter what I tried I couldn't get it to work.

Hey guys, with a bunch of you reporting this, I've moved it to the 2.5 milestone. I'll definitely have a look this weekend if not sooner. Thanks for your patience!

I can confirm this as well.

With allow_nether = false, mvnp doesn't work normally or even with linked portals.

With allow_nether = true, mvnp works as expected, (world X portals got to X_nether)
however your primary world will generate a nether.

Might be a good temporary solution to the problem. Just don't give multiverse.access. perms for the primary nether.

I think this is possibly the CB commit that broke this - I'm not a developer though, just trying to help. As far as I can tell, it's either this one or the original update commit, which is freaking massive.
Bukkit/CraftBukkit@e7cc42a

any word?

I did the allow_nether = true that drunken suggested and it is working for me. Just have an extra world loaded that is never used.

I defenitly feel you on that. The extra world is a tax on our system too.

You can always set the extra unused world to not keep the spawn in memory with the command /mvm set keepSpawnInMemory false world_nether (replacing world_nether with the actual world name, of course) and the burden on your system will be next to nothing.

Just as I posted that post I thought the same thing and did just that. Well I edited the config and reloaded.

that's a workaround, but not a fix, and i'd rather not have an extra world if i can avoid it. my machine is already overtaxed.

I could force that world to stay unloaded completely too - reducing the burden to nothing except hard disc space. All of which I've already done. Regardless, that's a workaround - and I'd prefer a fix.

@TheGurw It was almost certainly that commit that broke it. After having spoken with Amaranth, he has told me that in 1.4.4 this issue should be resolved. I'll keep the ticket open until we know.

I have confirmed that this is no longer an issue in 1.4.4