Bug 816851 - Links in forums/express/user-guides-for-openshift-express-flex are all broken in prod
Summary: Links in forums/express/user-guides-for-openshift-express-flex are all broken...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: David O'Brien
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-27 07:56 UTC by Xiaoli Tian
Modified: 2015-05-15 01:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-14 17:23:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Xiaoli Tian 2012-04-27 07:56:32 UTC
Description of problem:

Go to https://openshift.redhat.com/community/forums/openshift, 

Click the first thread "User Guides for OpenShift Express & Flex",

All the content there is very outdated, it still linked to the old express and flex  user guide link which are already broken.



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

How reproducible:
Always

Steps to Reproduce:
1.As description said , check https://openshift.redhat.com/community/forums/express/user-guides-for-openshift-express-flex

  
Actual results:
1. The user guide there is still linked to http://docs.redhat.com/docs/en-US/OpenShift_Express/2.0/html/User_Guide/index.html

2. Flex is still there


Expected results:
1. Linked to new link:
http://docs.redhat.com/docs/en-US/OpenShift/2.0/html/User_Guide/index.html

2. Remove flex

Additional info:

Comment 1 Xiaoli Tian 2012-04-27 08:13:54 UTC
Or suggest to remove this thread since related information is already in https://openshift.redhat.com/community/developers

Comment 2 Clayton Coleman 2012-05-01 04:20:43 UTC
I updated the thread to point to the developer center.

Comment 3 Xiaoli Tian 2012-05-02 10:37:42 UTC
Verified it on production, it's fixed.


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