weird behavour with db changes by hand

[b0n3m4n]

Hello!

I just spent a few hours over a problem that I just couldn't explain. Maybe someone can clear it up for me?

Whenever I access the cms database directly to apply changes to my website contents these changes do not appear on the website immediately. I can even go so far as to drop the complete cms_content_props table without any error in my website.

Only when I use the admin page to show the corresponding content I can see the changes. And when I submit the changes via the admin page then finally everything shows up on the website.

This behaviour seems very weird to me. My first guess was that there might be file copies of parts of the db for performance reasons but so far I couldn't find any.

I am using direct db access to migrate old data to a newly set-up cmsms so I don't really want to use the admin page to confirm each and every page of my contents.

Any ideas?
Thanks in advance.

EDIT: Uh, using cmsms 1.1

[RonnyK]

Some changes are only visible after doing a "clear cache" in "Global Settings". I think some "old" data was stilll available under the temp-directory of the CMS, and only got visible after, changes in the backend/clearing cache as it gets touched then.

Ronny

[b0n3m4n]

Cheers!

That was exactly it! Thanks a lot.

--
Cerno