DEV Community: Faisal Ahammad

Open Source WordPress Contribution: My July 2026 Recap

Faisal Ahammad — Mon, 10 Aug 2026 07:11:01 +0000

July felt different from the start. I opened the month with a WooCommerce logging bug and closed it 24 pull requests later, spread across 9 different WordPress repositories. Some fixes took ten minutes. One took a full week of back and forth with a maintainer over a single line of code.

This post is my open source WordPress contribution recap for July 2026. I am sharing the actual code from each pull request, not just a list of links, so you can see what changed and why it mattered.

Fixing WooCommerce, One Bug at a Time

WooCommerce took up the biggest chunk of my month. I merged 10 pull requests into the core plugin, ranging from a one-line performance tweak to a new REST endpoint. I will walk through each one.

Log Cleanup Was Silently Leaving Files Behind

The month opened with PR #66073. LogHandlerFileV2::delete_logs_before_timestamp() fetched expired log files without setting a per_page value, so it inherited the admin UI default of 20. On sites with more than 20 expired log sources, the daily cleanup cron deleted only the first 20 and left the rest sitting in wp-content/uploads/wc-logs/ forever.

The fix batches the deletion instead of trusting a single page:

// BEFORE:
$files = $this->file_controller->get_files( [ 'before' => $timestamp ] );
foreach ( $files as $file ) {
    $this->delete_log_file( $file );
}

// AFTER (batched with a no-progress guard):
do {
    $files = $this->file_controller->get_files( [
        'before'   => $timestamp,
        'per_page' => 100,
    ] );
    $deleted_this_pass = 0;
    foreach ( $files as $file ) {
        if ( $this->delete_log_file( $file ) ) {
            $deleted_this_pass++;
        }
    }
} while ( $files && $deleted_this_pass > 0 );

A site with 101 leftover log files now gets all of them removed instead of just 20. I added a no-progress guard so the loop stops if a batch cannot be deleted, which prevents an infinite loop on a stuck file.

The Order List Table Cache Ignored Custom Filters

PR #66207 fixed a subtler bug. ListTable::prepare_items() decides whether to skip SQL_CALC_FOUND_ROWS by checking the query args before any filters run. If a developer hooked woocommerce_order_list_table_prepare_items_query_args to add a meta_query, the cache fast path stayed blind to it and returned a stale total.

// BEFORE (checked pre-filter args):
if ( empty( array_diff( array_keys( $this->order_query_args ), $safe_keys ) ) ) {
    $args['no_found_rows'] = true;
}

// AFTER (checks post-filter args):
if ( empty( array_diff( array_keys( $order_query_args ), $safe_keys ) ) ) {
    $args['no_found_rows'] = true;
}

Moving the check to run after the filter means any key a plugin adds correctly disables the cache shortcut. Small change, but it stopped merchants from seeing wrong order counts whenever a custom query filter was active.

Combining Six Requests Into One

The most involved WooCommerce PR of the month was PR #66276. Every wp-admin page load fired 6 separate wc-analytics REST requests just to populate the Activity Panel bell icon and the "Things to do next" homescreen widget. Three endpoints, each called twice by two different components, with no shared cache between them.

I added a single combined endpoint instead:

class ActivityPanelCounts extends \WC_REST_Data_Controller {
    protected $namespace = 'wc-analytics';
    protected $rest_base = 'activity-panel/counts';

    public function get_counts( $request ) {
        return rest_ensure_response( [
            'orders_to_fulfill_count'   => $this->get_count_via( '/wc-analytics/orders', [
                'page'     => 1,
                'per_page' => 1,
                'status'   => $request->get_param( 'order_statuses' ),
                '_fields'  => [ 'id' ],
            ] ),
            'reviews_to_moderate_count' => $this->get_count_via( '/wc-analytics/products/reviews', [
                'page'     => 1,
                'per_page' => 1,
                'status'   => $request->get_param( 'review_status' ),
            ] ),
        ] );
    }
}

A matching activityPanelStore selector in @woocommerce/data means all three Activity Panel components now read from one place. The resolution cache collapses six network requests into one per page load, and nothing about the counting logic changed since the new endpoint just delegates to the existing ones internally.

If you want the fuller backstory on how I approach WooCommerce internals like this, my June 2026 open source recap covers a similar REST endpoint consolidation from the month before.

Guest Orders Finally Show a Name

PR #66279 fixed something that bugged store owners for a while. The WooCommerce Home Orders panel shows "Order #123 Customer Name" for actionable orders, but guest checkouts have no customer_id to look up, so the name always came back blank.

// BEFORE: only checked the registered customer record
const customerName = order.customer ? order.customer.name : '';

// AFTER: falls back to billing details for guest orders
const customerName = order.customer
    ? order.customer.name
    : [ order.billing?.first_name, order.billing?.last_name ]
          .filter( Boolean )
          .join( ' ' );

The order response already carried the billing address. I just added billing to the requested fields and used it as a fallback. Registered customers still get their name linked to their profile, guests just show as plain text like the rest of the row.

Product Taxonomy Boxes Hidden by Default

PR #65990 addressed a first-run annoyance. On a user's first visit to Appearance → Menus, WordPress hides every meta box except Pages, Posts, Custom Links, and Categories. That default list swallowed the Product Categories, Product Tags, and Brands boxes too, so new users had to dig into Screen Options before they could add these to a menu.

public function filter_default_nav_menu_hidden_meta_boxes( $result, $option, $user ) {
    global $wp_meta_boxes;

    if ( false !== $result || ! $user || ! isset( $wp_meta_boxes['nav-menus'] ) ) {
        return $result;
    }

    $visible = [
        'add-post-type-page', 'add-post-type-post', 'add-custom-links',
        'add-category', 'add-product_cat', 'add-product_tag',
        'woocommerce_endpoints_nav_link',
    ];

    if ( taxonomy_exists( 'product_brand' ) ) {
        $visible[] = 'add-product_brand';
    }

    $hidden = [];
    foreach ( $wp_meta_boxes['nav-menus'] as $priorities ) {
        foreach ( (array) $priorities as $boxes ) {
            foreach ( (array) $boxes as $box ) {
                if ( isset( $box['id'] ) && ! in_array( $box['id'], $visible, true ) ) {
                    $hidden[] = $box['id'];
                }
            }
        }
    }

    return $hidden;
}

This hooks get_user_option_metaboxhidden_nav-menus so it only fires when a user has no saved preference yet. Existing users with a saved Screen Options choice are never touched.

A Cache Poisoning Bug in the Brand Nav Widget

PR #65947 was the trickiest bug to trace this month. The Brand Nav widget's filter_out_cats() method hooks woocommerce_product_subcategories_args and returns an empty taxonomy when a brand filter is active in the URL. That empty-taxonomy query returns zero rows, and WooCommerce cached those zero rows under the same key used by regular, non-filtered requests. Every visitor after that, brand filter or not, read the poisoned cache and saw no subcategories at all.

// BEFORE: always cached the result, even an empty taxonomy query
wp_cache_set( $cache_key, $result, 'product_cat' );

// AFTER: only cache when the query actually resolved to a taxonomy
if ( ! empty( $args['taxonomy'] ) ) {
    wp_cache_set( $cache_key, $result, 'product_cat' );
}

An empty-taxonomy query never produces a meaningful result, so storing it just poisoned the shared cache for no benefit. Skipping the cache write when taxonomy is empty fixed it for every visitor, not just the one who triggered the brand filter.

Nine Default Colors for Visual Attributes

PR #65923 added a small quality-of-life feature. When a merchant creates a new "Color / image" attribute, the terms list starts empty and they have to add each color by hand. This seeds 9 common colors automatically:

private static function get_default_color_terms(): array {
    return [
        'black' => [ 'label' => __( 'Black', 'woocommerce' ), 'color' => '#121212' ],
        'white' => [ 'label' => __( 'White', 'woocommerce' ), 'color' => '#FFFFFF' ],
        'red'   => [ 'label' => __( 'Red', 'woocommerce' ), 'color' => '#D32F2F' ],
        'blue'  => [ 'label' => __( 'Blue', 'woocommerce' ), 'color' => '#1976D2' ],
        'green' => [ 'label' => __( 'Green', 'woocommerce' ), 'color' => '#388E3C' ],
        // gray, yellow, pink, and brown follow the same pattern
    ];
}

