<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dongtao Jiang</title>
    <description>The latest articles on DEV Community by Dongtao Jiang (@wpshieldpro).</description>
    <link>https://dev.to/wpshieldpro</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4216667%2F8667be67-2eb2-4894-ad8e-31c6a2b30eb0.png</url>
      <title>DEV Community: Dongtao Jiang</title>
      <link>https://dev.to/wpshieldpro</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/wpshieldpro"/>
    <language>en</language>
    <item>
      <title>A scheduled WordPress post is late: what to check before changing cron</title>
      <dc:creator>Dongtao Jiang</dc:creator>
      <pubDate>Tue, 10 Nov 2026 09:38:27 +0000</pubDate>
      <link>https://dev.to/wpshieldpro-notes/a-scheduled-wordpress-post-is-late-what-to-check-before-changing-cron-25c1</link>
      <guid>https://dev.to/wpshieldpro-notes/a-scheduled-wordpress-post-is-late-what-to-check-before-changing-cron-25c1</guid>
      <description>&lt;p&gt;A post is due at 9:00, but at 9:20 it still has not appeared. That is an example of the symptom, not a diagnosis. Changing a cron setting straight away can leave you with a second problem and less evidence of the first.&lt;/p&gt;

&lt;p&gt;Start by recording the expected publication time, the post’s current status and the time zone shown in Settings → General. Keep the post ID and a screenshot of its schedule. A time entered in one zone and checked in another can look like a delay; changing the site-wide time zone before understanding that difference can affect other work. See WordPress’s &lt;a href="https://wordpress.org/documentation/article/settings-general-screen/" rel="noopener noreferrer"&gt;General Settings documentation&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Find out what is supposed to trigger the work
&lt;/h2&gt;

&lt;p&gt;WordPress normally checks scheduled work during page requests. It does not behave like a system scheduler that wakes at a precise wall-clock time. Low traffic can therefore delay a due task. A site may instead use a hosting or system job to trigger WordPress, so establish which arrangement is actually in use. The &lt;a href="https://developer.wordpress.org/plugins/cron/" rel="noopener noreferrer"&gt;WP-Cron overview&lt;/a&gt; explains the default mechanism.&lt;/p&gt;

&lt;p&gt;Visitor analytics alone will not settle this. A cached response can reach a visitor without making the same request to WordPress. Treat that as a question for the hosting configuration, rather than proof that every recorded visit checked the schedule.&lt;/p&gt;

&lt;p&gt;If there is an external job, record its owner, command or endpoint, target installation and recent execution history. Check the associated WordPress configuration too. &lt;code&gt;DISABLE_WP_CRON&lt;/code&gt; being enabled can be intentional when an external trigger is in place. Do not remove it merely because a post is late, or enable it before a replacement trigger exists. WordPress documents that setup in its &lt;a href="https://developer.wordpress.org/plugins/cron/hooking-wp-cron-into-the-system-task-scheduler/" rel="noopener noreferrer"&gt;system scheduler guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Inspect the queue without replaying everything
&lt;/h2&gt;

&lt;p&gt;For an operator with authorised shell access, this WP-CLI command lists scheduled events:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;wp cron event list --fields=hook,next_run_gmt,next_run_relative,recurrence --format=table
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run it against the intended installation; a multisite network also needs the correct site context. Compare the GMT field with the expected time after accounting for the site’s zone. These are documented fields in &lt;a href="https://developer.wordpress.org/cli/commands/cron/event/list/" rel="noopener noreferrer"&gt;&lt;code&gt;wp cron event list&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The queue tells you what is scheduled. It does not prove that a callback completed its work. Keep the output private if hook names or operational details should not be public, and do not paste a whole production log into a community post.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate a trigger problem from a completion problem
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;wp cron test&lt;/code&gt; checks the spawning mechanism and attempts an HTTP spawn. It is an active diagnostic, so assess the effect of triggering pending work before using it on a live site. An intentionally configured external scheduler can also explain a complaint about disabled WP-Cron. A successful test does not certify every plugin job or business workflow. The distinction matters when interpreting the &lt;a href="https://developer.wordpress.org/cli/commands/cron/test/" rel="noopener noreferrer"&gt;command’s documented checks&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If the trigger appears to work, investigate the affected job: relevant errors, recent plugin changes, timeouts and the expected result. A backup starting is different from a usable backup finishing. A mail job running is different from a message arriving. Avoid replaying all due events as an exploratory shortcut; some callbacks send messages or change stored data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verify the repair against the original symptom
&lt;/h2&gt;

