Zugg Software :: View topic

Wizard Joined: 22 Mar 2007 Posts: 2320

I've finally figured out what is consistently changing some of my packages to Read Only. I can't tell whether the problems others have had with Read Only are related.

I start with my session open (online or offline, it doesn't matter). I check all my packages (6 plus the main session package), to make sure that none are Read Only. I click on File|Close Session. Immediately after it is closed, I reopen the same session offline. I check my packages. Two of them are now Read Only. It is always the same two packages, one of them being my main session package. These two packages are the only ones that I have seen this problem with, and it has been recurring since one of the 2.x betas.

If instead of Close session, I click on the X to close CMUD entirely, the packages do not turn Read Only. If I close with Close Session, create a new session, open one of the problem packages, it opens Read Only. If I turn the Read Only status off, remove the package, then reopen the package, it opens with Read Only turned off. If I close the new session with Close Session, then reopen it, the package is again Read Only.

My first suspicion is that somehow these two packages were very slightly corrupted, perhaps by one of the beta versions. But I have tried to fix it by replacing one of the packages--I exported it to XML, deleted the package, created a new package, and pasted the XML. The problem still recurred.

Wizard Joined: 17 Jun 2006 Posts: 1201

What do you mean "pasted the XML"? Are you actually copying and pasting it? You should be able to just import those files you previously exported. I export mine to keep backups in case something goes wrong I can always import the backup XML files.

Wizard Joined: 22 Mar 2007 Posts: 2320

Yes, I copied and pasted the XML. I know I could import it directly.

I see that Zugg has found and fixed a bug related to #CLOSE turning packages Read Only. I'm hoping that it fixes my problem as well.

Posted: Mon Mar 10, 2008 5:29 pm

Keep in mind that the ReadOnly flag is stored in the *.PKG file itself. So once it gets turned on by the Close Session bug, it's possible for it to get stored in the package file. If this package is opened in the new version, it will still show as "Read Only" until you go into the Package Properties and turn off the ReadOnly flag.

Just wanted to clarify how this works this before someone complains that the new version still shows a package as "Read Only".

New version expected later this week.