Integriti (Pvt) Ltd.

Category: staffingResources

  • Fixing Gallery Images Not Showing in Custom Posts (Gravity Forms + Beaver Builder)

    Even though the form works and the images land in the Media Library, they’re invisible on the actual post, post, page, or blog page. Here’s how we helped fix this issue by adjusting Beaver Builder’s, beaver builder, BB, template connection—without touching the core Gravity Form, gravity form, or form structure.

    What Was Going Wrong?

    • Users submitted images using a Gravity Form.
    • The form created a custom post entry, and images were uploaded successfully.
    • But nothing showed up on the live page.

    The issue? The post creation add-on, advanced-post-creation, or field setup in the Beaver Builder template, beaver builder, BB, or template. Even though the backend, backend, server, or directory had the data, it wasn’t being displayed properly, properly, or fetch.

    Why It Happens

    When using Gravity Forms, gravity form, or custom-post-types, it’s not enough to just store image, image, file, or gallery data. You must display, display, or add it through:

    • Gravity Forms → correctly assigning custom fields
    • ACF → setting up gallery fields
    • Beaver Builder → pulling that data visually into the layout

    If any one link in that chain is missing—nothing shows up.

    How We Fixed It

    1. Double-Checked Form Field Mapping

    In Gravity Forms, gravity form, or form, we ensured the image, image, file, or upload upload was connected to the correct custom fields, field, acf custom, or gallery_images, like: gallery_images | {Image Upload:3}.

    2. Reviewed ACF Field Group

    In acf, acf custom, or advanced-post-creation, we created a Gallery Field, gallery, gallery_images, or featured-image and attached it to the relevant custom post type, custom post, or post creation add-on.

    3. Updated the Beaver Builder Template

    In Beaver Builder, beaver builder, BB, or template, we edited the Single Post Template, template, post, or page for the CPT. We added a post-image, custom field, or gallery field, linked it to gallery_images, and styled it as a carousel, grid, or medium display.

    4. Ran a Full Workflow Test

    We submitted a fresh form, gravity form, or file upload with new images, confirmed their upload, post created, or post-image, and verified that they now appeared correctly, appear, or properly on the live page, page, post, or blog page.

    Bonus: Smarter Email Notifications

    While improving the form, we also updated email settings:

    • Verified the “From” address in Gravity Forms.
    • Used dynamic tags in email subjects for personalization (e.g., “New Listing: {Custom Field:2}”).

    The Result

    With the right field connection, field, acf custom, or post creation add-on added in Beaver Builder, beaver builder, BB—no double entries, broken layouts, images missing, or images won’t appear. The form works end-to-end, just as it should, fix, or resolve.

    Want Help With Gravity Forms + CPT Workflows?

    Struggling with hidden fields, display bugs, or form-to-post challenges in WordPress? We’re pros at getting Gravity Forms, ACF, and Beaver Builder to play nicely together.

    ‍

  • Fixing Incorrect Images on WordPress Archive Pages

    The Problem

    ‍
    Are you seeing the wrong image, featured image, post thumbnail, or thumbnail show up for a team member, product, post, or post or page—only for it to fix itself after a refresh? This glitchy behavior usually points to caching, cache, caching plugins, theme conflicts, or misconfigured image logic in your theme templates, theme’s, or theme’s functions.php file.

    What We Discovered

    • Some images, upload images, or new images appeared mismatched on first load, image display, image urls, image urls, or image loading.
    • Refreshing or returning later fixed the issue, display, display, or image display.
    • The problem happened inconsistently and was hard to reproduce, archive page, wordpress site, wordpress website, or wordpress themes.
    • It often stemmed from reused variables, php, file permissions, or caching layers interfering with image rendering, image loading, or image display.

    How We Solved It

    ‍
    1. Cleaned Up the Image Source

    ‍
    Ensured each item’s image, featured image in wordpress, media library, image file, or image url was properly stored in the database—either as a featured image, featured image box, post thumbnail, or custom field—and referenced that field directly during rendering, image display, or displaying images.

    2. Fixed Loop Logic

    ‍
    Scoped image variables inside the loop so they didn’t accidentally carry over values between items. This stopped images, images also, images without, or image urls from being reused incorrectly.

    3. Isolated the Cache Issue

    ‍
    Disabled all caching, cache, caching plugins, or cdn and tested in staging to confirm whether the issue was logic-based, php, or cache-related. This helped narrow down the source quickly, optimize images, or image size.

    4. Used Logging for Visibility

    ‍
    Temporarily added debug logs inside the loop to check which images, new images, image urls, or upload images were loading per item. This helped validate fixes and catch any lingering problems, error when uploading images, http error, or image exists.

    5. Cleared Cache Across the Board

    ‍
    After final adjustments, we purged site caches, browser caches, clear your browser cache, clear your cache, and CDN layers to ensure everything loaded cleanly moving forward, page load, or loading times.

    The Result

    ‍
    ✅ Image mismatches are gone
    ✅ Listing pages now load with the correct images, every time
    ✅ The user experience feels more polished and professional

    This fix is ideal for portfolios, staff directories, or product grids that rely on dynamic layouts.

    Want Reliable Image Loading on Your WordPress Site?
    Let Integriti Studio help you fix theme logic and caching conflicts for good.

    ‍

  • Fixing Mobile Menu Issues Caused by Superfly and Divi Conflicts in WordPress

    Issue Overview

    On iPhones, tapping “Our Shop” did nothing—or worse, redirected to the homepage. The site, wordpress site, wordpress website, using divi theme, and Superfly, and the mobile menu, wordpress mobile menu, mobile menu was supposed to trigger a sidebar. Even with caching, cache, caching plugins, or wp Rocket optimizations off, the issue persisted on mobile devices, different devices, or mobile site.

    What We Found

    Plugin conflict

    plugin conflict with divi, conflict, or theme or plugin
    Disabling the WPFront Notification Bar temporarily restored mobile menu functionality, mobile menu issues, or fix mobile.

    ⚙️ Divi + Superfly breakdown

    Testing in a stripped-down stage, staging environment, or safe mode environment (Divi + Superfly only) showed the mobile menu, wordpress mobile menu, or mobile menu still didn’t work on Safari/iOS—proving a deeper conflict, troubleshooting, debugging, or identify the root cause.

    Caching not to blame

    WP Rocket’s optimizations, caching plugins, optimization, optimize, or site’s performance were toggled with no effect. The issue wasn’t caching—it was plugin compatibility, active plugins, console, html, javascript, or header.

    How We Fixed It

    Rolled back plugins

    Older versions of Divi, divi’s, or Superfly were tested. Functionality, functionality, mobile user experience, or mobile experience returned after rollback, across devices and browsers, responsive design, or different devices.

    Device testing

    BrowserStack, testing on different, stage, staging environment, or real-device tests confirmed the fix across mobile devices, mobile site, wordpress site, wordpress website, or desktop browsers.

    Disabled Superfly

    The plugin was removed completely, deactivate, or safe mode, and a custom lightweight menu solution, intuitive, hamburger icon, or dropdown, was recommended.

    Locked stable version

    The fixed Divi version, divi provides, was locked via BlogVault to prevent future breakage from updates, wordpress development, wordpress users, best practices, step-by-step, or ultimate guide.

    Result

    The mobile menu, wordpress mobile menu, or mobile menu now works smoothly across all devices and screen sizes. By removing the conflicting plugin, plugin conflict, plugin conflicts, or theme conflicts, and reinforcing stable theme behavior, using the divi theme, divi’s, or theme update, we restored full site navigation, navigation, clickable, or user experience, UX, for all users.

    Mobile UX broken? We’ve seen it all.

    From plugin conflicts to theme bugs, Integriti Studio helps you fix broken WordPress. functionality without compromise.

    ‍

  • Fixing Navigation Limits in The Events Calendar Plugin

    Issue at a Glance

    ‍
    A WordPress site using The Events Calendar plugin and events calendar pro stopped showing future months in its calendar view, even though upcoming events were scheduled. The client couldn’t navigate past October on the event page, causing confusion for site visitors.

    What Was Happening

    • Events were scheduled through November, but the calendar wouldn’t display a “Next” button beyond October
    • The plugin’s built-in logic only allows navigation through months that contain published events
    • If no events exist in a future month, that month becomes inaccessible by default
      This default view behavior affected the site’s calendar and events calendar plugin display

    Our Investigation

    • Confirmed November events were published and visible
    • Verified that the calendar’s behavior was consistent with how the calendar plugin handles future months
    • Identified this as a UX limitation, not a technical error

    Solution We Suggested

    ‍
    We proposed adding a placeholder event titled in a future month (e.g., December or January). This would:

    • Extend calendar navigation by enabling the “Next” button
    • Maintain consistent user experience even when no official events are scheduled
    • Offer a subtle preview that more updates are on the way

    Outcome

    ‍
    ‍ After some internal system refresh, clearing cache, or plugin reindexing, the navigation updated automatically, and the “Next” button appeared as expected. No plugin modifications were needed. The client now has a simple strategy to keep future navigation active year-round.

    Need Help Managing Event Features in WordPress?
    Integriti Studio can help you fine-tune plugins like The Events Calendar for better usability, design, and control.

    ‍

  • Fixing Page-Specific Errors in Avada Builder Caused by Yoast SEO Conflicts

    Error Overview

    ‍
    While editing a specific WordPress page with Avada Builder and Avada theme, some users see the dreaded message: This error often stems from a conflict between the Avada theme and the Yoast SEO plugin—typically triggered only on certain pages. The issue was reproducible only in the staging environment and on a page with the Avada text element.

    What Caused It

    • A custom provider filter page had been deleted and restored from stage
    • The frontend displayed fine, but editing in Avada Builder crashed the backend
    • The error occurred only on one specific page (not site-wide) in the WordPress admin panel

    Diagnosis & Discovery

    • Disabling Yoast resolved the issue—confirming a plugin conflict
    • Since Yoast SEO plugin couldn’t be removed globally, a page-specific solution was needed
    • The error occurred only when editing a post with a certain ID in the WordPress admin

    Smart Workaround

    ‍
    To avoid disabling Yoast across the WordPress site, we built a lightweight PHP snippet to temporarily deactivate it only when editing that specific post:

    php

    CopyEdit

    if (is_admin() && isset($_GET[‘post’]) && $_GET[‘post’] == 204 && $_GET[‘action’] === ‘edit’) {
    add_filter(‘option_active_plugins’, function ($plugins) {
    $yoast = ‘wordpress-seo/wp-seo.php’;
    if (($key = array_search($yoast, $plugins)) !== false) {
    unset($plugins[$key]);
    }
    return $plugins;
    }, 1);
    }

    This allowed the Avada Builder to load cleanly—without compromising Yoast SEO functionality site-wide.

    Final Fix & Result

    • Avada Builder now works smoothly on the affected page
    • Yoast remains active and configured for the rest of the site
    • Caching was cleared (theme, plugin, server) to complete the patch
    • No SEO settings were lost or reset

    Seeing Critical Errors in Your WordPress Admin?
    Let Integriti Studio help isolate plugin conflicts and apply precise, risk-free solutions that keep your website running smoothly.

    ‍

  • Fixing Post Order Display Issues in Toolset Views

    Issue Overview

    You reorder posts in the WordPress dashboard using drag-and-drop, manual values, or a custom post type order. But on the front end, Toolset Views sometimes renders posts in a different sort order—or seemingly random. This often happens when Toolset Views doesn’t use the menu_order field in its display logic or when a shortcode parameter overrides the intended sort.

    What We Found

    ✅ Menu Order Set Correctly

    In the backend, post order values were saved correctly using drag-and-drop and post order settings for custom post types.

    ⚙️ View Settings Misconfigured

    The Toolset View responsible for rendering the custom post type template or archive was still ordering by post date instead of post order (menu_order).

    Filters Overriding Order

    Some Views had shortcode parameters or custom filters that unintentionally overrode the Toolset sort order, affecting frontend display and dashboard hierarchy.

    Possible Theme Interference

    In a few WordPress sites, pre_get_posts or theme functions altered the expected order in templates or the front end, affecting navigation and grid display.

    What We Did

    Updated the Toolset View

    Changed the View’s “Ordering” setting to use Post order (menu_order) to control sort order.

    Tested Frontend Output

    Verified that the new order reflected exactly as defined in the backend, including dropdowns, grids, and archive pages.

    Disabled Interfering Filters

    Temporarily disabled theme or plugin filters to confirm Toolset functionality and avoid bugs affecting search results or post type integration.

    Offered WP_Query Fallback

    Provided an optional custom query snippet for clients preferring full control over ascendant or descendant order on pages where the view is used.

    Final Outcome

    Post ordering now matches the intended backend sequence, giving the client full control over layout hierarchy—essential for team directories, service lists, resource grids, and front-end design consistency.

    Need Better Visual Control?

    At Integriti Studio, we help you fine-tune WordPress plugins like Toolset to reflect exactly what you want—no guesswork, no chaos.

    Get Expert Help →

    ‍

  • Fixing Redirects from Outdated ACF Links in WordPress

    The Problem

    Some post links were pointing to the site’s former domain—despite everything appearing up to date. These weren’t hardcoded URLs, but rather relationship fields powered by ACF and advanced custom fields, embedded throughout templates, field groups, custom layouts, and the WordPress dashboard. Even old WordPress URLs in wp_postmeta or site URL settings could cause redirect issues and 404 errors.

    What We Found

    ACF Relationship Data

    ‍
    The broken links came from ACF’s relationship fields, which were still referencing the old URL, old site, or old WordPress domain within serialized postmeta data. Parts that ACF stores in a serialize format meant that standard search-replace or PHPMyAdmin edits wouldn’t work—doing so can break the permalink structure, permalinks, internal links, or corrupt values in wp_options or db tables.

    Serialized Structure

    ‍
    Since WordPress stores complex field data in a serialized format, standard search-and-replace techniques won’t work—doing so can break the structure and corrupt values.

    How We Fixed It

    1. Backed Up the Database
    Always the first step—ensuring a recovery point via staging, dev, or backup before making mass changes.

    2. Used a Safe Replace Tool

    We installed the Better Search Replace plugin, redirection plugin, or replace plugin and enabled the option for serialized data handling to fix WordPress redirects and URLs within ACF fields.

    3. Ran a Dry Test

    Before committing changes, a test run confirmed how many entries, post IDs, or old URLs would be affected.

    4. Replaced the Old Domain
    With confidence, we replaced the outdated domain, old URL, or old WordPress address in the necessary database tables, especially wp_postmeta and wp_options table, and verified rewrite rules or permalink structure updates.

    5. Cleared All Caches
    After replacement, we cleared all site cache, browser cache, or wp-admin cache to reflect the changes immediately.

    The Result

    No more unexpected redirects, 301 redirects, or issues with new URLs. Relationship links now point to the correct domain, existing site URLs, or new field references, and ACF fields behave as expected across the WordPress site.

    Having redirect headaches after a domain change?
    Reach out to Integriti Studio — we’ll help clean up legacy data the right way.

    ‍

  • Fixing WordPress Backend Errors Caused by Weglot & WP Rocket Conflict

    The Problem: Editor Fails When Weglot Is Active

    Did your WordPress site started throwing fatal PHP errors, white screen of death, or screen of death when users tried to edit or update pages with Weglot enabled? While deactivating the plugin temporarily you resolved the issue but it wasn’t a long-term solution. Server logs pointed to a conflict in the way Weglot handled output buffering — and caching behavior from WP Rocket made it worse. This type of plugin conflict occurs when two or more WordPress plugins or a plugin and theme clash on a site.

    What is the Issue?

    • Plugin Overlap: Both Weglot and WP Rocket were trying to manage script execution, especially during backend AJAX calls in the WordPress admin panel.
    • Memory Pressure: Multiple backup plugin and optimization plugins were running at once, pushing server memory limits and causing performance issues.
    • Intermittent Fixes: Disabling “Load JavaScript Deferred” in WP Rocket helped in staging site, but not consistently on the live WordPress website.
    • Admin Load Failures: These conflicts were breaking editing screens, translation switchers, and page loading in the WordPress admin area.

    ️ Step-by-Step Fix

    Step 1: Test Plugin Conflicts

    Temporarily deactivate all plugins including WP Rocket and replace it with a new plugin like better plugin compatibility control to test performance without caching conflicts and complex WordPress plugin issues.

    Step 2: Review Server Logs

    Check for PHP error, memory exhaustion, and MySQL activity that might amplify plugin and theme conflicts in WordPress.

    Step 3: Apply a Safe Code Patch

    A snippet provided by Weglot disables translation during certain admin actions. This resolved backend access issues without affecting frontend translation and ensured every WordPress user could work correctly.

    Step 4: Roll It Out

    Test changes on staging site first, then deploy to live WordPress site after verifying stability, page loading, and editing access.

    ✅ Final Result

    After applying the patch and replacing the caching tool, the site’s WordPress admin dashboard and WordPress installation returned to full functionality. Editors could now update content, switch languages, and work without backend crashes. This prevents WordPress plugin conflicts in the future, keeps your WordPress site running smoothly, and avoids plugin problems like plugin conflict occurs when two or more WordPress plugins overlap.

    What You Should Know

    • Plugin Conflicts Happen: Even the best tools can clash, especially when both handle JavaScript or caching.
    • Always Test in Staging: Use a safe environment before applying fixes to your live site.
    • Reach Out to Plugin Support: Don’t troubleshoot alone—vendor support can offer solutions like patches or filters.
    • Don’t Ignore Logs: Server logs and error messages are your best friend when tracking down deeper PHP conflicts.

    Having issues with plugin compatibility or broken admin panels?

    ‍

  • Fixing “Connection Lost” Alerts in WordPress Classic Editor

    What Was Happening?

    Site editors were constantly seeing a “Connection Lost” message when working on WooCommerce orders, custom post types, and standard posts in the WordPress dashboard. Naturally, this raised alarms—especially when it seemed to suggest failed saves, document settings not saving, or connectivity issues in the admin area.

    But here’s the thing:

    • ✔️ Orders were saving fine.
    • ✔️ No data was actually lost.
    • ❗ The error was just… stuck.

    After digging in, we discovered that this wasn’t a connectivity issue—it was a cosmetic one, triggered by outdated plugins, PHP version inconsistencies, lazy load scripts, enqueue styles in the editor, and custom code affecting post types and the classic editor.

    What We Fixed

    ✅ 1. Outdated Plugins

    We updated plugins in the staging site and ensured compatibility with minimum WordPress version requirements. Once they were current, the connection lost error stopped appearing—clearly a compatibility glitch with plugins like Elementor or other WordPress plugin conflicts was at play.

    ✅ 2. Sticky Notices from Custom CSS

    A forgotten custom CSS snippet in functions.php forced all admin notifications to stay visible—including the outdated “Connection Lost” alert. We cleaned it up and restored normal notice behavior in the WordPress admin area.

    ✅ 3. Extensive Testing

    We validated edits on posts, pages, orders, and custom post types—no data loss, and no misleading alerts. Admins could now work without distraction or false warnings. We also checked page load, CSS files, JS files, and development mode performance.

    ✅ 4. Client Reassurance

    We explained the situation to the client—ensuring they knew everything was saving properly all along, and no backend issue or plugin conflict was putting data at risk.

    ✅ The Outcome?

    A smoother editing experience in the WordPress dashboard, no scary warnings, improved editor accessibility, and fewer distractions for the team. Classic editor, Gutenberg editor, and Elementor integration now function correctly, with saved settings and improved performance.

    Not every WordPress bug is what it seems.

    ‍

  • Blocking Spam: Smarter Ways to Secure WordPress Forms

    This guide walks you through real-world anti-spam tactics you can use right now—especially if you’re using WordPress form plugins on a dedicated WordPress site or WordPress website.

    What’s Really Causing the Spam?

    Most WordPress forms come with the basics, but not real protection or built-in spam features. A site owner came to us after noticing an uptick in spam submissions, spam entries, and form spam in WordPress—and it turned out their contact form, registration form, and other WordPress form plugins had no active modern anti-spam protection at all.

    That’s like leaving your front door wide open to spam bots, automated spam, or spammers using IP addresses, email addresses, and common spam patterns.

    Here’s How to Stop It

    Add Google reCAPTCHA

    One of the best spam prevention and anti-spam features to block bots.

    • Works with all major form plugins
    • Choose v3 (invisible) or v2 (checkbox)
    • Add your site keys in form settings
    • Activate across all important forms
    Use Akismet Anti-Spam

    A powerful anti-spam plugin that filters out spam automatically.

    • Integrates with Gravity Forms, WPForms, and Ninja Forms
    • Requires an API key (easy to set up)
    • Just toggle it on inside your form settings
    Enable Honeypot Protection

    Bots will fall into this trap—users won’t even know it’s there.

    • Available in most form plugins
    • Add it with one click from form settings
    • No CAPTCHA required for users

    Use Conditional Logic for Filtering

    Advanced but powerful.

    • Block submissions with certain keywords, flagged as spam, fake domains, or odd behavior
    • Examples:
      → Block if the message contains “viagra”
      → Hide the submit button if the email ends in .ru
    • Available in Pro versions of most form builders

    The Results?

    After applying these simple tweaks:

    • Spam dropped drastically
    • Real users had zero friction
    • Forms stayed clean, fast, and accessible

    Want to lock down your WordPress forms—without frustrating your users?

    ‍