&lt;p&gt;Agree on a small, authorised test, such as a test post scheduled for a future time. Observe its status and public availability under the intended trigger arrangement. Record any manual trigger used during the test: that intervention changes what the result demonstrates.&lt;/p&gt;

&lt;p&gt;Leave a handover note with the trigger owner, schedule, log location, test time and observed outcome. For &lt;a href="https://www.wpshieldpro.com/en/" rel="noopener noreferrer"&gt;WPShieldPro&lt;/a&gt;, this is a useful way to document WordPress maintenance and troubleshooting work: make the result understandable to the next person responsible for the site.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: this article was prepared with AI assistance. The 9:00/9:20 example is hypothetical. Commands are documentation examples, not results from a customer system.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>wordpress</category>
    </item>
    <item>
      <title>WordPress homepage works, internal pages return 404: compare the routes first</title>
      <dc:creator>Dongtao Jiang</dc:creator>
      <pubDate>Tue, 10 Nov 2026 06:02:50 +0000</pubDate>
      <link>https://dev.to/wpshieldpro-notes/wordpress-homepage-works-internal-pages-return-404-compare-the-routes-first-1n7a</link>
      <guid>https://dev.to/wpshieldpro-notes/wordpress-homepage-works-internal-pages-return-404-compare-the-routes-first-1n7a</guid>
      <description>&lt;p&gt;A working homepage does not tell you much about a failing product page. The two requests may reach different content, routing rules or cached responses. Before saving permalink settings or adding redirects, collect a small set of addresses you can test again.&lt;/p&gt;

&lt;p&gt;Start with the working homepage, one failing internal URL, and one other internal URL that still opens. Keep the language directory, spelling and trailing slash exactly as reported. Record when the problem started and any recent migration, slug change or deployment.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Favg2dmupe04hrsbbtmmc.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Favg2dmupe04hrsbbtmmc.webp" alt="Illustration of a working homepage and failing internal page paths" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Check what the request actually returns
&lt;/h2&gt;

&lt;p&gt;Open the failing address as a public visitor. Record the final URL, HTTP status and any redirects. A page displaying “not found” does not, by itself, establish that the response status is 404.&lt;/p&gt;

&lt;p&gt;Then describe the scope. Does one old address fail, every product page fail, or only the English version fail? Those patterns suggest different next checks. They do not establish a cause on their own.&lt;/p&gt;

&lt;p&gt;For a hypothetical comparison, one renamed campaign page might fail while current pages and archives still work. In that situation, checking the old link against the page's current permalink is a useful first step. It is not evidence that the whole site's routing needs replacing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Confirm the content and its current address
&lt;/h2&gt;

&lt;p&gt;Have someone with appropriate access check the original item in WordPress. Is it published? Is it private or still a draft? What permalink does the editor currently show?&lt;/p&gt;

&lt;p&gt;An author preview is not a public availability test. Compare the published address with the actual link in the menu, email or advertisement that brought the visitor there. If a slug changed, preserve that history rather than creating a second copy of the page to make the old URL appear to work.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://wordpress.org/documentation/article/customize-permalinks/" rel="noopener noreferrer"&gt;WordPress permalink documentation&lt;/a&gt; explains the difference between query-based addresses and readable paths, and notes that readable permalinks depend on the server configuration. A technician can compare the real content ID with its readable URL, recording any redirect as well as the final response. An ID-based request that redirects is not an independent test of everything along the route.&lt;/p&gt;

&lt;h2&gt;
  
  
  Give the maintainer a comparison they can repeat
&lt;/h2&gt;