The seeder only runs from WC_Admin_Attributes::process_add_attribute(), so it fires when a merchant creates an attribute through the UI, not through programmatic wc_create_attribute() calls or CSV imports. That distinction mattered during review since nobody wants a bulk import silently injecting terms nobody asked for.

Rounding Out the Month: Layout, Cron Status, and jQuery Cleanup

Three smaller WooCommerce fixes closed out the batch:

PR #66280 fixed missing layout styles on the product_brand_thumbnails_description shortcode. Its stylesheet never defined list-style: none or a clearfix, so the shortcode rendered as a bare bulleted list instead of a grid. I also clamped the columns argument with max( 1, absint( $args['columns'] ) ) so an invalid value like columns="abc" cannot throw a DivisionByZeroError.
PR #66188 fixed a false "Not scheduled" message on the WooCommerce Status page. The Daily Cron check looked for the old wp_next_scheduled('wc_admin_daily') hook, but that migrated to Action Scheduler as wc_admin_daily_wrapper a while back. Swapping the check to as_next_scheduled_action('wc_admin_daily_wrapper') fixed the false alarm on fresh installs.
PR #66273 replaced deprecated jQuery .focus() shorthand calls with .trigger( focus ) across six legacy JS files, clearing the JQMIGRATE: jQuery.fn.focus() event shorthand is deprecated warning that showed up on classic checkout.

If you want to try submitting a fix like these yourself, the WooCommerce Contributing Guidelines walk through the coding standards and PR process the core team expects.

Security Fixes for LifterLMS

LifterLMS gave me 7 merged pull requests in July, and most of them came from running the WordPress Plugin Check tool against the plugin and working through what it flagged.

Two Open Redirect Fixes for the Same Bug

PR #3201 and PR #3209 both replaced wp_redirect() with wp_safe_redirect() in the template loader and the lesson progression controller. I submitted the fix twice, once through a direct patch and once through a scan-driven pass, and both landed with the identical change:

// BEFORE:
if ( $redirect ) {
    nocache_headers();
    wp_redirect( $redirect );
    exit;
}

// AFTER:
if ( $redirect ) {
    nocache_headers();
    wp_safe_redirect( $redirect );
    exit;
}

The $redirect value can come from a filter, which means a third-party plugin could pass in an untrusted URL. wp_safe_redirect() blocks external hosts by default, closing off that open redirect path. The lesson-completion redirect got the same treatment since it also passes through a filter before use.

Fifteen Files Missing Direct Access Protection

PR #3198 added the standard defined( 'ABSPATH' ) || exit; guard to 15 PHP files that Plugin Check flagged, mostly builder view templates:

// BEFORE:
<?php
/**
 * Builder lesson model view
 */
?>
<script type="text/html" id="tmpl-llms-lesson-template">

// AFTER:
<?php
/**
 * Builder lesson model view
 */
defined( 'ABSPATH' ) || exit;
?>
<script type="text/html" id="tmpl-llms-lesson-template">

Two files that Plugin Check flagged already had an equivalent guard, so I left those alone. The fix is mechanical, but it closes off direct HTTP access to files that were never meant to run outside the WordPress bootstrap.

A Stale Cache Broke Media Protection

PR #3194 fixed a bug that only showed up with a persistent object cache like Object Cache Pro active. The authorization result for a protected file gets cached with wp_cache_add(), which only writes when the key does not already exist. If someone viewed an unprotected file first, the 'null' sentinel for "not protected" stayed in cache forever, even after the file was later protected.

// BEFORE:
wp_cache_add( $cache_key, 'null', 'llms_media_authorization', $cache_expiration );

// AFTER:
wp_cache_set( $cache_key, 'null', 'llms_media_authorization', $cache_expiration );

Switching to wp_cache_set() means the cache always reflects the current state. I also added an invalidate_authorization_cache() method and hooked it into the protection-save flow so the cache clears the moment a file's protection status changes.

A Mislabeled File in the Media Library

PR #3181 fixed a labeling bug. When a file was protected through the File block's lock icon, the Media Library attachment screen showed an add-on's label ("protected as an assignment submission") instead of the core label, because the add-on's filter ran for every protected file regardless of who protected it.

$auth_filter        = $protector->get_authorization_filter_name( $post->ID );
$is_addon_protected = $auth_filter && 'llms_attachment_is_access_allowed' !== $auth_filter;
$is_core_protected  = $protector->is_media_protected( $post->ID ) && ! $is_addon_protected;

if ( $is_core_protected ) {
    return $form_fields;
}

Core-protected files now return early with the correct label before the add-on filter ever runs. Add-ons still get to label their own files, since the check compares the actual authorization hook name instead of just checking a boolean.

Small Fixes: Voucher Width and Button Styling

PR #3236 widened the "Uses" input on the voucher edit screen from 50px to 80px, since 4-digit redemption counts like 1000 were getting clipped. PR #3237 added the wp-element-button CSS class to the access plan button so it correctly inherits theme button styling from theme.json on block themes, while leaving classic themes untouched.

Open redirects are a well documented attack pattern outside WordPress too. The OWASP Unvalidated Redirects and Forwards Cheat Sheet explains why letting user input control a redirect target is risky in any web application, not just WordPress plugins.

Teaching Plugin Check to Name Names

My single pull request to the official WordPress Plugin Check tool, the same scanner behind the Plugin Check plugin on WordPress.org, fixed a usability gap in how it validates the Requires Plugins header. Before this change, a plugin declaring more than one dependency got one generic "header is not valid" error with no hint about which slug was the actual problem.

private function check_requires_plugins_header( $result, $requires_plugins, $label, $main_file ) {
    $slugs = array_map( 'trim', explode( ',', $requires_plugins ) );

    foreach ( $slugs as $slug ) {
        if ( '' === $slug ) {
            continue;
        }

        if ( ! preg_match( '/^[a-z0-9]+(?:-[a-z0-9]+)*$/', $slug ) ) {
            // reports an error naming this specific slug
            continue;
        }

        $this->check_requires_plugins_slug_status( $result, $slug, $main_file );
    }
}

Each malformed slug now gets its own error naming that exact slug. Valid slugs get checked against the WordPress.org plugin directory through a transient-cached API call, and a warning appears if a declared dependency cannot be found there. During review, the maintainer pointed out that checking a plugin's local install state was not this check's job. A plugin_repo category check should validate whether a plugin is ready for the directory, so I dropped the original local-state approach entirely in favor of the directory lookup.

Yoast SEO: When a Passing Score Was Still Wrong

Yoast SEO PR #23466 fixed a scoring bug that had been quietly dragging down otherwise perfect SEO analyses. The functionWordsInKeyphrase assessment correctly returns an empty result when a focus keyphrase contains real content words, so it stays hidden from the UI. But the main SEO and taxonomy assessors still counted that empty row in the overall score denominator, which dropped a fully green analysis from around 99 down to about 94.

// BEFORE:
this.assessor = new SEOScoreAggregator();

// AFTER:
this.assessor = new ValidOnlyResultsScoreAggregator();

The related-keyphrase and collection-page assessors already used ValidOnlyResultsScoreAggregator, which skips results without a real score. Switching the main SEO and taxonomy assessors to the same aggregator brought them in line, and every subclass built on top (cornerstone content, product pages, store blog posts) inherited the fix automatically.

The official Yoast developer documentation has more detail on how the SEO analysis pipeline scores individual assessments if you want to dig into the aggregator pattern further.

Ultimate Member: A Redirect That Broke Every Page

Ultimate Member PR #1833 fixed a bug that redirected logged-out visitors to the homepage on every single post, but only on sites running Spectra block themes. The root cause took some digging. Ultimate Member's filter_protected_posts() hooks the_posts, which fires on every WP_Query, not just the main one. During block template resolution, Spectra runs a secondary query for the UM "User" page, and that page's access settings force a redirect. The redirect logic did not check whether it was running on the main query, so it exited the entire request on a background query meant only for template resolution.

