• Resolved khurt

    (@khurt)


    I get this error after clicking the “proceed” link from the wizard page.

    403 Permission Denied

    You do not have permission for this request /wp-admin/options-general.php?page=cc-configurator-options&license_url=http%3A//creativecommons.org/licenses/by/3.0/&license_name=Attribution%203.0%20Unported&license_button=http%3A//i.creativecommons.org/l/by/3.0/88×31.png&deed_url=http%3A//creativecommons.org/licenses/by/3.0/&new_license=1

    http://wordpress.org/plugins/creative-commons-configurator-1/

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Author George Notaras

    (@gnotaras)

    Hello,

    I’ll make some improvements to the way the admin interface of the plugin is constructed.

    Can you tell if the 403 error is from the web server or wordpress? I suspect this error comes from your web server.

    Plugin Author George Notaras

    (@gnotaras)

    Made improvements in 1.4.2. Should be fixed.

    Plugin Author George Notaras

    (@gnotaras)

    Version 1.4.2 will be skipped. Going ahead with 1.5.0.

    I get the same 403 error. It looks like it is coming from my server.

    Plugin Author George Notaras

    (@gnotaras)

    Yes, the error is definitely from your server.

    The plugin uses the CC Partner Interface, on which you select a license. Then the interface constructs a URL (the ‘proceed’ hyperlink).

    This is a simple URL to the ‘License Settings’ page, which also contains the license information as query arguments. These arguments include complete URLs, like the URL to the license deed page, which may trigger security mechanisms on your server, such as an application firewall.

    This is not a problem with the plugin, unless of course you provide some details about a bug in the code. However, I understand that this is a general problem, which has to be resolved.

    I’m considering dropping the use of the CC Partner Interface and use a drop-down list of the supported licenses. This will eliminate all these issues.

    Any other suggestions are welcome.

    Plugin Author George Notaras

    (@gnotaras)

    Also, do you use any security plugins?

    Hi George. Thanks for response. Yes, I use Wordfence. Good suggestion. I’ll try disabling that & see if I can activate the plugin.

    I think a drop down makes sense & be easier to use.

    Plugin Author George Notaras

    (@gnotaras)

    @clintlalonde: Thanks for your feedback regarding the dropdown box.

    If you use a security mechanism, such as a security plugin or an application firewall, please configure it in a way so that it does not block the URL that is generated by the CC Partner Interface (the ‘proceed’ hyperlink).

    I’d suggest checking the security logs for any rules that are triggered, then customize the rules accordingly.

    There is nothing I can fix in the plugin code.

    Thanks for your feedback. I’m marking this topic as resolved.

    Thanks George. Just in case anyone else stumbles upon this post, I did disable Wordfence, but that still triggered the 403 error.

    I am wondering is there a way I can manually configure the license so I can still use the plugin? I am comfortable with making changes at the db level. Are there fields that I could modify in the db that would achieve the same result as using the partner interface? I’d really like to use the plugin.

    Plugin Author George Notaras

    (@gnotaras)

    Thanks George. Just in case anyone else stumbles upon this post, I did disable Wordfence, but that still triggered the 403 error.

    I installed Wordfence in a test blog, set security level to 4 (lockdown) and I was still able to use Creative-Commons-Configurator without issues (activate, deactivate, select license).

    If you have access to any log files, the messages recorded there would be useful.

    Plugin Author George Notaras

    (@gnotaras)

    @clintlalonde: I’m working on a workaround that will help you manually set the license. I’ll post it shortly.

    Plugin Author George Notaras

    (@gnotaras)

    Setting the License Manually

    1. Paste the following code at the end of the bccl-settings.php file:

    function bccl_manual_license_settings() {
    
        $cc_settings = get_option('cc_settings');
        if ( empty($cc_settings) ) {
            $cc_settings = bccl_get_default_options();
        }
    
        // Set manual licnese settings.
        // EDIT BEGIN
        $cc_settings['license_url'] = 'http://creativecommons.org/licenses/by/4.0/';    // URL to license page. Eg: http://creativecommons.org/licenses/by/4.0/
        $cc_settings['deed_url'] = 'http://creativecommons.org/licenses/by/4.0/';   // Usually the same as license_url
        $cc_settings['license_name'] = 'Creative Commons Attribution 4.0 International License';  // The name of the license
        $cc_settings['license_button'] = 'http://i.creativecommons.org/l/by/4.0/88x31.png'; // URL to license image. Eg: http://i.creativecommons.org/l/by/4.0/88x31.png
        // EDIT END
    
        delete_option('cc_settings');
        update_option('cc_settings', $cc_settings);
        bccl_show_info_msg(__('CC-Configurator license has been manually set.', 'cc-configurator'));
    }
    // Uncomment the following line and visit the License Settings page (Settings->License) to auto set the license. The COMMENT the following line AGAIN.
    //add_action( 'admin_init', 'bccl_manual_license_settings', 999999 );

    2. Edit the license settings between the EDIT BEGIN and EDIT END marks. Find the license details by using the license chooser on the CC web site.

    3. Uncomment (remove //) the last line of the code (add_action statement), so that it becomes:

    add_action( 'admin_init', 'bccl_manual_license_settings', 999999 );

    4. Visit the license settings page in the WordPress admin panel (Settings -> License). The license should have been set automatically.

    5. Now comment (add //) the last line of the code, so that it becomes:

    //add_action( 'admin_init', 'bccl_manual_license_settings', 999999 );

    Continue using the plugin normally.

    Plugin Author George Notaras

    (@gnotaras)

    @clintlalonde: Please let me know if it worked. Thanks in advance.

    That did it!

    http://clintlalonde.net/2013/11/26/big-money/

    Awesome. Thanks for the workaround. A coffee is on the way :).

    Just one little glitch that I can see – some words in the license appear twice.

    unless otherwise expressly stated, is licensed under a Creative Commons Creative Commons Attribution 4.0 International License License.

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘403 Error’ is closed to new replies.