Issue Details (XML | Word | Printable)

Key: MDL-11776
Type: Bug Bug
Status: Resolved Resolved
Resolution: Duplicate
Priority: Major Major
Assignee: Nicolas Connault
Reporter: Brian Schmidt
Votes: 0
Watchers: 0
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Moodle

user profile pictures no longer display

Created: 15/Oct/07 11:21 PM   Updated: 16/Oct/07 12:23 AM
Return to search
Component/s: Other
Affects Version/s: 1.8.3
Fix Version/s: None

Environment: RHEL ES 2.1, PHP 4.3.10, MySQL 4.1.18
Issue Links:
Dependency
 

Database: MySQL
Participants: Brian Schmidt, Martin Dougiamas and Nicolas Connault
Security Level: None
Resolved date: 16/Oct/07
Affected Branches: MOODLE_18_STABLE


 Description  « Hide
After upgrading to 1.8.3+ from 1.8.2+, all of the user profile images have "disappeared." The correct images are still on the server and still located under moodledata/users/NN/f1.jpg, f2.jpg. However, these images no longer display when pulling up the student list in a course or looking at a particular student's profile. In both cases, Moodle is displaying the generic user icon for everyone.

This has never previously happened to us after any other upgrade of Moodle. However, just for the sake of checking, I turned off slash arguments (which has always been on in the past), but that did not make a difference either.

Here's the part that's confusing me - when I pull up the picture properties, the path (user/pix.php/13/f1.jpg) shows that it should be pulling up the custom image as it's pointed right at it. However, in every case, it's still the generic one. Is this an issue with pix.php? Something else?

I have verified that this is not a caching issue with the browser. I have tried with both Firefox and IE, both having cleared the cache completely, both having reloaded the pages, etc.

 All   Comments   Change History   Version Control      Sort Order: Ascending order - Click to sort in descending order
Martin Dougiamas added a comment - 16/Oct/07 12:20 AM
Yes, some buggy code unfortunately got into the stable release (a rare event). If you update again to the latest 1.8.3+ it should be fixed.

See MDL-8605.