404 on fresh install

Very weird. If you rename it back to cc-configurator.php does it still work (activate, deactivate)?

Also please make sure you clean the browser cache. Sometimes it can be a problem with WP error messages (404/403) because the browser does not refresh the page from the server and displays it from its cache.

Thanks for your feedback. Much appreciated.

Nope. If I rename it back the cc.php plugin gets deactivated and I can’t activate the cc-configuratior.php plugin. Same error.

Thank you, for creating this plugin and following up on this issue. Much appreciated.

Cheers.

So, if the main file is renamed to cc.php can you activate/deactivate the plugin without problems, but if the name is cc-configurator.php activation/deactivation is not possible? Is this correct?

This is really weird and I’m out of ideas.

BTW, do you use any security plugins?

Also is it possible to check the following file and directory permissions and ownership and compare with the permissions and ownership of the other files included in the plugin?

wp-content/plugins
wp-content/plugins/creative-commons-configurator-1
wp-content/plugins/creative-commons-configurator-1/cc-configurator.php

If you have shell access you could run (From the root directory of WordPress):

ls -ld wp-content/plugins
ls -ld wp-content/plugins/creative-commons-configurator-1
ls -ld wp-content/plugins/creative-commons-configurator-1/cc-configurator.php

Also, if possible enable debugging in wp-config.php, but please make sure error and notices are not displayed, but only recorded in the log. This can be done with the following settings:

// Enable WP_DEBUG mode
define('WP_DEBUG', true);

// Enable Debug logging to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);

// Disable display of errors and warnings
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors',0);

Then please try to activate the plugin and check the web server’s error log for error messages.

Thanks in advance.

Typo:

ls -l wp-content/plugins/creative-commons-configurator-1/cc-configurator.php

Hi,

I don’t have shell access. But from cPanel I can see the file has permissions like others – 0644. Not sure if it’s a permissions thing coz then renaming the file shouldn’t get it working, right?

I’ll try the debug thing and get back.

Also, no I don’t have any security plugins. I have WP Super Cache installed, but I tried disabling that just in case that could be an issue. Didn’t help.

I renamed the file back to cc-configurator.php but this time I removed the dash and called it ccconfigurator.php. And that too works! Doesn’t seem to be a filename length issue coz I can add additional characters and it still works. So the dash itself seems to be the issue.

But … at the same time I can edit files like bccl-deprecated.php from your plugin so the dash doesn’t seem to be an issue there. The dash only affects cc-configurator.php.

Ok, enough conjecture I’ll get some debug output and send to you …

Here you go –

