Quickedit caching problem

Hello!

I use the Quickedit Plugin for frontend-editing. And i have activated the caching-mechanism. But now following happens (i try to explain the steps):

1. Clearing cache (via FTP)
2. Open homepage of my site (now a new caching site in the caching folder is created)
3. Login into the manager
4. Go to homepage of my site
--> Now i should see the Quickedit button for editing the content. But there is none, because the site was cached before.

Now the other way round:

1. Clearing cache via FTP
2. Login into manager
3. Go to homepage of my site
--> Now i see the Quickedit button (like it should be)!
4. Logout from manager
5. Go to homepage of my site
--> HTML error appears because of Quickedit Tag inside the code:



This seems like a real caching problem to me. But how can i solve this?

Does anyone had the same problem and maybe a solution for it?

Thanks, captain

I have seen the same problem on some sites I’ve been working on...

I found it out when I checked the sites with the W3C XHTML Validator. Looks like it puts the quickedit tag in the cache

yeah, but is this a known bug and will be fixed in the next release?

Or is there a bugfix out there?

So tell me

From what I have read if you log out of the manager these tags will not be there. I guess that the cache does not identify the permission levels and the tags are present to all viewers when you are logged in. The identification seems to be after the cache.

Try validating while not logged in, the tags should not be visible.

I have noticed dissapearing quickedit buttons but have not noticed a pattern. Are you using the 0.9.6.1 release?

Just curious? Why are you clearing cache via FTP? I am not sure if that is a good idea. I use the clear cache button in the manager.

I use version 0.9.6.0. maybe i should upgrade?

i cleared thge cache via ftp, because i did not want to login everytime to clear the cache. But i think, it doesn’t make a difference , because clearing cache means deleting caching files.

(By the way: sorry for my bad english...)

Try to update to 0.96.1, I think it has been solved.