Deleting old blog posts

What version are you using? Try to save and publish that existing blog and see if you get an error, if not, then try to delete it again. If no success, you might have to manually go in and remove the database records if the records are corrupt (which could be the case in an older version). There are several tables in which this needs to happen to make sure this happens properly.

We are on version 8.1 without any hot fixes applied. I am getting errors with that too. Maybe I should concentrate on the hot fix issues and then tackle this issue. I get so many errors it's difficult to know which one to work on first. Any suggestions?

Sam S.

hello sam, did you recently upgrade to 8.1? if so did you go from 8.0 to 8.1 or did you go 7.0 > 8.0 > 8.1? It seems like either a stored procedure or a dll was not upgraded properly during some upgrade or hotfix

We upgraded from v5.x > v8.1 - This all happened before I was hired so I don't know what the process was but I heard a yarn spun about it taking several tries and with a great deal of tumult. Many people were permanently affected here, leaving them with a very poor opinion of Kentico since. I don't share that opinion but I feel like there is a lot wrong with our setup. I am feeling like it is irreparable and that we should scrub the whole thing and start over. When I attempt to apply hot fix 8.1.1 I stop IIS on the server and when I run the Hotfix Utility I get the error, "Failed to connect to the database with "CMSConnectionString" connection string." I'm pretty sure this is because I am logged in as the administrative user and not the principal administrator. We need some serious help but we have exceeded our budget for Kentico already for the year.

Sam S.

Hello Sam, I'm sorry to hear you guys are going through so much. I would recommend at this point to try downloading and installing a fresh install of 8.1; copy the CMS/bin directory from the new instance and overwrite your existing bin directory. It looks like the dll may be an older dll from before Kentico 7 even as that parameter existed in 7 as well.

Depending on how much customization you guys have done to Kentico it may be worth it to export your site from your Kentico 8.1 instance ( if there are no errors during export ) then import it to a fresh instance of 8.1. If you don't have many code customizations this should be viable

Depending on how the upgrades went, there very well could be a faulty procedure as Tim mentioned. If the upgrade failed at any point, it could have very well messed up some other pieces as well. Even the slightest error is issue can turn out to be a big problem later.

When running the hotfix, make sure the website is running in IIS, the update relies on the site to be in a running state. It will put it in an offline mode during the hotfix/update process.

just fixed the same issue, my project was upgraded from 5.5x. The problem is on the page type. I don't know what actual problem. Even through I imported the same blog post page type from a fresh 8.2 copy to overwrite the existing page type. The issue cannot be solved.

What I did is export the project site full copy and import into a fresh installed copy. when you import, please use select only new or uncheck all blogs page types if you would like to overwrite other page types, which would use import the data to a new set of blog page types.

I think this is the safe method to keep all data and use fresh your Kentico CMS. After this, I would think the problem may be caused by the whole set of blog document / page types, which does not upgrade probably along with many versions upgrade. (5.5 > 5.5 sp > 6 > 7 > 8 > 8.1 > 8.2). You may also try to export CMS.Blog, CMS.BlogMonth and CMS.BlogPost from a fresh copy and import to project site to overwrite them. The data will remain the same if there is no fields different. However, you may need to fix the field validation for some fields (I got problem on Post Title field after overwrite the CMS.BlogPost page type, just remove the validation of that field, save, and apply the same validation again will fix the issue of field validation fail when save the page.).

** Remind that, always keep a full backup before any try and fix. Good luck!!