Reach out
The best way to get in touch with PHP Everyday is by email:
That goes to a real inbox. Expect a reply within a few business days for most questions. During busier periods it might take a bit longer, but every message gets read.
What to include in your message
If you are reporting a problem with an article - broken code example, missing step, outdated information - it helps to include:
- The article URL (or at least the title). There are a lot of articles on this site and “the PHP one” narrows it down to roughly all of them.
- What you expected to happen versus what actually happened. “The PDO example on the insert page throws an error about parameter count” is much more useful than “it doesn’t work.”
- Your PHP version if the issue is version-specific. A lot of the older framework tutorials were written for PHP 5.x and some behaviors changed in 7.x and 8.x.
Types of questions we can help with
Content corrections. If a code example has a bug, a configuration value is wrong, or a step is missing from a tutorial, we want to know. Fixing broken examples is a priority.
Topic suggestions. If there is a PHP topic or framework feature you think the site should cover, send it over. No promises on timeline, but reader suggestions directly influence what gets written next.
Series and pack feedback. If the reading order in a series feels off, or a pack is missing a step that would make the workflow clearer, that is genuinely useful feedback. The series structure has been refined several times based on reader input.
General PHP questions. If you are stuck on something related to a topic we cover, go ahead and ask. Simple questions often get a quick reply. Complex ones might turn into a new article if the answer is interesting enough to share.
What we cannot help with
Debugging your entire application. If you have a 2,000-line CodeIgniter project that is throwing a white screen, we are not going to be able to step through it over email. But if you can isolate the problem to a specific controller method or database query, that is a different conversation.
Homework or exam answers. You will learn more by working through the series articles yourself. The PDO series in particular is structured so that each article builds on the last, and that progression is intentional.
Hosting, server configuration, or deployment. The site focuses on PHP code and framework usage. Apache configuration, Docker setups, and cloud deployment are outside our scope - not because they are unimportant, but because there are better resources for those specific topics.
Response times
Most messages get a reply within 2-3 business days. Content corrections are prioritized since they affect everyone reading the article. Feature suggestions and general questions are handled as time allows.
If your message is about a specific article, double-check that you are looking at the latest version of the page. Browsers sometimes cache older versions, and a hard refresh (Ctrl+Shift+R on most browsers, Cmd+Shift+R on Mac) solves that.
Other ways to stay updated
The changelog page tracks recent content updates, corrections, and new articles. If you want to see what has changed recently, that is the place to look.
The site does not currently have an RSS feed or newsletter. When one is added, it will be announced on the changelog.
A quick note on spam
The contact email gets a reasonable volume of messages. If your email looks like an automated SEO pitch, a guest post request, or a link exchange proposal, it will be filtered and ignored. The site does not accept guest posts, sponsored content, or paid links.