Bought a weird ceramic jar at a spring estate sale. It has a lid with a finger sized hole in the center and hand painted flowers. No smells, completel. Full article 👇

SPF: (Sender Policy Framework) This is the most common anti-spam measure used. If you are on a hosted system, there is a good chance your host has set this up for the mail server you are using. Have WordPress email you and check the message headers for evidence that the message passed the SPF check. You can get a message sent by following the Forgot Password link on the login page. To keep your old password, do not follow the link in the message.
If your system email failed the SPF check, you can set up the credentials if you have access to your DNS records and your mail server’s domain belongs to you. Check the return path of the email your system sent. If the mail server listed there has your domain name, you can set up SPF credentials. There are several how-tos on the Internet.

DKIM: (Domain Key Identified Mail) This system is also used. You can use both SPF and DKIM in the same message. Again, just as with SPF, you can check if your receiving mailserver verified your host’s domain key by examining the mail header. There is a fair chance no signature key was provided, indicating your host chose to not use this protocol. Also as with SPF, if you can edit your DNS records and the mail server belongs to your domain, you can set up DKIM credentials yourself. Some how-tos exist if you search the Internet.

Why can’t I see my posts? All I see is Sorry, no posts match your criteria?
Clearing your browser cache and cookies may resolve this problem. See also I Make Changes and Nothing Happens

How do I solve the Headers already sent warning problem?
Description: You got a warning message on your browser that says:

Warning: Cannot modify header information – headers already sent by
(output started at
Reason and Solution:

It is usually because there are spaces, new lines, or other stuff before an opening <?php tag or after a closing ?> tag, typically in wp-config.php. This can also happen in other edited PHP files that are not theme templates, so please check the error message, as it will list the specific file name where the error occurred (see “Interpreting the Error Message” below). Replacing the faulty file with one from your most recent backup or one from a fresh WordPress download is your best bet, but if neither of those are an option, please follow the steps below.

Just because you cannot see anything does not mean that PHP sees the same.

Download the file mentioned in the error message via FTP or the file manager provided in your host’s control panel.
Open that file in a plain text editor (NOT Microsoft Word or similar. Notepad or BBEdit are fine).
Check that the very first characters are with no blank lines or spaces after it.
Before saving, or use the Save as dialog, ensure the file encoding is not UTF-8 BOM but plain UTF-8 or any without the BOM suffix.
To be sure about the end of the file, do this:

Place the cursor between the ? and >
Now press the DELETE key on your computer Note to MAC users: The “DELETE” key on a PC deletes characters to the right of the cursor. That is the key noted here.
Keep that key pressed
For at least 15 seconds
Now type > and
save without pressing any other key at all.
If you press another key, you will bring the problem back.
DO NOT PUT CODE IN UNNECESSARY CODE BLOCKS, PUT THEM IN A SINGLE PHP BLOCK.
Wrong:

<?php some code; ?> <?php some other codes; ?>
Correct:

<?php code; some other code; ?>
Upload the file back to your server after editing and saving the file.

Note: Also check the encoding of the file. If the file is encoded as UTF-8 with BOM, the BOM is seen as a character which starts the output.

Interpreting the Error Message: