You must hook the form using wpcf7_before_send_mail and add your PHP code to functions.php (since the script is already in your theme folder)? You won’t lose any of CF7’s abilities. function wpse_process_form( &WPCF7Object ){ #process your form here } add_action(‘wpcf7_before_send_mail’, ‘wpse_process_form’ );
It seems to me that all you should need is this: function force_login_wpse_89581() { if (!is_user_logged_in()) wp_safe_redirect(wp_login_url()); } add_action(‘template_redirect’,’force_login_wpse_89581′); That should force users to the login page except for users who have already logged in. I don’t know what bells and whistles those plugins provide that my solution does not. Maybe you need something more … Read more
The following will assign capability requirements to your CPT. So, users will require edit_community, delete_community etc capabilities to perform those actions. function createCommunityPostType() { $args = array( ‘public’ => true, ‘label’ => ‘Community’ ‘capability_type’ => ‘community’, ‘map_meta_cap’ => true ); register_post_type(‘community’, $args ); } add_action(‘init’, ‘createCommunityPostType’); See the parts about capabilities in the codex. You … Read more
If CAS is the only login method, I think your blog should be protected. But, the atackers don’t care about alternative login methods. They simply send request against wp-login.php. So if you still have an account named “admin”, CAS cannot protect your blog. Let’s think about the worst case. Assuming you have an account named … Read more
/bin/false is a utility program, companion to /bin/true, which is useful in some abstract sense to ensure that unix is feature-complete. However, emergent purposes for these programs have been found; consider the BASH statement /some/program || /bin/true, which will always boolean-evaluate to true ($? = 0) no matter the return of /some/program. An emergent use … Read more
It sounds like google (and/or other search engines) could have made an error when indexing your site (but I highly doubt it). You shouldn’t have that many hit going to your archive pages. Recovery steps: Signup for Google Analytics. Use this to determine where those hit are coming from. (GA is more detailed then JetPack … Read more
There are pro’s and con’s for either pw or key-based authentication. In some cases, for example, key-based authentication is less secure than password authentication. In other cases, its pw-based that’s less secure. In some cases, one is more convenient, in others, less. It all boils down to this: When you do key-based authentication, you must … Read more
No, it will not work. You pretty much will disable php to work on your site admin. On wp-admin there are files being executed when entering the admin side of the site.
Your config file shouldn’t be public at all. It includes your database credentials in addition to the 8 SALTs WordPress. (The secret keys alone make it possible to brute force your log-in in a bout a week: http://codeseekah.com/2012/04/09/why-wordpress-authentication-unique-keys-and-salts-are-important/)
Link to none would only remove the hyperlink from the media. If the user clicks on the media, the media will not open separately in a window / tab. There is no way to hide the link to the resources. There is no security threat of accessing other files from external user.