Bug 453668 - Error message occurs when editing blog in Clearspace
Error message occurs when editing blog in Clearspace
Status: CLOSED NOTABUG
Product: Red Hat Collaboration Applications
Classification: Retired
Component: Clearspace (Show other bugs)
1.0
All Linux
low Severity medium
: ---
: ---
Assigned To: Jeremy Hansen
:
: 453675 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-01 15:46 EDT by Monty Hood
Modified: 2008-10-29 09:45 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-29 09:45:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Monty Hood 2008-07-01 15:46:25 EDT
https://rt.corp.redhat.com/rt3/Ticket/Display.html?id=687754

- - - - - - - - - - - - - - - - - - - - 

Subject:  	Clearspace issue
Date: 	Fri, 27 Jun 2008 12:24:39 -0400
To: 	helpdesk@redhat.com
From: 	Mark Sechrest <msechres@redhat.com>

While editing a blog post in clearspace, I keep seeing the following
error message appear:

"An error occurred trying to retrieve data from server. Please try again
in a few minutes. Error Code: data has no properties"

This didn't have any impact on my ability to save/publish the document,
however.

--MarkS
Comment 1 Bret McMillan 2008-08-22 11:52:34 EDT
Moving open clearspace items to jhansen for now
Comment 2 Bret McMillan 2008-08-22 12:23:02 EDT
Mark, is this still happening?
Comment 3 Bret McMillan 2008-08-22 12:24:41 EDT
*** Bug 453675 has been marked as a duplicate of this bug. ***
Comment 4 Sudhir Mallamprabhakara 2008-10-17 13:39:53 EDT
Mark - Is this still happening?
Comment 5 Mark Sechrest 2008-10-29 08:24:38 EDT
I just tried making a blog post, and did not see any of these errors.
Comment 6 Sudhir Mallamprabhakara 2008-10-29 09:45:27 EDT
Closing this bug..

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