Bug 1003501 - Can create duplicated thread on forum
Summary: Can create duplicated thread on forum
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Online
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: 2013-09-02 08:25 UTC by Tian Feng
Modified: 2015-05-15 01:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-10 13:51:37 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Tian Feng 2013-09-02 08:25:02 UTC
Description of problem:
Being able to create duplicated thread. Post a thread on forum using "testTitle" as title twice, two threads will be created and shown partly on the forum page, but they have same url just like /forum/openshift/testtitle .

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

How reproducible:
Always

Steps to Reproduce:
1. go to openshift forum on community
2. post two threads using "testTitle" as title
3. check the thread on forum and their url

Actual results:
Could create duplicated thread.

Expected results:
Cannot create two thread with same url or just not use the title as a part of the url

Additional info:

Comment 1 Jessica Forrester 2013-09-09 22:00:09 UTC
I can't reproduce this. When I create the first thread with the title of "testtitle" the url is /forums/openshift/testtitle.  But for the second thread i create with "testtitle" the url is /forums/openshift/testtitle-0

Drupal automatically appends the -0 to the end to get a unique url when the title matches.

Can you double check the behavior you were seeing?

Comment 2 Tian Feng 2013-09-10 00:42:31 UTC
I apologize. I can't reproduce it any more after filing this bug.
When I post a thread with same title, it will add -0 -1 -2 at the end of the title.
So I think it's not a bug.


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