Bug 860160 - Mysql account message displayed not well in the drupal and wordpress application get_started page.
Summary: Mysql account message displayed not well in the drupal and wordpress applicat...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Clayton Coleman
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-25 07:13 UTC by Mengjiao Gao
Modified: 2015-05-15 01:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-06 18:48:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
The get_started page of wordpress application. (268.47 KB, image/png)
2012-09-25 07:13 UTC, Mengjiao Gao
no flags Details

Description Mengjiao Gao 2012-09-25 07:13:41 UTC
Created attachment 616892 [details]
The get_started page of wordpress application.

Description of problem:
When creating druple and wordpress applications, I found that the auto-embed mysql account message shown not trimly as the attachment shown. 

Version-Release number of selected component (if applicable):
fork_ami_opensource_console_ruby19_2

How reproducible:
always

Steps to Reproduce:
1.Create druple or wordpress app on site.
2.Check the get_started page.
3.
  
Actual results:
The mysql account part in this page shown not trimly.

Expected results:
All the content should displayed well.

Additional info:

Comment 1 Mengjiao Gao 2012-09-25 08:05:19 UTC
Tested this issue on devenv_2223, found it also exist on the devenv. So it is not a special bug for the fork_ami.

Comment 2 Clayton Coleman 2012-09-25 17:34:06 UTC
Fixed in opensource_console_final 785c823 which will be in fork_ami_opensource_console_ruby19_2

Comment 3 Yujie Zhang 2012-09-26 04:56:51 UTC
(In reply to comment #2)
Tested this issue on fork_ami_opensource_console_ruby19_3, the display is correct now, thanks.


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