Corrupted Project/Permissions [#117239]

This is the second time it is happening;

Usually a case's number is 100-345 for example, right.
Mines all of a sudden change to -345. The project's prefix disappears, and the "view all cases" in casetracker does not return any cases. The main admin account can however view them by accessing the case's node directly. Some regular users cannot view a specific case why others can view the same case. Rebuilding permissions in Post Settings does not solve that issue.

Casetracker looks like a great module, but unfortunately this bug is now making me reconsider it. I guess I'll have to go back to regular nodes.

Comments

Comment #1

morbus iff

they/them

commented 8 February 2007 at 19:46

Status:

Active

» Postponed (maintainer needs more info)

Need more info. What kind of node types are you using? Are comments allowed on project nodes? Was a new comment recently submitted to a project node? Was the project node recently updated? What other non-core modules do you have installed?

Comment #2

Capnj commented 8 February 2007 at 20:43

I've had the same thing happen on 4.7. (Module version 1.68.2.3)
To add the info Morbus was asking about --
What kind of node types are you using? Project and case, only.
Are comments allowed on project nodes? Yes on both project and case.
Was a new comment recently submitted to a project node? No.
Was the project node recently updated? No.
What other non-core modules do you have installed? blogapi, flexinode, inline, links, notify, sitemenu, subscriptions, taxonomy_menu, tinymce, webform, systeminfo, panels, quote.

gil