WP-CLI secure all – Single-command WordPress security!

https://hackthewp.com/

NEW feature in >wp-cli to secure any WordPress instance in just 60 seconds.

One command to rule them all 🤘

80% of the attacks to WordPress instances could be mitigated by simply applying common security best practices [1].

wp secure all exactly does that for you. Via wp secure all common best practices are applied proactively, and you are ready to go.

What’s covered by secure all?

The security vulnerabilities identified in 2012 [2] are still the security vulnerabilities of today [1].

wp secure all made it its mission to fix this grievance and make security the defacto standard.

By executing wp secure all security best practices such as:

Fix permissions

Set the correct permissions of all files & directories in your WordPress installation.

Set security headers

We add HSTS (Strict-Transport-Security), X-XSS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy.

Disable file editor

Prevents hackers from using file editor on your WordPress Dashboard.

Prevent PHP execution on sensitive locations

To extend security, you can block direct access to PHP files in plugins, themes, wp-includes and uploads.

Block access to sensitive stuff

Prevent hackers from accessing sensitive files and directories.

And many more …

See the README for an overview of all features.

Read More

Koko Analytics – An open-source analytics plugin for WordPress

Koko Analytics – An open-source analytics plugin for WordPress that does not use any external services and respects your visitors’ privacy.

view a demo of Koko Analytics here.

Features

  • Plug and play. After activating the plugin, stats will be collected right away.
  • No external services. Any data about your visitors never leaves your site.
  • No personal information or anything that could lead back to a specific visitor is tracked.
  • Fast. Koko Analytics can handle thousands of daily visitors or sudden bursts of traffic without breaking a sweat.
  • Option to not use any cookies while still being able to determine returning visitors and unique pageviews.
  • Option to exclude certain user roles from being tracked.
  • Option to automatically delete older data.
  • Built-in blacklist to filter referrer spam.
  • Compatible with pages served from cache.
  • Compatible with AMP powered pages.
  • Completely open source (GPLv3 licensed).
  • GDPR compliant by design.

Disabling Gutenberg on certain templates

Using a plugin

The Classic Editor plugin is great for disabling Gutenberg site-wide, but is not a good choice for selectively using it on certain pages.

Gutenberg Ramp lets you disable Gutenberg on a per-post-type basis. You could use Gutenberg for posts, but keep the classic editor for pages.

Using a filter

We can use the use_block_editor_for_post_type filter for more fine-grained control. It passes two parameters:

  • $can_edit, boolean, whether Gutenberg should be used to edit
  • $post_type, string
Read More

commonWP

Description

commonWP is a plugin that enables usage of free, public CDN (jsDelivr) for open source JavaScript and CSS files. Those files are:

  • All files from WordPress core, unless development version of WordPress is used.
  • All files from plugins hosted by WordPress.org Plugins Repository, unless author of specific plugin doesn’t use SVN tags for releasing.
  • All files from themes hosted by WordPress.org Themes Repository.
  • All files from plugins and themes hosted on GitHub that support GitHub Updater.
  • All files marked as available on npm in any type of theme, plugin, or MU plugin.

Beaver Builder

Custom module developer guide

http://kb.wpbeaverbuilder.com/article/124-custom-module-developer-guide#overview

Create a plugin

  • Make a new folder in plugins: bb-plugin-custom
  • Create a php file with the same name: bb-plugin-custom.php
  • Copy-paste this in the file:<?php
    /**
    * Plugin Name: My Custom Modules
    * Plugin URI: http://www.mywebsite.com
    * Description: Custom modules for the Beaver Builder Plugin.
    * Version: 1.0
    * Author: Your Name
    * Author URI: http://www.mywebsite.com
    */

    define( ‘MY_MODULES_DIR’, plugin_dir_path( __FILE__ ) );
    define( ‘MY_MODULES_URL’, plugins_url( ‘/’, __FILE__ ) );
    function my_load_module_examples() {
    if ( class_exists( ‘FLBuilder’ ) ) {
    // Include your custom modules here.
    }
    }
    add_action( ‘init’, ‘my_load_module_examples’ );

  • Edit the information such as Plugin Name and Author. You should also rename the constants MY_MODULES_DIR and MY_MODULES_URL to match your plugin’s namespace, keeping the _DIRand _URL suffixes.

Add a module to your plugin

 

Overriding built-In modules

Any of the built-in modules can be overridden within your theme by following the steps below.

1. Create a new folder in your theme’s folder named fl-builder.

2. Create a new folder within your theme’s fl-builder folder named modules.

3. Copy the module you wish to override from wp-content/plugins/bb-plugin/modulesto your theme’s fl-builder/modules folder.

That’s it! You can now start editing the module to suit your needs. Note that even though you can customize the module’s code, the module’s folder name, main PHP file name, and main class name must remain unchanged to be recognized by the builder.

If you’re not seeing your changes, try clearing the Page Builder cache.