FlatPress support forum

Hello everyone,

although the FlatPres 1.3.1 Andante release was only launched in April this year, there are already a few improvements and a few new features in the 1.4 developer version. You can find the changelog here. You are cordially invited to feed and test your test system with FlatPress 1.4 dev. Please pay attention to general misbehavior or incorrect translations. The AI of Deepl is not perfect . If there are any anomalies, please let us know here in this thread.

It is known that currently FlatPress 1.4 dev does not work properly under PHP8.4. Therefore, please only use PHP8.3 at most for the time being.
The aim is to recognize and eliminate new errors as early as possible.

To the download: here

With best regards
Frank

Push: If you do not find any errors, please leave 1-2 words here so that we can see how many tests were run and under what conditions.

Have a relaxing weekend
With best regards
Frank

I just downloaded the pre-release version of Flatpress and wrote an entry. Everything went well, no problems in the writing of the article, adding categories or deleting an item in the menu list. What I did notice is that the date of the article is being displayed as November 10, 2024 when it is in fact late evening of October 11, 2024. I am attaching a screenshot to show you what I mean. I am also including a screenshot of the International time settings in the configuration module.

Hello Wineman,

Thank you for reporting. Very thoughtful.

I can reproduce the problem on my test system. Here the day is swapped with the month. The cause seems to be the DateChanger plugin. Although the date format in the toolbar is country-specific, it is also written as a file. However, the format of the file name must remain unchanged entryYYMMDD-HHMMSS. I am looking for a solution.

With best regards
Frank

Hello WineMan,

please download the customized DataChange plugin and copy it to your test system.
The DateChanger toolbar should show the following display logic:
English (US) -> MM/DD/YYYYY
Japanese -> YYYY/MM/DD
Standard format for most European countries: DD/MM/YYYY

The important thing is that when localizing the date format in the DateChanger toolbar, the date of the entry must not be displayed incorrectly.

As soon as you have tested it, post the result here.

Thank you in advance for your help.
With best regards
Frank

fraenkiman wrote: Sat Oct 12, 2024 4:26 pm Hello WineMan,

please download the customized DataChange plugin and copy it to your test system.

datechanger106-dev.zip

The DateChanger toolbar should show the following display logic:
English (US) -> MM/DD/YYYYY
Japanese -> YYYY/MM/DD
Standard format for most European countries: DD/MM/YYYY

The important thing is that when localizing the date format in the DateChanger toolbar, the date of the entry must not be displayed incorrectly.

As soon as you have tested it, post the result here.

Thank you in advance for your help.
With best regards
Frank

Unfortunately, after downloading the new plugin, nothing has changed. It is now showing a published date of 12/10/2024.

Perhaps, I don't know where the DataChanger toolbar is located?

Hello WineMan,

forget version 1.0.6. The error persists there because I didn't think of the plugin_datechanger_check function.

This is the DateChanger toolbar Please test version 1.0.7-dev. The date format of the DateChanger Toolbar should be as follows, depending on the language:
English -> MM/DD/YYYY
Czech, Russian and Japanese -> YYYY/MM/DD
All other European languages -> DD/MM/YYYYY (e.g. for de-de)

With best regards
Frank

Yep, it is working correctly now. Thanks for your help.

BTW, I am running this development version of Flatpress on php7.4.27 if that makes any difference.

Thank you for testing

I have uploaded the correction to the FlatPress repo and noted it in the changelog.

Best regards
Frank

Hello everyone,

The days are short and cold. That's why I'm calling on you to test the current FlatPress 1.4-dev Master branch on PHP 8.4.

What should you pay special attention to?
- PHP error messages
- Incorrect translations
- Unexpected behavior
- Incorrect links
- Downward compatibility down to PHP 7.1
- Correct behavior under PHP with OPcache and APCu

You can find the complete changelog here.

With best regards
Frank