annathepiper

OKAY YES GOOD CAN CONFIRM:

Blew away all my settings, deactivated the previous Premium version of the plugin I was using, and activated 2.0.6 of the free version. Rebuilt my groups, and am now successfully able to change between groups or “not assigned” on the Tags page. Issue is finally resolved for me!

(I’ll be in contact separately with the TaxoPress team about updating my license to use the Pro version, I need at least one or two of the Pro features!)

Thanks all, I’m content now with the fix. 🙂

New information from original poster:

I was still seeing this issue reproduce, but then realized that I actually had two versions of Tag Groups in my plugins list, the 2.0.6 release… which was not active… and the premium release that dated back to when this plugin was still owned by Chatty Mango, that was version 1.44.3. 1.44.3 of Premium is what I had active on my site, this is critical info and I should have said so before.

This would, I feel, explain why I was not actually seeing functionality change for me. ;P

I’m going to have to clean up my install of these plugins and see if the issue has cleared up for me. I will report back to this thread when I have done so. Stand by!

• This reply was modified 1 year, 4 months ago by annathepiper.
• This reply was modified 1 year, 4 months ago by annathepiper.
• This reply was modified 1 year, 4 months ago by annathepiper.

Also doublechecked the changes notes on the mod. I’m not seeing anything obvious in the change notes that indicates this issue has actually been fixed yet?

@stevejburge can you confirm if the intention was to release the fix in 2.0.5? Or will that be coming with a subsequent release? Because yeah, I have 2.0.5, and the issue’s still reproducing for me.

• This reply was modified 1 year, 4 months ago by annathepiper.

As per the plugin author’s comment just above, the solution is, it’s a known bug in the last release of the plugin, and it’ll be fixed in the next release.

• This reply was modified 1 year, 4 months ago by annathepiper.

Last update, I think: SUCCESS!

As of tonight I successfully installed the new version of the WordPress MU Domain Mapping plugin, and got the #2 blog on my network, unseeliecourt.annathepiper.org, remapped over to http://www.unseeliecourt.net where I wanted it. 😀

What I had to do to get it to work was:

1) Make sure my Apache vhost file for unseeliecourt.net was pointed to the same DocumentRoot as annathepiper.org
2) Make sure that the domain mapping plugin was pointed at http://www.unseeliecourt.net
3) ALSO edit the site data to change siteurl and home values to http://www.unseeliecourt.net so that my theme could work

So I think the majority of my questions are now resolved to my satisfaction. Thanks much everyone for your assistance and pointing me in the right direction! 🙂

Andrea,

#1 – I don’t need to remap the main blog, just all the subsequent ones. 🙂

#2 – Noted!

#3 – I AM the host! All of this stuff is being done on my own server. 🙂 I just need to know what might need fixing. My Apache vhost file for annathepiper.org hasn’t changed; the ServerName still says http://www.annathepiper.org, and my ServerAlias says “annathepiper.org http://www.annathepiper.org *.annathepiper.org”, now that I’ve set up wildcard subdomains.

Edited to add: Since the forum seems to automatically change www-type links, please to note all references to http://www.annathepiper.org above are actually without the http bit in the front!

Okay, update. Here’s where I am.

I was able to successfully create a test site, as I mentioned, and I spun off a second site on its network and tonight got content imported into it from one of my established sites.

What DIDN’T work was trying to set up the mu-domain-mapping plugin. It complained at me that it had to be installed in the root directory of my web server. I can’t do that on the grounds that I didn’t install this test install of WP 3 there–and I can’t, because there’s an established set of (non-Wordpress) webpages there already that I’m not going to overwrite.

What I’m trying to do instead is build a network off one of my previously established blogs, with its own domain, so that I can use THAT as the web root that the mu-domain-mapping plugin seems to want. I’ll report back if that works.