Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author finnj

    (@finnj)

    Hi,

    This messages should not appear unless someone is trying to do “Cross Site Request Forgery (CSRF)”.

    It should not show if you are testing og working normal, unless you use the back and forward buttons on your browser, and then only in the submit process (saving or deleting a post).

    Can you tell me what you did to get the Security Violation please.

    Plugin Author finnj

    (@finnj)

    If you changed som of the forms, or if you are using template forms, you need to update to the nev version 3 forms, especially the hidden fields for wpnonce

    Thread Starter robertosalemi

    (@robertosalemi)

    I see this message when I click on “Save” on Frontier Editor.
    If I do a rollback to 2.6.1 version the plugin work fine.
    Where It should be the problem?
    Thanks.

    Plugin Author finnj

    (@finnj)

    Hi Roberto,

    I need to know if you have changed any files ?
    (One of previous posts suggests that you have made some changes…)

    It could also be a conflict with another plugin, so in version 3.0.5 I have ensured that wp nonce uses a unique name, instead of the default “_wpnonce”

    Thread Starter robertosalemi

    (@robertosalemi)

    Hi finnj,
    I modified some files beause I would filter the post by category ID, but when you update the version of your plugin I upgrade it without modify any files.

    Probably there is a uncompatibily with other plugin, I will try to disable them and your plugin will work fine.

    Thanks.

    Thread Starter robertosalemi

    (@robertosalemi)

    Hi finnj,
    i found my problem.

    I added this code for block access to backend other user, but it generated me more problem:

    function restrict_admin(){
    //if not administrator, kill WordPress execution and provide a message
        if ( ! current_user_can( 'delete_others_posts' ) ) {
            wp_die( __('Non sei autorizzato ad accedere a questa sezione.') );
        }
    }
    add_action( 'admin_init', 'restrict_admin', 1 );

    Thanks for your disponibility and professionality.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Security violation’ is closed to new replies.