Warm-up: FlatPress 1.5 - Community Test

[eagleman]

Updated italian files since fp 1.5 rc1 release.
Part 2

[fraenkiman]

Hello everyone,

If I download master from github, can I just save fp-contents from my actual installation and then override all the other files using FTP to get a refreshed FlatPress ?

I recommend deleting the cache and compile directories from the backed-up fp-content directory before copying the fp-content directory to the newly set up instance.

Fraenkiman, I wonder if you're going to publish an RC2 ?

I think there will be an RC2 soon, as some fixes have been incorporated into RC1. First of all, thank you very much for the tests and bug reports.

Updated italian files since fp 1.5 rc1 release.
Part 1

Updated italian files since fp 1.5 rc1 release.
Part 2

Merged with commit 4e6348b.

Best regards,
Frank

[macadoum]

I tried the HTTP header Analyzer from the father of Drupal, Dries Buytaert on my test website and I found something strange.

https://dri.es/headers?url=https://macadoum.free.nf

In several cases, headers are considered missing while I'm still able to find reference of those headers in the fpprotect plugin on github :
https://github.com/flatpressblog/flatpr ... ct.php#L45

Code: Select all

	header('Strict-Transport-Security: max-age=15552000; includeSubDomains');
	header('Cross-Origin-Embedder-Policy: same-origin');
	header('Cross-Origin-Opener-Policy: same-origin-allow-popups');
	header('Cross-Origin-Resource-Policy: same-site');

So those headers shouldn't be considered as missing.

The FP Protect is active on my installation and I don't think it's something from my host as Rainer's test install got the same result : https://dri.es/headers?url=https://foss ... ivkasse.de

I do not know anything about HTTP headers but FP Protect could be misconfigured ?

[fraenkiman]

I tried the HTTP header Analyzer from the father of Drupal, Dries Buytaert ...
...
I do not know anything about HTTP headers but FP Protect could be misconfigured ?

For the headers in the FlatPress Protect plugin, I consulted Scott Helme's documentation (https://scotthelme.co.uk/author/scott/) and cross-checked it with the header analyzer from https://securityheaders.com/.

It is possible that Dries Buytaert's analyzer is no longer completely up to date. Dries Buytaert wrote in 2024: The complexity of the HTTP standard and the challenge to remember all the best practices led me to develop an HTTP Header Analyzer four years ago.

I will take another look at the headers in the FlatPress Protect plugin and see to what extent they are still up to date.

Best regards,
Frank

[eagleman]

Due to an oversight on my part, I forgot to change some sitrings into setup file.
Here is the new file.

[macadoum]

When I publish an entry, and then change my time zone, the entry keeps the previous time in memory. The publish date should be automatically changed too.

It could be nice also to choose the time zone based on my location. Imagine I travel a lot, I should just enter my location like how it is done in this phpbb forum (in user control panel-> Board Preferences) :



If I change my location, all publication times are updated.

[fraenkiman]

Hello macadoum

When I publish an entry, and then change my time zone, the entry keeps the previous time in memory. The publish date should be automatically changed too.
...

That's the bitter pill you have to swallow with a FlatFile CMS.
It would be possible in theory, but performance would suffer. With FlatPress, the creation date/time is stored in the respective entry/comment as UNIX epoch time. In addition, the entries (entryYYMMDD-HHMMSS.txt) and comments (commentYYMMDD-HHMMSS.txt) would have to be renamed. In my test scenario, a wrapper would have to read the UNIX epoch time from each file and add the time difference. Then, for example, 30.000 files would have to be renamed. After that, the corrected time for each entry/comment would have to be assigned to the template. With 3000 entries, each with 10 comments per entry = 30.000 files, it would run into a timeout. And the entry/comment would no longer be accessible -> 404 (/?x=entry:entry251223-142501).

There is already a similar issue.
This will not be feasible.

Best regards,
Frank

[macadoum]

Speaking of 404, if I choose the Pretty Mode in PrettyURL Configuration, I got a 404 error while trying to open an entry from the blog home.

But edit the entry or the blog home page still work.

Tell me what info you might need.

[fraenkiman]

Happy New Year,

Speaking of 404, if I choose the Pretty Mode in PrettyURL Configuration, I got a 404 error while trying to open an entry from the blog home.

Please take a screenshot of the PrettyURLs panel from the admin area.

If there is an .htaccess file in the FlatPress root directory (PrettyURLs panel), I need its contents.

Then I need a screenshot from the “Configuration file for the web server” section of the support plugin (Maintain -> Show Support data).

If an error was logged in the server/PHP error log at the time of access, please also send me the error message.

Best regards,
Frank

[macadoum]

Happy New Year,

Speaking of 404, if I choose the Pretty Mode in PrettyURL Configuration, I got a 404 error while trying to open an entry from the blog home.

Please take a screenshot of the PrettyURLs panel from the admin area.

If there is an .htaccess file in the FlatPress root directory (PrettyURLs panel), I need its contents.

Then I need a screenshot from the “Configuration file for the web server” section of the support plugin (Maintain -> Show Support data).

If an error was logged in the server/PHP error log at the time of access, please also send me the error message.

Best regards,
Frank

I also got an htaccess outside of the htdocs subfolder (my flatpress install is located in htdocs) :

##################################################
#
# DO NOT EDIT THIS FILE
#
# Create a new .htaccess file in your htdocs
# directory (or example.com/htdocs/ directory)
# to add your own rules or override these rules.
#
##################################################


DirectoryIndex index.php index.html index.htm index2.html

ErrorDocument 403 https://errors.infinityfree.net/errors/403/
ErrorDocument 404 https://errors.infinityfree.net/errors/404/
ErrorDocument 500 https://errors.infinityfree.net/errors/500/

Whatsoever, I got no php errors.

Happy new year