Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hope this gets fixed soon.
    Until then you can add this to your functions.php:

    add_action( 'enqueue_block_editor_assets', function() {
    
       wp_dequeue_style( 'shopisle-editor-style' );
    
    }, 100 );

    This removes the editor styles included by ShopIsle.
    Of course, it’s just a temporary solution … at least I can create & edit content in the visual editor again.

    dompauling

    (@dompauling)

    Same.
    To devs: You sould apply styles (and js) only to frontend.
    The way it is now, content is hardly editable …

    Same:

    #mapConElem_1_xxxxx {
        width: 100px;
    }

    The developers do have this in the to do list. However there is no time frame when it will be available.

    OK cool. Looking forward to it! Meanwhile I will use a separate plugin for this.

    So what you are after is another layer of security apart from the fact that only admins can make changes to the plugin, is this correct?

    Yes, wouldn’t that be a cool feature?!
    Read the link I posted. It describes it pretty well 😉

    Thanks and regards!

    • This reply was modified 6 months, 1 week ago by dompauling.

    Yes, this will be added soon. You can read more about it in the following support thread.

    I don’t mean captcha. I am thinking of Phone/SMS/Google Authenticator/Authy…

    Please check the following documentation. Is this what you mean.

    No, what I mean is e.g. the plugin is locked and there is an option to set an authentication key that unlocks it.

    Only administrators that know the authentication key can view/change plugin settings and deactivate/uninstall the plugin.

    This adds a second layer, that is independent from WordPress.

    Imagine some bad guy manages to find a way into our admin dashboard.
    Without the second layer he can just turn off all options in AIOWPSF.
    Like the option for DISALLOW_FILE_EDIT, which is supposed to prevent intruders from inserting and executing malicious code through the theme- and plugin-editor in the dashboard.
    Bad guy turns off this option and goes on with his evil work.
    Not so with a plugin protection mechanism 🙂

Viewing 5 replies - 1 through 5 (of 5 total)