i just tried testing your interesting package i set up a rule in the config file very basic, just the maxCount nothing else
<add maxCount="5"/>
if my judgement is correct, this should trigger on every docType, since no alias and root node were given.
i then, made some changes over and over again to a certain node, each time republishing if i then open up a roll back menu it says the node has 9 versions to go back to...
i believe that is wrong right? is there a way that i can help debug this problem? for example, if i could see that the before/after publish handler actually kicks in? i'd be glad to help out with more info. let me know if you need anything.
umbraco version: 4.5.2 i'm not sure, but i don't think there are any packages that have handlers active that might block your actions...
You are right in your assumptions in that it should apply to all docTypes, and testing it myself localy that is was I have happening. Can you just confirm your config is exactly:
Then republish entire site. But there are still multiple versions available :-( I also try publish single node using button from UI, but versions are still there.
I've just released a new version which should be comptable with SQLCE. Unfortunatley, due to limitations in SQLCE, UnVersion is a little more chatty than previously (the version before did everything in 1 SQL statement), but it should work. I'll look for way to optimise as soon as I can.
thank you, but I try new version and old versions is still here :-(
Maybe I do something wrong. My config looks like in my previous post. And then I press save and publish. Then I use right click on node and select rollback and there are still multiple versions available. Can I try something else, which can help you to identify problem?
Hmmm... FYI: 1.2.2 isn't working as it should on my 4.6.1 system. I downgraded from 1.3 from advise on codeplex but that made no difference. I tried all of the suggested fixes above; I've set my maxcount to 10 and have many nodes with many more versions.
still 9 versions available
hi,
i just tried testing your interesting package
i set up a rule in the config file very basic, just the maxCount nothing else
<add maxCount="5"/>
if my judgement is correct, this should trigger on every docType, since no alias and root node were given.
i then, made some changes over and over again to a certain node, each time republishing
if i then open up a roll back menu it says the node has 9 versions to go back to...
i believe that is wrong right?
is there a way that i can help debug this problem? for example, if i could see that the before/after publish handler actually kicks in? i'd be glad to help out with more info. let me know if you need anything.
umbraco version: 4.5.2
i'm not sure, but i don't think there are any packages that have handlers active that might block your actions...
Hi Sander,
You are right in your assumptions in that it should apply to all docTypes, and testing it myself localy that is was I have happening. Can you just confirm your config is exactly:
Many thanks
Matt
Hi Matt,
I have same problem, I want to clear old previous versions, so I install v 1.2.2 of unVersion and change config:
Then republish entire site. But there are still multiple versions available :-( I also try publish single node using button from UI, but versions are still there.
I'm using Umbraco 4.6.1 with SQLCE.
Petr
Hi Petr,
I've just released a new version which should be comptable with SQLCE. Unfortunatley, due to limitations in SQLCE, UnVersion is a little more chatty than previously (the version before did everything in 1 SQL statement), but it should work. I'll look for way to optimise as soon as I can.
Many thanks
Matt
Hi Matt,
thank you, but I try new version and old versions is still here :-(
Maybe I do something wrong. My config looks like in my previous post. And then I press save and publish. Then I use right click on node and select rollback and there are still multiple versions available. Can I try something else, which can help you to identify problem?
Thanks
Petr
Hi Matt, can you put sources of modified version to codeplex, please.
Petr
Hey Petr,
Only thing I can suggest, is maybe recycle your app pool so that any config changes get reloaded.
I've pushed the changes through to the codeplex repo, so you can checkout what has changed.
Cheers
Matt
Hi Matt,
I think app pool is recycled automatically, when you put file in bin directory, but for sure I run iisreset and still no efect.
I have not time to try look into sources and debug now :-(
Petr
Hey Petr,
Is you site externally accessible so that I could look at your setup?
Cheers
Matt
Hi Matt,
I put your code into app_code and debug it and I debug to this line:
if(published || newest || readerIndex <= configEntry.MaxCount || (versionDate - DateTime.Now).Days < configEntry.MaxDays) versionsToKeep.Add("'"+ versionId.ToString("D") +"'");When I try it it keep 2 version - first is newest and second is published.
Petr
Hmmm... FYI: 1.2.2 isn't working as it should on my 4.6.1 system. I downgraded from 1.3 from advise on codeplex but that made no difference. I tried all of the suggested fixes above; I've set my maxcount to 10 and have many nodes with many more versions.
is working on a reply...