#7457: No batch deleting of unhandled resources -------------------------------------------------+------------------------- Reporter: humdinger | Owner: deejam Type: bug | Status: in-progress Priority: normal | Milestone: Component: Website/User Documentation | Version: Translator | Keywords: user guide Resolution: | Blocking: Blocked By: | Platform: All Has a Patch: 0 | -------------------------------------------------+------------------------- Comment (by deejam): Replying to [comment:6 humdinger]: > Well, it does work as you describe... But doing a "Select all" or "Select all {extension}" and ending up with only 50 selected items is kinda fraudulent. :) Well, don't shoot the messenger. As I explained, I think it is a bad idea to change the Apache configuration. So this is what we have to live with. Vincent probably never tested with more than 100 checkboxes, which I can understand. > I guess you can't select really all matches and do the actual deleting in 50 item batches in the background?[[BR]] No, since Apache would only allow 100 items (I think) in each request. Ajax would work, or sending a text file containing the data. But both are lots of work for little effect. > Granted, having so many unhandled resources seems to be a very improbable situation. I think us having over 3000 of those resulted from some unintended import.[[BR]] > Can you delete all those ".svn-base" files directly in the database? After those are gone, I'd be fine with a 50 item limit. I do not have access to the server. That complicates things. Also, I think that they are deleted from the database but kept on disk in case you need to undo. Which is good. > PS: Is there a way to see if Niels has already pushed one of your changes to the server? Maybe some version/date info on an admin page? Not easily, no. Maybe he could send an e-mail to some mailing-list after each upgrade. But that's off-ticket. If you e-mail me the instructions of what you want to delete, then I can help you. It will not take that long to do and it is a one-time job. I will also e-mail Niels and ask him to manually change to 95, which should be the maximum since there are 5 form inputs (form, 2 buttons and a textbox). I selected 50 because I was certain that it would work. If 95 works, I can create a patch using 95 instad of 50 and also change the Select All button label to something less "fraudulent". In my word this ticket is now solved. Agreed? -- Ticket URL: <http://dev.haiku-os.org/ticket/7457#comment:7> Haiku <http://dev.haiku-os.org> Haiku - the operating system.