PropDB is built to be straightforward, but we know not everyone wants to spend their evening wrestling with WordPress plugins, database settings, and configuration screens — especially when there’s a show to put on. That’s where our install service comes in.

We’re the team behind PropDB, and we also happen to run a WordPress agency. So when you ask us to install PropDB on your site, you’re getting it set up by the people who built it.

What’s included

When you book an install, we take care of everything from start to finish. We’ll log into your WordPress site, install and activate PropDB, configure it for the way your company actually works, and walk you through it so you and your team feel confident using it on day one. If your site needs a few preliminary tweaks — a PHP version bump, a missing dependency, a quick performance check — we’ll sort those out too.

A typical install covers:

• Installing and activating PropDB on your existing WordPress site
• Configuring user roles and permissions for your team (designers, stage managers, wardrobe heads, volunteers)
• Setting up your initial categories, locations, and any custom fields you need
• Importing your existing inventory if you have it in a spreadsheet
• A short walkthrough session so your team isn’t left guessing
• Thirty days of follow-up support to iron out anything that comes up once you’re actually using it.

Don’t have a WordPress site yet?

No problem. We can spin one up for you, host it on Canadian infrastructure, and have PropDB live on it within a few days. Your data stays in Canada, which matters if you’re a public arts organization with funding requirements around data sovereignty.

The post Purchase & Install The PropDB Inventory Management System For WordPress appeared first on Web321: Your Best WordPress Support.

Running LearnDash and Breakdance Builder together on WordPress 6.7 or later? You may have already hit the wall: a white screen, a PHP fatal error in your logs, or course list shortcodes silently breaking inside Breakdance-built pages. This plugin fixes that.

What it solves

When WordPress 6.7 tightened strict type enforcement, it exposed a long-standing bug in LearnDash: shortcodes like [ld_course_list] pass comma-separated strings to WP_Query arguments that expect proper PHP arrays. The result is a fatal TypeError in class-wp-query.php that can take your entire site down. On top of that, when Breakdance renders pages server-side, any fatal error inside a LearnDash shortcode crashes the whole page render rather than failing gracefully.

Three targeted fixes, zero configuration required

• WP_Query normalization — Intercepts malformed array arguments via pre_get_posts and converts them to properly typed integer or string arrays before WordPress processes them.
• LearnDash filter normalization — Hooks directly into LearnDash’s own query filters to correct the data at the source, before it ever reaches WP_Query.
• Breakdance SSR guard — Wraps all LearnDash shortcode callbacks in a safe error-recovery buffer so a crash inside [ld_course_list] returns a placeholder instead of killing the page.

Activate it and all three fixes are live immediately — no setup, no API keys, no configuration needed. Each fix can be individually toggled from the settings page if you need to isolate behaviour.

Who it’s for

Any WordPress site running LearnDash (sfwd-lms) and Breakdance Builder together, particularly after upgrading to WordPress 6.7+. The plugin is safe to install even if only one of the two plugins is active — all fixes check for the relevant plugin before hooking in.

Built by Web321 Marketing Ltd. — WordPress specialists, working on the Internet from Vancouver Island since 1996.

The post Learndash + Breakdance Connector appeared first on Web321: Your Best WordPress Support.

WooCommerce reCAPTCHA Checkout adds two independent layers of Google reCAPTCHA to your checkout page simultaneously:

v2 (checkbox) asks the customer to tick “I’m not a robot” — simple, familiar, and effective.
v3 (invisible) silently scores every checkout attempt in the background. Requests below your threshold never reach WooCommerce.

Both layers must pass for an order to go through. Either failure blocks the submission and shows a clear error message to the customer.

Don’t have both key pairs yet? No problem. The plugin detects what’s configured and runs the strongest available mode automatically — v2 only, v3 only, or both.

A built-in key testing tool lets you verify your Google API credentials right from the Settings page — instant pass/fail feedback, no guesswork.

Free, no subscription, no upsell. Built by Web321 Marketing Ltd. in Saanichton, BC to WordPress coding standards.

