|
[
Permalink
| « Hide
]
Nicolas Connault added a comment - 08/Oct/08 03:50 PM
You're right, there is more going on: 1.9 is XHTML compliant (a requirement for several large universities) while 1.65 is not. This has been explained in many places if you would care to research a bit
Is part of the XHTML compliance that the "Force download" setting cannot be unset (not even by the Admin) once set but manages to frequently unset itself?
Robert,
I've added a resource "Link to a file or web site" linking to an uploaded pdf file. Not only does the file open fine in Firefox (FF3 on linux), but I don't have any problems with the "force download" setting. Could you confirm that you are still having this problem, and, if so, could you give more details of the steps required to reproduce it? Thanks Bonjour Nicolas,
We recently migrated from Moodle 1.8.6 to Moodle 1.9.4 Symptoms:
Note that:
You can reproduce Thanks Since upgrading to Moodle 1.9.4 this is now an issue for me with Vista and Firefox 3.0.4 and 3.0.6.
it worked fine with the same config, but Moodle 1.9.3. Symptoms are as Arnaud above, but intermittent. To me, it seems that the first time you try to view a PDF it works, but thereafter it does not. It never seems to like you moving from one PDF directly to another using the pull down resource menu. Ctrl F5 (refresh) rarely seems to work for me. The browser crashes quite often. We do not use eaccelerator and our Moodle site is not in secure mode. Is there any progress with this issue? It continues to be mentioned in the forums. Regards, For what it is worth, I too was having difficulty viewing pdfs from a 1.9 site from my Ubuntu 8.10 machine using FF 3.0.7; however, now that I have installed Acrobat Reader 9.1 (the .deb version) I have no problems. For me, this confirms what I had suspected all along that the issue was in fact more of an Adobe issue than a Moodle issue. Now that the 9.1 version is available for Linux hopefully this will be cleared up. To be reasonably certain that i it was the adobe installation, on a virtual machine I tried to open a file using the older 8.? version and it did not work. I installed the 9.1 version and it worked so it is not a matter of me having applied Firefox patches or anything else in the Moodle code. Peace - Anthony
I also recommend everyone to upgrade Acrobat Reader to 9.1. It solved the issue for us (Moodle 1.9.4).
We just started getting this with 1.9.4+. The same computer/browser/Adobe Reader 8.1 plugin can view PDFs fine in a moodle 1.9.3+ install.
It's not possible to tell everyone who might log in to u/g adobe so we're going to not embed pdfs. Change $embedded = true; to $embedded = false; for PDFs around line 268 in resource/type/file/resource.class.php The embedded view is poor design anyway - as well as freezing up firefox 3, it has no site header breadcrumbs and a fixed 800x800 object (double scrollbars!). Next, I want to get rid of the 'same window' option - we don't want people losing their course window or having to use the browser back button to find it. If you want to fix this bug and retain normal moodle behaviour, you can replace the pdf object with an iframe containing the PDF. That's around line 695 of resource/type/file/resource.class.php. I have made some changes to the /mod/resource/type/file/resource.class.php file that has resulted in the uploaded files being displayed correctly in when a user opens an uploaded file. The changes have been tested primarily with .pdf, .doc, .xls, .ppt, .pub files and FF 3.0.9, IE7, Opera 9.64. Acrobat Reader 8 (which was freezing prior to these changes)
The changes mean that the drop down menu for opening the file in the "Same Window" or "New Window" has been removed and the default is set to "New Window". Our feeling was that opening the file in the same window wasn't the best and when it did display the presentation wasn't that good (double scroll bars, etc). The setting for "Force download" is still there and if "Show Advanced" button is clicked the settings for the new window can be set. If the file is set to "Force download" (checked) then the advanced settings are disabled. So far as presentation goes pdf files will open in a new window, of the specified size and attributes with the window displaying the pdf file as you would expect. When it comes to the files that are created from MS Office (.doc, .xls, .ppt, .pub) these will be forced to download regardless. The presentation of these files wasn't great when not set to "Force download" as a new browser window would open and then the file would open either in an instance of the particular program - Word, Excel etc or the browser window depending on the browser. With the changes made the user is now prompted to either open, save or cancel from the File download window, if they open the file will open in the application, or save (download) as you would expect. The changes to the code in the attached file occur at lines 138 - 143 - this forces the setting for downloading of MS Office files. Other changes were made at lines: 820 - added note to explain about the automatic setting of "Force download" on MS Office files (hard coded in English - should be moved to a lang file) Each change is commented in the attached file. For those who are experiencing a blank screen or crashing browser on some PDF files, I hit a similar issue with Dariem this morning. We managed to solve the problem with a very simple fix.
In /mod/resource/type/file/resource.class.php file the following line Strangely enough this little fix solved the problem of the unviewable PDF in Firefox for both Dariem and myself. I was running Ubuntu 9.04, FF 3.0.10.0, Adobe Reader 8 If anyone is having similar problems and tries this please let us know whether it solved your problems Upgrading to Reader 9+ is a better solution for those who can
The change suggested by Sam above worked for our installation. Huge help!
Has this been implemented in Moodle core? We have been struggling with this for months. 1.9.3+ Apache MySql moodle.blakeschool.org Only appears to help in some situation. Still a lingering issue for us. A few things we know now....
1. happens to files that are created when scanned from our Sharp MFD's 2. happens with firefox as client. Not good. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||