Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache Issue #75

Closed
krishnaguragain opened this issue Jul 22, 2016 · 4 comments
Closed

Cache Issue #75

krishnaguragain opened this issue Jul 22, 2016 · 4 comments

Comments

@krishnaguragain
Copy link

Hello @ivantcholakov ,
Currently i am doing one project on it. When I have added data from back-end(administrative) panel , data is successfully submitted to database but mean while reading from the database due to cache in platform/writable (WRITABLEPATH) it is not showing over browser, Please help me here how to turn off all those cache.
CI_VERSION = 3.0.6
PLATFORM_VERSION = 4.0.128

@ivantcholakov
Copy link
Owner

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

@krishnaguragain
Copy link
Author

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 notifications@github.com
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
.

@ivantcholakov
Copy link
Owner

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.

@ivantcholakov
Copy link
Owner

Send me a private email at ivantcholakov@gmail.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants