post_max_size

post_max_size is the PHPPHP is a programming language that builds your web pages on the computer that hosts your site, just before they reach the visitor. WordPress runs on it. setting that limits the total size of incoming POST data. This limit matters for forms and uploads. The request is considered as a whole, not just the largest file you select.

When a submission fails, establish what the application receives and where the request is stopped. Looking only at the size of one attachment may leave an important part of the investigation unanswered.

What is being limited?

The PHP configuration reference defines post_max_size as the maximum size of POST data. That includes uploads. The individual file setting, upload_max_filesizeupload_max_filesize is the PHP setting that limits the size of an individual uploaded file., therefore has a different scope.

Ask your administrator to assess both settings together when the affected form sends files as part of its submission. The PHP manual also notes that memory_limitmemory_limit is a PHP setting that decides how much memory the code behind one page may use. If it needs more, it stops with an error. should generally be larger than post_max_size; have both assessed together.

Describe the complete form when reporting the issue. Which fields do you fill in and which files do you attach? Record the submission you are actually trying to make.

A test containing only a small file does not reproduce a form with several attachments and completed text fields. Keep the intended test case clear.

Why can a submission appear empty?

The PHP manual says the usual $_POST and $_FILES collections are empty when POST data exceeds post_max_size. That gives a developer a specific question to investigate. A form reporting empty data does not by itself prove this limit was exceeded.

Ask for the observation to be checked against the effective configuration.

Ask which evidence supports the diagnosis. You do not need to publish the contents of a customer form in a support ticket. The time, route, overall test setup and error message are useful starting details.

Have the developer explain the technical observation without copying sensitive field values into the maintenance handover.

Also record what you see in the browser. Is there an error, does the form remain on screen, or do you see confirmation without the expected result? These are different observations.

Write down what happened before assigning a cause. That keeps the investigation open to another restriction elsewhere along the request route.

Where should the setting be checked?

The administrator needs the effective value for the relevant domainA domain name is the address people type to reach your website, such as yourcompany.com. It points visitors to wherever your site is hosted.. The name php.iniphp.ini is the settings file for PHP on your hosting. It sets limits, such as how much memory a script may use, how big an upload may be and if errors show. alone does not establish which configuration your request uses. Ask where the value is managed and how the operator confirmed that it applies to this form.

Do not let a terminal check silently become evidence for the website environment.

The hosting guides help locate the appropriate management route. Record the environment that will be changed. If you use a test copy, ask which relevant settings match the live website.

A test result becomes useful handover evidence only when the environment being tested is clearly identified and understood.

How should a change be prepared?

First describe the submission that needs to work. Include the files and fields involved. Ask for an appropriate limit and an explanation of the choice.

Do not copy a large value from an unrelated tutorial without having someone assess why your form requires that allowance and whether the proposed configuration fits its use.

Keep the previous and new values with the maintenance task. Agree who will assess the change and how the original configuration can be restored if it does not help. This turns an isolated hostingWeb hosting is the service that keeps your website's files on a computer that is always online, so visitors can open your site at any time. experiment into a focused adjustment with an outcome you can review through the form you normally use.

Use fictional form data for testing. Check more than the confirmation message: verify that every expected field and attachment appears at its destination. Choose that destination beforehand, such as the dashboard where submissions should be stored.

Avoid a test that unintentionally contacts real recipients while you are investigating a technical limit.

What if the form still fails?

Request the relevant error logAn error log is a file where your website's software writes down what went wrong, with the time and place. It is the first thing to check when a site breaks. entry if one is available. Compare its time with your test. An older message in the same file may belong to another request.

The Error Hub explains recognisable errors; use that explanation as context for the actual observation, rather than as a substitute for investigation.

Ask the administrator which explanation has now been ruled out. If the request remains within the verified limit, raising it again without further evidence is not a focused next step. Ask which component needs examination next and what result that examination is expected to provide for this specific form.

Ask for help with the form route, test setup and verified settings. If a version change is also planned, include this complete form test when you update PHP in WordPress. Using the same input before and after maintenance makes the result easier to compare.