Weceem

Moving a node to a new location in the repository does not refresh the URI to node cache - 404s result

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.9
  • Fix Version/s: 0.9.1
  • Component/s: None
  • Labels:
    None
  • Request Controller:
    Please Select
  • External Supervisor:
    Please select
  • Executing Programmer:
    Please select

Description

If you drag and drop a node to a new parent in the repository, the URI cache is not updated for that node, so the previous entry still exists (and works), but the new one 404s.

Workaround: edit and re-save the node after moving it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Marc Palmer added a comment - 28/Jul/10 3:47 PM

Also made caches flush when a space is imported, and when nodes are updated or moved.

Show
Marc Palmer added a comment - 28/Jul/10 3:47 PM Also made caches flush when a space is imported, and when nodes are updated or moved.

People

Vote (0)
Watch (0)

Dates

  • Created:
    23/Jul/10 1:26 PM
    Updated:
    28/Jul/10 3:47 PM
    Resolved:
    28/Jul/10 3:47 PM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for Grailsflow. Try JIRA - bug tracking software for your team.