WordPress Case Studies & Practical Application 4 — Questions and Answers
Question 1: A staging WordPress site was cloned from production. Users on staging are receiving real emails meant for production customers. What is the fastest safe fix?
- Delete all users on the staging site
- Install a plugin like WP Mail Catcher or disable email sending via wp-config.php constants (Correct answer)
- Change all user email addresses manually
- Move staging to a different server
Correct answer: Install a plugin like WP Mail Catcher or disable email sending via wp-config.php constants
Setting a mail-intercept plugin or defining constants to disable email prevents staging actions from triggering real outbound messages.
Question 2: A WordPress site's Yoast SEO breadcrumbs display incorrectly on WooCommerce product pages after a theme update. What is the recommended first diagnostic step?
- Reinstall WooCommerce
- Switch to a default theme like Twenty Twenty-Four to check if the theme is overriding breadcrumb output (Correct answer)
- Clear the Yoast SEO sitemap cache
- Downgrade Yoast SEO to the previous version
Correct answer: Switch to a default theme like Twenty Twenty-Four to check if the theme is overriding breadcrumb output
Switching to a default theme isolates whether the theme's breadcrumb template is overriding Yoast's output.
Question 3: A client reports that their WordPress site shows 'This site is experiencing technical difficulties' after they activated a new plugin. wp-admin is inaccessible. How do you recover?
- Restore the database from backup
- Rename or delete the plugin's folder via FTP/SSH to deactivate it without wp-admin (Correct answer)
- Re-run the WordPress installer
- Change the admin password via phpMyAdmin
Correct answer: Rename or delete the plugin's folder via FTP/SSH to deactivate it without wp-admin
Renaming the plugin folder via FTP/SSH forces WordPress to deactivate it since the activation record no longer matches an existing directory.
Question 4: An agency builds WordPress sites for clients who are non-technical. They want clients to update content without accidentally breaking layouts. Which approach best achieves this?
- Lock all pages and only allow the agency to edit them
- Use a page builder with locked sections and provide clients with only an Editor or Author role (Correct answer)
- Give clients full Administrator access with a user manual
- Disable the Gutenberg block editor site-wide
Correct answer: Use a page builder with locked sections and provide clients with only an Editor or Author role
Restricting user roles limits dashboard access while page builder lock features prevent accidental structural edits.
Question 5: A WordPress developer is tasked with reducing server load on a high-traffic blog. Query Monitor shows the homepage fires 87 database queries. What is the most effective single change?
- Add more database indexes manually
- Implement a full-page caching plugin to serve static HTML to anonymous visitors (Correct answer)
- Split the homepage into multiple pages
- Disable WordPress comments
Correct answer: Implement a full-page caching plugin to serve static HTML to anonymous visitors
Full-page caching eliminates nearly all database queries for anonymous users by serving pre-generated HTML directly.
Question 6: After importing 50,000 products via WP All Import, the wp_postmeta table has grown to 8GB and queries are slow. What is the primary cause and fix?
- The server's MySQL version is outdated; upgrade MySQL
- Post meta was imported with duplicate or empty meta keys; run cleanup queries and add a composite index on meta_key+post_id (Correct answer)
- WordPress does not support more than 10,000 products natively
- The wp_options table is corrupted
Correct answer: Post meta was imported with duplicate or empty meta keys; run cleanup queries and add a composite index on meta_key+post_id
WP All Import can create duplicate or empty meta rows; cleaning orphaned rows and ensuring proper indexes dramatically speeds up meta queries.
Question 7: A law firm's WordPress site must display a GDPR-compliant cookie consent banner that blocks all tracking scripts until consent is given. Which implementation approach is correct?
- Add a CSS overlay that hides the page until clicked
- Use a consent management plugin that conditionally loads tracking scripts only after user acceptance (Correct answer)
- Move all tracking scripts to the footer so they load last
- Set all cookies to HttpOnly to prevent JavaScript access
Correct answer: Use a consent management plugin that conditionally loads tracking scripts only after user acceptance
A consent management platform gates script execution based on user consent categories, which is the GDPR-compliant approach for tracking cookies.
A staging WordPress site was cloned from production.
Users on staging are receiving real emails meant for production customers.
What is the fastest safe fix?