Staging seems not logging tasks for some objects after upgrade from 8.2 to 9

Milan Lund asked on April 12, 2016 10:20

Hi, recently I made an upgrade (8.2 to 9) for my client and everything works fine except staging (it was working fine before the upgrade). I am pretty sure that all the basic settings are just fine. At this stage I don't really know where to look on how to fix it. I just went through Devnet Q&A as well as fixed bugs in Hotfixes and nobody seems to have this kind of problem... So I am kindly asking you if anybody has experienced that or just has a clue where to look...

The issue:

After the upgrade I was working on some changes in the website. Updating Custom table data and adding fields, editing templates, CSS, transformations in the development stage. When all the changes were done I just staged all the changes to production. Unfortunately, approx. 90% of those changes got to the production stage and the rest just disappeared. No staging tasks left in the Staging application. To fix that, I had to re-save missing objects in the development stage and synchronize them with production once again.

The only thing that comes to my mind is to re-sign all macros in the System application (There are some CHECKSECURITY MacroResolver errors in the Event log but I am not sure if this might be related to the staging issue). Thanks for any help.

staging

Recent Answers

Chetan Sharma answered on April 12, 2016 12:51 (last edited on April 12, 2016 12:51)

Hi Milan,

I faced this error today. May be for you :)

Please check going to settings -> Versioning & Synchronization -> Object versioning

Look for genral section and make sure "Enable object versioning" is checked and see.

Cant attach screen shot here.

Cheers, Chetan

0 votesVote for this answer Mark as a Correct answer

Milan Lund answered on April 12, 2016 12:58 (last edited on April 12, 2016 12:59)

Hey Chetan,

Thanks for you answer. The checkbox "Enable object versioning" is already checked. However, it doesn't have anything to do with Object versioning rather than Staging in my opinion. As I have stated, all the basic settings should be correct in my case.

Cheers.

0 votesVote for this answer Mark as a Correct answer

Chetan Sharma answered on April 12, 2016 13:20 (last edited on April 12, 2016 13:20)

Hi Milan,

Object versioning and staging modules are inter linked. When you create a new version of an object by saving some template and checking in it automatically become candidate for staging module to put it into queue.

You need to check what all objects are enable for object versioning. If that object is not enabled for object versioning I don't think it will come to the staging queue.

My settings under same directory looks like this

http://pasteboard.co/863GwKG.png

0 votesVote for this answer Mark as a Correct answer

Milan Lund answered on April 12, 2016 13:43

Thanks Chetan. Everything is checked in my case.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on April 12, 2016 14:10

Milan,

In your case I'd say the macro errors you're seeing are probably the culprit to your problem. In every upgrade after I have successfully upgraded the code and database, after I'm able to log in, I check the event log and fix any major issues then I resign all the macros. I've had it where full sections of the Kentico Admin UI were not available because of macro signatures.

If you're not able to re-run the upgrade then I'm afraid the way to stage the items is make a simple change like you're mentioning. Another way is to run an export of the global objects from the Sites app and uncheck everything, then go back and check items in which you want to export and import them into your live site.

0 votesVote for this answer Mark as a Correct answer

Chetan Sharma answered on April 12, 2016 16:05

I agree to what Brenden is saying. if all your above settings are okay then you should definitely re-asign all macros and see.

Let us know

0 votesVote for this answer Mark as a Correct answer