Troubleshooting File Uploads in UpdateProfile

This legacy case came from a profile form where worked, but file uploads only appeared when the debugging snippet was removed or the snippet order changed. The root problem in cases like this is usually not the upload field itself, but how the form is rendered and processed.

Original Setup

[[!outP]]
[[!UpdateProfile]]

<form action="[[~8]]" method="post" enctype="multipart/form-data">
    <input type="file" name="file" id="file" />
    <input type="submit" name="submit" value="Save" />
</form>

<?php
print_r($_POST);
print_r($_FILES);

What Usually Goes Wrong

• The form misses enctype="multipart/form-data".
• A debugging snippet runs before the processor and changes request flow.
• The file field name does not match what the profile processor expects.
• The page contains multiple forms and the wrong snippet handles the request first.
• The upload is blocked by PHP limits such as upload_max_filesize or post_max_size.

Recommended Debug Order

1. Confirm that the form submits to the correct page.
2. Keep UpdateProfile uncached.
3. Temporarily dump $_POST and $_FILES after submission.
4. Check PHP error logs and server limits.
5. Verify whether the upload field should be handled by Login extras directly or by a custom hook.

Safer Pattern

If you need avatar or attachment uploads, it is often cleaner to let a dedicated hook or processor handle the uploaded file, then pass the stored value into the user profile update logic. That keeps the form easier to debug and avoids hidden assumptions inside the Login package.

When $_FILES is empty only in one template or only when another snippet is present, the problem is almost always in page flow, snippet order, or form markup rather than in the upload itself.