When one makes a "comment" to an entry, there is a "Title" field (default-filled with "Comment to [original entry's title]"), but one could change the Title.  However, whatever is in the title field for the comment does not show up with the Comment entry.  It would be nice to tag your comment/sub-entry with Title.

Not sure what the deal is with my photos, but for some reason alog chooses to not let some of my photos upload to an entry.  Have used original names of images, and changed names of files.  Have tried from home and from work to no avail.  Will keep trying.  Attached is the error message I get afer I try uploading the file I select.

Entries made via MacBook Pro & with Firefox.

Not sure how I did it, but I accidentally hit the back button on my browser while making an entry, and went back to see that the entry I was just about to post had vanished.  :(

Came up again with this issue today :

When I  modify an aLog from a "draft" that has been saved for a certain time (not clear how long), it won't let me post, save or preview the modified alog. It will actually delete the modification if trying to do so, and go back to the original draft.

I was looking to upload the source code tar ball for the record in LHO aLOG 8325, but after selecting the file in the browser, I hit the "upload file" button and the file just disappears from the browse field without uploading anything.

We've requested that *any* file type should be upload-able, as long as it's under the 10 Mb limit (see LHO aLOG 3798 and subsequent comments) but I guess the infrastructure doesn't allow for it?

P.S. looking if we've requested this before ('cause I thought ), I rediscovered a report of a bug that's still present:
.

If a user is in the middle of uploading files (or even just getting started), and he forgets to select a file for uploading and subsequently hits "UPLOAD FILE" with nothing selected, it takes the user to a blank white screen. Thankfully, nothing is lost, and one can just hit his browser's back button, but the log should throw a warning / error when this situation arises. A pop-up that gray's out the log, saying "You've not selected anything to attach, please browse for a file" with an "OK" acknowledge button would suffice. Or if that's too sophisticated for the infrastructure of the log, this user error should at least take you to another page with the same warning, and a link back to the upload page and/or the add report page. 

When writing a comment to an aLOG, the user has the option to change the title (as opposed to the default "Comment to [insert original subject here]"), or change the Section / Task. However, after submitting the entry, these additions / edits are not reflected on the resulting comment. Interestingly enough, the information is stored, however, because when one clicks to edit the comment, the changes and new title are still there.

See, for example, LHO aLOG 3727, LHO aLOG 3550, or LLO aLOG 4156.

No production GS-13s on this unit but it does have good parts.  No issues getting it in the Storage Container.

See Jim worry it down into position.

After saving a new version of a wiki page, you see the new version of the page with a message at the top that says:

For my instance in the Pcal wiki, I finish editing the wiki and arrive at this page:

https://awiki.ligo-wa.caltech.edu/aLIGO/pcalWiki#preview

If I click through a link and come back, I get popups.

But if I go through the normal wiki page:

https://awiki.ligo-wa.caltech.edu/aLIGO/pcalWiki

...everything works as expected.

I often use HTML tags in my aLOG entries to change fonts or colors in my entry. Sometimes, I forget to close the tag. This causes the rest of the page of logs below it to inherit the property of the tag I left open. (Others have done this / use HTML tags / caused this error -- I say this only to emphasize that it's not just me; it's beside the point).

For example, search the log for my name, and the keyword "/Common/MatlabTools/." This returns several entries (to be sure I demonstrate them getting "infected" by my left-open <font face="courier"> tag). Scroll to entry 1507 (a comment to Jeff Garcia's entry 1506, 5 entries down), and see that all entries below it have their font changed.

EVEN MORE CURIOUS: The bug manifests itself differently on different platforms. On a workstation-like machine ( Ubuntu 10.04 LTS, running FireFox 3.6.24), the open tag affects rest of the page in it entirety. On my laptop (Mac OS X 10.7.2, FireFox 8.0.1) it only affects the headers and footers to the entry (Subsystem/Task, Author and Date, and Title; any attachment indicators), the bodies retain their formatting.

I usually catch this user error, because I run preview before I post, but sometimes it slips. 

Regardless, I think the log should be robust against this sort of user error.

While continuing to be logged in, after posting a comment, one should be able to edit comments that you've written in a similar fashion as the main entry.

Comments do not show up as results of search queries for them (I've tested by searching for entry ID #, author name, and keyword search).

Where a comment to an aLOG is attached under the main entry, the formatting that a user enters into the comment is not retained (carriage returns, tabs, spacing, etc.). However, the redundant separated comment (that appears at the top of the viewing page) does contain all formatting. This fix will be imperative once the requested feature of Comments Only Showing Up Under the Main Entry is implemented.

When hitting "enter" in quick search, it doesn't execute the search, it just returns the entire alog.