Differences

This shows you the differences between two versions of the page.

--- en:doc:basic:troubleshooting [2023/02/27 22:00] – [E-mail delivery failed] non-ASCII lines in the e-mail header fraenkiman
+++ en:doc:basic:troubleshooting [2024/03/28 02:10] (current) – [Incorrect date and/or time] fraenkiman
@@ Line 4: / Line 4: @@
 ===== Case of error: =====
+  * [[en:doc:basic:troubleshooting#the_directory_fp-content_is_not_writable|The directory fp-content/ is not writable]]
   * [[en:doc:basic:troubleshooting#the_theme_is_displayed_incorrectly|The theme is displayed incorrectly]]
   * [[en:doc:basic:troubleshooting#instead_of_the_flatpress_blog_an_error_is_displayed_in_the_browser|Instead of the FlatPress blog, an error is displayed in the browser]]
+  * [[en:doc:basic:troubleshooting#incorrect_date_and_or_time|Incorrect date and/or time]]
   * [[en:doc:basic:troubleshooting#e-mail_delivery_failed|E-mail delivery failed]]
+==== The directory fp-content/ is not writable ====
+Grant the directory fp-content/ the access rights (File permissions 0666, Directory permissions 0777). By default, the owner is www-data.
+Hint: [[https://filezilla-project.org/|FileZilla]] is a great free FTP tool for this task.
@@ Line 19: / Line 28: @@
   - Check the security settings of the device used.
   - If the device is using a VPN tunnel, disable the VPN for testing.
+  - If you are hosting yourself, check your network configuration. Disable public and local IPv4 for testing.
+  - If you host yourself and use [[https://en.wikipedia.org/wiki/HTTPS|https]] for FlatPress, make sure that the [[https://letsencrypt.org/|certificate]] is issued for your domain.
 If the theme continues to display incorrectly, check if the problem is reproducible with another device.
@@ Line 36: / Line 47: @@
 ** Carry out the following actions one after the other and check after each action if the problem has been solved. **
+  - If you are not using the Leggero theme, make sure that your theme is [[doc:tips:smarty2to4|Smarty4 compatible]].
   - Make sure that the internet connection the device is using is not disrupted.
   - If the device is using a VPN service or tunnel, disable the VPN for testing.
@@ Line 42: / Line 54: @@
   - Make sure that mod_rewrite, mod_headers, and GDlib are installed on the web server.
   - Check that all FlatPress files are in the correct directory on the web server – ideally in www-root.
-  - Check that all ownership- and access rights are set correctly. By default, the owner is www-data. The FlatPress files and directories are on 0777.
+  - Check that all ownership- and access rights are set correctly. By default, the owner is www-data. The FlatPress files 0666 and directories are on 0777.
   - Check if a .htaccess file is present on the webserver. If so, rename them test-wise.
   - Check for anomalies in the log files of the web server, e.g. syslog, error.log.
@@ Line 51: / Line 63: @@
 If the problem persists and you were unable to perform some actions because you are not hosting yourself, other causes may be the hosting provider.
+==== Incorrect date and/or time ====
+My self-created static page or entry has the wrong date/time.
+** Carry out the following actions one after the other and check after each action whether the problem has been resolved. **
+  - Check in the admin area in the Configuration menu -> International settings whether the UTC is displayed correctly.
+  - Check in the admin area in the Configuration menu -> International settings whether the time offset is correct.
+  - If you run your own web server, make sure that your web server has the correct UTC.
+  - If you run your own web server, make sure that the [[https://www.php.net/manual/de/timezones.php|correct time zone]] (e.g. ''date.timezone="Europe/Berlin"'') is entered in php.ini.
+**Note 1:** FlatPress cannot distinguish between winter and summer time. Either the web server takes over this task or you have to correct the time offset in the admin area in the Configuration menu -> International settings.
+**Note 2:** If the entry was initially saved as a draft and is only published later, this entry will bear the date/time when the draft was saved. ([[https://github.com/flatpressblog/flatpress/issues/66|#66]])
+If the problem persists and you were unable to perform some actions because you are not hosting yourself, other causes may be the hosting provider.
 ==== E-mail delivery failed ====
@@ Line 65: / Line 92: @@
 error_reporting(E_ALL);
 $recipient = "your-mail-server@domain.ltd";
-$subject = "test e-mail";
+$subject = "Subject with non-ASCII characters: ÖöÄäÜüó¿¡á";
 $from = "From: Sender <your-mail-server@domain.ltd>";
 $text = "The e-mail was sent successfully";
@@ Line 79: / Line 106: @@
   * Make sure your mail server uses authenticated mail delivery – with secured SMTP and SMTP authentication.
 	Reason:
-	Emails sent directly from the PHP-mailer end up easily in spam as unauthenticated mails or are not forwarded or separated by mail servers as suspected spam.
+	Emails sent directly from the PHP mailer easily end up as unauthenticated emails in spam or are not forwarded by mail servers or are sorted out as suspected spam.
-	In addition, it may happen that the web server (e.g. Shared Webhosting) is hosted on the FlatPress and is blacklisted for e-mail.
+It can also happen that the web server (e.g. shared web hosting) is hosted on FlatPress and is blacklisted for email.
   * If you are sending emails via a mail provider (mail-relay), make sure that “third-party programs” (your mail server) are allowed to access your mail account.