Hi
I have a problem, when I try to empty the site cache in modx manager.
When I click "Empty Cache" the console window opens and it says "console running..." but nothing more. After a few seconds, I can click the ok button.
I’m not quite shure but I think the first time I saw this, was after installing TinyMCE but I’m really not shure.
So far, everything seems to work well but I’m very new to ModX so I’m not shure if this is a problem.
Btw: I changed this morning from 2.0.4 to 2.0.5 but the problem persists.
Any help is appreciated.
Cheers!
Modx 2.1.3, PHP 5.2
This happens to me regularly (even in the current dev. version). It’s been reported, but is very hard to replicate in the developer’s environments.
If you keep trying, eventually the cache will clear and you’ll see the report. My record is 5 times in a row.
If you can remember make it happen, say by following a particular sequence of Manager operations, reporting that would really help.
I think it happens more often after I’ve been working for quite a while in the Manager, but I’m not sure.
Thank you for the reply.
I have to say, that I’m very new to ModX and the whole caching thing is not quite clear to me.
This error happens to me all the time. It doesn’t matter, if I’m working 5 seconds or 5 hours in the manager. Everytime I clear the cache, the console window opens and there is a "console running..." message. What I’m asking myself is, if the cache is deleted and there is only a problem with the message or if there is really a serious problem with the whole caching system in my ModX installation.
Is there a way, I can check if the cache is deleted properly? For a newbie like me, everything seems ok but I would be shure, that there is no serious problem because our website is still in production and we have some time left to fix this issue.
Thank you!
Modx 2.1.3, PHP 5.2
Yes, look in the core/cache directory. If there are any files there in the directories, the cache is not cleared.
You can delete the entire contents of the core/cache directory to clear the cache manually. Be very careful not to delete the core directory by mistake, though!
Are you using FireFox with any add-ons? If so, you could try disabling them one-by-one to see if that clears things up. FireBug is probably a prime suspect.
Most of the time I’m using Coda on a Mac but sometimes also FF with FireBug but the problem appears everytime.
I now deleted the cache manually and now it works. It seams, that one of the files in the cache caused the problem. Thank you very much for your help, Bob.
Cheers!
Modx 2.1.3, PHP 5.2
Quote from: shotup at Dec 15, 2010, 03:40 AM
Most of the time I’m using Coda on a Mac but sometimes also FF with FireBug but the problem appears everytime.
I now deleted the cache manually and now it works. It seams, that one of the files in the cache caused the problem. Thank you very much for your help, Bob.
Cheers!
If only we knew which one.
It sounds like this may be some kind of weird permission problem (as OpenGeek suggested). Although if there were a read-only file in the cache, you’d think it would be hard to delete.
Quote from: shotup at Dec 15, 2010, 03:12 PM
For now, I’m happy that it works again but that helps not so much in solving the problem, I know 
When it happens again, i will delete one folder after another to find out, which one causes the problem.
Or do it one file at a time if you really want to know.
I’m glad it’s working for you now.
I think I’ve found the issue. Apparently unlink is intermittently unreliable in Windows. There’s been some discussion of this in the mysysGit mailing list.
unlink will fail if it thinks the file is in use (and it’s sometimes confused about that).
unlink will fail if it gets too busy.
rmdir will fail if you try to delete a non-empty directory.
I think you will get ERROR_ACCESS_DENIED back in all cases, but you might get ENOTEMPTY or EBUSY.
