Pixelbart

@jdembowski I get it. I would never publicly ask for access data here. Otherwise it is so regulated in Germany anyway that I would have to send a contract first because of the GDPR. So even if I would ask times for access data, a contract would have come before. At it I hold myself naturally, simply because I would like that myself also to the security.

Thank you for your information!

@ubcsecurity That’s great to hear! I’m happy that Helpful is running with you now. If there is anything else, just let me know again.

@ubcsecurity This should be fixed with version 4.0.10 for you. If I forgot another array and you notice something, feel free to comment again!

Many thanks for your help!

@wegerl

Danke für dein Feedback!

Eine Einstellung dafür gibt es nicht, weil das jedes Plugin für sich selbst regelt und es für jedes Plugin anzupassen (bei der Masse an Plugins) für mich fast unmöglich ist. Aber du kannst Helpful in den Einstellungen -> Details -> Allgemein -> “Helpful im Post-Content ausblenden” für Beiträge ausblenden. Wenn du das gemacht hast, kannst du folgendes in die functions.php deines Themes packen:

add_filter( 'the_content', 'custom_helpful_content', 1 );
function custom_helpful_content( $content ) {
     return $content . do_shortcode( '[helpful]' );
}

Die 1 in der add_filter() Function gibt an, dass Helpful möglichst als erstes nach dem Inhalt eingebunden werden soll. Wenn jetzt alles gut geht, sollte Helpful immer direkt nach dem Inhalt erscheinen. Wenn Plugins von sich aus auch die erste Position wählen, dann verschiebt sich Helpful eventuell wieder und dann lässt sich das Problem leider nicht lösen.

Falls du das WordPress Theme nicht bearbeiten kannst weil es z.B. kein Child-Theme ist oder weil du es vor Updates schützen möchtest, habe ich hier eine Anleitung für das Erstellen eines Plugins geschrieben:

Wie du Änderungen an deiner WordPress Seite vornimmst, ohne das Theme zu berühren.

Dort in die Hauptdatei (im Beitrag heißt die Datei custom-functions.php) dann den Code von mir oben einfügen.

Zusatz:

Ich habe gesehen, dass du ein Child-Theme verwendest. Also kannst du den Code auch einfach ans Ende deiner functions.php packen. Diese findest du mit Hilfe von bspw. FileZilla oder dem Theme-Editor unter Design (wp-admin oder deine-seite.de/wp-admin/theme-editor.php) hier: .../wp-content/themes/twentyfourteen-child/functions.php

Ich hoffe ich konnte dir helfen.

Einen schönen Abend noch!

• This reply was modified 6 years, 10 months ago by Pixelbart.
• This reply was modified 6 years, 10 months ago by Pixelbart.
• This reply was modified 6 years, 10 months ago by Pixelbart.
• This reply was modified 6 years, 10 months ago by Pixelbart.
• This reply was modified 6 years, 10 months ago by Pixelbart.
• This reply was modified 6 years, 10 months ago by Pixelbart.
• This reply was modified 6 years, 10 months ago by Pixelbart.
• This reply was modified 6 years, 10 months ago by Pixelbart.

@anefarious1 That’s correct. Helpful was previously a little buggy. With the update all found old entries will be added to the database. You would then have to delete them again manually. (recycle bin symbol)

@anefarious1

4.0.8
– he maintenance procedure in the Helpful settings, which can be found there under System, now also checks whether the database tables exist and creates them if they do not exist.
– FAQ updated

I hope this solves the problem.

@larissakeepmake Perfect! The space should be fixed with one of the newer versions.

@ubcsecurity

I can’t reproduce these errors and other users don’t seem to have these errors either. WordPress itself now needs a higher version.

Since I can’t support every PHP version and always try to program safely, I use more recent versions.

I fixed the error with the table and also the checks of the post type array, as you can see in your example. There it is correctly queried if it is an array.

The database table is created automatically when performing maintenance or updating the plugin.

If you have such problems with the plugin, you are welcome to try other plugins. I don’t force anyone to use my plugin here.

If you come up with solutions for your case, please feel free to tell me. Personally I don’t see any mistakes there.

Nevertheless as always: Thank you for your feedback!