Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-16123

Implement cURL for SCORM due to ISPs disabling allow_url_fopen

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • 1.9.4
    • 1.9.2
    • SCORM
    • None
    • Moodle 1.9.2+ (Build 20080806), PHP 5.2.5, Apache 1.3.41, MYSQL 4.1.22
    • MySQL
    • MOODLE_19_STABLE
    • MOODLE_19_STABLE

      Apologies if the SCORM cURL implementation is covered by the following:

      http://tracker.moodle.org/browse/MDL-8018
      http://tracker.moodle.org/browse/MDL-7947

      I am getting an IE Error 404 (and Firefox) when I try and open SCOEs with non-local resources (i.e. stored on a supplier's server). They were previously working and local SCOEs (with resources stored on our server) still work, but like many ISP's, they have recently disabled the allow_url_fopen function, as this is proving to be a major issue for my site as I have a large number of 'Midleaders' SCORMS (potentially 200) which I can no longer access, my ISP recommending that cURL is used as an alternative. They will not re-enable the function. We have around 800 users which means my site is in maintenance mode with a around 800 users unable to access their learning - so things are pretty desperate! I am on a semi-maintained shared server hosting plan with a UK company called Evo Hosting, so cannot make Apache configuration changes myself, although I have CPanel access and maintain our installation.

      I'd be happy to provide a test login if required, and use our site to test implementation.
      Thanks
      Stuart

            danmarsden Dan Marsden
            shiles Stuart Hiles (Inactive)
            Piers Harding Piers Harding (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.