CMSimple_XH–Forum

Bei mir alles OK.

Danke für den Tipp!
Nicht nur das Leeren des Browser-Caches brachte es,
sondern auch das Umbenennen von xhstyles.css in xhstyles.cs, weil ich nicht weiß/wusste, was das bringt. Diese Datei wurde dann neu geschrieben.

mhz wrote: ↑

Wed Oct 14, 2020 8:59 pm

sondern auch das Umbenennen von xhstyles.css in xhstyles.cs, weil ich nicht weiß/wusste, was das bringt. Diese Datei wurde dann neu geschrieben.

Die Datei xhstyles.css wird von XH erzeugt. Sie fasst die core.css (System) und alle Stylesheet-Dateien der Plugins zusammen um Server-Anfragen zu minimieren.
Wenn du im Stylesheet von Calendar Änderungen vornimmst, wird diese Datei jedesmal neu erzeugt.
XH schaut also immer, ob es irgendwo Änderungen gibt.
Der Download von XH 1.7.4RC1 enthält eine neue core.css.
Da der Download nun aber evtl. schon etwas älter als deine letzte Änderung sein könnte, bekommt XH diese Änderung nicht mit und erzeugt keine neue xhstyles.css. Das ist der Grund dafür, dass man in besonderen Fällen die xhstyles.css per Hand löschen muss.

Danke für die ausführliche Erklärung.
Ich habe nach der Löschung gemerkt, dass die neu angelegte Datei wesentlich größer ist.

frase wrote: ↑

Thu Oct 15, 2020 7:36 am

Da der Download nun aber evtl. schon etwas älter als deine letzte Änderung sein könnte, bekommt XH diese Änderung nicht mit und erzeugt keine neue xhstyles.css. Das ist der Grund dafür, dass man in besonderen Fällen die xhstyles.css per Hand löschen muss.

Würde es helfen, wenn wir hier auch die filectime($ofn) prüfen?

Hi, just tested an installation in ~userdir. Everything fine after setting permissions accordingly.

A small note: Including an empty cmsimple/log.txt may be easier for a new user.

Btw: I hadn't installed cmsimple in a while and the information what permissions are needed was not easily found from
https://www.cmsimple-xh.org/ . If I had not know from the old days, that there are indeed permissions to set, I would have
turned away from a seemingly broken installation. I was presented with *no* error messages, but a completly blank screen with some garbled content found after some scrolling down. May be, if the permissions are not set, "some" warning should be given?

All in all these commands were needed to get a working installation in ~userdir:
touch cmsimple/log.txt
chmod a+w assets/css cmsimple/languages content userfiles userfiles/downloads userfiles/images userfiles/media
chmod a+w cmsimple/config.php cmsimple/languages/* cmsimple/log.txt content/content.htm

Great work, as always! Happy to see cmsimple_xh alive and kicking!

Detlef

cmb wrote: ↑

Thu Oct 15, 2020 2:01 pm

Würde es helfen, wenn wir hier auch die filectime($ofn) prüfen?

Dazu müsste ich wissen, was das ganze phpisch bedeutet.
Ich kann also keine qualifizierte Antwort geben.
Wenn gemeint ist, dass geprüft werden sollte, ob die core.css neuer ist (nicht nur die Plugin-CSS), dann vermute ich, dass das ganz gut wäre.

dsteuer wrote: ↑

Thu Oct 15, 2020 2:03 pm

Btw: I hadn't installed cmsimple in a while and the information what permissions are needed was not easily found from
https://www.cmsimple-xh.org/ . If I had not know from the old days, that there are indeed permissions to set, I would have
turned away from a seemingly broken installation. I was presented with *no* error messages, but a completly blank screen with some garbled content found after some scrolling down. May be, if the permissions are not set, "some" warning should be given?

You are right, information about XH is sometimes hard to find. This is due to the decentralized structure of the OpenSource project - which will be hard to change in the future.
The normal procedure would be to look for installation at https://www.cmsimple-xh.org first. There you will find a link to the wiki for the requirements (https://wiki.cmsimple-xh.org/doku.php/s ... quirements).
There you will find a link to the read and write permissions (https://wiki.cmsimple-xh.org/doku.php/f ... ermissions).
Once you have come so far, you will find the link to the installation where you can find the specific information (https://wiki.cmsimple-xh.org/doku.php/installation).
This is quite funny. A real odyssey.

frase wrote: ↑

Thu Oct 15, 2020 2:43 pm

The normal procedure would be to look for installation at https://www.cmsimple-xh.org first. There you will find a link to the wiki for the requirements (https://wiki.cmsimple-xh.org/doku.php/s ... quirements).
There you will find a link to the read and write permissions (https://wiki.cmsimple-xh.org/doku.php/f ... ermissions).
Once you have come so far, you will find the link to the installation where you can find the specific information (https://wiki.cmsimple-xh.org/doku.php/installation).
This is quite funny. A real odyssey.

At least you proved the existence of a path to the relevant docu.

My point is: on https://www.cmsimple-xh.org (which looks really great btw), there is no mention of file permissions at all. So a new user
running into this has no clue what went wrong.

Maybe add under point "3. Watch" the following at the end "If the page looks somehow broken, chance is you have to check on some file permissions, see https://wiki.cmsimple-xh.org/doku.php/f ... ermissions"

A nice solution imho to this hen-and-egg problem is implemented in flatpress, which shows a page with permission hints at first run.

dsteuer wrote: ↑

Thu Oct 15, 2020 4:39 pm

[...]
A nice solution imho to this hen-and-egg problem is implemented in flatpress, which shows a page with permission hints at first run.

Well, good suggestions.
Actually, after an installation in admin mode, you should call the item Settings -> Info. Then you will get some very useful hints.
If we need another pre-check, we can discuss here. I am not sure about that.