Thanks, nant.

I'm down to just the second issue. I installed the latest CB language plugin (not the CB Subs language plugin, which was already the latest) from the forge (the one I was using was a couple months old), and that apparently solved the first problem. I'm not sure why, because they're both CB 2.0 language plugins. But the first string now reads "13 June 2014 - 31 March 2015 Expired 03/31/2015" as it should.

The second problem remains. As you suggested, I tried changing the Price display from [AUTOMATIC} to either [PRICE][FOR][PERIOD] or a non-breaking space character, but it didn't affect the display at all for either string after clearing caches, etc.

Right now, both the back end and the front end still show "Reactivate: $115.00 per calendar year starting UNHANDLED FORMAT IN CBPTxt::Tdate: F j" in the reactivation button. It should say "Reactivate: $115.00 per calendar year starting April 1" It also displays that way in the back end for every available plan in the user's membership tab at the select radio button. The date it's formatting must come from the CBSubs --> Plan --> Pricing tab in the "Start date of calendar year" field, which now reads "04-01".

I think this isn't a language problem but is something else. I'm not sure what to try next on that one or how to diagnose it. CB says that all of my plugins are up to date.

The offending formatting is definitely coming from the CBSubs --> Plan --> Pricing tab in the "Start date of calendar year" field, as I mentioned in the last post. If I change that field to "01-01", the reactivation button will correctly show "Reactivate: $115.00 per calendar year". If I change that field to anything else, it shows "Reactivate: $115.00 per calendar year starting UNHANDLED FORMAT IN CBPTxt::Tdate: F j" in both the front and back ends.

Should I be looking at whatever program formats that field? Again, it was fine in CB Subs 3.0. I really can't make the move to CB 2.0 unless I can figure this one out.

Hi, Kyle. Yes, that's the format I'm using. Earlier in the thread, I mentioned that the formatting was failing using "04-01", and it works great in CBSubs 3.0. It's the upgrade (perhaps incompletely done on my part if you experience this nowhere else), not the value in the field, that causes the error. However, my post was intended to indicate that that field is definitely where the error occurs, and whatever code is formatting it currently can't do it.

But yes, I've always used MM-DD.

Note: the installation does state that all CB Plugins are properly updated. But something must not be.

Thanks for the help!