Terms of Use

Acceptance and scope

Using elephantphp.com means accepting the terms on this page. They cover this site and the content published on it. They do not cover services reached from it: a linked repository, a vendor’s documentation, or a newsletter provider each have their own terms, and those apply once you are there.

Prose and code are not licensed the same way

Readers copy code out of technical articles and run it in production, so the license split matters more than a line in a footer suggests. Code blocks on this site are not marked individually, which makes this page the only place the split is stated.

Article prose and images are all rights reserved. Quoting a reasonable extract is permitted — a paragraph, a figure, enough to make your point — with attribution to ElephantPHP and a link back to the article you took it from. Republishing an entire article, translating one in full, or reposting one on another site is not permitted, with or without attribution. Ask first at [email protected]; permission for a specific reuse is usually straightforward.

Code samples embedded in articles are MIT-licensed. The permission and warranty text is reproduced here in full, so that relying on it does not require finding it somewhere else:

Copyright (c) 2026 ElephantPHP

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR OTHER DEALINGS IN THE SOFTWARE.

In that text, “the Software” means the code samples published on this site. Paste them, change them, ship them in commercial work; keep the notice above with any substantial portion you redistribute as code.

No warranty

The content is provided as is. A technical article describes behavior observed on the PHP version, extension set, and configuration it names, and the same code on a different version, a different opcache configuration, or different hardware can behave differently. A measurement taken on one machine has not been taken on yours.

Nothing published here is professional advice, and it is not a substitute for testing a change against your own system before you deploy it. What you run in production remains your decision.

Limitation of liability

To the extent permitted by law, ElephantPHP is not liable for loss or damage arising from use of this site or its content, including lost data, downtime, or lost revenue following from applying something you read here.

Nothing in this section limits or excludes liability that cannot be limited or excluded under mandatory law. That includes liability for death or personal injury caused by negligence, liability for fraud or fraudulent misrepresentation, and the rights you hold as a consumer under EU consumer protection law, which remain unaffected by anything on this page.

External links

Articles link out to documentation, RFCs, source code, and other people’s writing, because that is where the evidence for a claim usually lives. Those sites are not controlled by ElephantPHP and their content can change after the link is published. A link is a pointer to something worth reading, not an endorsement of the site that hosts it.

Trademarks

PHP, Symfony, Laravel, Composer, PHPStan, Xdebug, and other product and project names are the property of their respective owners. They are used here to name the subject being written about — nominative use — and imply no affiliation with, or endorsement by, their owners.

Changes

These terms can change. The version on this page is the one in force, dated at the top of the page, and earlier versions are not archived. Continuing to use the site after a change means accepting the version published at that time.

Contact

Questions about these terms: [email protected]. The identity and contact details of the party responsible for personal data are stated in the Privacy Policy, which is also where the site’s data processing is described in full.