• Dual-layer protection — v2 checkbox + v3 invisible score, both verified server-side
• Automatic mode detection — works with v2-only, v3-only, or dual key pairs
• Built-in key tester — validate your Google credentials before going live
• Adjustable v3 score threshold — raise or lower sensitivity to match your store’s needs
• Auto-created documentation page — a setup guide published on your site at activation
• WooCommerce HPOS compatible — tested with Custom Order Tables
• WordPress nonce protection — CSRF layer on top of reCAPTCHA
• No third-party dependencies — pure WordPress + Google APIs, nothing else
• Free, no subscription — donate if you love it, that’s all we ask

The post WooCommerce reCAPTCHA Checkout appeared first on Web321: Your Best WordPress Support.

It happens to everyone. You install a plugin, it solves a problem, you move on. Then a year later, $89 appears on your credit card statement. Then another $49. Then $119. You try to remember what each one was for. Half the time you can’t.

WordPress site owners routinely spend $50–$300+ per year on plugin and theme subscriptions with zero consolidated view of what they’re paying. There’s no built-in dashboard. No renewal calendar. No total. Just a growing pile of charges and a credit card statement that doesn’t care whether you’re still using the software.

WP Subscription Tracker fixes that.

Install it once and it automatically scans your WordPress site, identifies your paid plugins and themes, and builds you a single dashboard showing what everything costs, when it renews, and what your WordPress subscriptions total per month and per year.

You’ll get reminder emails before renewals hit. You’ll be able to see at a glance which subscriptions are worth keeping and which ones you’ve been paying for on autopilot. You can add manual subscriptions for anything the auto-detector misses, export the whole list to CSV, and finally have an honest answer to the question every site owner eventually asks: “How much is this WordPress site actually costing me?”

It’s completely free. No account. No data sent off your server. Built in Canada by the team at Web321 Marketing, with privacy and PIPEDA compliance baked in from the start.

Take back control of your WordPress spending.

The post License Tracker for WordPress appeared first on Web321: Your Best WordPress Support.

The post LLMS.txt appeared first on Web321: Your Best WordPress Support.

1. BC unveiled a new budget with higher taxes, service cuts and a spiralling deficit going to $9.6-billion. The BC government needs to find a way to do more with less. It needs to look for efficiencies.
2. The Code With Us put out a project for bids: “Improvements to Air Quality Warnings Shiny App” ( https://marketplace.digital.gov.bc.ca/opportunities/code-with-us/7f216ab7-44ed-414b-b5a9-48988ea44655 ). It’s to be coded with the programming language “R.” It’s a powerful language and used in the BC government IT projects. At $16k, this is a decent little project for some R conversant developer.

I asked myself: How much of this could be done by AI?

First, I drafted the proposal to answer the bid (link) using Claude AI. I’m not going to create a winning proposal. I can’t get this work. I don’t know R and I don’t have any projects with R experience. Nevertheless,a project like this can’t be won if one doesn’t submit a proposal.

Second, I took the project details from the Code With Us post and had Claude AI draft a project requirements document (PRD) ( link ). If the project details were accurate and descriptive, the PRD should reflect what’s involved to build this application.

Third, I built the app. I don’t know R. I have almost 45 years of coding experience, so I know how to get a grasp of a technology that I don’t understand. I know what questions to ask. I took what little I knew. I combined that with a new Github code repository ( link ). I opened up the OpenAI service, Codex and began the code generation. It took several rounds of steering the code, but in the end I had a working application written in R. I put it up in a deployment environment and tried it out. It works. It’s important to note that this works according to the plan and a plan built according to the marketplace opportunity. In a real world use, it may fall short of what’s needed. If it does come up short, the planning step can be re-evaluated and the code build can be re-run.

This isn’t the first time I’ve used Codex to build code. I have used it to quickly build WordPress plugins and apps. I have used other systems like Claude, Loveable, Bolt and Minimax, and Grok to build applications. These AI systems work great to build applications quickly. They all need good planning and oversight, but they can all turn out good code.

In a cash strapped world, we need to find ways to do things better and faster. I used artificial intelligence to write a proposal for this $16,000 project; write a plan; implement that plan; and deploy the application in something like 3 hours.

The Anatomy of a Software Project

An application development project can be described as having three components:

• Planning
• Development
• Viability

Using Artificial Intelligence (AI) to develop applications is sometimes called “Vibe coding.” Almost all of the development is left up to the AI. Taken to the extreme: the planning, development and viability can all be turned over to your favourite AI builder.

Organizations ranging from private industry through to national governments are looking at AI and wondering how it can help them. How AI can speed delivery; drop the headcount in their organization; and/or deflate the budget requirements. AI can accomplish all three.

Planning, development and the application viability could be thought of as a three legged bar stool. If not built right, that bar stool will be a disaster to use. When building a project, these three elements can compete for a finite well of time, money and attention. Short-changing one element, can force the other elements to balloon to cushion the shortfall. It’s the adage of “you can have fast, cheap or good– pick two.” The competing priorities could live in harmony. At the same time, they could be faster, cheaper and better. Pick all three?

Maybe we don’t need to build project bar stools. If we break down these parts of a project when armed with AI, project completion could look very different.

Planning

Planning doesn’t need to be a formal, drawn-out process. In the most simple terms: it’s the headline. What should the application do? What should it work with? What does it do?

Project planning captures the timeline, specifications, diagrams, and details and anything to trap the elements of the project. This planning includes the user interface (UI), the user experience (UX) and a firm picture of what work the application does.

Planning is the most important and least visible part of an application. My personal experience: if a project is exhaustively planned, it can land on a dime. All of the pieces make sense. All of the details are captured. All of the stakeholders appreciate the project.

It’s pretty clear that planning is sometimes skimped out. Many programs show up full of holes. The functionality doesn’t work. There are glaring security holes. They just don’t work.

Development

From a programmer’s perspective, the development is “the work.” We know better, but for all intents and purposes, the programming appears to be the work. Without the code, all you’d have is great planning documents. It often takes up the lion’s share of the time and budget involved. If the planning is clear and succinct, the development phase will be the majority of the project. If planning is shortcut, the development goes from a smooth ride to bumpy disaster. Questions arise. Vagaries fester. It plays out the phrase, “If you fail to plan, you plan to fail.” Inadequate planning will drag out a project. Development without a plan can be an expensive, exhausting exercise in frustration.

Viability

A plan is a good idea. Development is the realization of that plan. Viability: it’s how the project goes out into the world. UI and UX from the planning phases hits the screen. Does it work? Do the users make sense of it? If people dislike the interface, they won’t use it.

Beyond the look and feel, the really big consideration: security. As code does more things– more connectivity, more utility and more performance– there are more opportunities for problems that arise from security holes. Can the logins be faked? Can the data be scooped? Can financial and personal data be siphoned out of the application? An attractive app with big security holes is radioactive.

Assume the application is pretty and all of its security is locked down. Will it work long term? There is a concept called “technical debt.” Technical debt are the awkward parts of launching a program. Can the program be added easily by the user? Is its data portable when needed (migrating to a new device; or restoring a backup)? Can the program be upgraded as needed? Will the code work with newer operating systems? There are thousands of fantastic programs, plugins and tools that worked on old computers, but die on anything from the 2000s. When an application works but hides fussy elements– that application isn’t going to flourish.

After the coding is all done, the other front of viability: adoption. Marketing, documentation, support and marketplace fit are all challenges to the longevity of an application. If a great product is also an unknown product, it’s eventually doomed through a lack of adoption.

Good planning, smart development and lots of testing will expose issues. Viability comes down to the survivability of the application when it goes out into that big cruel world.

How AI Changes The Game

People are still confused about how artificial intelligence works. While touted as intelligence, what it really does well is a colossal exercise in auto complete. Give a chatbot a prompt and it runs with it to satisfy the prompt. Chatbots have indexed massive amounts of programming code from other available projects. They can use that code as an example of how to build new code.

AI works very fast. In the last year, AI gained the capacity to work long. It can take on increasingly larger projects, spending the time to code elaborate solutions. The OpenAI service, Codex, is capable of developing very large and elaborate applications. It can store its code in a code repository– a storage tool to track changes and manage the sharing of the code between developers.

At its core, AI is a computer system: it needs explicit direction to do anything. AI is fantastic at filling in the blanks but those blanks are where variability can creep in. The solution is to be exhaustive on the details. AI can take in a very large set of instructions to work from.

Our workflow: we write a detailed product requirements document (PRD). It outlines what the project needs to succeed. We build that with Claude, iterating the project plan until it’s detailed enough for a developer to work with. If it’s good enough for a developer, it’s good enough for an AI. We hand that PRD to Codex and ask it to develop the application drawing from the PRD details. After the work is detailed, we do a combination of manual and AI driven code reviews. We draft security documents to cover testing and find issues that could threaten the success of the application and the security of its data.

Before the chatbot era, development step took the lion’s share task of a project. A deep planning exercise was always good, but it could be abbreviated by personalities and budget pressures. No one wants to short change the security and viability aspects, but those aspects get squeezed just to get a product out the door. What resulted were applications that did the work, thin on planning and band-aided security.

AI flips the script. The biggest component– the development– can be handed over to Codex and similar tools to build the code. That bulk can be externalized. The work happens much faster. It can happen better. It can be coded at an expert level. The found time and found budget can go into planning to get a clear target. The breathing room can go into the viability topics to ensure it’s safe, it’s appreciated and its utility has some longevity.

How Is This Relevant to 2026 British Columbia?

The BC government’s Digital Marketplace posted a $16,000 opportunity. Depending on billable rates, $16k ranges from 320 hrs. of development at $50/hr.; all the way to 80 hrs. of development at $200/hr.. That 80 – 320 hours of development time should cover planning, development and security / viability. It will likely be a 25%-60%-15% split of where the hours go. Arguably, the majority of any budget goes to the development phase. What happens to project labour breakdowns if the majority of the work can get replaced with AI?

Imagine if the project splits were to radically change:

• 40% of the budget into planning and prep;
• 20% of the budget goes to the development;
• 40% of the budget goes to security and the longevity of the application.

Beyond re-cutting the resource pie, shrink the pie. Look at the $16k project above. If they forecast that 60% of the project or $9600 went to development, but that could be done with a few hours of vibe coding and a strong requirements document– then a project needs less time to deliver. Replace that $9600 bulge with 12 hours of development; precede it with 24 hours of planning; and follow it with 24 hours of viability work. Use AI to get more out of the planning work; and then get more out of the viability steps at the end of the project. Maybe a $16k project could become a $10k project delivered faster and better thanks to AI. That’s a savings. Wherever there is knowledge work (coding, number crunching, etc.), AI can play a role in delivering that work better, faster and for less money. The delivery comes down to skill.

Organizations look at AI with technological superstition. They think it will simultaneously take all the jobs and do the work poorly. Some organizations have laid off people or stalled hiring because they’re replacing people with AI systems. Those organizations have seen minimal wins. They’re missing the role of AI.

AI in the workplace is not about replacing people. It’s about enhancing them. Think of a good suite of AI tools and techniques as an Iron Man suit, not a robot worker. Your people could do more, do it better and do it faster. That found time can be sunk into making solutions that are more ruggedized and well tested.

Organizations looking to deliver more for less need to look at what artificial intelligence can do to help. Imagine if the BC government could deliver its IT projects for less money? That’s not going to knock down the tremendous BC government deficit, but every little bit helps.

The post AI Led Programming appeared first on Web321: Your Best WordPress Support.

This article explores the key reasons why Breakdance outperforms Elementor across performance, features, cost-effectiveness, and overall user experience.

1. Performance: Clean Code vs. "Divitis"

The Problem with Elementor

Elementor has become infamous for what developers call "divitis"—the excessive nesting of HTML div containers that bloat your site's code. Every section, column, and inner section adds layer upon layer of unnecessary markup. A simple "About Us" page can end up with 47+ nested <div> containers.

Real-world Elementor performance:

• Google PageSpeed Score: 35-50 (mobile)
• Load time: 4-7 seconds
• Requires 3-4 caching plugins just to be "acceptable"

Breakdance's Superior Approach

Breakdance was built in 2021 with a clean slate—no legacy code, no backward compatibility baggage, no bloat.

Performance comparison:

Breakdance achieves this through:

• Themeless architecture — disables the WordPress theme entirely, eliminating theme-related bloat
• jQuery independence — doesn't rely on heavy JavaScript libraries
• Loads only needed assets — no unnecessary CSS/JS loading
• "Divception" elimination — minimal, semantic HTML output

"When we migrated one of our clients from Elementor to Breakdance—same design, same content, same hosting—their Core Web Vitals scores went from red to green overnight. Their bounce rate dropped by 23%. Their conversion rate increased by 18%." — Web321

2. Built-In Features: No More "Add-On Hell"

Elementor's Hidden Cost

Elementor's ecosystem is massive—but that's also its weakness. To build a professional site, you typically need:

• Elementor Pro ($399/year for 1000 sites)
• Essential Addons for Elementor
• Premium Addons for Elementor
• WooCommerce add-ons
• Form plugins
• Mega menu plugins

Total annual cost: $1,200+

Breakdance's "Everything Included" Philosophy

Breakdance ships with 145+ built-in elements—no add-ons required:

Breakdance pricing: $199.99/year for unlimited sites

"I just dumped Elementor on a few client sites and rebuilt with Breakdance. I dropped 8 plugins that Elementor needed." — Jonny Stalnaker, Lumos Agency

3. Superior Dynamic Data & Conditional Logic

Breakdance includes advanced dynamic data features that Elementor locks behind third-party add-ons:

Breakdance supports both ACF and Metabox natively—no additional plugins needed.

4. Form Builder & Power Features

Forms That Actually Work

Advanced Builder Features

5. WooCommerce: Designed for E-Commerce

Breakdance was built from the ground up to be the best visual builder for WooCommerce. Here's what makes it special:

Breakdance WooCommerce advantages:

• Deep, seamless integration out of the box
• Granular control over cart and checkout pages
• Product loop builder for custom product displays
• Global WooCommerce styles (no theme dependency)
• Beautiful default designs—zero styling required

With Elementor, you need:

• Elementor Pro for basic WooCommerce widgets
• Separate WooCommerce theme or template pack
• Hours of custom styling
• Additional WooCommerce add-on plugins

"Breakdance's default WooCommerce pages look incredible. Install WooCommerce, activate Breakdance, and your shop pages, product pages, cart, and checkout all look professionally designed—without touching a single setting." — Web321

6. Global Styles & Design System

Breakdance offers superior global styling capabilities:

The Bottom Line: Why Breakdance Wins

When to Choose Each Builder

Choose Elementor if:

• You already have an Elementor site that works fine
• You need a specific third-party add-on only available for Elementor
• You don't mind managing multiple plugins and slower load times

Choose Breakdance if:

• You want a fast, professional website that ranks well in Google
• You value clean code and design freedom without bloat
• You want full-site editing that actually makes sense
• You sell products online and want beautiful WooCommerce pages
• You want one tool that does everything instead of 12 add-ons
• You value your time, money, and sanity

Conclusion

Breakdance represents the next evolution of WordPress page builders. Built with modern standards, optimized for performance from day one, and packed with features that Elementor charges extra for, it's the clear choice for professionals who demand more from their tools.

The migration path is straightforward—same designs, same content, dramatically better results. As Web321's real-world testing shows, the only variable that needs to change is the builder itself.

Ready to make the switch? Your clients (and your PageSpeed scores) will thank you.

Sources

• Breakdance Official Comparison
• WPAllImport Comparison
• Web321 Analysis
• Pronto Marketing Review

The post Why Breakdance is Better Than Elementor: A Comprehensive Comparison appeared first on Web321: Your Best WordPress Support.

You updated WordPress.
Your site now shows a blank page, error messages, or does not load.

This situation is common.
It affects thousands of sites every week.

In early 2026, one cause explains most failures.

Short answer:
Your server runs an outdated PHP version. WordPress no longer supports it.

WordPress 6.7 and later require newer PHP. Many hosts still run PHP 7.4. That version reached end of life in 2022. It no longer receives fixes or security patches. Modern WordPress code does not work reliably on it.

When WordPress updates and PHP stays old, the site breaks.

Why WordPress Fails After Updates

1. PHP Version Mismatch

This is the primary cause in 2026.

WordPress core now assumes PHP 8.x features.
PHP 7.4 cannot parse that code.

PHP 7.4 reached end of life on November 28, 2022.
It receives no security updates.
It receives no bug fixes.

Many plugins and themes no longer support it.
WordPress itself is removing backward compatibility.

Hosts keep PHP 7.4 active to avoid server work.
They expect customers to react after failures appear.

Common error messages include:

Fatal error: Uncaught Error
Parse error: unexpected token
Call to undefined function

If your server runs PHP 7.4 or lower, this explains the failure.

2. Plugin Conflicts

Plugins that connect deeply to WordPress core often fail first.

Security plugins intercept file loading.
Caching plugins override output logic.
Page builders rely on internal WordPress functions.

When WordPress updates, those internals change.

Older plugins call functions that no longer exist.
Newer plugins assume PHP 8 syntax.

PHP 7.4 cannot interpret that syntax.

This mismatch causes fatal errors before pages render.

3. Theme Incompatibility

Themes fail when developers stop maintaining them.

Risk increases when:

• The theme has not updated in over a year
• The developer no longer supports it
• The theme targets PHP 7.x only

A single unsupported function can block page output.

4. Hosting Infrastructure Problems

Many shared hosts run outdated server stacks.

They delay PHP upgrades.
They restrict memory and execution time.
They cache files aggressively at the server level.

After an update, WordPress loads new files.
The server still serves cached old files.
The system enters a mixed state.

This conflict breaks page output.

5. Database Errors

Database issues occur less often but cause total failure.

Common causes include:

• Interrupted updates
• Permission changes
• Table corruption
• Encoding conflicts

These errors stop WordPress before content loads.

6. File Permission Issues

Updates can change file ownership on some servers.

Security plugins may lock files.
FTP uploads may assign incorrect permissions.

WordPress then fails to read or write required files.

Why This Started Happening More Often

PHP 7.4 support ended years ago.
Compatibility lasted longer than expected.

WordPress maintained backward support to protect users.
That window has closed.

WordPress 6.7 uses PHP 8 features by default.

PHP 7.4 cannot parse them.

This change affects every site that updates core or plugins.

How to Fix a Broken WordPress Site

Emergency Option 1: Restore a Backup

Restore the last working version.

This returns the site to a stable state.
It buys time to apply proper fixes.

Emergency Option 2: Disable Plugins

If admin access fails:

1. Rename the plugins directory
2. Reload the site
3. Restore plugins one at a time

This process isolates the failure source.

Emergency Option 3: Switch Themes

Rename the active theme directory.

WordPress loads a default theme automatically.

If the site loads, the theme caused the failure.

Permanent Fix: Upgrade PHP

This step is required.

Modern WordPress needs PHP 8.1 or higher.

Upgrade PHP through your hosting control panel.
Test the site after the change.

If the host cannot upgrade PHP quickly, the host is the issue.

When Hosting Is the Problem

Warning signs include:

• PHP upgrades require paid plan changes
• Support avoids technical explanations
• Updates take days to approve
• PHP versions lag behind standards

These conditions increase failure risk.

How to Prevent Future Failures

Use Staging

Test updates on a copy of the site first.
Match PHP versions between staging and live.

Maintain Backups

Use daily automated backups.
Store them off the server.
Verify restore access.

Monitor PHP Compatibility

Check plugin and theme requirements before updates.

Maintain the Site

Routine checks prevent emergency failures.

When to Get Professional Help

Get help if:

• The site generates revenue
• Errors persist after basic fixes
• Database errors appear
• No recent backups exist

Downtime costs more than repair.

Final Takeaway

WordPress failures after updates follow a pattern.

Outdated PHP causes most issues.
Budget hosting increases risk.
Lack of testing triggers downtime.

PHP 7.4 will continue to break sites.

Upgrade now under control.
Do not wait for the next failure.

The post WordPress Broken After an Update? Here’s What Actually Happened appeared first on Web321: Your Best WordPress Support.

The post WordPress Consultants appeared first on Web321: Your Best WordPress Support.

Layout Structure

Basic Content Elements

Media Elements

Interactive Elements

Form Elements

Navigation Elements

Dynamic Content & Templates

WooCommerce Elements

Advanced Widgets

Key Terminology Differences

The post The WordPress Page Builder Rosetta Stone appeared first on Web321: Your Best WordPress Support.