File module reports server is not capable of using uploadprogress when running on Litespeed

Created on 15 February 2012, over 13 years ago
Updated 30 January 2023, over 2 years ago

I have uploadprogress enabled on Lightspeed, and it works with Drupal, yet the status report page says "Your server is not capable of displaying file upload progress. File upload progress requires an Apache server running PHP with mod_php."

Can we remove if (!$apache) from file_requirements() since it is highly likely uploadprogress still works with forks of Apache? Or would this specifically require detection of Lightspeed?

πŸ› Bug report
Status

Needs work

Version

9.5

Component
File systemΒ  β†’

Last updated about 14 hours ago

Created by

πŸ‡¦πŸ‡ΊAustralia mstrelan

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • The Needs Review Queue Bot β†’ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide β†’ to find step-by-step guides for working with issues.

  • Status changed to Postponed: needs info 4 months ago
  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    This came up as a daily BSI target

    Wonder after a few years if still an issue?

  • πŸ‡¦πŸ‡ΊAustralia mstrelan

    As the original reporter of this issue 13 years ago I would imagine it probably is still a problem. But I haven't used Litespeed in probably 10 years and I'm guessing not many others are using it either.

    I'd vote to close it as outdated, but let's give it a couple months at postponed in case any of the folks who commented in the last few years want to continue this.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Sounds like a plan, we don't close issues till after at least 3 months.

  • πŸ‡¦πŸ‡ΊAustralia kim.pepper πŸ„β€β™‚οΈπŸ‡¦πŸ‡ΊSydney, Australia

    I'd say this is outdated since we just check if the extension is enabled now.

  • πŸ‡¦πŸ‡ΊAustralia mstrelan

    @kim.pepper it looks like we first check for the extension, but even if it's enabled we then go on and check if we're using apache or nginx. If it's neither we say it's disabled. https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/file/...

  • πŸ‡¦πŸ‡ΊAustralia kim.pepper πŸ„β€β™‚οΈπŸ‡¦πŸ‡ΊSydney, Australia

    Yeah, not sure of the history of this one. I think we could do away with the check for apache and nginx and just display the default "extension missing" message.

  • Status changed to Closed: outdated 17 days ago
  • πŸ‡¦πŸ‡ΊAustralia acbramley

    Came up in BSI again, it sounds like this can be closed.

Production build 0.71.5 2024