&lt;p&gt;Use a short record rather than a list of changes already attempted:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Address or check&lt;/th&gt;
&lt;th&gt;What to record&lt;/th&gt;
&lt;th&gt;What it helps distinguish&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Working homepage&lt;/td&gt;
&lt;td&gt;Final URL and status&lt;/td&gt;
&lt;td&gt;One responding entry point&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Failing internal page&lt;/td&gt;
&lt;td&gt;Exact URL, status and redirect path&lt;/td&gt;
&lt;td&gt;The reported failure&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Another published internal page&lt;/td&gt;
&lt;td&gt;Same observations&lt;/td&gt;
&lt;td&gt;One item versus a wider pattern&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Current editor permalink&lt;/td&gt;
&lt;td&gt;Publication state and public URL&lt;/td&gt;
&lt;td&gt;Missing content versus an outdated link&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Other language, if applicable&lt;/td&gt;
&lt;td&gt;Actual corresponding page and URL&lt;/td&gt;
&lt;td&gt;Translation availability versus a shared path problem&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;This is a blank investigation template, not a completed test or a customer incident. Do not put private preview links, credentials or unreviewed request logs into a public support discussion.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fke82h3ereel0pbdy1dko.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fke82h3ereel0pbdy1dko.webp" alt="Concept diagram comparing content availability, routing and language paths" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Make one justified change, then repeat the comparison
&lt;/h2&gt;

&lt;p&gt;If failures began after a migration, ask the person responsible for hosting to compare the change record with the current route configuration. Record the existing permalink structure before an authorised adjustment. Changing that structure can change public URLs; a successful dashboard save is not proof that incoming requests now work.&lt;/p&gt;

&lt;p&gt;If cached responses may be involved, compare the same address under documented conditions. Clearing a cache is an action to evaluate, not a diagnosis. After a correction, repeat the original failing request and sample the paths that worked before it. Include the other language where relevant.&lt;/p&gt;

&lt;h2&gt;
  
  
  Leave genuinely missing content missing
&lt;/h2&gt;

&lt;p&gt;A deleted page without an equivalent replacement can correctly return 404. If content moved, consider a redirect to its relevant new destination. Sending every missing URL to the homepage can produce a soft 404 and confuse visitors, as &lt;a href="https://support.google.com/webmasters/answer/2445990?hl=en" rel="noopener noreferrer"&gt;Google's 404 guidance&lt;/a&gt; explains.&lt;/p&gt;

&lt;p&gt;A useful error page can help a visitor navigate while keeping the appropriate response status. The aim is to restore the intended route or handle a missing item honestly, rather than make every address appear successful.&lt;/p&gt;




&lt;p&gt;Adapted from &lt;a href="https://www.wpshieldpro.com/en/wordpress-internal-pages-404/" rel="noopener noreferrer"&gt;WPShieldPro's guide to WordPress internal-page 404 errors&lt;/a&gt;. WPShieldPro is operated by Zhengzhou Wozhitao Technology Co., Ltd. and provides WordPress maintenance and technical support. This adaptation was prepared using AI; the existing concept illustrations are AI-assisted. The technical points were checked against the official documentation linked above. No customer case or completed test is claimed.&lt;/p&gt;

</description>
      <category>wordpress</category>
    </item>
    <item>
      <title>A slow WordPress admin: capture one request before changing plugins</title>
      <dc:creator>Dongtao Jiang</dc:creator>
      <pubDate>Tue, 10 Nov 2026 02:38:06 +0000</pubDate>
      <link>https://dev.to/wpshieldpro-notes/a-slow-wordpress-admin-capture-one-request-before-changing-plugins-2g9g</link>
      <guid>https://dev.to/wpshieldpro-notes/a-slow-wordpress-admin-capture-one-request-before-changing-plugins-2g9g</guid>
      <description>&lt;p&gt;The public homepage loads quickly, but an editor waits after clicking Save. That observation gives you two different paths to investigate. A visitor may receive a cached page; an authenticated save involves application work and may be followed by more requests in the browser.&lt;/p&gt;

&lt;p&gt;Start by describing one action precisely. Avoid changing several plugins and the cache configuration before you have a comparison you can repeat.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnwm9wo9x734ijd6eakbg.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnwm9wo9x734ijd6eakbg.webp" alt="An illustration of a WordPress admin investigation: identify the wait and compare evidence" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Write down the operation
&lt;/h2&gt;

&lt;p&gt;Pick an agreed test item and one action: opening its editor, loading its media library, or saving a harmless change. Record the account role, page, time and time zone, browser, and observed result. Use test content rather than repeatedly changing a customer's live information.&lt;/p&gt;

&lt;p&gt;For example, “the post list opens normally, but this particular editor takes longer to become usable” is a useful hypothetical starting point. It narrows the comparison without proving that the post, browser, or a plugin is responsible.&lt;/p&gt;

&lt;p&gt;If Save appears to stall, check the saved item before pressing it repeatedly. A delayed success message does not establish that the write failed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate the browser's wait from the server's work
&lt;/h2&gt;

&lt;p&gt;Use the browser's Network panel to identify the request associated with the action. Check when it starts, how long it waits, and whether further requests or browser work continue after the response arrives.&lt;/p&gt;

&lt;p&gt;Keep the comparison consistent. Try the same action in another authorised browser session, changing one condition at a time. One quick attempt is a lead; a repeatable difference is stronger evidence.&lt;/p&gt;

&lt;p&gt;Request records can include session information, form contents and personal data. Inspect and redact the material before sharing it with a host or support provider. A full unreviewed HAR file is not a suitable public forum attachment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compare timings, not just query counts
&lt;/h2&gt;

&lt;p&gt;An application diagnostic tool can help explain what happened during a particular request. The &lt;a href="https://querymonitor.com/wordpress-debugging/how-to-use/" rel="noopener noreferrer"&gt;Query Monitor usage guide&lt;/a&gt; describes database and HTTP-call views. Database duration and the component making a query provide context that a query count alone does not.&lt;/p&gt;

&lt;p&gt;Keep two perspectives separate: HTTP calls made by WordPress on the server and requests made by the browser. They describe different parts of the operation. Neither should be presented as a complete historical performance record of the site.&lt;/p&gt;

&lt;p&gt;Have someone with the appropriate access decide where to enable diagnostic tools. A component appearing in a report is a reason to investigate its contribution, rather than sufficient evidence to remove it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Give the host a narrow time window
&lt;/h2&gt;

&lt;p&gt;Share the affected address, operation, actual time and time zone. This helps the host compare application observations with its own records.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://developer.wordpress.org/advanced-administration/performance/optimization/" rel="noopener noreferrer"&gt;WordPress performance overview&lt;/a&gt; covers several factors, including hosting and configuration. A resource spike alongside a slow request is a lead; it does not establish that buying a larger hosting plan will fix the cause.&lt;/p&gt;

&lt;p&gt;Ask what evidence supports the proposed change and which operation should improve afterwards. Public-page speed scores provide context, but they cannot replace testing the editor action that prompted the investigation.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgmhbkfwjudk2cqm2tx5z.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgmhbkfwjudk2cqm2tx5z.webp" alt="Record the affected action, compare evidence, then repeat the same test" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Repeat the original action
&lt;/h2&gt;

&lt;p&gt;Test a suspected cause in an appropriate environment where possible. Agree on backup and recovery arrangements before changing the live site, particularly when forms, checkout or integrations may be affected.&lt;/p&gt;

&lt;p&gt;Keep a small comparison record:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Operation&lt;/th&gt;
&lt;th&gt;Conditions&lt;/th&gt;
&lt;th&gt;Observation&lt;/th&gt;
&lt;th&gt;Next check&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Open the same editor&lt;/td&gt;
&lt;td&gt;Agreed account and browser&lt;/td&gt;
&lt;td&gt;Record the actual wait&lt;/td&gt;
&lt;td&gt;Compare request timing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Save an agreed test change&lt;/td&gt;
&lt;td&gt;Same content and access&lt;/td&gt;
&lt;td&gt;Check the saved result&lt;/td&gt;
&lt;td&gt;Match the timestamp with host records&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Repeat after one change&lt;/td&gt;
&lt;td&gt;Comparable conditions&lt;/td&gt;
&lt;td&gt;Record improvement and new errors&lt;/td&gt;
&lt;td&gt;Keep, revert or investigate further&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;This is a recording template, not a set of completed tests or measured results. If a change does not produce a repeatable improvement, leave the cause unresolved rather than treating one smooth attempt as proof.&lt;/p&gt;




&lt;p&gt;Adapted from &lt;a href="https://www.wpshieldpro.com/en/wordpress-admin-slow/" rel="noopener noreferrer"&gt;WPShieldPro's WordPress admin investigation guide&lt;/a&gt;. WPShieldPro is the WordPress maintenance and technical support brand of Zhengzhou Wozhitao Technology Co., Ltd. This adaptation was prepared using AI; the existing concept illustrations are AI-assisted. Technical points were checked against the official documentation linked above. No customer incident, benchmark or performance promise is presented.&lt;/p&gt;

</description>
      <category>wordpress</category>
    </item>
    <item>
      <title>A WordPress backup finished. What should a restore test prove?</title>
      <dc:creator>Dongtao Jiang</dc:creator>
      <pubDate>Fri, 06 Nov 2026 03:26:59 +0000</pubDate>
      <link>https://dev.to/wpshieldpro-notes/a-wordpress-backup-finished-what-should-a-restore-test-prove-48pi</link>
      <guid>https://dev.to/wpshieldpro-notes/a-wordpress-backup-finished-what-should-a-restore-test-prove-48pi</guid>
      <description>&lt;p&gt;A completed backup job gives you a file, snapshot or recovery point to investigate. It does not yet show that the restored website contains the right content or that its important business journeys work.&lt;/p&gt;

&lt;p&gt;Before touching production, restore a chosen backup into a separate environment. Agree on what you will check and what that environment is allowed to send or change outside itself.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0dflbkj3s36rhiq11f58.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0dflbkj3s36rhiq11f58.webp" alt="Backup files and a database restored to a separate test environment beside a live website" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Concept illustration of a restore exercise, not evidence from a customer incident.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Identify the recovery point
&lt;/h2&gt;

&lt;p&gt;Record the backup identifier, completion time, contents and restore method. Follow the instructions for the actual backup tool or hosting service. Keep credentials and decryption details out of the test report.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://developer.wordpress.org/advanced-administration/security/backup/files/" rel="noopener noreferrer"&gt;WordPress distinguishes files from the database&lt;/a&gt;. Copying the website directory alone does not normally include the database. A database export cannot replace missing product photographs either. Check that the selected backup covers both the files and data needed for the exercise.&lt;/p&gt;

&lt;p&gt;Choose a known record from before that recovery point, such as an existing article or an agreed page change. It gives you something specific to find after restoring.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check isolation before importing
&lt;/h2&gt;

&lt;p&gt;Confirm that the destination has separate files and a separate database. A different web address does not prove that its database is independent of production.&lt;/p&gt;

&lt;p&gt;Also review outgoing connections: form notifications, CRM updates, stock synchronisation, payment services and fulfilment integrations. Route necessary test messages to a mailbox you control and handle each integration according to its supported testing procedure.&lt;/p&gt;

&lt;p&gt;For WooCommerce, &lt;a href="https://woocommerce.com/document/managing-orders/testing-orders/" rel="noopener noreferrer"&gt;test orders can trigger emails and appear in analytics&lt;/a&gt;. Connected services may treat them as real orders. Use a staging environment and the payment provider's supported test mode; settle the integration arrangements before testing checkout.&lt;/p&gt;

&lt;p&gt;A restored copy can still contain customer information. Limit access and use only the information needed for the agreed checks.&lt;/p&gt;

&lt;h2&gt;
  
  
  Follow a complete journey
&lt;/h2&gt;

&lt;p&gt;Start with a representative service or product page. Check its images, navigation and downloads on a phone as well as a larger screen. If the site is multilingual, follow one established translation pair.&lt;/p&gt;

&lt;p&gt;Then continue through a controlled enquiry or order. Use a distinctive marker for a form submission and verify the result at the agreed test destination. Include attachments, department routing or restricted content only where they belong to that site's actual workflow.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzvmz1c2ov3fzkcbqjin6.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzvmz1c2ov3fzkcbqjin6.webp" alt="Backup copy, isolated restore and business checks, with the live site kept separate" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The table below is a planning template, not a completed test result.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Check&lt;/th&gt;
&lt;th&gt;Choose beforehand&lt;/th&gt;
&lt;th&gt;Record afterwards&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Content&lt;/td&gt;
&lt;td&gt;One item created before the backup&lt;/td&gt;
&lt;td&gt;Whether it appears in the restored copy&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Media&lt;/td&gt;
&lt;td&gt;A known image on an agreed page&lt;/td&gt;
&lt;td&gt;Whether the file exists and its page displays it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Language switch&lt;/td&gt;
&lt;td&gt;One translation pair&lt;/td&gt;
&lt;td&gt;The actual destination reached&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Enquiry&lt;/td&gt;
&lt;td&gt;Controlled contact details and a test marker&lt;/td&gt;
&lt;td&gt;Submission, storage and delivery observations within the test arrangements&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Checkout&lt;/td&gt;
&lt;td&gt;A staging payment method and agreed integrations&lt;/td&gt;
&lt;td&gt;The steps tested, observed results and services left unverified&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Explain the gaps
&lt;/h2&gt;

&lt;p&gt;An image can exist in the restored files while its page still requests the production address. Investigate the reference before calling the backup incomplete.&lt;/p&gt;

&lt;p&gt;Similarly, an intentionally disconnected mail service cannot demonstrate delivery to a real customer's inbox. Record that part as unverified. A successful test checkout does not establish that live payments or fulfilment have passed.&lt;/p&gt;

&lt;p&gt;Keep the recovery point in view. In a hypothetical example, Tuesday's enquiries will not be present in a backup completed on Monday. A production recovery plan must account for newer data before anyone overwrites the current site.&lt;/p&gt;

&lt;h2&gt;
  
  
  Leave a usable record
&lt;/h2&gt;

&lt;p&gt;Record the backup identifier, test destination, pages and journeys checked, actual observations, unresolved issues and the person responsible for each follow-up. If you time the exercise, include its scope and environment rather than presenting it as a promise for the next incident.&lt;/p&gt;

&lt;p&gt;Agree what evidence to retain and what should happen to temporary access and test data afterwards. Changes to hosting, the backup service or important site features may justify repeating the exercise.&lt;/p&gt;




&lt;p&gt;Adapted from &lt;a href="https://www.wpshieldpro.com/en/wordpress-backup-restore-test/" rel="noopener noreferrer"&gt;WPShieldPro's backup restore test guide&lt;/a&gt; and shared under its DEV organization. AI assistance was used to prepare and edit this adaptation; the existing concept illustrations are AI-assisted. Technical points were checked against the official documentation linked above. No customer test results are presented here.&lt;/p&gt;

</description>
      <category>wordpress</category>
    </item>
    <item>
      <title>A WordPress form says “sent”. Trace one message before changing SMTP.</title>
      <dc:creator>Dongtao Jiang</dc:creator>
      <pubDate>Mon, 02 Nov 2026 01:51:36 +0000</pubDate>
      <link>https://dev.to/wpshieldpro-notes/a-wordpress-form-says-sent-trace-one-message-before-changing-smtp-ojl</link>
      <guid>https://dev.to/wpshieldpro-notes/a-wordpress-form-says-sent-trace-one-message-before-changing-smtp-ojl</guid>
      <description>&lt;p&gt;A contact form displays a success message, but the enquiry never appears in the team's mailbox. Before replacing the mail plugin or changing DNS, follow one identifiable test through the form, the sending route and the receiving mailbox. Each stage answers a different question.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fu4z3ch26srvvjcr1u0en.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fu4z3ch26srvvjcr1u0en.webp" alt="Three separate checks: the active form notification, the sending record and the receiving mailbox" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Concept illustration prepared for this article, not a screenshot of a delivery log or a customer incident.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Start on the page that is actually failing
&lt;/h2&gt;

&lt;p&gt;Use contact details and a mailbox you control. Submit a short message with a distinctive marker, such as &lt;code&gt;Enquiry test A1&lt;/code&gt;, and note the page URL, time and time zone. Avoid real customer information in the test.&lt;/p&gt;

&lt;p&gt;Keep the initial configuration unchanged. If you change the recipient, sender and sending service together, a successful result will tell you very little about what was wrong.&lt;/p&gt;

&lt;p&gt;Identify the form embedded on that page. A site can contain an old form that nobody uses alongside the current one. Check the active notification's recipient and any conditional routing: choosing a department may send the message to a different address.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate a successful request from a received message
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://developer.wordpress.org/reference/functions/wp_mail/" rel="noopener noreferrer"&gt;WordPress reference for &lt;code&gt;wp_mail()&lt;/code&gt;&lt;/a&gt; explains that a successful return does not prove the recipient received the email. It means the sending method processed the request without reporting an error.&lt;/p&gt;

&lt;p&gt;The form plugin can introduce another distinction. In Contact Form 7, &lt;code&gt;demo_mode: on&lt;/code&gt; displays a successful response while skipping email. Its &lt;code&gt;skip_mail: on&lt;/code&gt; setting also bypasses sending. These are &lt;a href="https://contactform7.com/additional-settings/" rel="noopener noreferrer"&gt;documented Contact Form 7 settings&lt;/a&gt;, not options that necessarily exist in another plugin.&lt;/p&gt;

&lt;p&gt;Check whether such a setting was deliberately left on after testing. Do not enable it as a remedy for missing mail.&lt;/p&gt;

&lt;h2&gt;
  
  
  Find the same test in the sending records
&lt;/h2&gt;

&lt;p&gt;If the site already has a mail log or a sending provider dashboard, search for the test's time, subject and recipient. Establish which sending route the log covers and when logging began. An empty log does not, by itself, show that a visitor never submitted a form.&lt;/p&gt;

&lt;p&gt;Then record the evidence rather than shortening everything to “sent”:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Observation&lt;/th&gt;
&lt;th&gt;Useful next check&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;No matching record&lt;/td&gt;
&lt;td&gt;Check the active notification and the log's coverage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sending error&lt;/td&gt;
&lt;td&gt;Investigate that error with the website or email administrator&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Provider accepted the request&lt;/td&gt;
&lt;td&gt;Read the provider's subsequent delivery or bounce events&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Recipient cannot locate the message&lt;/td&gt;
&lt;td&gt;Check spam, quarantine, filtering and mailbox tracing where available&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Status names vary by provider. Read the definition of the event you actually have; do not treat acceptance at one stage as proof that a person can see the message in their inbox.&lt;/p&gt;

&lt;h2&gt;
  
  
  Retest the real form, not just the mail tool
&lt;/h2&gt;

&lt;p&gt;After addressing an identified issue, use a new marker on the original page. Verify the notification reaches the intended recipient with its expected fields. If department routing, attachments or automatic replies belong to that form's workflow, check those paths too.&lt;/p&gt;

&lt;p&gt;A mail plugin's test button can help test its sending connection. It does not exercise the form's recipient rules or field mapping, so receiving that test is not the end of the investigation.&lt;/p&gt;

&lt;p&gt;Also establish whether enquiries are stored independently of email notifications. Stored entries can help recover a missed enquiry if storage was already enabled; enabling storage later cannot reconstruct submissions that were never retained. Limit access and retention because entries may contain personal information.&lt;/p&gt;

&lt;p&gt;For a handover, leave the form URL, test marker and time, active recipient, relevant sending event, observed mailbox result, and changes already tried. Remove unrelated customer details from shared logs and screenshots. Send credentials through an established secure channel, not in a public troubleshooting thread.&lt;/p&gt;




&lt;p&gt;Adapted from &lt;a href="https://www.wpshieldpro.com/en/wordpress-form-email/" rel="noopener noreferrer"&gt;WPShieldPro's form email troubleshooting article&lt;/a&gt; and shared under the WPShieldPro organization. AI assistance was used to prepare and edit this adaptation and its concept illustration. Technical points were checked against the documentation linked above.&lt;/p&gt;

</description>
      <category>wordpress</category>
    </item>
    <item>
      <title>Before changing a broken WordPress site, write down what failed</title>
      <dc:creator>Dongtao Jiang</dc:creator>
      <pubDate>Fri, 30 Oct 2026 08:28:49 +0000</pubDate>
      <link>https://dev.to/wpshieldpro-notes/before-changing-a-broken-wordpress-site-write-down-what-failed-4mi1</link>
      <guid>https://dev.to/wpshieldpro-notes/before-changing-a-broken-wordpress-site-write-down-what-failed-4mi1</guid>
      <description>&lt;p&gt;A WordPress site loads normally one day and shows a blank page the next. Disabling plugins, switching themes and restoring a backup may each help in the right circumstances. Trying them all at once makes it harder to tell which change mattered. A database restore can also overwrite newer records.&lt;/p&gt;

&lt;p&gt;Before making changes, put together a short incident note. It gives whoever investigates a place to start.&lt;/p&gt;

&lt;p&gt;This blank record is a place to begin. Include the time zone, and keep passwords, complete orders and customer details out of shared screenshots.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;First observed failure and time zone:
Last known working time:
Affected URL and steps to reproduce:
Results while signed out and in the admin area:
Impact on enquiries, orders or account activity:
Recent updates, configuration changes or deployments:
Backup time and what it includes:
Changes already tried, their times and results:
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Record the affected requests
&lt;/h2&gt;

&lt;p&gt;Check the home page, an ordinary inner page and the admin login separately. Repeat the check while signed out. Record what appears: a blank response, a critical error, a timeout or a database connection error.&lt;/p&gt;

&lt;p&gt;Include the URL and steps if a particular action triggers the failure. “The product page loads, but adding an item to the cart fails” is more useful than “the shop is broken.” Establish whether enquiries, orders or account activity are still being recorded.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make a timeline
&lt;/h2&gt;

&lt;p&gt;Note the last known working time, then list updates, theme changes, code snippets, PHP changes, cache settings and migrations. If nobody made a manual change, check automatic updates, hosting notices and deployment records.&lt;/p&gt;

&lt;p&gt;Have one person coordinate further work. Keep a note of each change and result, including unsuccessful attempts, so another person can take over without repeating every test.&lt;/p&gt;

&lt;h2&gt;
  
  
  Preserve current data
&lt;/h2&gt;

&lt;p&gt;Confirm that backups include files and the database. Where possible, preserve a copy of the current failed state and relevant logs. An older backup may help with recovery; the current copy may contain newer orders, content and evidence.&lt;/p&gt;

&lt;p&gt;Restoring files and restoring a database are separate decisions. For shops, membership sites and connected systems, account for records created after the backup before deciding what to restore.&lt;/p&gt;

&lt;p&gt;An isolated copy can help with testing. Prevent it from sending real email, triggering payments or repeating external synchronisation before using it to investigate.&lt;/p&gt;

&lt;h2&gt;
  
  
  Match logs to the request
&lt;/h2&gt;

&lt;p&gt;WordPress, PHP and server logs may provide evidence. Match entries to the request and time rather than treating every historical warning as part of the incident. A plugin path is a lead, not a complete diagnosis.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/" rel="noopener noreferrer"&gt;WordPress debugging documentation&lt;/a&gt; explains logging and error-display options. These tools are intended for local testing and staging; WordPress does not recommend using them on live sites. Start with the host’s existing PHP and server logs where available. If more evidence is needed, have someone familiar with the environment choose a logging approach in an isolated copy. Prepare an appropriate backup before modifications, keep detailed errors away from visitors and check logs for sensitive data before sharing them.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://wordpress.org/documentation/article/faq-troubleshooting/" rel="noopener noreferrer"&gt;official troubleshooting reference&lt;/a&gt; describes options when the admin area is unavailable. File and database changes still require care; ask the host or maintenance provider for help if these operations are unfamiliar.&lt;/p&gt;

&lt;h2&gt;
  
  
  Change one factor at a time
&lt;/h2&gt;

&lt;p&gt;If the failure followed an update, investigate the relationship before making unrelated changes. Where practical, test plugin, theme or environment changes in an isolated copy. Change one factor at a time and record the before-and-after result. Disabling every plugin on a live shop may also disable payments, forms and accounts; a home page that loads afterward is not enough to establish recovery.&lt;/p&gt;

&lt;p&gt;When an adjustment removes the symptom, record what you can reproduce and what remains unexplained. Clearing a cache or reverting a version can change the symptom without establishing the cause.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verify the business flow
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ff6i3vvmym6eub3r667cd.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ff6i3vvmym6eub3r667cd.webp" alt="Troubleshooting sequence: establish impact, preserve, investigate and verify" width="800" height="556"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;A process illustration, not a record of a particular incident.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Check affected pages as an ordinary visitor, then test the relevant function. For an enquiry site, verify submission and receipt. For a shop, check the cart, checkout and order state. For a membership site, check sign-in and permissions. Use controlled tests that avoid real charges and unnecessary customer notifications.&lt;/p&gt;

&lt;p&gt;Leave a record of the symptoms, confirmed findings, changes, checks and unresolved questions. If the cause remains unclear, say so. A temporary recovery should not be described as a permanent repair.&lt;/p&gt;

&lt;p&gt;Adapted from the &lt;a href="https://www.wpshieldpro.com/en/wordpress-critical-error/" rel="noopener noreferrer"&gt;WPShieldPro troubleshooting article&lt;/a&gt;. AI assistance was used to prepare and edit this adaptation. Technical points were checked against the sources linked above.&lt;/p&gt;

</description>
      <category>wordpress</category>
    </item>
  </channel>
</rss>
