Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)
  • Thread Starter Patrick Boehner

    (@patrick-b)

    Hi Mark,

    I had looked at the code but completely missed that. Thank you for making the plugin extendable. I’ll try that out.

    Thread Starter Patrick Boehner

    (@patrick-b)

    Hi @tharg3

    While those are nice things to have, and I am aware of them, they don’t really address the main issue.

    The plugins should not be auto-selected. A client who doesn’t understand what is happening ( because it’s unclear) shouldn’t need to opt out. It should be an opt-in-only feature.

    They should also be separated from the other options and have text that clarifies that these are separate plugins that would be installed if selected and aren’t required.

    The fact that they keep getting installed by clients who didn’t intend to demonstrates that the pattern needs to be more explicit.

    Also wanted to report a similar issue with an updated to 3.1.5

    An error of type E_ERROR was caused in line 41 of the file /www/wp-content/plugins/blockmeister/includes/Pattern_Builder/BlockMeister_Pattern_Category_Taxonomy.php. Error message: Uncaught Error: Call to undefined method WP_Taxonomy::get_default_labels() in /www/wp-content/plugins/blockmeister/includes/Pattern_Builder/BlockMeister_Pattern_Category_Taxonomy.php:41
    Stack trace:
    #0 /www/wp-content/plugins/blockmeister/includes/Pattern_Builder/BlockMeister_Pattern_Category_Taxonomy.php(23): ProDevign\BlockMeister\Pattern_Builder\BlockMeister_Pattern_Category_Taxonomy->register_blockmeister_pattern_category_taxonomy()
    #1 /wordpress/wp-includes/class-wp-hook.php(307): ProDevign\BlockMeister\Pattern_Builder\BlockMeister_Pattern_Category_Taxonomy->ProDevign\BlockMeister\Pattern_Builder\{closure}(”)
    #2 /wordpress/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
    #3 /wordpress/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
    #4 /wordpress/wp-settings.php(590): do_action(‘init’)
    #5 /www/wp-config.php(120): require_once(‘/wordpress/wp-s…’)
    #6 /wordpress/wp-config.php(5): require(‘/www/wp-config….’)
    #7 /wordpress/wp-load.php(50): require_once(‘/wordpress/wp-c…’)`

    A form plugin is only ever going to be able to do so much to prevent spam. At a certain point, you will need to consider other options. I say this as someone managing multiple websites using Ninja Forms also experiencing the same attacks over periods of time. But this isn’t a new issue for any form plugin, so instead of waiting for an update to somehow fix this ( to which the spammers will eventually overcome again ), you might be better served to implement some spam filtering tools like CleanTalk or others filtering services.

    Thread Starter Patrick Boehner

    (@patrick-b)

    I finely hunted down the issue in my setup and wanted to post just encase someone else has a similar setup issue. The html wasn’t saving because I had define( ‘DISALLOW_UNFILTERED_HTML’, true ) in my wp-config.php

    Thread Starter Patrick Boehner

    (@patrick-b)

    Definitely an issue with my local development server. Tested it on another setup and the issue went away. Sorry to drag you down the rabbit hole.

    Thread Starter Patrick Boehner

    (@patrick-b)

    Yep. No MU plugins but I will go ahead and test it on another environment.

    Thread Starter Patrick Boehner

    (@patrick-b)

    I’m making these updates to account for the class changes between the plugins on my local test site using Local by flywheel.

    I’ve gone ahead and installed the Twenty Nineteen theme and disabled all other plugins. Issue remains.

    The HTML that is output looks like:

    
    <div class="spu-content">
    <p style="margin-top: 0px; padding-top: 0px; margin-bottom: 0px; padding-bottom: 0px;">
    Subscribe To Our Newsletter<br>
    Sign up for our monthly newsletter and get the latest financial news, tips, and insights.[gravityform id=”4″ title=”false” description=”false” ajax=”true”]<button class="spu-close-popup ">No Thank You</button>
    </p>
    </div>
    
    Thread Starter Patrick Boehner

    (@patrick-b)

    Here is a dump from site health. I will do a little more testing on my end.

    
    ### wp-core ###
    
    version: 5.3.1
    site_language: en_US
    user_language: en_US
    timezone: America/Los_Angeles
    permalink: /blog/%postname%/
    https_status: true
    user_registration: 0
    default_comment_status: open
    multisite: false
    user_count: 10
    dotorg_communication: true
    
    ### wp-plugins-active (18) ###
    
    ACF Content Analysis for Yoast SEO: version: 2.3.0, author: Thomas Kr?ftner, ViktorFroberg, marol87, pekz0r, angrycreative, Team Yoast
    Advanced Custom Fields PRO: version: 5.8.7, author: Elliot Condon
    Autoptimize: version: 2.5.1, author: Frank Goossens (futtta)
    Classic Editor: version: 1.5, author: WordPress Contributors
    Disable Comments: version: 1.10.2, author: Samir Shah
    Gravity Forms: version: 2.4.15, author: rocketgenius
    Gravity Forms MailChimp Add-On: version: 4.6, author: rocketgenius
    Maintance Testing Tools: version: 1.0.3, author: Patrick Boehner
    Native Lazyload: version: 1.0.2, author: Google
    Query Monitor: version: 3.5.2, author: John Blackbourn
    Redirector: version: 3.0.1, author: Ralf Hortt
    Relevanssi: version: 4.4.1, author: Mikko Saari
    Shared Counts: version: 1.3.0, author: Bill Erickson & Jared Atchison
    Tada: version: 1.1.1, author: Ben Gillbanks
    TinyMCE Advanced: version: 5.3.0, author: Andrew Ozz
    WordPress Zero Spam: version: 3.1.1, author: Ben Marshall
    WP Popups Lite: version: 2.0.0.6, author: timersys
    Yoast SEO Premium: version: 12.0.1, author: Team Yoast
    
    ### wp-plugins-inactive (3) ###
    
    CAOS: version: 2.9.4, author: Daan van den Bergh
    SendGrid: version: 1.11.8, author: SendGrid
    Simple History: version: 2.33, author: P?r Thernstr?m
    
    ### wp-server ###
    
    server_architecture: Linux 4.9.93-boot2docker x86_64
    httpd_software: Apache/2.4.10 (Debian)
    php_version: 7.2.0 64bit
    php_sapi: fpm-fcgi
    max_input_variables: 3000
    time_limit: 900
    memory_limit: 256M
    max_input_time: -1
    upload_max_size: 1000M
    php_post_max_size: 1000M
    curl_version: 7.38.0 OpenSSL/1.0.1t
    suhosin: false
    imagick_availability: true
    htaccess_extra_rules: false
    
    ### wp-constants ###
    
    WP_HOME: undefined
    WP_SITEURL: undefined
    WP_CONTENT_DIR: /app/public/wp-content
    WP_PLUGIN_DIR: /app/public/wp-content/plugins
    WP_MAX_MEMORY_LIMIT: 256M
    WP_DEBUG: true
    WP_DEBUG_DISPLAY: false
    WP_DEBUG_LOG: true
    SCRIPT_DEBUG: false
    WP_CACHE: false
    CONCATENATE_SCRIPTS: undefined
    COMPRESS_SCRIPTS: undefined
    COMPRESS_CSS: undefined
    WP_LOCAL_DEV: undefined
    DB_CHARSET: utf8
    DB_COLLATE: undefined
    
    ### wp-filesystem ###
    
    wordpress: writable
    wp-content: writable
    uploads: writable
    plugins: writable
    themes: writable
    
    
    Thread Starter Patrick Boehner

    (@patrick-b)

    Sure. Nothing fancy, just a heading and a paragraph. I’ve tried using the formatting options in the text editor and writing the html myself.

    <h2>Subscribe To Our Newsletter</h2>
    
    <p>Sing up for our monthly newsletter and get the latest financial news, tips, and insights.</p>
    

    Yes I will definitely test it and get back to you on github to see whats causing the issue or narrow it down.

    Just something i noticed quickly while testing. It conflicts with Beaver Builder loading the front end editor if your using the block editor for posts and BB for pages.

    Thread Starter Patrick Boehner

    (@patrick-b)

    Thanks Robin,

    The update looks good!

    On their website under the roadmap for the plugin (might be somewhere on the page) they seem to list this as something they have planed on fixing (also overlaps the admin bar).

    Forum: Plugins
    In reply to: [Display Widgets] Broke

    Seems to have fixed it. At least for me.

Viewing 15 replies - 1 through 15 (of 20 total)