-
Notifications
You must be signed in to change notification settings - Fork 88
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
After time "x" a call lands on an unknown site template #857
Comments
The CSS files get cached by the browser, so in some scenarios you would really need to force-refresh the old CSS out of the browser. |
That's not true. As I said, I deleted all available caches, both on the server side and on the client side. The "templatechooser" plugin I don't use due I like to have only one. |
Ah alright, I misread your statement then, I'm sorry. There are two places where Serendipity puts things:
I must admit I haven't looked at this into ages, but maybe it helps as a pointer :D |
Ty a lot. I will look at; just killing the entrys by hand? |
Every file in templates_c is a cache file that can be regenerated. Should be safe to delete all files (also in subdirs) of that directory. Make a backup for safety though. ;-) |
... but I'll make a backup first ;) |
Looks good so far. I'll keep an eye on it for a few days. If it works then, that's the solution. First of all, thank you very much for your support; you've helped me a lot! |
NOPE :( |
For the backend, a used template might be stored in a PHP session variable IIRC. Did you try to delete cookies so that PHPSESSID gets reset and you might start fresh? Can't research atm as I'm only on mobile. Unsure if serendipity_options DB table held some backend related caching. Maybe @onli remembers more of this? 😅 |
Hi! Great that you could already solve the frontend template issue, though it'd be interesting to know what went wrong there that deleting templates_c helped. That bug of changing templates is new to me. The frontend and the backend template are set separately, I'd wager this is misleading. If the backend design breaks (like in the screenshot) have a look at what is written in the CSS used, serendipity_admin.css. There likely is a PHP error that prevents its output. If the CSS is just an empty file, you would have to look in the PHP error log of your server/hoster for the error message. |
Yep, more than I can count. After every change, I have deleted all available caches and cookies.
You can ask questions ;) I have no idea and can at best read and use a little SQL and PHP... ;)
Where can I find the file respectively, where should it be? Also in the "templates_c" folder? |
Logical thought given the problem solving route so far :) But no, look at it just in the browser, yoururl/serendipity_admin.css (the file is dynamically generated by serendipity). It's linked in the head of each backend page, best to have a look at the html code to get the link. |
LOL You have to say things like that to a dummy like me ;) |
So... Waiting time is over. I call the admin center and got the same broken view. But the css is filled with data. |
You can create a gist, https://gist.github.com/ - but have a look that there is no data you don't want to share in there. But if the CSS data is there, the likely scenario is that the error is intermittent. The design returns after a reload? Then it might have been only missing on the first load. Share the file if possible please, but I'd also suggest you have a look in the PHP error log file to see whether something lines up with time of the page load. |
... I have no idea about gist. I was there and drag&drop the css-output... And now? This?
Yes, that's right. If I then generate a forced reload, the view remains OK until I leave the page for about an hour and then come back. Then it is broken again. Crazy, isn't it?! I can't touch the error-log at my provider. I have open a ticket to ask for read permission. Can take a while... |
Exactly! CSS is there and looks fine to me. I bet it did not load before though. That could be a error in a plugin, or something on the server - let's hope there is something in the log. |
... no idea ... |
@onli In our serendipity.css.php we do have this ETag and HTTP caching logic, so in case the ETag that is sent from the browser to the server matches the hash of the generated CSS, we emit a HTTP 304 header and the cache of the browser should be used. Not sure if meanwhile something in ETag handling and browsers changed, or if a proxy (reverse proxy?) is involved. @EmEiBee Maybe you could edit serendipity.css.php and change this all of this:
just to:
and see if the behaviour goes away. Note that this:
allows the browser to cache the response for exactly one hour. After that a CSS file is allowed to be rechecked, but it seems this ETag handling interfers. However, I find it odd that this is only reported now - I do believe some kind of reverse proxy or local proxy might be mangling the response here. |
Ty for the hint. I have comment it out and the 1st try right now give me the perfect GUI. It's more than an hour since I call it last. That let me hope. So for now many thx for your help. I come back tomorrow and will report |
Cool thanks. Would be interesting if you use either a client-side proxy, or if your webserver is behind a reverse proxy / CDN setup.2 |
Good morning all (muahhh).... About your question: Meanwhile, I have access to the php-log. There are no errors touching the serendipity-installation. Good Morning again... I hate Mondays... |
Hello everyone,
First of all, thank you very much for the nice, easy to install and easy to use blog system. It's exactly what I was looking for!
I have, however, come across a problem that I cannot solve:
If I haven't been on the blog for a few hours (nobody else is using it anyway), the page appears in an unfamiliar look.
At the beginning, of course, I tried out a few different styles, but there were problems and despite deleting all caches (server and client), sometimes this style and sometimes that style was displayed when I called it up.
In the end, I decided on the "Timeline" frontend.
Although this is now the only themefront end, something always appears on the visitor page and in the admin area, but not "TimeLine". Then only a repeated refresh with the SHIFT key pressed helps (complete reload). Even a new installation (--forced) didn't change anything.
The same effect in FireFox, EDGE and Opera.
I don't know if this is a BUG or if I'm just too stupid.
Would anyone like to help me fix this?
Greetz
Micha
EDIT say:
There I can find many entries of frontends that I tried out in the past like t_clean-blog, t_next, t_bartleby, t_chocolate_fudge. Can that be right?
The frontend should be "TimeLine", the backend "2k11" (is there anything else?)
The text was updated successfully, but these errors were encountered: