Knowledgebase
Browser Troubleshooting (2)
Clearing your browser’s cache can help fix loading issues, display the latest version of a website, and improve overall browsing performance. Below are step-by-step instructions for deleting cache in the most commonly used browsers.
Google Chrome
- Open Chrome and click the three dots in the top-right corner.
- Select More tools > Clear browsing data.
- In the popup, choose a time range (e.g., All time to clear everything).
- Check Cached images and files.
- Click Clear data.
Mozilla Firefox
- Open Firefox and click the three horizontal lines in the top-right corner.
- Go to Settings > Privacy & Security.
- Scroll to Cookies and Site Data.
- Click Clear Data….
- Check Cached Web Content and click Clear.
Microsoft Edge (Chromium-based)
- Open Edge and click the three dots in the top-right corner.
- Select Settings > Privacy, search, and services.
- Under Clear browsing data, click Choose what to clear.
- Select Cached images and files, and choose a time range.
- Click Clear now.
Safari (macOS)
- Open Safari.
- In the menu bar, click Safari > Preferences.
- Go to the Advanced tab and enable Show Develop menu in menu bar.
- From the top menu, click Develop > Empty Caches.
Safari (iPhone/iPad)
- Open Settings.
- Scroll down and tap Safari.
- Tap Clear History and Website Data.
- Confirm by tapping Clear History and Data.
Google Chrome (Android/iOS)
- Open the Chrome app.
- Tap the three dots (menu).
- Go to History > Clear browsing data.
- Select a time range.
- Check Cached images and files, then tap Clear data.
Pro Tips
- Clearing the cache does not delete saved passwords or bookmarks (unless you select those options).
- After clearing the cache, you may need to re-log into some websites.
- If a website still doesn’t load correctly, try clearing cookies as well.
Sometimes your browser shows an older cached version of a webpage. A hard reload forces the browser to fetch the latest files from the server instead of using the cache. Here’s how to do it on the most common browsers:
Google Chrome
- Windows/Linux: Press Ctrl + Shift + R or Ctrl + F5
- Mac: Press Command + Shift + R
Mozilla Firefox
- Windows/Linux: Press Ctrl + Shift + R or Ctrl + F5
- Mac: Press Command + Shift + R
Microsoft Edge (Chromium)
- Windows/Linux: Press Ctrl + Shift + R or Ctrl + F5
- Mac: Press Command + Shift + R
Safari (Mac)
- Hold Shift and click the Reload button in the toolbar
- Or press Command + Option + R
👉 Tip: If a hard reload doesn’t work, you can also clear your browser cache from the settings menu and then reload the page.
Really Simple Google Analytics (1)
Your Google tag (also called a Google Analytics Measurement ID or Google Tag ID) is what you paste into plugins or your site settings to connect your website with Google Analytics.
Steps to find your Google tag:
- Log in to Google Analytics at analytics.google.com.
- In the left-hand menu, click Admin (gear icon).
- Under Property, select Data Streams.
- Choose the web data stream for your site.
- At the top right, you’ll see your Measurement ID, which looks like:
G-XXXXXXXXXX
Notes:
- This ID is unique to your property and must be copied exactly.
- If you’re using multiple websites, make sure you select the correct data stream before copying the tag.
RestoreShield Backup (0)
WordPress (3)
To troubleshoot website issues with Edge’s InPrivate mode, open a new InPrivate window and visit the problematic website to see if issues persist—this isolates problems tied to cache, cookies, or extensions[1][2]. If a website works in InPrivate mode but not in your regular window, the problem is likely related to cached data, cookies, or a browser extension interfering with the site[1][3].
Steps for Troubleshooting with InPrivate Mode
- Open Edge and click the three dots in the top-right corner, then select “New InPrivate window,” or press Ctrl + Shift + N for a shortcut[1][2].
- Navigate to the site you want to troubleshoot in the newly opened InPrivate window[1][2].
- Attempt to replicate the issue in this window. If the problem disappears, it’s likely due to cache, cookies, or an extension in your normal browser session[1][3].
- If the issue remains even in InPrivate, it may not be browser-related and could require further investigation of the site or system[1].
Why This Works
- InPrivate mode starts a fresh session with no existing cookies, cached files, or login states, letting you see how the site behaves for a “first-time” visitor[1][2].
- Most extensions are disabled by default, which helps identify extension conflicts[2].
- If testing resolves the issue, clearing cache/cookies or disabling problematic extensions in your regular browser session can fix it[1].
Using InPrivate mode is a standard first diagnostic step for web access, login, or display issues[1][2].
Sources
[1] How to Use InPrivate Mode in Microsoft Edge for Troubleshooting https://knowledge.prokeep.com/knowledge/how-to-use-inprivate-mode-in-microsoft-edge-for-troubleshooting
[2] How to Use Incognito/InPrivate Window – MyHelp https://myhelp.northwoodtech.edu/kb/article/258-how-to-use-incognito-inprivate-window/
[3] Problems accessing sites except in InPrivate mode https://techcommunity.microsoft.com/discussions/edgeinsiderdiscussions/problems-accessing-sites-except-in-inprivate-mode/2702957WordPress debugging allows you to see PHP errors, warnings, and notices, which can help you troubleshoot issues with your site. Debugging is controlled by a few constants in the
wp-config.phpfile.Steps to enable debugging:
- Connect to your site using FTP or your host’s File Manager.
- Locate and edit the
wp-config.phpfile in the root directory of your WordPress install. - Add or update the following lines above the line that says “That’s all, stop editing!”:
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false );WP_DEBUGturns debugging on.WP_DEBUG_LOGsaves errors to a file calleddebug.loginside/wp-content/.WP_DEBUG_DISPLAYhides errors from showing on the front end (recommended for live sites).
- Save your changes and reload your site. Errors will now be logged to
debug.log.
Notes:
- Remember to disable debugging (
false) when you’re done troubleshooting. - For a step-by-step tutorial with examples, check out our Complete Guide to Enabling and Configuring WordPress Debugging.
Common Locations of wp-config.php
By default, wp-config.php is located in the root directory of your WordPress site — the same folder that contains
index.php,wp-content, andwp-includes. If you log into your hosting account and browse to the public_html or www folder, you’ll usually find it there.Some site owners or hosts move wp-config.php one directory above the root for an extra layer of security. If you don’t see it next to your other WordPress files, check one level higher. Just remember, its exact location can vary slightly depending on your hosting setup.
Methods to Locate the File
There are several ways to access wp-config.php, depending on the tools you have available:
- File Manager in Hosting Control Panel
If your host provides cPanel, Plesk, or a custom dashboard, log in and look for File Manager. Navigate to your site’s root directory (commonlypublic_html) and you’ll see wp-config.php listed there. - FTP or SFTP Client
Programs like FileZilla or Cyberduck let you connect directly to your server. Once connected, browse to the root folder of your website and look for wp-config.php. This method is handy if you want a copy of the file on your computer before making changes. - SSH Command Line
For advanced users, SSH access allows you to use commands likecdandlsto move around directories and list files. Head to your site’s root directory and wp-config.php should appear in the listing. - Managed WordPress Hosts
If you’re on WordPress.com or a managed host like WP Engine, direct file access may be restricted. In those cases, wp-config.php is managed behind the scenes, and you won’t be able to edit it directly.
Troubleshooting if You Can’t Find It
Still not seeing the file? Double-check that you’re in the right folder by looking for other WordPress files like
index.phpandwp-content. If your host hides certain files by default, make sure hidden files are enabled in your file manager or FTP client. And if you’re on a platform that doesn’t grant file access, you may need to reach out to your hosting provider for support.- File Manager in Hosting Control Panel
If your WordPress site’s emails (helpdesk emails, order confirmations, contact form messages, password resets) keep landing in spam, it’s usually because mail servers can’t verify that your domain is authorized to send them.
By adding SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) records to your DNS and routing WordPress mail through a proper SMTP service, you can dramatically improve email deliverability.
What Are SPF & DKIM?
- SPF: A DNS TXT record that lists which mail servers are allowed to send email for your domain.
- DKIM: A cryptographic signature added to outgoing messages, proving they haven’t been altered and were sent by an authorized server.
Most modern inbox providers (Gmail, Outlook, Yahoo) expect both SPF and DKIM to pass for best deliverability.
Before You Begin
- Access to your domain DNS manager (GoDaddy, Cloudflare, Namecheap, etc.).
- Access to your email provider’s admin panel (Google Workspace, Microsoft 365, or your SMTP service).
- An SMTP plugin for WordPress (recommended options below).
Step 1 — Add or Update Your SPF Record
- Log in to your domain DNS host.
- Locate existing SPF TXT record (starts with
v=spf1). - If you don’t have one, create a new TXT record:
Name/Host: @ Type: TXT Value: v=spf1 include:_spf.google.com include:spf.yourhost.com ~all- Replace includes with the services you use (e.g., SendGrid, Mailgun, Microsoft 365).
- Keep only one SPF record — combine all senders in it.
- Keep under 10 DNS lookups.
- Use
~all(soft fail) or-all(hard fail) at the end.
Step 2 — Enable DKIM Signing
- In your email provider’s dashboard, look for “Authenticate Email” or DKIM settings.
- It will give you a TXT record similar to:
Name/Host: google._domainkey Type: TXT Value: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBA...- Some providers use selectors like
selector1._domainkey. - Publish exactly as provided.
- Use 2048-bit keys if available for stronger security.
- Wait for DNS to propagate (can take up to 24 hours).
- Verify DKIM status in your email provider’s dashboard.
Step 3 — Route WordPress Mail Through SMTP
WordPress’ built-in
mail()function is unreliable and often flagged as spam. Use an SMTP plugin so your messages are sent through your authenticated mail server.Popular SMTP plugins:
- WP Mail SMTP
- Post SMTP
- FluentSMTP
Once installed:
- Connect to your email provider (Gmail, Outlook, Amazon SES, SendGrid, etc.).
- Authenticate using API or SMTP credentials.
- Send a test email to verify.
Step 4 — Test Your Setup
- Use Mail-Tester.com to send a test and check if SPF=PASS and DKIM=PASS.
- Tools like MXToolbox SPF & DKIM Lookup can verify DNS propagation.
Step 5 — Add DMARC for Extra Protection (Optional)
Once SPF & DKIM pass, add a DMARC record to tell mail servers what to do if a message fails authentication:
Name/Host: _dmarc Type: TXT Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; aspf=r;- Start with
p=noneto collect reports. - Later, change to
p=quarantineorp=rejectfor stricter protection.
Quick Troubleshooting
- Duplicate SPF records cause failure — merge them.
- DNS changes may take up to 24 hours to propagate.
- If you use multiple mail services (e.g., WooCommerce + newsletter), include all in SPF and set DKIM for each.
- Check email headers (Gmail: More → Show original) to see SPF/DKIM pass/fail.
Summary
- Add SPF to list approved sending servers.
- Add DKIM to sign messages.
- Use an SMTP plugin to send from your authenticated mail server.
- Optionally enable DMARC for extra trust and reporting.
With these steps, your WordPress emails are far more likely to land in your customers’ inboxes — not spam.
WordPress Debug Log Viewer (3)
WordPress debugging allows you to see PHP errors, warnings, and notices, which can help you troubleshoot issues with your site. Debugging is controlled by a few constants in the
wp-config.phpfile.Steps to enable debugging:
- Connect to your site using FTP or your host’s File Manager.
- Locate and edit the
wp-config.phpfile in the root directory of your WordPress install. - Add or update the following lines above the line that says “That’s all, stop editing!”:
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false );WP_DEBUGturns debugging on.WP_DEBUG_LOGsaves errors to a file calleddebug.loginside/wp-content/.WP_DEBUG_DISPLAYhides errors from showing on the front end (recommended for live sites).
- Save your changes and reload your site. Errors will now be logged to
debug.log.
Notes:
- Remember to disable debugging (
false) when you’re done troubleshooting. - For a step-by-step tutorial with examples, check out our Complete Guide to Enabling and Configuring WordPress Debugging.
Overview
The WordPress Debug Log Viewer (WDLV) Premium edition lets you receive real-time alerts in Slack whenever errors appear in your WordPress debug log. This guide walks you through connecting your Slack workspace to WDLV using Incoming Webhooks.
Step 1 — Create a Slack App with Incoming Webhooks
- Go to the Slack API Apps page.
- Click Create New App → From Scratch.
- Enter an app name (e.g.
WDLV Alerts) and choose your Slack workspace. - In the left sidebar, click Incoming Webhooks.
- Toggle Activate Incoming Webhooks → On.
- Scroll down and click Add New Webhook to Workspace.
- Choose the channel where alerts should appear (e.g.
#debug-alerts) and click Allow. - Copy the generated webhook URL, which looks like:
https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX
Step 2 — Enable Slack in WDLV
- In WordPress, go to Debug Log Viewer → License and activate Premium with your license key.
- A new submenu will appear: Debug Log Viewer → Alerts (Integrations).
- On this page:
- ✅ Check Enable Slack.
- Paste the Slack webhook URL you copied earlier.
- Click Save Settings.
Step 3 — Test the Integration
- Scroll to the bottom of the Alerts (Integrations) page.
- Click Send Test to Slack.
- Within a few seconds, a message will appear in your chosen Slack channel:
WDLV Test: Slack alerts are configured and working.
Step 4 — Receive Real Alerts
Once Slack is connected:
- WDLV will post alerts automatically when errors are logged.
- You can adjust:
- Severities (Fatal, Error, Warning, Deprecated, Notice).
- Thresholds (e.g. 5+ errors in 5 minutes).
These settings help ensure your team is only notified when it matters.
FAQ
Q: Is Slack free?
Yes. The free plan supports Incoming Webhooks. Older messages are limited to 90 days of history, but alerts will always deliver in real-time.Q: Can I use multiple channels?
Yes. Create multiple Slack webhooks (one per channel) and rotate them in WDLV as needed.Q: What if I don’t use Slack?
WDLV also supports generic webhooks, so you can connect to services like Discord, Microsoft Teams, Zapier, or your own monitoring tools.
✅ You’re all set! Slack alerts ensure you’ll know about critical WordPress errors the moment they happen.
Overview
The WordPress Debug Log Viewer (WDLV) Premium edition supports generic webhooks, letting you send real-time error alerts to any service that accepts HTTP POST requests. This includes Zapier, Make.com, Discord, Microsoft Teams, custom APIs, SMS gateways, and more.
This article shows you how to configure and test webhook alerts in WDLV.
Step 1 — Get a Webhook URL
You need a destination URL where WDLV can send alerts.
- For testing: use Webhook.site. It instantly generates a unique URL and displays any payloads it receives.
- For production: use a URL provided by your automation or monitoring platform (e.g. Zapier Webhook trigger, Discord channel webhook, Microsoft Teams Incoming Webhook).
Example URL:
https://webhook.site/abcd1234-5678-efgh-ijkl-9876543210
Step 2 — Enable Webhook in WDLV
- In WordPress, go to Debug Log Viewer → License and activate Premium with your license key.
- Navigate to Debug Log Viewer → Alerts (Integrations).
- On this page:
- ✅ Check Enable Webhook.
- Paste your webhook URL into the Webhook URL field.
- (Optional) Enter any custom headers in Webhook Headers (JSON). Example:
{ "Authorization": "Bearer XYZ123", "X-Custom-Header": "MyValue" } - Click Save Settings.
Step 3 — Test the Integration
- Scroll to the bottom of the Alerts (Integrations) page.
- Click Send Test to Webhook.
- If you’re using Webhook.site, you’ll immediately see a JSON payload appear, like:
{ "site": "https://example.com", "timestamp": "2025-09-30T00:00:00Z", "message": "WDLV test webhook payload" }
Step 4 — Receive Real Alerts
When enabled, WDLV will automatically post webhook alerts if:
- Errors in
debug.logmatch your selected severities (Fatal, Error, Warning, Deprecated, Notice). - The number of errors exceeds your configured threshold (e.g. 5+ errors in 5 minutes).
Payloads include details like:
- Site URL
- Timestamp
- Severity
- Error count
- Sample log line
You can then process this data in your chosen system (e.g. trigger Zapier to send SMS, log into a database, or open a ticket in a helpdesk).
FAQ
Q: Do I need coding skills?
No. Just paste in a webhook URL. Services like Zapier or Make.com can handle the rest.Q: Can I use multiple webhooks?
At this time, WDLV supports one webhook URL. You can rotate URLs or use a tool like Zapier/Make.com to fan out alerts to multiple services.Q: What’s the difference between Webhook and Slack alerts?
Slack is a specialized webhook with formatting. The generic webhook option gives you more flexibility for custom systems.
✅ With webhook alerts, WDLV can connect to almost any service — giving you complete control over how and where error alerts are delivered.
Would you like me to also draft a combined KB landing page for “Alerts & Integrations” that links out to both the Slack and Webhook articles, so users can choose their preferred setup?