Le 29/04/11 01:18 PM, Christian Lohmaier a écrit :
I could explain if it would just be some pages, and not others, but
not "works in one browser, but doesn't in other browser".
For ther first one it could have been that it couldn't properly write
the cached copies because it exceeded disk-quota, but then everyone
would have gotten the empty page, at least when not logged in.
So is the browser really the difference? Or are you logged in in one
browser, but not in the other?
Do you have other pages that show the behaviour? Does it make a
difference whether you call it
http://wiki.documentfoundation.org/Main_Page (uses cache) vs
http://wiki.documentfoundation.org/index.php?title=Main_Page (forces
dynamic rendering)?
I'll prune all cached pages, so the first problem should not occur anymore.
ciao
Christian
Thanks. When this happened, I was not logged in, I made sure that all
browsers had cleared caches and cookies. Had it happened only on my
machine, then I would have suspected the problem was my computer setup.
However, other people were having the same problem.
Thanks for the help. Let me know if you would like me to test anything.
Cheers
Marc
--
Unsubscribe instructions: E-mail to website+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/website/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-website] Blank page on wiki (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.