Bug 6802 - with IndependantBranches on can still edit items
Summary: with IndependantBranches on can still edit items
Status: RESOLVED DUPLICATE of bug 10225
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: master
Hardware: All All
: P5 - low critical (vote)
Assignee: Galen Charlton
QA Contact: Bugs List
: 5289 (view as bug list)
Depends on:
Reported: 2011-08-28 15:55 UTC by Nicole C. Engard
Modified: 2013-05-18 08:05 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2011-08-28 15:55:13 UTC
When you're logged in to Koha with IndependantBranches turned on you shouldn't be able to edit other people's items, but there is a way around this.  Even though you don't see the edit and delete links next to the items on this page: /cgi-bin/koha/cataloguing/additem.pl?biblionumber=509 you can click on an item and the edit and delete links show up - once that happens you can click edit and when you go to edit the item it forces the branch to be changed to yours - all bad things.

I have a video, but jing isn't letting me upload it right now, so I'll add it if necessary.
Comment 1 Paul Poulain 2011-10-26 15:52:35 UTC
Still bugguy in 3.6.0, i just checked
Comment 2 Jared Camins-Esakov 2012-02-19 15:44:51 UTC
*** Bug 5289 has been marked as a duplicate of this bug. ***
Comment 3 Nicole C. Engard 2012-03-29 14:13:54 UTC
This is fixed in master. Is it still a problem is 3.6?
Comment 4 Owen Leonard 2013-03-26 23:48:11 UTC
I can reproduce this bug in master as of 3.12 beta1. The JavaScript-driven edit/delete menu links which appear when you click on a table cell are not affected by the IndependantBranches preference.
Comment 5 Magnus Enger 2013-05-18 08:05:46 UTC
Looks like this has been fixed on bug 10225.

*** This bug has been marked as a duplicate of bug 10225 ***