Bug 999111 - Partner portal company logo upload fails to upload the logo
Summary: Partner portal company logo upload fails to upload the logo
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jessica Forrester
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-20 18:36 UTC by Jessica Forrester
Modified: 2015-05-15 02:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-29 12:54:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jessica Forrester 2013-08-20 18:36:21 UTC
Description of problem:
When a partner uploads their company information from the partner portal, the logo is not being successfully attached to their partner record.  So the partner logo does not appear on the /partners page and instead creates a blank section.

How reproducible:
always

Steps to Reproduce:
1. As an admin make a user an Active Partner from /partner/admin/user  (find the user and click the Edit link)
2. As the partner log in and access /partner/portal
3. As the partner choose to upload company information, on the company upload info page fill out all required info and select an image to upload as the logo.
4) View the /partners page

Actual results:
A blank section will show up as the first entry in the grid of partner images.

Expected results:
The uploaded logo should appear.  (Note: this is true even in devenvs where the existing partner logos do not appear)

Comment 1 Jessica Forrester 2013-08-20 18:37:10 UTC
Fixed in https://github.com/openshift/li/pull/1838

Comment 2 Yujie Zhang 2013-08-21 06:26:37 UTC
Will test it when devenv_3681 is ready.

Comment 3 Tian Feng 2013-08-22 08:23:02 UTC
Test on devenv-stage_448, and can upload logo successfully. And hit /partners page, the logo can be seen. So verified this bug, thanks!


Note You need to log in before you can comment on or make changes to this bug.