Title: capabilities bug? (cannot reply)
Last modified: August 21, 2016

---

# capabilities bug? (cannot reply)

 *  Resolved [gregorio.samsa](https://wordpress.org/support/users/gregoriosamsa/)
 * (@gregoriosamsa)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/capabilities-bug-cannot-reply/)
 * Hi,
 * I’ve been using wpsc Support Tickets for a while, and it worked great, but i 
   just installed the current version on a different site and I couldn’t reply tickets.
 * I suposed it was a capabilities issue and installed User Role Editor trying to
   figure out what was going wrong and I saw the capability “manage_wpsct_support_tickets”.
   After checking wpsc-support-tickets.php and php/reply_ticket.php, I realized 
   that on the first one it’s called “manage_wpsct_support_tickets” (lines 466 and
   474) while on the second it’s called “manage_wpsc_support_tickets” (line 67).
 * As soon as I changed (added ‘t’ after wpsc) php/reply_ticket.php I was able to
   reply tickets.
 * I guess it’s affecting every capability related with tickets.
 * Did this happen to anyone else? Can the creator confirm it’s a bug?
 * THX
 * [http://wordpress.org/plugins/wpsc-support-tickets/](http://wordpress.org/plugins/wpsc-support-tickets/)

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [mother.of.code](https://wordpress.org/support/users/imazed/)
 * (@imazed)
 * The Mother of Code
 * [12 years, 3 months ago](https://wordpress.org/support/topic/capabilities-bug-cannot-reply/#post-4565025)
 * Hi gregorio.samsa,
 * I’ve encountered the same problem and used your fix to resolve the issue. Guess
   it’s a bug that needs to be fixed!
 *  [uncovery](https://wordpress.org/support/users/uncovery/)
 * (@uncovery)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/capabilities-bug-cannot-reply/#post-4565028)
 * i have fixed that problem and provided a pull-request:
 * [https://github.com/wp-plugins/wpsc-support-tickets/pull/2](https://github.com/wp-plugins/wpsc-support-tickets/pull/2)
 * You can also download a complete version here:
 * [https://github.com/uncovery/wpsc-support-tickets](https://github.com/uncovery/wpsc-support-tickets)
 * Please tell me if it worked.
 *  Plugin Author [jquindlen](https://wordpress.org/support/users/jquindlen/)
 * (@jquindlen)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/capabilities-bug-cannot-reply/#post-4565043)
 * Fixed in 4.2.0
 *  Plugin Author [jquindlen](https://wordpress.org/support/users/jquindlen/)
 * (@jquindlen)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/capabilities-bug-cannot-reply/#post-4565044)
 * If anyone is wondering why this happened, I code another plugin which uses manage_wpsc_support_tickets
 * This escaped me because I develop both plugins on the same test environment, 
   so I had both permission:
    manage_wpsc_support_tickets manage_wpsct_support_tickets
 * The elegant solution to prevent this stuff from happening is full unit test code
   coverage.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘capabilities bug? (cannot reply)’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wpsc-support-tickets_3eaded.svg)
 * [IDB Support Tickets](https://wordpress.org/plugins/wpsc-support-tickets/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wpsc-support-tickets/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wpsc-support-tickets/)
 * [Active Topics](https://wordpress.org/support/plugin/wpsc-support-tickets/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wpsc-support-tickets/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wpsc-support-tickets/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [jquindlen](https://wordpress.org/support/users/jquindlen/)
 * Last activity: [12 years, 3 months ago](https://wordpress.org/support/topic/capabilities-bug-cannot-reply/#post-4565044)
 * Status: resolved