// BEFORE: exits on any query, including secondary ones
exit( wp_redirect( esc_url_raw( add_query_arg( 'redirect_to', urlencode_deep( $curr ), um_get_core_page( 'login' ) ) ) ) );

// AFTER: only exits on the main query
if ( is_object( $query ) && $query instanceof WP_Query &&
     ( $query->is_main_query() || ! empty( $query->query_vars['um_main_query'] ) ) ) {
    exit( wp_redirect( esc_url_raw( add_query_arg( 'redirect_to', urlencode_deep( $curr ), um_get_core_page( 'login' ) ) ) ) );
} else {
    $filtered_post = $this->maybe_replace_title( $post );
    $filtered_posts[] = apply_filters( 'um_access_restricted_post_instance', $filtered_post, $post, $query );
}

Secondary queries still apply content restriction through title replacement and post hiding, they just no longer call exit() and kill the page. Direct visits to a genuinely restricted page still redirect correctly, since the main-query check preserves that behavior.

Gutenberg: Bringing Back the Phone-Shaped Preview

Gutenberg PR #80271 restored something editors had lost a while back. Mobile and tablet previews in the post editor used to show a phone or tablet shaped frame. A prior change deprecated the old useResizeCanvas hook, which had injected a fixed device height, and replaced it with a width-only model. The width was correct after that change, but the height just collapsed to fill the editor.

// New private selector deriving device-shaped preview height
function getCanvasHeight( state ) {
    const width = getCanvasWidth( state );
    const ratios = { mobile: 8 / 5, tablet: 4 / 3 };
    const device = getDeviceForWidth( width );

    if ( ! device || ! ratios[ device ] ) {
        return undefined;
    }

    return Math.round( width * ratios[ device ] );
}

Mobile gets an 8:5 portrait ratio and tablet gets 4:3, both matching how the editor looked before the regression. The height only applies at the exact preset width set by the Preview dropdown, so dragging the frame to a custom width frees it to fill the editor again. Desktop preview and the Site Editor's separate resizable frame are untouched.

ElasticPress: Cleaning Up Translator Comments

ElasticPress PR #4323 fixed two warnings that showed up when running wp i18n make-pot. One string had two conflicting translator comments attached to it, and one placeholder had no comment at all.

// BEFORE: two different comments for the same string literal
/* translators: %1$s: first feature name, %2$s: second feature name */
__( '%1$s and %2$s', 'elasticpress' );
// ... elsewhere in the file:
/* translators: %1$s: comma-separated list of feature names, %2$s: last feature name */
__( '%1$s and %2$s', 'elasticpress' );

// AFTER: one consistent comment for both call sites
/* translators: %1$s: feature name(s), %2$s: last feature name */
__( '%1$s and %2$s', 'elasticpress' );

I also added a missing /* translators: %d: Page number. */ comment above a pagination string. Translator comments do not affect runtime behavior, but a clean POT file matters a lot to anyone localizing the plugin, since a missing or duplicate comment leaves translators guessing what a placeholder actually represents.

Pods Framework: Getting Ahead of PHP 8.5

Pods PR #7550 was the largest single-purpose change of the month by file count. PHP 8.5 deprecates the (boolean) cast, and it becomes a fatal error in PHP 9.0. I swapped every occurrence to the canonical (bool) form across 25 files, 139 occurrences total.

// BEFORE:
$params->single = (boolean) $params->single;

// AFTER:
$params->single = (bool) $params->single;

(bool) has been valid PHP since the language's earliest versions, so this is a pure one-to-one swap with zero behavior change. No new tests were needed since the runtime result is identical either way. I grepped the full repository afterward to confirm zero remaining (boolean) occurrences.

The full list of casts and functions PHP is phasing out lives in the official PHP migration guide, which is worth a scan if you maintain a plugin that has not been updated in a while.

WP Rocket: A Tiny Schema Fix With a Real Impact

WP Rocket PR #8583 was the smallest diff of the month, just one line, but it fixed a real WP-CLI compatibility issue. The wp-rocket/get-recommendations ability declared its input schema as [ 'type' => 'null' ], which caused WP-CLI's ability command to reject it outright with "input must be an object, null given."

// BEFORE:
'input_schema' => [
    'type' => 'null',
],

// AFTER:
'input_schema' => [],

An empty array represents "no input properties" in JSON Schema terms and is what WP-CLI expects for an ability that takes no input. One line, but it unblocked WP-CLI from running the ability at all.

What I Learned This Month

Twenty-four pull requests across nine plugins taught me a few things worth writing down.

Security fixes cluster once you start looking. Three separate plugins this month had open redirect or direct-access issues that Plugin Check flagged. Once you run the scan on one plugin, you start spotting the same pattern everywhere else. That is not a coincidence, it is what happens when a whole ecosystem grows organically over a decade.

Cache bugs are the hardest to find and the easiest to miss in review. The Brand Nav cache poisoning issue and the LifterLMS media authorization cache bug both needed a persistent object cache active to reproduce. A plugin can look completely correct in testing and still poison a shared cache key for every visitor on a production site with Redis or Object Cache Pro running.

Duplicate work happens, and that is fine. I submitted the exact same LifterLMS redirect fix through two separate pull requests, and both got merged with identical code. Open source is not always a perfectly coordinated pipeline. Small overlaps happen, and maintainers handle them without much drama.

Small PRs still need real testing. The WP Rocket one-liner and the ElasticPress translator comment fix both look trivial. Both still needed a clear repro, a clear fix, and clear test steps, because a maintainer reviewing a "small" PR still needs to trust that it actually works.

Looking Ahead

July pushed me across more repositories than any month so far, from a REST endpoint that cuts admin requests by 6x to a one-line JSON Schema fix that unblocks WP-CLI. Every plugin here is used by thousands or millions of WordPress sites, and each fix, no matter how small, chips away at friction someone else was living with.

If any of these bugs sound familiar from your own site, that is exactly the kind of thing worth reporting on a plugin's issue tracker. You do not need to write the fix yourself. Flagging the problem clearly is often the hardest part.

If you liked this format, take a look at my May 2026 open source recap and my Co-Authors Plus contributions write-up for more real code from past months.

For the official rules WordPress.org uses to review plugins, the Plugin Check plugin page is the best place to start if you want to run these same checks against your own plugin.

How to Allow “www.” in the Website Field in Gravity Forms

Faisal Ahammad — Thu, 29 Jan 2026 03:50:50 +0000

Allow "www." in the Website Field by accepting URLs that start with "www" even when users omit the protocol. When creating contact forms or user-input forms on websites, it’s common to include a field for users to enter their website URL. Many form plugins, including Gravity Forms for WordPress, validate this website field to ensure users enter a properly formatted URL. However, this validation can sometimes cause issues for users who enter URLs beginning with “www” without specifying the full protocol (e.g., "https://").

This article explains how to customize Gravity Forms’ website field validation to allow URLs starting with “www.” without requiring the “https://” prefix. You’ll also find step-by-step instructions and code snippets that you can add to your WordPress child theme or via a plugin like Code Snippets.

Customizing Validation for “www.” URLs

The good news is that Gravity Forms provides hooks and filters that allow developers to customize validation rules. You can add a filter that intercepts the website field validation process and accepts URLs starting with “www.” by automatically prepending the “https://” protocol internally before validating.

Here is the exact code snippet you can use:

add_filter( 'gform_field_validation', function( $result, $value, $form, $field ) {
    if ( $field->type !== 'website' ) {
        return $result;
    }

    if ( ! $result['is_valid'] && preg_match( '/^www\./i', trim( $value ) ) ) {
        $url_with_protocol = 'https://' . trim( $value );

        if ( GFCommon::is_valid_url( $url_with_protocol ) ) {
            $result['is_valid'] = true;
            $result['message']  = '';
        }
    }

    return $result;
}, 10, 4 );

How This Code Works

The filter hooks into gform_field_validation, which runs during the validation of each form field.
It checks if the field is of type website.
If the validation failed ($result['is_valid'] is false) but the input starts with “www.”, it prepends “https://”.
Using GFCommon::is_valid_url(), it validates the updated URL.
If valid, it sets the validation result to true and clears any error message.

This approach ensures that users entering URLs like www.example.com will pass validation without needing to type the full protocol.