[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: Non-static method WP_Hotfix_Controller::init() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-content/plugins/hotfix/hotfix.php on line 11
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::init() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 496
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp_review::reviewinit() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 496
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:23 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::smcwpd_set_plugin_meta() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:26 UTC] PHP Strict Standards: Non-static method WP_Hotfix_Controller::init() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-content/plugins/hotfix/hotfix.php on line 11
[02-Jan-2015 08:04:26 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::init() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 496
[02-Jan-2015 08:04:26 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp_review::reviewinit() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 496
[02-Jan-2015 08:04:26 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::ipwp_the_content_filter() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:26 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::ipwp_the_content_filter() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 213
[02-Jan-2015 08:04:26 UTC] PHP Notice: Undefined index: full_width_footer in /home/prgmrio/public_html/rakhesh.com/wp-content/themes/atahualpa/footer.php on line 92
[02-Jan-2015 08:04:26 UTC] PHP Notice: Undefined index: full_width_footer in /home/prgmrio/public_html/rakhesh.com/wp-content/themes/atahualpa/footer.php on line 120
[02-Jan-2015 08:04:29 UTC] PHP Strict Standards: Non-static method WP_Hotfix_Controller::init() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-content/plugins/hotfix/hotfix.php on line 11
[02-Jan-2015 08:04:29 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::init() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 496
[02-Jan-2015 08:04:29 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp_review::reviewinit() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 496
[02-Jan-2015 08:04:29 UTC] PHP Notice: Trying to get property of non-object in /home/prgmrio/public_html/rakhesh.com/wp-content/themes/atahualpa/functions.php on line 926
[02-Jan-2015 08:04:29 UTC] PHP Notice: Undefined index: full_width_footer in /home/prgmrio/public_html/rakhesh.com/wp-content/themes/atahualpa/footer.php on line 92
[02-Jan-2015 08:04:29 UTC] PHP Notice: Undefined index: full_width_footer in /home/prgmrio/public_html/rakhesh.com/wp-content/themes/atahualpa/footer.php on line 120
[02-Jan-2015 08:04:30 UTC] PHP Strict Standards: Non-static method WP_Hotfix_Controller::init() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-content/plugins/hotfix/hotfix.php on line 11
[02-Jan-2015 08:04:30 UTC] PHP Strict Standards: Non-static method WP_Hotfix_Controller::init() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-content/plugins/hotfix/hotfix.php on line 11
[02-Jan-2015 08:04:30 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::init() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 496
[02-Jan-2015 08:04:30 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp_review::reviewinit() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 496
[02-Jan-2015 08:04:30 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp::init() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 496
[02-Jan-2015 08:04:30 UTC] PHP Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method itempropwp_review::reviewinit() should not be called statically in /home/prgmrio/public_html/rakhesh.com/wp-includes/plugin.php on line 496
[02-Jan-2015 08:04:30 UTC] PHP Notice: Undefined variable: bfa_ata_debug in /home/prgmrio/public_html/rakhesh.com/wp-content/themes/atahualpa/css.php on line 12
[02-Jan-2015 08:04:30 UTC] PHP Notice: Undefined variable: bfa_ata_debug in /home/prgmrio/public_html/rakhesh.com/wp-content/themes/atahualpa/css.php on line 2952
[02-Jan-2015 08:04:30 UTC] PHP Notice: Undefined variable: bfa_ata_debug in /home/prgmrio/public_html/rakhesh.com/wp-content/themes/atahualpa/css.php on line 2956

I saw lot of references to the Hotfix plugin in the logs above. So I removed that just in case it was conflicting with your plugin. Didn’t help.

Hi Rakhesh,

Thanks for your replies and efforts. Much appreciated.

But from cPanel I can see the file has permissions like others – 0644. Not sure if it’s a permissions thing coz then renaming the file shouldn’t get it working, right?

It depends on the user that is used to perform the renaming. For instance, the file has 0644 permissions and, assuming that the container dir (wp-content/plugins/creative-commons-configurator-1) has 0755 and also assuming that the ownership of files and directories is for example userA:groupA, then, if the process that renames the file runs as userA, then the renaming is allowed. If the renaming process’s group is groupA, then it wouldn’t be able to rename or perform any write operation inside the wp-content/plugins/creative-commons-configurator-1 directory. So, in this case, if the user that runs WordPress through the webserver is userA, then any write operation would be possible. Contrariwise, if the user that runs WordPress through the webserver is _NOT_ userA, but its group is groupA, it would not be able to rename or perform any other write operation, because of the 0644 (files) and 0755 (folders) permissions. If I’ve written this in a way that it’s unclear, please let me know so I can rephrase.

Is this the only plugin that behaves like that? Have you ever noticed similar behavior with any other plugin?

Regarding the debug output, none of the log messages refers to CC-Configurator. If there was a PHP error or Notice it would have been recorded there.

Your tests with the name of the main plugin file (cc-configurator.php) are very interesting.

However, the name of this file is not hard-coded anywhere in the plugin code. Its name could be whatever and the plugin should work without the slightest issue. And it seems to do so, unless its name is cc-configurator.php… This is odd behavior! I have absolutely no idea what might be causing it.

Another thing I can tell for sure is that the plugin behaves as expected in the systems I’ve tried. So far it has been impossible to reproduce the error, which means we are not close to the real problem that causes it.

If the renaming process’s group is groupA, then it wouldn’t be able to rename or perform any write operation inside the wp-content/plugins/creative-commons-configurator-1 directory.

Small correction. The above should be:

If the renaming process’s user is NOT userA but its group is groupA, then it wouldn’t be able to rename or perform any write operation inside the wp-content/plugins/creative-commons-configurator-1 directory.

Marked this topic as ‘not resolved’.