Add tutorial: Change WordPress PHP memory and upload limits

[DeclanE47]

I have read and understood the Contributor's Certificate of Origin available at the end of
https://raw.githubusercontent.com/hetzneronline/community-content/master/tutorial-template.md
and I hereby certify that I meet the contribution criteria described in it.
Signed-off-by: DeclanE47 declan@emeryholdings.org

Description

This pull request adds a new Hetzner Community tutorial explaining how to change WordPress PHP memory and upload limits.

The tutorial covers:

• Increasing WordPress memory limits via wp-config.php
• Increasing PHP limits (memory_limit, upload_max_filesize, post_max_size)
• Multiple configuration paths depending on the PHP handler:
  • .htaccess for Apache with mod_php (recommended for Hetzner WordPress Cloud Apps)
  • .user.ini or php.ini for PHP-FPM environments
• Verification steps using WordPress Site Health and phpinfo
• Rollback and troubleshooting guidance

The content is written to be platform-agnostic while reflecting common Hetzner setups.

Scope and assumptions

• Apache-based WordPress installations
• Generic Linux environments (not OS-specific)
• No third-party plugins required

Checklist

• Tutorial follows the Hetzner template
• Original content
• Screenshots included and referenced correctly
• Commands tested
• Commit signed off (DCO)

Additional notes

Step 5 Option A is marked as recommended when Apache uses mod_php, which aligns with the current Hetzner WordPress Cloud App image.

[svenja11]

Thank you for your contribution and sorry for the delay in the review @DeclanE47

I just went through your tutorial and noticed several mentions of citeturn1view0 which indicate that the text may have been copied from AI-generated content. See:

• Line 139
• Line 164
• Line 173

Can you please confirm if your text was written by AI?

[DeclanE47]

Hello,

I used AI to reformat my text but the content is written by me

[svenja11]

I see, thank you for clarifying.

[DeclanE47]

That can be changed back I was sure I fixed that.

[svenja11]

The tutorial looks good to me now.

@DeclanE47 Please add the Contributor’s Certificate of Origin block to the description of this pull request (as a comment in the PR description).

So basically edit #1350 (comment) and add the Contributor’s Certificate of Origin block at the top (with your own name and email).

Contributor’s Certificate of Origin block:

I have read and understood the Contributor's Certificate of Origin available at the end of
https://raw.githubusercontent.com/hetzneronline/community-content/master/tutorial-template.md
and I hereby certify that I meet the contribution criteria described in it.
Signed-off-by: YOUR NAME [YOUR@EMAILPROVIDER.TLD](mailto:YOUR@EMAILPROVIDER.TLD)

Once this is added, I will merge this PR.

[DeclanE47]

The tutorial looks good to me now.

@DeclanE47 Please add the Contributor’s Certificate of Origin block to the description of this pull request (as a comment in the PR description).

So basically edit #1350 (comment) and add the Contributor’s Certificate of Origin block at the top (with your own name and email).

Contributor’s Certificate of Origin block:

I have read and understood the Contributor's Certificate of Origin available at the end of
https://raw.githubusercontent.com/hetzneronline/community-content/master/tutorial-template.md
and I hereby certify that I meet the contribution criteria described in it.
Signed-off-by: YOUR NAME [YOUR@EMAILPROVIDER.TLD](mailto:YOUR@EMAILPROVIDER.TLD)

Once this is added, I will merge this PR.

Added :)

[svenja11]

Thank you 🙂