Letzte Aktualisierung: 14. Januar 2023 um 21:36 Uhr
Sodele, #Echtma hat alle wichtigen Funktionen bekommen, aber etwas fehlt noch.
Vieles hab ich ja gestrichen, weil ich den Sinn ernsthaft hinterfragt habe. Es fehlt jetzt nur noch eine wichtige Funktion – die, die euch auf dem laufenden hält. Von den #Feeds hab ich ja Abstand genommen und ein E-Mail-Abodingens als vielleicht besser erachtet. Da ist die #DSGVO die größte Hürde und so wirklich mag ich mich mit dem Mist nicht auseinandersetzen.
Da wieder #Kommentare möglich sind, frag ich einfach mal in die Runde – was mögt ihr eigentlich mehr? Eine #Mail, wenn hier was passiert, die, wenn man Pech hat, auch noch im Spam landet. Oder holt ihr doch lieber #Feeds ab? Da ich die #Feeds ja recht klein halten kann, sollte der Traffic kein Problem sein. Die meisten der “Contentausleiher” greifen ja in der Zwischenzeit eh ins Leere – die waren bei mir ja durchaus schon problematisch.
Auch wenn ich gestern noch ganz sicher war – ich mach keine #Feeds mehr – sind die aber wohl doch die bessere Wahl. Das Thema war ja auch im Forum von FlatPress auf dem Tisch und Arvid hat eigentlich die passende Frage gestellt – Warum das Rad zweimal erfinden? Recht hat er…
Die Datenbank habe ich ja ohnehin schon auf Beitragsbeschreibungen eingestellt. Dafür habe ich mir einen begrenzten Platz in der Datenbank reservier – mehr als 160 Zeichen gehen da nicht rein und es ist auch ein anderer Text, als im Beitrag selbst. Ich laufe also nicht Gefahr, das die Feeds als doppelter Content gewertet werden. Also werden es vermutlich doch wieder Feeds, oder besser ein Feed? Ach – ich weiß es nicht.
Was meint ihr?
Ich hab mal eine kurze Nacht drüber geschlafen und mich gegen die E-Mails entschieden. Es gibt ab sofort 2 RSS 2.0 – Feeds, einen für neue Beiträge und einen für neue Kommentare. Bei den Kommentaren kommt ihr durch einen Klick auf den Namen des Autors direkt zum entsprechenden Beitrag. Sollte der Kommentar auf einer statischen Seite (Startseite, Suche, Impressum und was es alles gibt, so werden diese auch auf allen “nicht Beitragsseiten” angezeigt.
Huch, hab beim Kommentar-Feed das Datum vergessen. Das wurde mal berichtigt.
Since I am the one that started the forum post about email notifications, I am sorry that you have decided not to have email notifications, although I understand your reasoning. Having used other blog systems with email notifications, I never had a problem with the emails ending up in the spam folder and to me, it is the best way to keep the reader engaged in the blog. While I understand yours and Arvids position, I am still trying to figure out how it can be done. As always, thanks for your input…I really enjoy reading your blog.
In theory, of course, its the more comfortable way for the reader. The reader gets an email when there is a new comment. But – for this the user must first deposit his email address and the system must query these. Then this mail is simply sent via PHP and thats it. My problem with this story: I have to save email addresses, but thats exactly what I dont want. For me, that just means overcoming the GDPR hurdles, which wouldnt necessarily be a problem either. But what if the software I created has a security hole somewhere and someone can read the saved email addresses? Or even worse – was malware or phishing mails then sent via my mail function? No, I dont want to take that risk at all. Thats why I offer an RSS feed again and also show the last comments on the right. So nobody has to miss anything ,)
I understand your hesitation to deal with the GDPR issues and respect your decision to not provide an email notification. At this point, I have it all set up…I collect the emails and I have a file that generates the email notification if I enter the file name in the address bar. What I am trying to figure out is how to have the email notification sent out automatically once the blog article is published and saved. Thanks for your response.
At the point where the contribution is saved (action from the form) it would then have to be queried who has subscribed to everyone and then send the mails. But I might have another idea. How about e.g. one newsletter per week or month. Your readers could subscribe to this and you then write it yourself with references to activities on your site. It would be a little more work for you (just write a newsletter yourself), but the effect might even be a little more personal. You could then send the newsletter via any external service without having to change the blog (apart from a link to subscribe to the newsletter).
I had thought of a newsletter option and I might end up doing that in the long run. I just want to see if I can figure out how to send the email notification automatically.
After saving the post just send the mail to the desired addresses. I cant say exactly where this has to go, it always depends on the system used. See https://www.php.net/manual/en/function.mail.php for the code to send mails.
The email notification is being sent if I go to address bar and enter the url with the file name that sends the email…what I am trying to do is get the email sent automatically when the blog post is saved and published. I have used the include tab pointing to the file, but that is not working.
You also pass all necessary variables to the script correctly ($_POST or $_GET or whatever?)
As you have probably figured out by now is that I am not a good coder…what I have done is tried to add an include tag in the location of the core.entry.php file (line 721) to point to the relative path location of the file generating the email notification. If I manually enter the url address of the file generating the email notification, the email notification is being sent correctly with a link to the blog post. I wouldnt know where/how to pass the variables you describe. The file I am pointing to is in a folder under the flatpress folder as follows: flatpress notification/email_notification.php The core.entry.php file is located flatpress fp-includes core/core.entry.php
I understand and yes, I thought that the programming skills are not very good (I would call my own amateurish). That’s why I had the idea for the newsletter. Well – I don’t know if we can both get this together, but you can try. You call your notification function as an include ( include(‘./flatpress notification/email_notification.php’); <- matching your FlatPress path). This should then work exactly as if you called the file directly - otherwise the path is probably wrong. In order to easily check this, you could simply build a small screen output into the email_notification for testing (e.g. echo 'Email notification was called';), then you would see somewhere on the page that the function for the notification is already active was called - if there is nothing there, the path is wrong, if the text is somewhere, we have to find out where it is stuck. But what I'm wondering is: how does the function know which post it is if the correct URL is transmitted and the file is called up directly? And how does the script know who should get the email? But we can take care of that later.
I made a mistake in showing the paths. flatpress/fp-includes/core/core.entry.php flatpress/notification/email_notification.php The email addresses are added to a text file using a subscription form…that is working just fine. The email notification file checks another text file that contains the titles of the blogs posted and compares the content of the file each time the file is generated. If no new blogs have been posted, no email is sent. There is already a screen output that would show if the email has been sent…nothing is being shown so evidently I dont have the correct path listed. The path I am using is ./flatpress/notification/email_notification.php I cobbled the script together using the code in the url listed below. https://www.formget.com/php-newsletter/ I appreciate your willingness to help.
If paths are correct, then it must be somewhere in your tinkered script. Unfortunately I cant really help there.