After updating to 2.13.0 Build 201302R01 (87) we have a number of issues that have appeared. 1. Our blog has multiple pages but only the first page shows and of the listed postings. all other pages are blank. This occurs on all sections that use the blog functionality like our Press Releases. Out ASPX form pages are displaying with code errors now.
Hi Jerome,
First, I want to let you know that there’s a known bug in CM1 2.13 that affects server-side scripts embedded in HTML widgets (ASPX, PHP, etc.), where certain characters required for the scripts become encrypted. We have been trying to stay ahead of this one, and have highlighted the issue at the top of our Upgrading CM1 page here: http://help.percussion.com/admin-topi…. My apologies that I was not aware that this issue would affect you when I assisted Ben with your upgrade.
This problem will be corrected in our next release, CM1 3.0, which is planned to be made available in two days (Friday, 4/26). The issue should only be triggered when an HTML widget containing this code is opened in an editor. However, once this content has been opened and the error triggered, upgrading to 3.0 alone will not fix the problem; the scripts will need to be manually reinserted into the HTML widget after upgrading for the problem to be corrected.
That being the case, can you tell me if you made a backup of your CM1 filetree and database (or a snapshot of the VM, if applicable) following the 2.10 upgrade portion of your phased upgrade? If so, the simplest way to correct this may be to roll back to 2.10 for now, and then upgrade from 2.10 to 2.13 then 3.0 in one go, being sure not to touch any ASPX content until reaching 3.0.
Regarding your Blog issue, this issue has to do with accessing your blog content within CM1 and is not an issue with your published site, is that correct? Are you trying to access the blog posts through the Blog gadget, or load them directly through the Finder?
I’ll check with Ben on the ASP and Update backup side of things.
Regarding Blog, it is on the published site where we cannot see anything after the first page of content. I can open posts and create new ones fine. It’s the published side that has issues.
Jerome,
Odd, I’m not having trouble viewing your Blog content. Here’s the page I’m looking at: http://www.verint.com/news-events/pre…. Let me know if you’re seeing this issue elsewhere.
The behavior you outlined makes it sound like there was no page meta-data housed in your DTS database when you connected to these pages, which would result in the associated Ajax request pulling back no content. This would be the case if you deployed a new DTS Tomcat server as part of your upgrade process. A subsequent full site publish might have repopulated your DTS database with the page meta-data information.
If you haven’t already, please double check your blog pages and confirm that the content still isn’t showing up for you. If it’s not, as a test can you try accessing http://www.verint.com:9980 to ensure there is no local networking policy blocking traffic to your DTS Tomcat server?
Let me know what you find out regarding the 2.10 backup.
It appears there is some issue with the page in Internet Explorer and not FF or Chrome. I can see the initial listing page and the other two pages of listed content in FF and Chrome but when in IE 8 or 9, I can only see the first page. When I try to click to page two or there the list never repopulates.
I can see the tomcat test page.
Jerome,
My apologies, I had mistakenly thought your were referring your blog’s various press release years, not the pagination at the bottom of your blog lists. I see the behavior you’re referring to. Unfortunately, this is going to be strike two for us today, as this is actually associated with another known bug that I filed surrounding CM1 2.13, where the query made for the pagination links is malformed and doesn’t return any content. Like the scripting issue, a fix for this problem has already been identified and is locked in for our upcoming 3.0 release.
Is Friday an official release date for v3.0?
Hey Jerome,
While we do expect to have 3.0 complete and ready to go by end of day tomorrow, the concurrent marketing and Help site documentation updates may push the public release to early next week.