Cache Issue about starter-public-edition-4 HOT 4 CLOSED

I don't understand the case. Could you explain it with more details?

from starter-public-edition-4.

I mean that due to cache written in /platform/writtable/ the exact data
from database is not rendered/display in browser although database is
updated.
Please do let me know how to turn off those cache.

On Sat, Jul 23, 2016 at 4:25 AM, Ivan Tcholakov [email protected]
wrote:

I don't understand the case. Could you explain it with more details?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#75 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF0ktVjihjoqcIEOJUHRk_xY7pKmEqY_ks5qYUbvgaJpZM4JSvQT
.

from starter-public-edition-4.

You did not tell me anything new.

The starter contains "site_example" application that has only a login for and a landing page. There is no code that works with database at all. So, you or somebody else created this admin panel, how can I guess what is going on within it.

• /platform/writtable/ caches different things under subfolders, which one contains the old data or view?
• Do you use a template engine, Twig for example, or you use plain PHP for the views?
• What kind of old data is cached - database query results or rendered templates?
• Where you see the old cached data - within the admin panel or within the fornt-end? If you open the browser development tools, what kind of response code do you get - 200, 307 or something else?

This is what I can say so far.

from starter-public-edition-4.

Send me a private email at [email protected]

from starter-public-edition-4.