How to Implement This in Your Website

Method 1: Add to Child Theme’s functions.php File

If you have access to your child theme’s files, add the above code snippet at the end of your functions.php file. Make sure to back up your site before editing theme files.

Method 2: Use a Code Snippets Plugin

For a safer and more manageable approach, use a WordPress plugin such as Code Snippets:

Install and activate Code Snippets.
Go to Snippets > Add New in your WordPress admin panel.
Paste the code snippet into the editor.
Save and activate the snippet.

This method avoids touching theme files and makes it easy to manage custom PHP code.

Frequently Asked Questions (FAQ)

Q1: Why does Gravity Forms require URLs to start with “https://”?
By default, Gravity Forms validates URLs strictly to ensure proper formatting and security protocols.

Q2: Can I allow other URL formats besides “www.”?
Yes, you can customize validation further using similar filter hooks depending on your needs.

Q3: Will this code affect other types of fields?
No, this code only targets fields of type “website” in Gravity Forms.

Q4: What if users enter invalid URLs starting with “www.”?
The code still validates URLs using Gravity Forms’ internal function, so invalid URLs will be rejected.

Conclusion

Allowing users to enter URLs starting with “www.” in your Gravity Forms website fields improves user experience and reduces unnecessary validation errors. By adding a simple filter hook in your child theme or using a Code Snippets plugin, you can easily modify Gravity Forms’ default behavior while keeping URL validation robust.

Feel free to reach out if you encounter any issues or want help with other customization!

How to Get Top VPNs for FREE?

Faisal Ahammad — Tue, 25 Nov 2025 05:35:16 +0000

Would you like to get the best VPNs for free or receive a full refund after 3-4 months while still having access to use them for the rest of your purchase plan? The following VPNs currently offer the cashback amounts listed below. These amounts may change when you check.

ExpressVPN - 100%
Surfshark VPN - 100%
Private Internet Access (PIA) - 100%
CyberGhost VPN - 100%
FastestVPN - 100%
NordVPN - 95%

Step 1: Create an Account

First, sign up for a free account on TopCashBack. If you already have an account, skip to Step 3. TopCashBack handles the cashback process and supports multiple payout methods, including PayPal, Virtual Visa Prepaid Card, ACH-supported bank accounts, and gift cards.

FYI, TopCashBack USA has 13,397 ratings on Trustpilot with a 4.6 out of 5 rating, and TopCashBack UK has 157,001 reviews with a 4.5 out of 5 rating.

Step 2: Verify Your Account

Complete your account verification by adding the following information:

Full name
Date of birth

Note: You do not need to add your address. Even if you are outside the USA, it will not affect receiving your cashback.

This verification ensures you can claim full cashback on every purchase without issues.

Step 3: Add Payment Details for Cashback Withdrawal

Go to the Payment Details page and add your withdrawal information. If you want to withdraw via PayPal, just add your PayPal email.

If you want to withdraw cashback to a Virtual Visa Prepaid Card, you don’t need to add payment details now. You can select Virtual Visa later for withdrawal.

For Bank withdrawals, enter:

Account Holder’s Name (must exactly match your bank account)
Account Name (can be any identifier like Wise, Payoneer, nSave, ElevatePay)
Routing Number
Account Number
Account Type (usually “Checking”)

Double-check this info to avoid withdrawal failures or delays, ensuring smooth cashback claims on every AppSumo purchase.

Step 4: Temporarily Disable Ads & Tracker Blockers

Disable any ad blockers or tracker blockers in your browser or computer temporarily. These can block the tracking needed for your purchase to qualify for cashback. Disabling blockers increases the chance of receiving VPN cashback.

Step 5: Activate Cashback

Visit your desired VPN page through the TopCashBack site and click the “Get up to 100% Cash Back” button.

Cashback percentages may vary over time. You will receive the exact percentage shown at purchase time. Following this activation step is crucial to claim full cashback on every AppSumo purchase.

Step 6: Make the Purchase

Shop for any VPN without limits. You can purchase the same items multiple times using new email addresses. After purchase, cashback will appear in your TopCashBack account within 2-48 hours and will become withdrawable in about 14-16 weeks. Withdrawals typically process in 2 business days.

When your cashback posts, you can confirm that you successfully claimed VPN cashback for your purchase.

Using third-party coupon codes will void your cashback. Avoid coupons to ensure full cashback and claim full cashback on every VPN purchase. You may use only the coupon codes listed on the TopCashBack VPNs page.

Withdraw Your Cashback

After receiving the email confirming your purchase tracking, visit your TopCashBack Earnings page to see important details: retailer’s name, purchase date, purchase amount, and cashback amount. Expanding the details shows the estimated payout speed and order ID.

After about 14 to 16 weeks, TopCashBack will email you when your balance is available for withdrawal. On the Earnings page, a "Cash Out" button will appear at the top. Click it to choose how much money you want to withdraw or if you want to donate.

Next, select a payment method. One option is the ACH method, which shows your previously saved bank account info. Confirming this will process your payout; funds should arrive within two days.

Shopping via computer is recommended. Buying from mobile devices often causes tracking issues.

Frequently Asked Questions

Is there a chance I could be scammed?

