[
https://issues.apache.org/jira/browse/JS2-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Woonsan Ko resolved JS2-1175.
-----------------------------
Resolution: Fixed
Fix Version/s: 2.2.1
Fixed.
The path for the new node is selected when user clicks a tree node in the tree.
When a user didn't click any tree node in the tree, the default path as same as
the document path has been used. This made this problem.
Therefore, I just made it select the default root node initially in the tree.
This simple addition solved the problem.
> Portal Site Validation logic prevents simple rename move operations
> -------------------------------------------------------------------
>
> Key: JS2-1175
> URL: https://issues.apache.org/jira/browse/JS2-1175
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Admin Portlets
> Affects Versions: 2.2.1
> Environment: Portal Site Manager
> Reporter: Randy Watler
> Assignee: Woonsan Ko
> Priority: Minor
> Fix For: 2.2.1
>
>
> PortalSiteManager.CopyMoveWindow.copyForm.onValidate() accesses getDocName()
> to validate name change, but this field is not set with values from the form
> when the validation is performed. When the button is submitted later,
> setDocName() is invoked correctly.
> This bug results in the the code thinking that the move, (or copy), name is
> unchanged and thus will not allow the move to occur. Changing the path is
> required for the operation to pass validation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
