Version 1.2 has been many months in preparation and has been in beta testing for more than a month.

Release to production clusters and dedicated servers will begin February 07 and is expected to complete before the end of the month.

Please watch your emails for notification of the exact schedule for upgrading your site.

See details about version 1.2.0 features here.

You know I honestly don't understand why my company continues to use infopop. It makes no sense to me why you'd roll out the backend without asking the customer if they want the update. Your update was not necessary for us and it totally rheemed the styles on our forums and chat pages.

Now I'm going to have to spend hours sorting through your stylesheets and basically cloning them while removing sweeping statements like "div {background-repeat: none;}" so the next time you decide to upgrade the backend this doesn't happen. Do we really think it's a good idea to overwrite all div tags in the first place???

argh.

If you are experiencing specific issues related to the upgrade, fill out a support ticket so that Infopop Support may assist you.

That would also be a more appropriate forum to address your specific complaints about the upgrade.

Ron while I appreciate the suggestion I must respectfully say that I don't have time to fill out a support ticket and wait for a response. Our clients and users get mad instantly and they get mad at us.

Also I feel it's important for other people to see what infopop is doing and how it's affecting their users.

The temporary solution for us [and possibly others] is to not allow infopop to insert their css into any of the forums if they're going to use bold code like:

DIV {background-repeat: no-repeat}

...

* {
font-family: Verdana, Arial, Helvetica, sans-serif;
color: #000000;
}

TABLE, DIV, TD, TH {
border-color: #999999;
border-style: solid;
border-width: 0px;}

TD, TH {
vertical-align: top;}

IMG {
border: 0px;}

I'm more disappointed though, that that our community seemed to be inaccessible when I came in to work this morning:

12 fw001.wh01.sea1.infopop.net [63.251.4.7] reports: Destination host unreachable.

It seems I will have to try the trouble ticket route now.

You will get a faster response to your specific issues through the support ticket. They check the queue more frequently than the forums here. (I know from experience, as I have gotten half an hour response times on tickets in the wee hours of the morning).

ParadiseFH -- we'll be happy to work with to make the transition smoother. That's what we're here for.

As for upgrades - it is necessary for perfromance and security to continue to update the code. The style/css changes were made for faster page loading and in 99% of cases have no effct on sites at all. Where they do, we generally can pinpoint the issue and it's a faster fix.

The major update to version 1.2 has to do with performance where there are many messages stored. The trend is toward larger and larger collections of stored messages and the 1.2 architecture handles that significantly better.

I sympathize with the efforts required for updates. We'll try to make that effort entirely worthwhile.

If you'd like to enter a support ticket about the situation and flag it to my attention -- I'll be sure it's handled successfully.