-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 0.18
-
Fix Version/s: 0.18
-
Labels:None
1) sign in by any user
2) create topic in any branch
3) click Delete button (to topic) screen 1.png. I see message "delete Post"
4) Confirm delete. i see page of topic with button Answer, without posts. screen 2.png
5) Go to main page. Click to branch (which created the topic). I see error page screen 3.png (and text of trace in file)
expected:
step 3. I should see text "... delete Topic?"
step 4. After removing of topic i should see branch page.
- relates to
-
-
- Closed
-
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Evgeniy Naumenko [ jk1 ] | Anuar Nurmakanov [ shogun ] |
| Assignee | Anuar Nurmakanov [ shogun ] | Evgeniy Naumenko [ jk1 ] |
| Component/s | view [ 10100 ] | |
| Due Date | 04/Jul/12 | |
| Remaining Estimate | 2h [ 7200 ] | |
| Original Estimate | 2h [ 7200 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Worklog Id | 14510 [ 14510 ] | |
| issue.field.resolutiondate | 2012-07-03 23:17:27.0 | 2012-07-03 23:17:27.655 |
| Remaining Estimate | 2h [ 7200 ] | 0h [ 0 ] |
| Time Spent | 2h [ 7200 ] |
| Fix Version/s | 0.18 [ 12200 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Done [ 5 ] |
| Assignee | Evgeniy Naumenko [ jk1 ] | Julia Atlygina [ julik ] |
| Status | Done [ 5 ] | In QA [ 10004 ] |
Evgeniy Naumenko we can't be sure that nobody do it on our uat instance.
Last night I've repaired uat instance manually.
If some branch is still unavailable simply contact me to fix it.
btw, deploy.jtalks.org/jcommune is guaranteed to be ok regardless of your actions, so you can recheck there, if in doubt
| Assignee | Julia Atlygina [ julik ] | Ilya Zhulanov [ ilzul ] |
Verified. Step 3 - Appropriate message appears; step 4 - After removing of topic a user is on branch page.
| Status | In QA [ 10004 ] | Closed [ 6 ] |
| Component/s | view [ 10100 ] |
Important: this bug corrupts the database. At the moment of fix all the server databases have been repaired manualy. Be sure fix code is deployed via ci.jtalks.org on your target environment before even trying to reproduce the problem. Otherwise topic data will be corrupted once again and manual correction will be required.