We're Moving to a New Support Platform – Starting June 1st!

We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.

You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.

While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.

We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.

Thanks for your continued support and trust – we’re excited to bring you an even better support experience!

Okay
  Public Ticket #3985863
Problem with Attached file bigger than 200Ko
Open

Comments

  • Arthur started the conversation
    4 days ago on Friday at 8:30am
    1. Environment
    ItemDetails
    HostingHostinger (Open-/LiteSpeed stack)
    WordPress8.6.1
    AmeliaLatest build (Step-by-Step Booking, Events Calendar, Catalog, etc.)
    PHP limitsupload_max_filesize = 2048 M, post_max_size = 2048 M
    Server cacheLiteSpeed Cache disabled during tests
    ModSecurityTemporarily disabled via SecFilterEngine Off / SecFilterScanPOST Off


    2. Issue

    Any Amelia form that contains the Attachment custom field fails to reach the final “Thank-you” page when the uploaded file is larger than ≈ 200 KB.

    Effects:

    • Booking is created in the back-end and file is stored.

    • Front-end wizard freezes; no redirect or success screen.

    Occurs in all Amelia modules (Step-by-Step, Events Calendar, Catalog, etc.).

    3. How to reproduce

    1. Add an Attachment field to any Amelia event or service.

    2. On the front-end, upload a file < 200 KB → works.

    3. Upload a file > 200 KB → wizard hangs (booking still saved).

    4. What we see in DevTools
    CaseResponse from admin-ajax.php?action=wpamelia/api/booking
    Success (< 200 KB)HTTP 200 + valid JSON
    Failure (> 200 KB)HTTP 200 but body = corrupted binary / garbled characters.

    The next /success request is never made when failure.

    5. Troubleshooting already done

    • Raised PHP limits (see §1).

    • Disabled LiteSpeed Cache completely → no change.

    • Disabled ModSecurity via .htaccess → no change.

    • Same result across different browsers.

    6. Help needed

    1. Why does the JSON response become corrupted for files > ~200 KB?

    2. Is there any Amelia buffer/attachment handling that could leak binary data into the AJAX response?

    3. Recommended server settings (LiteSpeed / Hostinger) to let larger files pass?

    4. Road-map: will front-end file-size validation or a “Max file size” setting be added soon?

    Screenshots of both responses and current PHP info are ready to share.

    Thank you for your assistance!