Sérgio C.S.

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 22 total)
1 2
  • Forum: Plugins
    In reply to: [Yoast SEO - Advanced SEO with real-time guidance and built-in AI] PHP notice since new release 19.3
    Sérgio C.S.

    (@sergiorcs82)

    3 years, 10 months ago

    Further confirmation: i am getting this exact same problem on a distinct site, on a completely different server (Fastcomet, shared hosting, cPanel 102.0).

    Here, wp-cron does still run through a system cron job, with CLI PHP (PHP 8.0.21).

    The error log is getting filled up with messages like this one:
    [14-Jul-2022 06:22:02 UTC] PHP Warning: Undefined array key "SERVER_NAME" in /home/{{redacted for privacy}}/wp-content/plugins/wordpress-seo/src/helpers/url-helper.php on line 245

    Forum: Plugins
    In reply to: [Yoast SEO - Advanced SEO with real-time guidance and built-in AI] PHP notice since new release 19.3
    Sérgio C.S.

    (@sergiorcs82)

    3 years, 10 months ago

    I confirm this.

    I am running wp-cron through an actual cron job, so it is command line PHP ( 8.0.20).

    My site is hosted in Digital Ocean in a droplet running Ubuntu 20.04.4 LTS.

    Because my cron job runs every minute, i was showered with notifications…

    So, i mitigated this by replacing the offending line with $current_url .= ( isset( $_SERVER['SERVER_NAME'] ) ? $_SERVER['SERVER_NAME'] : '' ) . $suffix;, as to affect as little code as possible.

    Forum: Plugins
    In reply to: [Quiz and Survey Master (QSM) - Easy Quiz and Survey Maker] Submit button not displaying after update
    Sérgio C.S.

    (@sergiorcs82)

    4 years, 3 months ago

    I am having the same problem, but i found the culprit and two workarounds.

    My problem
    After an update, our simple, one-page quiz was no longer showing its submit button.

    The bug
    Upon inspecting the code, i found that display of the form footer is oddly connected to the “Random Questions” option: when that option is set to “Disabled”, the code will append the qsm-d-none CSS class to the end section of the quiz, where the submit button is contained. This CSS class will disable display of the section, thus hiding the submit button.

    Workaround 1
    If you’re OK with changing the order of the questions and/or answers, just set “Random Questions” to anything other than “Disabled” and the submit button should show up again.

    Workaround 2
    If you’d prefer to keep the order of questions and answers, you can use Appearance > Customize > Additional CSS to append this here CSS rule:
    .qsm-quiz-form>.quiz_section.quiz_end { display:block; }
    This should overrride the effect of qsm-d-none, marking the end section always visible – so do check your forms for any undesirable side-effects.

    Forum: Plugins
    In reply to: [Pods - Custom Content Types and Fields] Missing Fields from Field Groups
    Sérgio C.S.

    (@sergiorcs82)

    4 years, 6 months ago

    Status update:

    The missing fields thing was my fault.
    I had accidentally deleted the field group from the database.
    This is now fixed for me.
    (That order thing isn’t, though.)

    Forum: Plugins
    In reply to: [Pods - Custom Content Types and Fields] Missing Fields from Field Groups
    Sérgio C.S.

    (@sergiorcs82)

    4 years, 6 months ago

    Hello, @keraweb and @wlcreative .

    I am having the exact same problem.
    Cleared cache too and that didn’t solve it.
    Also cleared podscache (just in case), and that didn’t work either.

    As a bit of context, i was trying to troubleshoot the issue that the field order is being ignored. (Something for another ticket, maybe.)

    Forum: Plugins
    In reply to: [Easy Social Feed - Social Photos Gallery and Post Feed for WordPress] issue with new update 6.2.0
    Sérgio C.S.

    (@sergiorcs82)

    5 years, 3 months ago

    I ended up removing the plugin entirely, @maltathemes , but thanks anyway.

    Forum: Plugins
    In reply to: [Easy Social Feed - Social Photos Gallery and Post Feed for WordPress] issue with new update 6.2.0
    Sérgio C.S.

    (@sergiorcs82)

    5 years, 3 months ago

    I second this bug report. I woke up to a corrupted site after an auto-update last night.

    I reverted to the previous version, but i also had to restore yesterday’s database backup to get things working.

    Forum: Plugins
    In reply to: [Login No Captcha reCAPTCHA] reCAPTCHA v3?
    Thread Starter Sérgio C.S.

    (@sergiorcs82)

    5 years, 9 months ago

    Wow, i wasn’t expecting such a quick reply! Thanks!

    I’ve reached the same conclusion as you: invisible reCAPTCHA isn’t so great, which is why i opt for v3 visible. So, you may ask “What’s the point, then?”.

    Recently i’ve tried to use your plugin on a site whose main theme is Divi. Divi has integrated support for reCAPTCHA v3 in its forms, so it generated a conflict that i could only solve by replacing Login No Captcha reCAPTCHA with a plugin that supports v3. This pained me, because i feel the alternatives currently available on ww.wp.xz.cn are poor. (Either bloated or could use some polish.) Your plugin really is the best, as far as i’m concerned.

    I totally understand that you may not have the need or time (or will!) to invest in this, though. I’ll happily contribute the code if i can find some time too. 🙂

    Feel free to close this topic if you have nothing to add. Thanks for the awesome plugin.

    Forum: Plugins
    In reply to: [Tracking code for Matomo, by Sérgio Coelho Santos] Request to update plugin with regards to the trademark guidelines
    Plugin Author Sérgio C.S.

    (@sergiorcs82)

    6 years, 2 months ago

    Hi, @ipstenu !

    Thanks for your assistance. I went and made the adjustments you suggested.

    The description i can live with. The new name makes me cringe. I’m not that important that something should bear my name so explicitly.

    I did include my name to be able to take a bit of credit, to maybe help me get a few more gigs and make a little more money. Placing my name ahead of the actual title screams of “Look at me, this is my plugin. I’m damn important, and you should notice me.”. I hate it.

    @matomoteam , can we please put the name back to “Tracking code for Matomo, by Sergio Santos”?

    Forum: Plugins
    In reply to: [Tracking code for Matomo, by Sérgio Coelho Santos] Request to update plugin with regards to the trademark guidelines
    Plugin Author Sérgio C.S.

    (@sergiorcs82)

    6 years, 2 months ago

    I don’t disagree that “Tracking code for Matomo” bears some resemblance to “Matomo Tracking Code”, but i’ll point out that:

    • I chose to write in lowercase. It’s a tracking code, not the Tracking Code.
    • “tracking code” is a generic expression.
    • The official term i see on that page seems to be “Matomo Tracking Code”. Otherwise, i can only find a number of generical references to “tracking code”.
    • I can’t think of a more accurate title than “tracking code for [something]” to describe what this kind of plugin is and does.
    • As a general rule, the plugin title should be as succinct and accurate as possible. Prepending a verb would defeat that purpose, make it look out of place among most other plugins on ww.wp.xz.cn .
    • The small, generic icon on the plugin is quite different from the official Matomo logo and app colour scheme. This should further help avoid confusion.

    As it is now, i fail to see how my plugin violates trademarks.

    I believe my plugin is still chosen by users because it is about as lightweight and uncomplicated as can be. Here is how my plugin compares to the two currently most relevant solutions:

    • Compressed, version 1.0.3 of https://ww.wp.xz.cn/plugins/matomo/ takes up nearly 16MiB.
    • Compressed, version 1.0.22 of https://ww.wp.xz.cn/plugins/wp-piwik/ is close to 1MiB.
    • Both of the above require generating an auth token on Matomo.
    • My plugin, compressed, takes up less than 20KiB and requires nothing but the site Id and address; and it has just one discrete and plain-looking settings page.

    I created my plugin as a free service to others, at a personal expense, and i believe it has made a humble contribution to the growth of Matomo. Your insistence on dictating what my plugin’s name should be is causing me stress, and i’m thinking it might be easier to take down the plugin altogether. I’ve contacted [email protected] to ask for guidance and help.

    Forum: Plugins
    In reply to: [Tracking code for Matomo, by Sérgio Coelho Santos] Request to update plugin with regards to the trademark guidelines
    Plugin Author Sérgio C.S.

    (@sergiorcs82)

    6 years, 2 months ago

    Hello again, @matomoteam ,

    I take this kind of thing quite seriously, so i wanted to fix the issue without delay.

    I have just published an update meant especially to address any trademark infringements. Please have a look. Hopefully, that will have been enough.

    I looked into changing the slug of the plugin. For technical reasons, ww.wp.xz.cn very rarely allows that. Still, if you feel it’s absolutely necessary, let me know and i’ll present our case to them.

    I appreciated your patience and understanding. If i neglected to fix anything else, please inform me.

    Best regards,
    @sergiorcs82

    Forum: Plugins
    In reply to: [Tracking code for Matomo, by Sérgio Coelho Santos] Request to update plugin with regards to the trademark guidelines
    Plugin Author Sérgio C.S.

    (@sergiorcs82)

    6 years, 2 months ago

    Hi, @matomoteam . Thanks for bringing this to my attention.

    The name may not have been the best choice, but it was one i made a very long time ago.

    I understand that this plugin may now compete with your own solutions. This wasn’t my initial intention, and i’ll do my best to avoid any unnecessary friction.

    Because that might be seen as an endorsement on my part, i’d prefer not to include specific names or direct links.

    In order to make my plugin comply with ww.wp.xz.cn’s trademark policies, i propose the following:

    • Change the name to “Tracking code for Matomo, by Sergio Santos”.
    • Study the possibility of renaming the slug to something more suitable.
    • Exclude any images from the product (e.g. banner).
    • Update the existing description to:

      This simple plugin helps you include the tracking code for Matomo into your WordPress website, for an easier integration.
      For more information about Matomo, visit matomo.org .

    • Append the following disclaimer to the new description:

      NON-AFFILIATION DISCLAIMER:
      Matomo is a registered trademark of its original owner. The name “Matomo” is used for identification and reference purposes only and does not imply any association with the trademark holder of their product brand, or any of its subsidiaries or its affiliates. This plugin is not affiliated, associated, sponsored, authorized, endorsed, maintained by, or in any way officially connected with Matomo.

    Hopefully, this will be enough.

    I will be making these changes as quickly as possible – this week still, if i find the time.

    • This reply was modified 6 years, 2 months ago by Sérgio C.S.. Reason: Correct formatting
    Forum: Plugins
    In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] Missing clause in condition causing PHP warnings
    Thread Starter Sérgio C.S.

    (@sergiorcs82)

    6 years, 3 months ago

    Hello again, @wfgerald .

    I was happy to see Wordfence release an update yesterday. I quickly updated all of my 30+ sites. I’m going to paste something below. This is just from one site. Notice the last entry date and time.

    [26-Sep-2019 07:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[01-Oct-2019 02:40:03 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[05-Oct-2019 15:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[12-Oct-2019 13:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[17-Oct-2019 20:45:03 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[13-Nov-2019 12:20:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[15-Nov-2019 20:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[15-Nov-2019 23:35:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[16-Nov-2019 01:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[16-Nov-2019 01:45:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[27-Nov-2019 14:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[30-Nov-2019 22:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[12-Dec-2019 19:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[24-Dec-2019 06:25:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[28-Dec-2019 13:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[05-Jan-2020 15:35:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[05-Jan-2020 22:00:06 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[09-Jan-2020 13:45:08 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[11-Jan-2020 21:10:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[12-Jan-2020 09:30:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[15-Jan-2020 05:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[20-Jan-2020 11:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[20-Jan-2020 14:10:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[20-Jan-2020 15:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[21-Jan-2020 00:20:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[25-Jan-2020 11:25:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[27-Jan-2020 06:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[28-Jan-2020 15:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[30-Jan-2020 20:30:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[31-Jan-2020 01:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[31-Jan-2020 03:00:07 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[04-Feb-2020 11:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[04-Feb-2020 14:25:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[04-Feb-2020 16:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[04-Feb-2020 20:45:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[04-Feb-2020 21:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[04-Feb-2020 21:30:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[04-Feb-2020 22:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[07-Feb-2020 13:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[07-Feb-2020 15:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[07-Feb-2020 21:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[07-Feb-2020 22:00:03 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[07-Feb-2020 23:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[08-Feb-2020 06:25:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[08-Feb-2020 07:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[10-Feb-2020 22:30:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[11-Feb-2020 00:30:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[11-Feb-2020 07:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[12-Feb-2020 16:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[13-Feb-2020 17:00:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[14-Feb-2020 00:30:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[14-Feb-2020 05:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[14-Feb-2020 06:25:05 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[14-Feb-2020 07:50:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989
[14-Feb-2020 08:00:04 UTC] PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in {{redacted for privacy}}/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/waf.php on line 1989

    This just showed me how little the Wordfence Dev team cares about the quality of its code.

    I’m going to close this topic and start switching my sites to Sucuri. I’ll advise all of my clients to do the same.

    Still, thank you @wfgerald for all your efforts. Have a great day!

    • This reply was modified 6 years, 3 months ago by Sérgio C.S.. Reason: Correct markup
    Forum: Plugins
    In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] Missing clause in condition causing PHP warnings
    Thread Starter Sérgio C.S.

    (@sergiorcs82)

    6 years, 3 months ago

    Excellent, @wfgerald . Thank you!

    Forum: Plugins
    In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] Missing clause in condition causing PHP warnings
    Thread Starter Sérgio C.S.

    (@sergiorcs82)

    6 years, 4 months ago

    Hello again, @wfgerald .

    I just wanted to let you know that this problem isn’t solved yet.

    I’m a little frustrated. The solution is as easy as adding a tiny clause (which i’ve even given to you), and at least one update has been released since my report. Yet, on any given week i still get several notifications from dozens of sites, across multiple servers, on distinct locations.

    Seriously, if you want i can even do the change myself and submit a diff file for approval and merging.

    This bug is “low-hanging fruit” and i see no reason why your plugin should continue to fill up error logs across so many sites – and not just mine, but worldwide.

    Sergio

Viewing 15 replies - 1 through 15 (of 22 total)
1 2