Bug 915415 - Need to display default username and password after WordPress app creation on console
Summary: Need to display default username and password after WordPress app creation on...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Clayton Coleman
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-25 17:19 UTC by John Poelstra
Modified: 2015-05-15 01:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-15 13:59:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot1 (66.10 KB, image/png)
2013-02-26 18:21 UTC, John Poelstra
no flags Details
screenshot2 (26.87 KB, image/png)
2013-02-26 18:22 UTC, John Poelstra
no flags Details

Description John Poelstra 2013-02-25 17:19:10 UTC
Description of problem:
The default username and password WordPress are not reported on the console after app creation leaving many first time users wondering how to log in.

Previously discussed with Clayton and realize work is under way.  We continue to see questions about this so opening a bug to track to completion.

Comment 1 Clayton Coleman 2013-02-26 01:52:09 UTC
Fixed in the wordpress example - installation now stops right after the db is setup but before tables are created.  User gets the "setup wordpress" experience which is far superior. 

Also included hooks so that pushes don't automatically delete plugins (unless the user wants to).

Fixed in prod

Comment 2 Yujie Zhang 2013-02-26 06:09:06 UTC
(In reply to comment #1)
Tested this issue on PROD, user can set username and password successfully when first time visit wordpress, so verify this bug.

Comment 3 John Poelstra 2013-02-26 18:20:08 UTC
Something is not happy with the way the theme directory gets set up.  It's like it knows about the theme, but can't find the files.  See screenshots.

Comment 4 John Poelstra 2013-02-26 18:20:49 UTC
The new approach is awesome, BTW! Thanks for implementing it.  Screenshots coming real soon now.

Comment 5 John Poelstra 2013-02-26 18:21:20 UTC
Created attachment 703053 [details]
screenshot1

Comment 6 John Poelstra 2013-02-26 18:22:26 UTC
Created attachment 703054 [details]
screenshot2

Comment 7 Clayton Coleman 2013-02-26 21:57:16 UTC
That's to be expected - you have to have at least one theme, but we don't create it.

Comment 8 John Poelstra 2013-02-26 22:13:56 UTC
Where are we getting the WordPress code from?

That's not how the WordPress tarball works from wordpress.org.  The tarball from wordpress.org comes with the files for two themes, both of which work out of the box.  

Showing one theme in the UI of a running OpenShift instance that is broken, and expecting the user to install one to make it work makes our implementation look half-baked and like we don't know what we are doing.  I just don't think it is a good first impression.

Comment 9 Clayton Coleman 2013-02-28 01:00:44 UTC
Fixed in: https://github.com/openshift/wordpress-example/pull/28.  When it's validated I'll pull the request.

Comment 10 Mengjiao Gao 2013-02-28 12:17:06 UTC
Since the newest code have not merged to the devenv, I will test it tomorrow when the newer devenv comes out.Thanks.

Comment 11 John Poelstra 2013-03-01 19:59:52 UTC
From what I'm seeing it looks like this is fixed.  I'll let QE do the final sign-off.  Thanks Clayton!

Comment 12 Mengjiao Gao 2013-03-04 02:54:20 UTC
Verified this issue on devenv_2888. User can set username and password successfully when first time visit wordpress. And the wordpress had a default theme now. Thanks!


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