I was upgrade our OJS from 2.3.1.2 to 2.3.7.0 (April 27, 2012). Possible, after the this upgrade sometimes we see interesting problem.
Our journal within the server roots. And cache and subfolders folder permission writeable.
Mostly, I and our readers complaints for empty main page as "we can not see main page, only seeing blank page".
http://www.neuroquantology.com
we try many times F5 or CTRL+F5 for refreshing but problem is persist.
But If we use direcly journal page, not redirected root, everything is normal and also after the this view, we can go to main root page as page view is normal (possible from cache).
http://www.neuroquantology.com/index.php/journal
Our journal redirected in the "Home > User > Site Administration > Site Settings" to the journal.
And also I see errors in the w3 validation
http://validator.w3.org/check?uri=http% ... ator%2F1.3
Could you suggest any solution?
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Unable to Determine Parse Mode!
The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
the MIME Media Type (text/html) can be used for XML or SGML document types
No known Document Type could be detected
No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.