Title: 3UU's Replies | WordPress.org --- # 3UU [ ](https://wordpress.org/support/users/3uu/) * [Profile](https://wordpress.org/support/users/3uu/) * [Topics Started](https://wordpress.org/support/users/3uu/topics/) * [Replies Created](https://wordpress.org/support/users/3uu/replies/) * [Reviews Written](https://wordpress.org/support/users/3uu/reviews/) * [Topics Replied To](https://wordpress.org/support/users/3uu/replied-to/) * [Engagements](https://wordpress.org/support/users/3uu/engagements/) * [Favorites](https://wordpress.org/support/users/3uu/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 114 total) 1 [2](https://wordpress.org/support/users/3uu/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/3uu/replies/page/3/?output_format=md) … [6](https://wordpress.org/support/users/3uu/replies/page/6/?output_format=md) [7](https://wordpress.org/support/users/3uu/replies/page/7/?output_format=md) [8](https://wordpress.org/support/users/3uu/replies/page/8/?output_format=md) [→](https://wordpress.org/support/users/3uu/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] Version 4.6.17 crashed site](https://wordpress.org/support/topic/version-4-6-17-crashed-site/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 hours, 13 minutes ago](https://wordpress.org/support/topic/version-4-6-17-crashed-site/#post-18910171) * Please try 4.6.22 and let me know if do you still find any problem. BTW: Noop, I do for shure not write code with AI. But I often found it helpful for refactoring tasks of code I dont have developed myself in the past. On one hand automated bug reports created with AI by people how dont really understand the code are a really waste of time. And with a 1-man-project the (spare) time is a key factor. Please have in mind that this plugin has been coded on holidays because I was bored 🙂 It never has been intended to become as big. But on the other hand over the last 12 month I worked often with AI (many different models and implementations) to check old code losts its maintainer long time ago. And I found the input often very helpful. Suggestions often have been on the level of a junior developer, often complete nonsense… but also often found parts that should have been fixed years ago. And it founds much more critical parts that has been fixe than it lead me to false asumtions. But it has for shure an impact on how we write code. So I think it is a question of good manners to let people know that these tools had have influance on the process. If do you check all the changes we made you will find that it has been a good idea to use it for the refactoring we should have done long ago. So I hope, you will not lose your hope. There are still people in the bunker working with vi and brain 😉 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] Upgrade 4.6.15 to 4.6.18 removed sharing buttons; serialization shariff3uu_basic](https://wordpress.org/support/topic/upgrade-4-6-15-to-4-6-18-removed-sharing-buttons-serialization-shariff3uu_basic/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [2 days, 19 hours ago](https://wordpress.org/support/topic/upgrade-4-6-15-to-4-6-18-removed-sharing-buttons-serialization-shariff3uu_basic/#post-18908527) * Probiert mal bitte, auf die aktuelle Version 4.6.22 zu updaten. * Wir haben im Rahmen eines notwendigen Bugfixes auch einen generellen code review gemacht. Dabei hat sich herausgestellt, dass wir an einigen Stellen staerkere type-Pruefungen machen sollten. Leider hat das dazu gefuehrt, das einige bestehende Einstellungen nicht mehr akzeptiert wurden. Das ist jetzt insofern behoben, dass erneutes Speicher die korrekten Werte neu setzt und gleichzeitig mit dem Update auch eine Migration dieser Einstellungen von < 4.6.15 automatisch erfolgt. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] security vulnerability](https://wordpress.org/support/topic/security-vulnerability-139/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [1 year, 11 months ago](https://wordpress.org/support/topic/security-vulnerability-139/#post-17829999) * If do you follow the CVE links you will end up [https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3069111%40shariff%2Ftrunk&old=3061040%40shariff%2Ftrunk&sfp_email=&sfph_mail=#file1](https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3069111%40shariff%2Ftrunk&old=3061040%40shariff%2Ftrunk&sfp_email=&sfph_mail=#file1) As you can see with the code changes version 4.6.13 has addressed this issue. However I would recommand to use the recent 6.6.14 because there is an other fix (more importand!!!) to the share count api. So please update. BTW: Please also open the admin page within WP because this will do some “self healing” to to option if needed. Update to 4.6.14, open the admin page, save it and you are done 😉 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] Error in WP 5.5: “register_rest_route was called incorrectly”](https://wordpress.org/support/topic/error-in-wp-5-5-register_rest_route-was-called-incorrectly/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [5 years, 4 months ago](https://wordpress.org/support/topic/error-in-wp-5-5-register_rest_route-was-called-incorrectly/#post-13885201) * Ich kann es aktuell leider nicht testen. Aber koenntest Du mal in der wp-content/ plugins/shariff/shariff.php an Zeile 195 ein * ‘permission_callback’ => ‘__return_true’, * einfuegen. Der Code sollte dann inentwa so aussehen * ``` array( 'methods' => 'GET', 'callback' => 'shariff3uu_share_counts', 'permission_callback' => '__return_true', 'args' => array(... ``` - This reply was modified 5 years, 4 months ago by [3UU](https://wordpress.org/support/users/3uu/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] W3C](https://wordpress.org/support/topic/w3c-6/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [9 years, 7 months ago](https://wordpress.org/support/topic/w3c-6/#post-8233685) * Hm, zu diesem “W3C-Fehler” stehe ich jetzt vielleicht auf dem Schlacuh, aber die Elemente sind imho ordentlich im fieldset-Block drin. Und werden ja auch genutzt, um nicht plausible Eingaben zu markieren. Und Browser-Unterstuetzung ist laut [http://www.w3schools.com/tags/tag_fieldset.asp](http://www.w3schools.com/tags/tag_fieldset.asp) auch ganz gut. Ich waere da jetzt eigentlich nicht sonderlich motiviert, diese Funktionalitaet rauszuwerfen, nur weil der W3C parser damit nicht klar kommt. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] Set Language](https://wordpress.org/support/topic/set-language-4/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [9 years, 8 months ago](https://wordpress.org/support/topic/set-language-4/#post-7723001) * Sorry but I do not really see what problem does this solve??? Please have in mind the we have to find one of the translations supported by the form. And we are looking for the language that the _client_ supports. Because I often have seen browsers in English versions used by staff that does not speak this language… we first try to use GeoIP. If this fails the http_negotiate_language functionality is imho the next best choise. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] Shariff-Buttons neben RSS-Button im Widget](https://wordpress.org/support/topic/shariff-buttons-neben-rss-button-im-widget/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 years, 3 months ago](https://wordpress.org/support/topic/shariff-buttons-neben-rss-button-im-widget/#post-6853982) * Version 3.4.0 hat jetzt auch nen RSS-Button. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] Extend: add option to use external shariff service](https://wordpress.org/support/topic/extend-add-option-to-use-external-shariff-service/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 years, 5 months ago](https://wordpress.org/support/topic/extend-add-option-to-use-external-shariff-service/#post-6752007) * So, denn externen backend-host gibt es ja nun schion ne Weile. Natuerlich erstmal nur per Konfigurations-Vriable auf dem Backend. Aber ich denke, wenn sich da nicht riesen Badarf kuenftig hier meldet, dann lassen wir das auch erstmal so in ich setze das hier mal auf resolved 🙂 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] How to hide it on certain custom post types?](https://wordpress.org/support/topic/how-to-hide-it-on-certain-custom-post-types-1/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 years, 5 months ago](https://wordpress.org/support/topic/how-to-hide-it-on-certain-custom-post-types-1/#post-6476441) * With version 3.3.2 there is a dynamic generated list of all used custom post types. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] Facebook Counter Version 3.3.1](https://wordpress.org/support/topic/facebook-counter-version-331/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 years, 5 months ago](https://wordpress.org/support/topic/facebook-counter-version-331/#post-6855577) * Version 3.3.2 mit dem Fix von JP habe ich gerade online gestellt. Probier bitte mal. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] Timeout issues](https://wordpress.org/support/topic/timeout-issues-1/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 years, 5 months ago](https://wordpress.org/support/topic/timeout-issues-1/page/2/#post-6553876) * I had have spoken with the WP plugin support team and they also can not find these files in the repository. Strange. But if it fixed now I think this was a temporarily problem at the server that we can not solve. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] Timeout issues](https://wordpress.org/support/topic/timeout-issues-1/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 years, 5 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553873) * There are no pot-files in the plugin. Please have a look at [https://plugins.svn.wordpress.org/shariff/trunk/](https://plugins.svn.wordpress.org/shariff/trunk/) However I have an idea of what it could be. Do you have an multi-language plugin installed like “CodeStyling Localization” or do you use “WPMU”? These tool try to check all strings in a new/updated plugin and use po/pot-files. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] wrong domain error](https://wordpress.org/support/topic/wrong-domain-error/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 years, 5 months ago](https://wordpress.org/support/topic/wrong-domain-error/#post-6781902) * In Version 3.3 wird es die Option fuer eine “exteren Server” geben. Der zieht sich CSS, JS und counter von einem “externen” Server. Auf diesem kannst Du dann auch ein Array mit saemtlichen erlaubten Domains anlegen. Das behebt schonmal den “Wrong Domain”-Fehler. * Wenn Du natuerlich lokal entwickelst, macht es keinen Sinn, alles vom externen Server zu laden 😉 Dann einfach in Deiner lokalen Installation das Backend direkt im Shariff-Tag eintragen. * 3.3 braucht aber noch was an Tests. Du kannst Dir die Entwicklungsversion aber natuerlich auch jetzt schon von Github [https://github.com/3UU/wordpress-shariff-wrapper/](https://github.com/3UU/wordpress-shariff-wrapper/) holen. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] problems with wp in sub-folder](https://wordpress.org/support/topic/problems-with-wp-in-sub-folder/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 years, 6 months ago](https://wordpress.org/support/topic/problems-with-wp-in-sub-folder/page/2/#post-6487679) * Oh, I see. I will have a look into it. I think fixed version will be online on Saturday. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shariff Wrapper] problems with wp in sub-folder](https://wordpress.org/support/topic/problems-with-wp-in-sub-folder/) * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 years, 6 months ago](https://wordpress.org/support/topic/problems-with-wp-in-sub-folder/#post-6487677) * Aua, you are right. Not sure why I did not see it at the review 🙁 However in function * `rsearch($folder, $pattern) {` * I do not see why * ``` $dir = new RecursiveDirectoryIterator($folder); $iterator = new RecursiveIteratorIterator($dir); $files = new RegexIterator($iterator, $pattern, RegexIterator::GET_MATCH); ``` * is needed. Would * `$iterator = new RecursiveIteratorIterator($folder)` * not work too? Viewing 15 replies - 1 through 15 (of 114 total) 1 [2](https://wordpress.org/support/users/3uu/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/3uu/replies/page/3/?output_format=md) … [6](https://wordpress.org/support/users/3uu/replies/page/6/?output_format=md) [7](https://wordpress.org/support/users/3uu/replies/page/7/?output_format=md) [8](https://wordpress.org/support/users/3uu/replies/page/8/?output_format=md) [→](https://wordpress.org/support/users/3uu/replies/page/2/?output_format=md)