You will never be scammed because payments go directly to AppSumo, not TopCashBack. Even if TopCashBack disappears, you will still have access to your purchased products. TopCashBack USA has over 13,397 ratings on Trustpilot with an average rating of 4.6 out of 5 (https://www.trustpilot.com/review/topcashback.com). Their UK site has a 4.5 out of 5 rating from over 157,001 reviews. There is no risk of being scammed.

Why do they offer cashback?

They partner with American companies and pay bonuses to drive large volumes of traffic. They then share a portion with customers as cashback. You can find more details about lead generation costs on their help page: https://www.topcashback.com/help/

What if my cashback doesn’t show?

If your cashback doesn’t appear after 72 hours, submit a Missing Cashback Claim form on TopCashBack. This may delay cashback availability by another 4-6 weeks, but rest assured you will receive it. Filing a claim is how you recover and claim full cashback on any AppSumo purchase that didn’t track initially.

If you face any issues, please leave a comment below, so I can help you.

How much PHP knowledge is needed for WordPress and where can you easily learn PHP for WordPress?

Faisal Ahammad — Tue, 30 Sep 2025 14:51:19 +0000

💡 To learn WordPress theme and plugin development, the following PHP stuff would be more than sufficient. This guideline is provided by Kamal Ahmed, who has worked for WPDevelopers, rtCamps, UberSuggest, SiteCare, and other companies.

Variables & Data Types: (string, integer, float, array, object). Minimum 15 array function & 10 string function.
Functions and Scopes.
Loops (for, foreach, while) & Conditions (if, else, switch, try catch).
Working with FORMS: get, post, delete, put difference. Validating and Escaping user submitted data.
Global variables: GET, POST, REQUEST differences and usage.
Include and Require
For Object Oriented PHP:
1. Class,
2. Object,
3. Class property,
4. Class method,
5. Visibility,
6. Static,
7. Inheritance
A little intermediate or relatively less common topics but very important and found sometimes in plugins and themes.
1. Interface, traits, Singleton, Magic Methods, Namespace etc.
2. Output Buffering, SESSION, COOKIES, Working with APIs using curl. Date and Times,
3. Working with files (opening, reading, writing etc)

The most commonly used Functions for manipulating Arrays in PHP.

Please see the documentation for example and details understanding.

Array Functions in PHP

sizeof($array): Use this function to find out how many elements an array contains
array_values($array): Use this function to retrieve all the values from an associative array.
array_keys($array): Use this function to retrieve all the keys from an associative array.
array_pop($array): Use this function to remove an element from the end of an array.
array_push($array, $value): This function adds an element to the end of an array.
array_shift($array): This function removes an element from the beginning of an array.
array_unshift($array, $value): This function adds an element to the beginning of an array.
array_map($callback, $array1): This function returns an array containing all the elements of array1 after applying the callback function to each one. You can pass more than one array. The number of parameters that the callback function accepts should match the number of arrays passed to the array_map()
sort($array): This function sorts the elements of an array in ascending order. String values will be arranged in ascending alphabetical order. Other sorting functions include asort(), arsort(), ksort(), krsort() and rsort().
array_reverse($array): This function reverses the order of elements in an array.
array_merge($array): Use this function when you need to combine data from two or more arrays into a single structure
array_rand($array): This function selects one or more random elements from an array.
array_search($search, $array): This function searches the values in an array for a match to the search term, and returns the corresponding key if found. If more than one match exists, the key of the first matching value is returned.
array_slice($array, $offset, $length): Use this function to break a larger array into smaller ones.
array_unique($array): Use this function when you need to remove non-unique elements from an array
extract($array): Import variables into the current symbol table from an array. For Better understanding read the doc about this function. It is very nice. Its opposite is compact().
array_key_exists($key, $array): This functions returns TRUE if the given key is set in the array.
in_array($searched_value, $array): This functions returns TRUE if the given value exists in the array

The most commonly used Functions for manipulating Strings in PHP

substr(): This function returns the part of the string as an output.
strlen(): This function returns the length of the string
trim(): This function removes the white-spaces from both start and the end of the string.
ltrim(): This function removes the white-spaces from the left part of the string.
rtrim(): This function removes the white-spaces from the right part of the string.
strtolower(): This function converts the string to lower case
strtoupper(): This function converts the string to upper case
str_replace(): The str_replace() function replaces some characters with some other characters in a string.
explode(): This function breaks the string into array on the basis of delimiter passed.
implode(): This function join array elements with a string on the basis of delimiter passed.

Resources

PHP for Beginners (2023 Edition) by Jeffery Way

PHP for Beginners (2023 Edition)

Learn PHP The Right Way by Gio

Learn PHP The Right Way - Full PHP Tutorial For Beginners & Advanced

Credits: Kamal Ahmed

ইংরেজিতে দক্ষতা বাড়ানোর পরিপূর্ণ গাইডলাইন

Faisal Ahammad — Fri, 19 Sep 2025 13:23:54 +0000

ইংরেজি যেহেতু আমাদের মাতৃভাষা না, তাই এই ভাষা শেখা টা একটু কষ্টসাধ্য। তবে বর্তমানে অনেক ফ্রি অ্যাপস, ভিডিও বা কোর্স আছে যেগুলো ইউজ করে দ্রুত সেই সমস্যার কাটিয়ে উঠা সম্ভব। আমাদের উচ্চারণ বা ফ্লুয়েন্সি নেটিভদের মতো হবে না, বা সেটা হয়ত অনেক লং টার্ম গোল হতে পারে। আমাদের উচিত ২য় ভাষা হিসাবে যতটুকু জানলে আমাদের পড়াশোনা বা চাকুরির ক্ষেত্রে সাহায্য করে সেটুকু আগে রপ্ত করা। তারপর ধীরধীরে আরও উন্নতি করতে করতে এক সময় ইংরেজির দক্ষতা আরও উপরে নিয়ে যাওয়া।

লেখাটা মূলত আমার WordPress Support Engineer Resources এর অংশ বিশেষ। যারা নিজেদের সাপোর্ট ইঞ্জিনিয়ার হিসাবে গড়ে তুলতে চান, তারা উক্ত রিসোর্স ফলো করতে পারেন।

How to Learn English: A Structured Approach

Explanation

🆓 - Free
👌 - Recommended
❤️ - Favorite

1. Set Clear Goals

Determine your desired level (beginner, conversational, fluent).
Set a daily practice time such as 10-30 minutes per day.

2. Start with Vocabulary

Focus on high-frequency words used in everyday conversations.
Resources:
- Learn Vocabulary by Maisuns world 🆓 👌
- English Vocabulary 🆓
- Learn Basic English Vocabulary 🆓
- Learn Basic English Vocabulary - Season 2 🆓
- Remember English Vocabulary - Word Association 🆓
- English Words for Every Day 🆓
- American Holiday Words 🆓

3. Move on to Basic Grammar

Learn sentence structure (Subject + Verb + Object).
Focus on common tenses: present, past, future.
Resources:
- A2 English for Developers by FreeCodeCamp 🆓 👌 ❤️
- English Grammar Fundamentals 🆓
- Academic English Grammar 🆓
- Know Your Verbs! 🆓
- English Grammar Made Easy with Alisha 🆓
- Master English Grammar 🆓

4. Learn Common Phrases and Idioms

Practice daily conversation phrases.
Resources:
- Idioms and Phrases 🆓
- English Conversational Phrases 🆓
- Learn English Idioms 🆓

5. Develop Listening Skills

Listen to English podcasts or audiobooks. Try Podcasts in English or BBC Podcasts.
Watch videos with subtitles (e.g., on YouTube).
Resourses:

6. Practice Speaking

Use language exchange platforms (Mobile Apps) like:
- Tandem
- HelloTalk 🆓
- Amar Partner 👌 🆓 ❤️
Resources:
- English for Everyday 🆓
- English Fluency Development 🆓
- English Skills for Academic and Corporate Success 🆓
- Speaking Practice - Speak With Me! 🆓

7. Enhance Reading Skills

Gradually read news or short stories.
Resourses:

8. Work on Writing

Start with simple tasks like a daily journal.
Progress to emails, blog posts, or even short essays.
Resourses:
- IELTS - Writing Test Preparation 🆓

9. Improve Pronunciation

Use apps like Elsa Speak for phonetics and pronunciation practice.
Resources:
- Pronunciation Mistakes 🆓
- Pronunciation Practice! 🆓

❤️ Favorite Resourses

Apps

Websites

YouTube Channels

This structured plan will help you learn English step-by-step, whether you're aiming for basic conversational skills or advanced fluency. Stay consistent, immerse yourself in the language, and use the recommended resources to track your progress.

Let’s find out the best FREE WordPress Form plugin

Faisal Ahammad — Fri, 19 Sep 2025 13:15:15 +0000

WordPress form plugins are no longer limited to just contact forms. Currently, you can use form plugins for booking, subscriptions, CRM integration, product sales, and more! If you want, you can even use the form plugin's API to create your own integrations.

Free or Lite?

There are many free form plugins for WordPress. But most are not free, rather lite versions. To be direct, the plugin available on WordPress.org is usually a limited feature lite version, where you won't get many things. You have to purchase the paid version to unlock all features.

Limited Fields

Even if the plugin name doesn't include "Lite", the following plugins don't allow all fields, settings or options such as form submission, reCaptcha, pre-made form templates, form submission export. Many basic fields are also locked. Only installing the pro version allows using all fields.

Bit Form (43 total fields, 7 locked fields)
- Mollie, Advanced, Singature, PayPal, RazorPay, Stripe, Draft Button
Fluent Forms (48 total fields, 27 locked fields)
- Image Upload, File Upload, Phone, reCaptcha, hCaptcha, Turnstile, Shortcode, Action Hook, Form Step, Ratings, Checkable Grid, Range Slider, Net Promoter Score, Chained Select, Color Picker, Repeat Field, Post/CPT Selection, Quiz Score, Rich Text Input, Save & Resume, Payment Item, Subscription, Custom Payment Amount, Item Quantity, Payment Method, Payment Summary, Coupon
Formidable Forms (42 total fields, 27 locked fields)
- File Upload, Rich Text, Time, Star Rating, Toggle, Lookup, Section, Embed Form, NPS, Tags, Summary, AI, Ranking, Date, Scale, Slider, Dynamic, Repeater, Page Break, Likert Scale, Password, Address, Signature, Appointment, Product, Quantity, Total
Forminator Forms (29 total fields, 1 locked field)
- eSignature
Ninja Forms (30 total fields, 2 locked fields)
- File Upload, Save
weForms (31 total fields, 16 locked fields)
- Repeat Field, Numeric Field, File Upload, Address Field, Country List, Google Map, Step Start, reCaptcha, Shortcode, HP Anti-Spam, Action Hooks, Terms and Conditions, Ratings, Linear Scale, Checkbox Grid, Multiple Choice Grid
WPForms Lite (40 total fields, 24 locked fields)
- Phone, Date / Time, File Upload, Layout, Page Break, Rich Text, HTML, Rating, Custom Captcha, Likert Scale, Address, Website / URL, Password, Repeater, Section Divider, Content, Entry Preview, Hidden Field, Signature, Net Promoter Score, PayPal Commerce, Square, Authorize.net, Coupon
WS Form Lite (55 total fields, 35 unavailable field)

Formidable Forms Date field locked

WPForms Entries locked

weForms locked some essential fields

Free Add-ons

How developer-friendly a form plugin is can be somewhat gauged by looking at community add-ons. Many form plugins have very rich documentation, but they don't provide developer licenses or any support for add-on development for third-party developers. On WordPress.org, you can find quite a few third-party plugins or add-ons for Fluent Forms, Formidable, Forminator, Ninja Forms, and WPForms plugins, which help extend the default features of the plugin.

Support

Another important issue is plugin support. It turns out I got into trouble, but there's no chance of getting help. Free form plugins will only support you in the WordPress.org support forum, and that's always low priority. As a result, you often have to sit with an open ticket for a long time on urgent issues. Also, since WordPress forums have some specific rules, outside of which plugin companies can't offer support, you have many limitations in terms of getting support.

Comparison Table

Plugin Name	View Entries	Export Entries	Embed Entries	Import/Export Form	Free Templates	Forum Support	Ticket Support	WPML Support	Gutenberg Block
Bit Form	✅	✅	❌	✅	Limited	✅	❌	❌	✅
Fluent Forms	✅	✅	❌	✅	Limited	✅	❌	❌	✅
Formidable Forms	✅	✅	❌	✅	Limited	✅	❌	✅	✅
Forminator Forms	✅	✅	❌	✅	Limited	✅	❌	❌	✅
Ninja Forms	✅	✅	✅	✅	All	✅	✅	✅	✅
weForms	✅	✅	❌	✅	Limited	✅	❌	❌	✅
WPForms Lite	❌	❌	❌	✅	Limited	✅	❌	✅	✅
WS Form Lite	✅	✅	❌	✅	All	✅	❌	❌	✅

Selection

Considering all the above issues, the Ninja Forms plugin allows us to use all fields for free. You don't need a pro version to access any features, and they don't sell a pro version either. You'll get everything from reCaptcha, form submission, submission export to pre-made templates for free. You won't see any notice to upgrade to the pro version anywhere.

And even if you're a free user, you'll get free support from their website along with the WordPress.org support forum. This means you won't have to sit with an open ticket for limited support on any urgent issue.

Note: If any information above is incorrect, please let me know in the comments, I'll edit it. You can also inform me if any new features have been added to any form after I wrote my post. Thank you.

How to Protect Sensitive Ninja Forms File Uploads in WordPress

Faisal Ahammad — Fri, 31 Jan 2025 05:07:28 +0000

When handling Ninja Forms file uploads on WordPress websites, ensuring the privacy of sensitive documents becomes paramount. This guide explores how to secure these uploaded files, making them inaccessible to search engines while maintaining full functionality of your forms.

Understanding the Security Concern

When users upload files through Ninja Forms, these documents are stored in your website's wp-content/uploads/ninja-forms directory. While Ninja Forms implements basic security measures, there's always a possibility that these files could be discovered through search engines if additional precautions aren't taken.

The Simple Yet Effective Solution

You can implement two powerful methods to prevent search engines from indexing your sensitive uploads. These methods work together to create a robust security layer that keeps your files private.

Method 1: Utilizing robots.txt

The robots.txt file is like a set of instructions for search engines, telling them which parts of your website they should or shouldn't look at. To protect your Ninja Forms uploads, you'll need to add a simple directive to your robots.txt file:

User-agent: *
Disallow: /wp-content/uploads/ninja-forms/

This code tells all search engines (that's what the asterisk means) to stay away from your Ninja Forms upload directory.

Method 2: Implementing .htaccess Protection

The .htaccess file provides an additional layer of security by sending special headers to browsers and search engines. Create or edit the .htaccess file in your wp-content/uploads/ninja-forms/ directory and add:

<IfModule mod_headers.c>
    Header set X-Robots-Tag "noindex, nofollow"
</IfModule>

This code explicitly tells search engines not to index or follow any links to files in this directory.

Why This Two-Layer Approach Works

Think of it like having both a fence and a security system for your house. The robots.txt file acts as your fence, providing the first line of defense, while the .htaccess file works like your security system, adding an extra layer of protection.

This combination is particularly effective because:

It works with all major search engines
It requires no ongoing maintenance
It doesn't affect the functionality of your forms
It keeps your uploads secure without using external services

Best Practices for File Upload Security

While implementing these protective measures, consider these additional tips:

Regularly review and clean up old uploads
Use strong file upload restrictions in Ninja Forms
Monitor your server logs for any unusual access attempts
Keep WordPress, Ninja Forms, and all plugins updated

Implementation Tips for Non-Technical Users

If you're not comfortable working with website files, don't worry. Here are your options:

Ask your web developer to implement these changes
Contact your hosting provider's support team
Use a website management service

Most hosting providers can implement these changes in just a few minutes.

Frequently Asked Questions

Are uploaded files automatically protected in Ninja Forms?

While Ninja Forms has basic security measures, implementing these additional protections ensures maximum security for your uploads.

Will these changes affect how my forms work?

No, these security measures only affect how search engines interact with your uploaded files. Your forms will continue to work normally.

Do I need both robots.txt and .htaccess files?

While using either method alone provides some protection, implementing both creates a more robust security solution.

Can I still access the uploaded files myself?

Yes, these measures only prevent search engines from indexing the files. You can still access them through your WordPress dashboard or direct links.

Final Thoughts

Implementing these security measures is a crucial step in protecting sensitive information uploaded through your WordPress forms. It's a simple yet effective solution that provides peace of mind for both you and your users, ensuring that confidential documents remain private and secure.

Remember, when it comes to handling sensitive information, it's always better to implement more security rather than less. These measures help maintain trust with your users while protecting their private information from unauthorized access.

The post previously published in my blog post here: How to Protect Sensitive Ninja Forms File Uploads in WordPress

How to Disable WordPress RSS Feeds

Faisal Ahammad — Wed, 08 Jan 2025 04:41:39 +0000

In today’s digital landscape, website owners often seek ways to manage and control the content available to their audience. One such method is disabling RSS feeds in WordPress. This article will walk you through a simple code snippet that effectively disables all WordPress RSS feeds, ensuring that your content remains exclusive to your website visitors.

Understanding RSS Feeds

RSS (Really Simple Syndication) feeds allow users to receive updates from their favorite websites without having to visit them directly. While this feature can be beneficial for some, it may not be suitable for all website owners. Disabling RSS feeds can prevent content scraping and help maintain control over how your content is shared.

Why Disable RSS Feeds?

There are several reasons why you might consider disabling RSS feeds on your WordPress site:

Content Control: By disabling RSS feeds, you retain more control over your content. Visitors will need to visit your site to access your posts and updates, which can increase traffic.
Prevent Content Scraping: Disabling feeds can help protect your content from being copied or scraped by other sites, which is a prevalent issue in the online space.
User Experience: If you prefer that users engage directly with your website rather than through third-party aggregators, disabling feeds can enhance their experience.
SEO Considerations: While RSS feeds are generally good for SEO, some website owners may feel that they dilute the uniqueness of their content, leading to a stronger focus on direct engagement.

The Code Snippet

To disable RSS feeds on your WordPress site, you can use the following PHP code snippet. This code should be added to your theme’s functions.php file or a custom plugin.

/**
 * Disable WordPress RSS Feeds
 * Description: Completely disables all WordPress RSS feeds, including feeds for posts, comments, and categories.
 * @author Faisal Ahammad <me@faisalahammad.com>
 */
function wpb_disable_feed() {
    wp_die( __( 'No feed available, please visit our <a href="' . get_bloginfo( 'url' ) . '">homepage</a>!' ) );
}

add_action( 'do_feed', 'wpb_disable_feed', 1 );
add_action( 'do_feed_rdf', 'wpb_disable_feed', 1 );
add_action( 'do_feed_rss', 'wpb_disable_feed', 1 );
add_action( 'do_feed_rss2', 'wpb_disable_feed', 1 );
add_action( 'do_feed_atom', 'wpb_disable_feed', 1 );
add_action( 'do_feed_rss2_comments', 'wpb_disable_feed', 1 );
add_action( 'do_feed_atom_comments', 'wpb_disable_feed', 1 );

Breaking Down the Code

Function Definition: The function wpb_disable_feed() is defined to stop the feed from being displayed. It uses wp_die() to display a message indicating that no feed is available and prompts users to visit the homepage instead.
Action Hooks: The following action hooks are used:
- do_feed
- do_feed_rdf
- do_feed_rss
- do_feed_rss2
- do_feed_atom
- do_feed_rss2_comments
- do_feed_atom_comments

By adding these hooks, you ensure that all types of feeds are disabled across your site.

How to Implement the Solution

You have several options to implement this code:

Method 1: Using Code Snippets Plugin (Recommended)

Install and activate the Code Snippets plugin
Navigate to Snippets → Add New
Paste the complete code
Enable "Only run in admin area"
Save and activate

Method 2: Via functions.php

You can add this code to your theme's functions.php file, but remember that it will stop working if you change themes.

Frequently Asked Questions

Q1: What happens if I disable RSS feeds?

A1: Disabling RSS feeds means users will not receive updates through feed readers. They will need to visit your site directly for new content.

Q2: Can I enable RSS feeds again after disabling them?

A2: Yes, you can remove the code snippet from your functions.php file or Code Snippets plugin to re-enable RSS feeds at any time.

Q3: Will disabling RSS feeds affect my SEO?

A3: Disabling RSS feeds may affect SEO positively or negatively depending on your content strategy. It could lead to increased direct traffic while reducing visibility through feed readers.

Q4: Is it safe to edit the functions.php file?

A4: Yes, but always ensure you have a backup before making changes as incorrect modifications can break your site.

Q5: Can I disable specific types of feeds instead of all?

A5: Yes, you can choose to disable only specific types of feeds by removing or modifying corresponding action hooks in the code snippet provided.

Conclusion

Disabling RSS feeds in WordPress can be an effective strategy for certain website owners who want to maintain control over their content and enhance user engagement directly on their site. By using the simple PHP code provided, you can easily disable all RSS feeds and redirect visitors to your homepage.

For more tips on managing your WordPress site, feel free to check out Faisal Ahammad's blog.

How to Completely Disable WordPress Admin Notices

Faisal Ahammad — Tue, 07 Jan 2025 08:52:52 +0000

Are you tired of seeing endless notifications cluttering your WordPress dashboard? Those pesky admin notices from plugins and themes can be distracting and sometimes even overwhelming. Today, I'll show you a practical solution to remove all WordPress admin notices permanently while following best practices.

The Problem with WordPress Admin Notices

WordPress admin notices serve an important purpose – they keep us informed about updates, warnings, and important messages. However, when you're managing multiple websites or using several plugins, these notifications can quickly get out of hand. They can:

Distract you from important tasks
Make it harder to focus on essential dashboard elements
Create a cluttered and messy admin interface
Slow down your workflow significantly

The worst part? Some plugins bypass WordPress's standard notification system, making it challenging to manage them effectively.

The Solution: Disable WordPress Admin Notices

I've developed a simple yet powerful code snippet that completely removes all admin notices from your WordPress dashboard. This solution is different from others because it:

Removes ALL types of admin notices
Prevents plugins from bypassing the removal
Uses multiple approaches to ensure complete removal
Follows WordPress coding standards
Works with the latest WordPress version

The Final Code

<?php
/**
 * Disable Admin Notices WordPress
 * Description: Completely removes all admin notices from the WordPress dashboard,
 * including core WordPress notices and those added by plugins and themes.
 * @author Faisal Ahammad <me@faisalahammad.com>
 */

/**
 * Remove all notice actions
 */
function disable_all_admin_notices() {
    remove_all_actions('admin_notices');
    remove_all_actions('all_admin_notices');
    remove_all_actions('user_admin_notices');
    remove_all_actions('network_admin_notices');
}
add_action('admin_init', 'disable_all_admin_notices', 1);

/**
 * Add CSS to hide notice elements
 */
function hide_admin_notices_css() {
    ?>
    <style>
        .notice, 
        .notice-error, 
        .notice-warning, 
        .notice-success, 
        .notice-info, 
        .updated, 
        .error, 
        .update-nag {
            display: none !important;
        }
    </style>
    <?php
}
add_action('admin_head', 'hide_admin_notices_css', 1);

/**
 * Disable notice output
 */
function return_false() {
    return false;
}
add_action('admin_notices', 'return_false', 1);
add_action('all_admin_notices', 'return_false', 1);
add_action('user_admin_notices', 'return_false', 1);
add_action('network_admin_notices', 'return_false', 1);

/**
 * Remove update nags
 */
function remove_core_update_notices() {
    remove_action('admin_notices', 'update_nag', 3);
    remove_action('admin_notices', 'maintenance_nag', 10);
}
add_action('admin_init', 'remove_core_update_notices', 1);

The Code Explained

Let's break down the key components of our solution:

1. Notice Action Removal

function disable_all_admin_notices() {
    remove_all_actions('admin_notices');
    remove_all_actions('all_admin_notices');
    remove_all_actions('user_admin_notices');
    remove_all_actions('network_admin_notices');
}

This function removes all action hooks related to admin notices, preventing them from being displayed in the first place.

2. CSS-based Notice Hiding

The snippet includes CSS rules to hide any notices that might slip through:

function hide_admin_notices_css() {
    ?>
    <style>
        .notice, 
        .notice-error, 
        .notice-warning, 
        .notice-success, 
        .notice-info, 
        .updated, 
        .error, 
        .update-nag {
            display: none !important;
        }
    </style>
    <?php
}

3. Update Nag Removal

function remove_core_update_notices() {
    remove_action('admin_notices', 'update_nag', 3);
    remove_action('admin_notices', 'maintenance_nag', 10);
}

This specifically targets and removes WordPress core update notifications.

How to Implement the Solution

You have several options to implement this code:

Method 1: Using Code Snippets Plugin (Recommended)

Install and activate the Code Snippets plugin
Navigate to Snippets → Add New
Copy the complete code
Enable "Only run in administration area"
Save and activate

Method 2: Via `functions.php`

You can add this code to your theme's functions.php file, but remember that it will stop working if you change themes.

Performance Impact

The good news is that this solution has minimal impact on your website's performance. It only runs in the admin area and uses efficient hooks and methods to remove notices. The CSS rules are also lightweight and only loaded in the dashboard.

Frequently Asked Questions

Will this remove important security notifications as well?

Yes, this will remove all notifications, including security ones. If you need to keep security notices, you'll need to modify the code to exclude specific notice types.

Is it safe to remove all admin notices?

While it's generally safe, you should ensure you have alternative ways to stay updated about important changes and updates on your WordPress site.

Will this affect my website's front end?

No, this code only affects the admin dashboard. Your website's front end remains completely unchanged.

Conclusion

This solution provides a clean, efficient way to declutter your WordPress dashboard by removing all admin notices. While it's important to stay informed about your website's status, having a clean, distraction-free admin interface can significantly improve your workflow efficiency.

Remember to regularly check your site's updates and maintenance needs through other means if you implement this solution, as you won't receive the standard WordPress notifications anymore.

The Post previously published on my blog here: How to Completely Disable WordPress Admin Notices

কিভাবে ওয়ার্ডপ্রেসের বিভিন্ন টিমে কন্ট্রিবিউশন শুরু করবেন?

Faisal Ahammad — Wed, 23 Oct 2024 16:18:27 +0000

ওয়ার্ডপ্রেসে বিভিন্ন ভাবে কান্ট্রিবিউট করা যায়। আপনি একজন নন টেক পারসন হলেও সহজেই কান্ট্রিবিউট করতে পারবেন কোন প্রকার কোড না করেই। চলেন তাহলে দেখি কোন কোন রিসোর্স ফলো করে কিভাবে কন্ট্রিবিউট শুরু করতে পারেন।

আমি #bn_BD polyglots টাইমে GTE হিসাবে আছি। সহজ ভাষার আপনদের থিম/প্লাগিনে কাউকে PTE হিসাবে অ্যাড করতে, কিংবা আপনাদের ট্রান্সলেট করা কোন পেন্ডিং স্ট্রিং আমি অ্যাপ্রুভ করতে পারি। আমার আরেকটা পরিচয় সামনে শেয়ার করব ইনশাআল্লাহ।

১। ছবি তুলে সাবমিট করা

লিঙ্ক: WordPress Photos

রিসোর্স:

২। থিম/প্লাগিনের ইংলিশ শব্দ গুলো বাংলায় অনুবাদ করা।

লিংক: Polyglots

রিসোর্স:

৩। বেশি বেশি অনুবাদ করে প্রজেক্ট ট্রান্সলেশন এডিটর (PTE) হওয়া:

লিংক: ❌

রিসোর্স:

৪। প্যাটার্ন ডিজাইন করা

লিংক: Create New Pattern

রিসোর্স:

৫। ফোরামে সাপোর্ট দেওয়া

লিংক: WordPress Support Forums

রিসোর্স:

৬। ওয়ার্ডপ্রেস কোরে কন্ট্রিবিউট করা

লিংক: ❌

রিসোর্স:

কোন কিছু জানার থাকলে নিচে কমেন্ট করবেন। আপনার কোন পেন্ডিং ট্রান্সলেশন থাকলেও জানাতে পারেন। আমি শনি - রবিবার ফ্রি থাকি। তখন সব অ্যাপ্রুভ করে দেওয়ার চেষ্ঠা করব, ইনশাআল্লাহ।

How and where to start learning free WordPress theme and plugin development?

Faisal Ahammad — Tue, 08 Oct 2024 08:38:09 +0000

Resource Sharing - Sharing is Caring

I have been involved with WordPress plugin and theme development for a long time. Currently, I'm working full-time as a plugin developer for one of the most renowned companies in the WordPress world, based in Florida, USA, for almost 2 years now. There's hardly anyone who uses WordPress but hasn't used our plugins or resource site! Before this, I worked for 2 years at another popular Australian-based WordPress company.

Today, I'll share some resources for getting involved in WordPress development.

WordPress development now uses many advanced and cutting-edge technologies. For example, object-oriented PHP, serverless development, React and Vue.js for plugin dashboard UIs, and much more.

To get into WordPress development, you first need to have basic programming knowledge and know basic web design. You'll find these resources at the end of the post.

Theme Development:

Absolute Basics: Advanced WordPress Theme Development Course by Imran Sayed:

https://www.youtube.com/playlist?list=PLD8nQCAhR3tT3ehpyOpoYeUj3KHDEVK9h

(This shows the very fundamentals of WordPress development)

Headless WordPress Theme Development: Advanced React WordPress Theme Development by Imran Sayed:

https://www.youtube.com/playlist?list=PLD8nQCAhR3tQSv-U_LNdiHEViB1kj6LrM

(This tutorial shows how to create a headless site using React on the frontend and WordPress theme on the backend. Headless sites are in high demand)

Headless WooCommerce: React WooCommerce Theme With Nextjs and REST API by Imran Sayed:

https://www.youtube.com/playlist?list=PLD8nQCAhR3tSRwsvzRtogv9MFkEWo5d9c

(Same thing, but shows in detail about WooCommerce REST endpoints on the backend)

Plugin Development:

Basic WordPress Plugin Development Bangla by Robiz Show:

https://www.youtube.com/watch?v=HxoVIpBfufQ&list=PLFsAA7EWSBTIkLxZDhumQMlfQqNrDyLhP&pp=iAQB

Absolute Basics: WordPress Plugins Development Tutorials by Alessandro Castellani:

https://www.youtube.com/playlist?list=PLriKzYyLb28kR_CPMz8uierDWC2y3znI2

GitHub Source code:

https://github.com/Alecaddd/WordPressPlugin101

Advanced: Advanced WordPress Plugin Development by Imran Sayed:

https://www.youtube.com/playlist?list=PLD8nQCAhR3tTjCulq0Fw3wZxIoN1wVOaV

WordPress Plugin UI Development with React:

https://www.youtube.com/watch?v=XMJrdhvW4vs

https://www.youtube.com/watch?v=k2W5W_I4_H4

Gutenberg Block Development:

Gutenberg Block Development by Robiz Show:

https://www.youtube.com/playlist?list=PLFsAA7EWSBTLd7OREET_-O72lPkxz1GJV

Create Custom Gutenberg Blocks by Alessandro Castellani:

https://www.youtube.com/playlist?list=PLriKzYyLb28lHhftzU7Z_DJ32mvLy4KKH

For Learning React JS:

https://www.youtube.com/playlist?list=PLC3y8-rFHvwgg3vaYJgHGnModB54rxOk3

(I personally learned React from Viswas of Codevalution)

(Let me share a secret, the React beginner tutorial by Sumit Bhai on YouTube - all the examples he gives are taken from Codevalution's tutorial. This suggests that his Bangla playlist is kind of a copy of Codevalution)

Thank you everyone. If you need any more resources, let me know in the comments.

This resource is collected from Ohidul Islam's Facebook post. Full credit goes to him.

Main Post: Learn Wordpress Theme Plugin Development

Let’s find out the best FREE WordPress Form plugin

Faisal Ahammad — Mon, 30 Sep 2024 05:03:50 +0000

Free or Lite?

Limited Fields

Bit Form (43 total fields, 7 locked fields)
- Mollie, Advanced, Singature, PayPal, RazorPay, Stripe, Draft Button
Fluent Forms (48 total fields, 27 locked fields)
- Image Upload, File Upload, Phone, reCaptcha, hCaptcha, Turnstile, Shortcode, Action Hook, Form Step, Ratings, Checkable Grid, Range Slider, Net Promoter Score, Chained Select, Color Picker, Repeat Field, Post/CPT Selection, Quiz Score, Rich Text Input, Save & Resume, Payment Item, Subscription, Custom Payment Amount, Item Quantity, Payment Method, Payment Summary, Coupon
Formidable Forms (42 total fields, 27 locked fields)
- File Upload, Rich Text, Time, Star Rating, Toggle, Lookup, Section, Embed Form, NPS, Tags, Summary, AI, Ranking, Date, Scale, Slider, Dynamic, Repeater, Page Break, Likert Scale, Password, Address, Signature, Appointment, Product, Quantity, Total
Forminator Forms (29 total fields, 1 locked field)
- eSignature
Ninja Forms (30 total fields, 2 locked fields)
- File Upload, Save
weForms (31 total fields, 16 locked fields)
- Repeat Field, Numeric Field, File Upload, Address Field, Country List, Google Map, Step Start, reCaptcha, Shortcode, HP Anti-Spam, Action Hooks, Terms and Conditions, Ratings, Linear Scale, Checkbox Grid, Multiple Choice Grid
WPForms Lite (40 total fields, 24 locked fields)
- Phone, Date / Time, File Upload, Layout, Page Break, Rich Text, HTML, Rating, Custom Captcha, Likert Scale, Address, Website / URL, Password, Repeater, Section Divider, Content, Entry Preview, Hidden Field, Signature, Net Promoter Score, PayPal Commerce, Square, Authorize.net, Coupon
WS Form Lite (55 total fields, 35 unavailable field)

Formidable Forms Date field locked

WPForms Entries locked

weForms locked some essential fields

Free Add-ons

Customer Support

Comparison of Free Features

Plugin Name	Math Calculation	Manage Entries	Embed Entries	Free Templates	Input Mask	Support Channel	WPML Support
Bit Form	✅	✅	❌	Limited	❌	Forum	❌
Fluent Forms	❌	✅	❌	Limited	✅	Forum	❌
Formidable Forms	❌	✅	❌	Limited	✅	Forum	✅
Forminator Forms	✅	✅	❌	Limited	❌	Forum	❌
Ninja Forms	✅	✅	✅	All	✅	Forum & Ticket	✅
weForms	❌	✅	❌	Limited	❌	Forum	❌
WPForms Lite	❌	❌	❌	Limited	✅	Forum	✅
WS Form Lite	✅	✅	❌	All	✅	Forum	❌

Form Selection

Note: If any information above is incorrect, please let me know in the comments, I'll edit it. You can also inform me if any new features have been added to any form after I wrote my post. Thank you.

Main Post: Let's find out the best FREE WordPress Form plugin