summaryrefslogtreecommitdiff
path: root/indra/newview/llgroupmgr.cpp
AgeCommit message (Collapse)Author
2015-08-13MAINT-5219 FIXED "Ban Member" from the group chatters list context menu is ↵AndreyL ProductEngine
greyed out when you have the ability to manage the ban list
2015-06-08MAINT-5237 FIXED Everyone Roles are not allowed to view the member's listAndreyL ProductEngine
but the Viewer claims that it is retrieving the member list
2015-02-18MAINT-4242 FIXED Just clear ban list before populating it with new data.Mnikolenko ProductEngine
2014-07-17MAINT-4241 FIXED [Group Bans] Ban member(s) button is not greyed out for ↵andreykproductengine
banning group owners. Viewer gives message that you ejected group owner.
2014-06-23MAINT-4182 Cleaning upandreykproductengine
2014-06-19MAINT-4182 FIXED The group ban list always appears emptyandreykproductengine
2014-06-16viewer-release mergeChris Baker
2014-05-19mergeBrad Payne (Vir Linden)
2014-05-13sunshine-external merge WIPBrad Payne (Vir Linden)
2014-05-07Pull and merge viewer-release as version 3.7.8simon
2014-06-04MAINT-3386 FIXED [vwr] Banned Agents list does not show newly-banned residentsandreykproductengine
2014-05-29MAINT-3351 FIXED Misleading failure message when user is successfully ↵maksymsproductengine
removed from a group's Owners role
2014-03-12mergeBrad Payne (Vir Linden)
2014-03-12merge with releaseRichard Linden
2014-02-18Pull in viewer-lion to lock down next releasesimon
2014-02-14[MAINT-3555] Crash in LLPanel::~LLPanel() on shutdownBaker Linden
- Added clear() after DeletePointer() call to hopfully fix this...
2013-12-04MAINT-3351 FIXED Misleading failure message when user is successfully ↵maksymsproductengine
removed from a group's Owners role
2014-05-08viewer-release merge (to 3.7.8)Baker Linden
2014-04-08[GroupBan] [MAINT-3722] - Banning from 'banned agents' tab does not eject ↵Baker Linden
them from the group - Banning a resident from the "Banned Agents" tab should not properly eject them from the group. - Renamed "Banned Agents" to "Banned Residents". Updated tool tip as well. - You should now receive an eject notification when banning an agent from the "Banned Residents" tab.
2014-03-113.7.4. mergeBaker Linden
2014-02-06[GroupBan] When adding "Manage Ban List" ability additionally grant ↵Baker Linden
requisite abilities - Viewer side implementation for MAINT-3467 complete
2013-10-09[GroupBan] Minor fixes / Code reviewBaker Linden
Reviewer: Richard Linden - Minor fixes from code review - Continue stubbing out ban_reason, or implement it (depending on how quickly I can do it, though stubbing out ban_reason will be sufficient, which it is now) - Fixed an issue where a ban list string in the actions tab wasn't showing up properly
2013-10-02Enum typo, whoops!Baker Linden
2013-10-02Attempting fix for TC build issue.Baker Linden
2013-09-13- Added ban date to ban list uiBaker Linden
- Code cleanup
2013-09-09- Start of code cleanupBaker Linden
- Added refresh button to ban list panel - Added an additional signal to LLNameListCtrl to indicate when the entire name cache is complete.
2013-08-30- Got all major functionality workingBaker Linden
- Changed PUT and DEL to POST which accepts an enum for a create or delete
2013-08-29Initial commit for GroupBanBaker Linden
- Lots of crap isn't working as intended yet.
2013-08-09second phase summer cleaningRichard Linden
replace llinfos, lldebugs, etc with new LL_INFOS(), LL_DEBUGS(), etc.
2013-06-05merge with viewer-releaseRichard Linden
2013-05-21mergeBrad Payne (Vir Linden)
2013-05-05Spring cleaning: removed unused .cpp and.h files, and cleaned up header ↵Richard Linden
dependencies
2013-04-19merge changes for DRTVWR-294Oz Linden
2013-03-29Update Mac and Windows breakpad builds to latestGraham Madarasz
2013-03-13Large changes to the LLCurl::Responder API, as well as pulling in some ↵Don Kjer
changes to common libraries from the server codebase: * Additional error checking in http handlers. * Uniform log spam for http errors. * Switch to using constants for http heads and status codes. * Fixed bugs in incorrectly checking if parsing LLSD xml resulted in an error. * Reduced spam regarding LLSD parsing errors in the default completedRaw http handler. It should not longer be necessary to short-circuit completedRaw to avoid spam. * Ported over a few bug fixes from the server code. * Switch mode http status codes to use S32 instead of U32. * Ported LLSD::asStringRef from server code; avoids copying strings all over the place. * Ported server change to LLSD::asBinary; this always returns a reference now instead of copying the entire binary blob. * Ported server pretty notation format (and pretty binary format) to llsd serialization. * The new LLCurl::Responder API no longer has two error handlers to choose from. Overriding the following methods have been deprecated: ** error - use httpFailure ** errorWithContent - use httpFailure ** result - use httpSuccess ** completed - use httpCompleted ** completedHeader - no longer necessary; call getResponseHeaders() from a completion method to obtain these headers. * In order to 'catch' a completed http request, override one of these methods: ** httpSuccess - Called for any 2xx status code. ** httpFailure - Called for any non-2xx status code. ** httpComplete - Called for all status codes. Default implementation is to call either httpSuccess or httpFailure. * It is recommended to keep these methods protected/private in order to avoid triggering of these methods without using a 'push' method (see below). * Uniform error handling should followed whenever possible by calling a variant of this during httpFailure: ** llwarns << dumpResponse() << llendl; * Be sure to include LOG_CLASS(your_class_name) in your class in order for the log entry to give more context. * In order to 'push' a result into the responder, you should no longer call error, errorWithContent, result, or completed. * Nor should you directly call httpSuccess/Failure/Completed (unless passing a message up to a parent class). * Instead, you can set the internal content of a responder and trigger a corresponding method using the following methods: ** successResult - Sets results and calls httpSuccess ** failureResult - Sets results and calls httpFailure ** completedResult - Sets results and calls httpCompleted * To obtain information about a the response from a reponder method, use the following getters: ** getStatus - HTTP status code ** getReason - Reason string ** getContent - Content (Parsed body LLSD) ** getResponseHeaders - Response Headers (LLSD map) ** getHTTPMethod - HTTP method of the request ** getURL - URL of the request * It is still possible to override completeRaw if you want to manipulate data directly out of LLPumpIO. * See indra/llmessage/llcurl.h for more information.
2013-03-05Fixing issues with not detecting when LLSD XML parsing fails. Changing most ↵Don Kjer
http error handlers to understand LLSD error responses. Fleshing out most http error handler message spam.
2012-12-03MAINT-1979 Viewer crashes while attempting to join group in the moment of ↵Kelly Washington
loading group members * Fix one race condition that could dereference a dangling pointer. reviewed with Simon and Baker.
2012-10-03- Fixed an issue where group list wouldn't fall back to UDP if the region ↵Chris Baker
doesn't support the new GroupMemberData capabaility - Fixed a potential null pointer crash. Thanks to Ansariel from Firestorm for these! Reviewer: Myself
2012-09-06Do the proper fix this time...Baker Linden
2012-09-06Added explicit casting for Linux build, hopefully making it work.Baker Linden
2012-09-05[MAINT-513] Large group managementBaker Linden
- Reduced the timeout to 5 minutes, down from 10 minutes. - Provided output for GroupMemberResponder error - Removed commented calls to sendGroupMembersRequest - Reordered calls to sendCapGroupMembersRequest so it's called last
2012-09-04Cleaned up commentsChris Baker
2012-08-31- Fixed an issue where service was called twice in a frameChris Baker
- Changed level of output logs - Cleaned up comments
2012-08-28Got viewer displaying new data formatChris Baker
2012-08-23Start of getting WSGI service on viewerChris Baker
2012-07-03MAINT-1231 Investigate increasing MAX_CACHED_GROUPS in llgroupmgr.cppKelly Washington
* increased max groups to 20 * changed cache to LRU instead of 'delete half when overfull' reviewed with Baker
2011-07-15STORM-1355 Memory issues from UI for very large groupsRoxie Linden
This change is not guaranteed to fix this issue as the issue is difficult to repro, but there was a sketchy case group member responses come back from the simulator in message packets. For very large numbers of members, there may be a large number of packets received. The member data is placed in a structure of type LLGroupMgrGroupData, based on the group id. The problem is, if the user refreshes the group before the entire contents of the previous request comes back, response packets from the previous request will be intermingled with the responses from the refresh. Both the request call and the response handler would create the group data structure, if the structure wasn't already there. There may be a case where a response from the previous request causes creation of the group data, populating it with the contents of the response, and the responses from the second request would use that group data structure. Also, cleaned up some comments and variable names to be consistent
2011-01-21Code fixes for VS2010 compatibilityMark Palange (Mani)
2010-09-13Bunch of trivial typo fixes that were bothering me on another branch!Tofu Linden
2010-08-13Change license from GPL to LGPL (version 2.1)Oz Linden