FileBrowser: Set HazaarCWD cookie path when setting cookie #54
Labels
No labels
bug
confirmed
critical
database
discussion
documentation
email-support
enhancement
feature
suggestion
support
warlock
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference: hazaar/hazaar-mvc-old#54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The path is currently getting set as the same as the current page path on which the browser is being loaded. We should leave this as the default action, but allow a path to be set in the filebrowser widget so that the root path of the application can be set if needed. This will make the cookie application wide rather then getting overwritten and reset each time.
This is done with:
Status changed to closed