First of all thanks very much for developing Cobalt. It's really revolutionised the speed at which we can edit content and admin settings.

My problem is that I'm seeing that a deleted user is still coming up in the results when using Cobalt. Is this old data cached somewhere and can it be cleared?

thanks

Martin

Comments

Hugo Wetterberg’s picture

Hugo Wetterberg commented

Yeah, there's a lag before updates reaches cobalt, we also got problems when plugin modules are deactivated.
It can be a hassle, I know, but I will probably not put very much effort into the invalidation of the client-side records at the moment.
One solution could be to add the catalogs (nodes, menu, users) as items and create actions for clearing and updating them. The cobalt_nodes plugin node keeps track of nodes that are deleted and removes them from client side databases, this behaviour could also be duplicated for cobalt_users.

Feel free to give it a try (any or both of the solutions), fork cobalt at github and start coding.

Cheers,
/Hugo

Anonymous’s picture

Anonymous (not verified) commented

Update: I noticed that I'm also seeing deleted nodes still being available in Cobalt.

I noticed the cobalt_nodes_deletions table and it has no records. Is that as it should be? In our situation, nodes are either being deleted manually and also within FeedAPI we have nodes being automatically deleted after they are 12 weeks old.

In the meantime, is there an easy way to reset Cobalt so it recreates its index of nodes and users?

thanks

Martin