• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: WEB-302
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: Boroondas Gupte
Votes: 5
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
3. Second Life Website - WEB

Possibility for Residents to run account-fixing scripts themselves

Created: 28/Aug/07 03:56 AM   Updated: 27/Feb/09 03:02 PM
Return to search
Component/s: Account summary, secondlife.com
Affects Version/s: None
Fix Version/s: None

Issue Links:
Duplicate
 
Relates


 Description  « Hide
Make it possible for Residents to run non-dangerous account-fixing database scripts themselves from the secondlife.com website.
(This is not my own idea, I just made a feature request from Gypsy Paz' comment cited below.)

Often, when a bug has been addressed in the code (be it server or client) or hardware-wise, accounts damaged/altered by the bug still need repair/cleanup in the database. (MISC-567 is an example, I'm quite sure there are and will be more of this sort). When Lindens write automated scripts that can fix the problem, but would be a too great load to just preventively be run over all accounts, there could be a link on the account page of secondlife.com, that lets Residents initiate an automated run of the script for their specific account, when they're affected. Of course this should only be enabled for scripts that don't need any manual sanity check before being run.

Citing Gypsy Paz' comment on MISC-567:
"You know what would be cool, if you guys could give us some account maintenance tools when we login to the main website, stuff like rebuilding the inventory or friends list, or even the whole account. Have it queue it up in a separate database, and then have some procedures that run these maintenance routines based on what that database has queued up. And keep it from getting flooded by making it clear that doing it will make that account unavailable while its being run, lol but anyway, this is probably not the right place for suggestions like that "



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
WarKirby Magojiro added a comment - 28/Aug/07 11:18 PM
This sounds like a neat idea, actually. If there are automated tools to do such things, anything which doesn't pose a security risk should be available to use ourselves.