stock-replies: Custom scripts not saved after saving them

[rusivi2]

1) lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10

2) apt-cache policy firefox-lp-improvements
firefox-lp-improvements:
  Installed: 0.98-0ubuntu1~ppa1
  Candidate: 0.98-0ubuntu1~ppa1
  Version table:
 *** 0.98-0ubuntu1~ppa1 0
        500 http://ppa.launchpad.net/gm-dev-launchpad/ppa/ubuntu/ maverick/main i386 Packages
        100 /var/lib/dpkg/status

3) What I expected to happen is after a fresh, native install via:

http://gb.releases.ubuntu.com/10.10/ubuntu-10.10-beta-desktop-i386.iso

and fully updating, I could go to the following website:

https://bugs.launchpad.net/ubuntu/+source/xine-ui/+bug/116086

create a custom response by clicking +edit+, then after creating a couple custom responses saving them by clicking "Save Stock Replies".

4) What happens instead is that it does not save the stock replies. I tried restarting the browser, then going back to the site, same phenomenon.

[rusivi2 (rusivi2-deactivatedaccount)]

Also happened at:

https://bugs.launchpad.net/ubuntu/+source/ddd/+bug/116639

[Brian Murray (brian-murray)]

I've been unable to recreate this bug report and the reply I am adding is being saved in the standard responses.

A couple of things that you could do to debug this issue are using the Firefox Error Console to observe any error messages that appear when trying to add, save or use the new reply.

Of course it would help to set debug = 1 in the stockreplies user script.

Also inspecting about:config and looking for the reply that you have added or trying to add might be informative.

[rusivi2 (rusivi2-deactivatedaccount)]

I just went to the website mentioned previously, clicked the down arrow, +edit+, Add New Stock Replies twice, inputted into both "name" and "status" fields, clicked Save Stock Replies, and after a couple minutes still did not get the prompt to click the Ok button noting the scripts were save. Then when I reloaded the page and clicked "edit" the two ones I added were there. Marking as new, may need a more appropriate bug title.

[Bryce Harrington (bryce)]

The capability to edit custom scripts has been removed from the codebase, and at this time is not planned to come back, so am marking this bug as a won't fix.

Greasemonkey got a major update a few years ago, which busted stock-replies fairly badly. I've done a rewrite of the script to get it functional once again. In the old script, a lot of it's code was devoted to the management and UI for custom scripts, making it challenging to debug (and maintain) the code. So, dropping this feature permitted majorly simplifying the code and thus making it a lot easier to debug (and hopefully to maintain). The old code's custom script functionality had some imperfections, such as the bug described here; it never did work quite right, and there wasn't an easy way to share (or backup) your customizations.

Ideally, I think a better solution for custom scripts would be to store them in a web app, where they could be loaded and saved via a REST API. A nearer-term solution would be a git repo the data can be loaded from and where collaborative editing of responses can be done. This latter idea I think may be in the works soon; the former idea is probably too blue sky, at least for now.