2999: Tried to re-upload the screenshot after it became inaccessible.
- SetupIssue
- Review Board
VMX***@motoro****** (Google Code) (Is this you? Claim this profile.) | |
Aug. 8, 2013 |
What version are you running? I don't know where to find this information. What's the URL of the page containing the problem? (confidential) What steps will reproduce the problem? 1. Add a screenshot image to a review board entry. 2. Use the entry for a while until the screenshot becomes inaccessible. 3. Try to re-upload the screenshot image. What is the expected output? What do you see instead? Expected: Original screenshot does not become inaccessible over time. or At Least: Screenshot can be re-uploaded at any time. Instead: Original screenshot becomes inaccessible over time. and: Screenshot cannot be re-uploaded. What operating system are you using? What browser? Fedora 14 with Firefox 19.0 Please provide any additional information below.
Hi, The version should be listed right next to "Review Board." There's nothing Review Board does that would make the screenshot inaccessible over time. This sounds more like something custom happening on the server. I'd recommend asking your sysadmin.
Review Board Revision 1.7.7.1
I'm wondering what a sysadmin might do that would prevent me from adding a new screenshot to an existing entry. Review Board allowed me to delete the old entry, so why not allow me to add a new one?
Actually, I'm not even seeing a Screenshot section any more, as though it can only be added when the issue is opened. So instead I tried to use Update > Add File. Yesterday that failed without an error message (as I recall). Today it works.
Ah yes, in 1.7.x, the "screenshots" are deprecated in favor of the more general file review UIs. If uploading files works as expected, then I'm tempted to say this isn't an issue. There may still be something weird with the way your server is set up to store uploaded files, but you'll have to engage with whoever runs that server to debug that.
Please keep in mind that all of these issues transpired without my saying anything to the server administrator. If it's working now then it went through a period of instability that would be difficult to account for by anything a system administrator would do.
There are plenty of things that might cause a period of instability with regards to file storage, such as momentary issues caused by upgrades or server maintenance, all the way to things like disk partitions filling up. If you can find error messages either on your client or in the server logs, we can look into them, but we're pretty limited with the information you've given us so far.