History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: FC-950
Type: Bug Bug
Status: Resolved Resolved
Resolution: Cannot Reproduce
Priority: Major Major
Assignee: Matthew Bryant
Reporter: Scott Stroz
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FarCry Core Framework

Custom Cocntent Type with bUseInTree set to TRUE cannot be edited/approved from outside the tree.

Created: 12/Sep/07 07:06 AM   Updated: 06/Jan/09 02:20 PM
Component/s: Webskins, Webtop Admin UI
Affects Version/s: 4.0.8
Fix Version/s: FarCry 5.1

Time Tracking:
Not Specified

File Attachments: 1. File renderObjectOverview.cfm (7 kb)

Environment: Windows, Apache


 Description  « Hide
If you have a custom content type that can be used in the tree AND managed elsewhere the following occurs.

1. If an item is created in the management area, not in the tree, you can create and approve the item as expected. However, if you try to edit the item, you will be unable to approve it again. The permissions will not show the 'Send Content Live', 'request approval', etc links in the overview screen. Only the 'Preview' link appears on overview screen after trying to edit an item that has already been approved.

2. If the item is created from within the tree, you can go to the other management area and edit and approve the item, as often as you wish, without issue.

It seems to me the behavior should be consistent. You should be able to approve/request approval, etc from overview screen regardless of where the item was created.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Stroz - 12/Sep/07 07:08 AM
Also please note that the items that are unable to be approved are created by the same user trying to update them.

Scott Stroz - 12/Sep/07 07:16 AM
This is a modified file that gives the expected results. However, I am not sure if this will mess things up elsewhere.

Basically the issue stems from the fact that when you create an item outside the tree when it can also be used inside the tree, there is no parentID, as such the permissions get set to 'preview' only when viewing from generic admin interface.

Geoff Bowers - 14/Sep/07 05:33 PM
With any luck this will be cleaned up with the implementation of webtopoverview webskins.

Matthew Bryant - 06/Jan/09 02:20 PM
This file has changed significantly in 5.1 and we can't reproduce your issue so I can only assume that it has inadvertently been fixed.

Please open a new ticket if you are still having difficulty with the latest release of 5.1