|
|
forum: can't edit posts and/or attachments/licensingThe forum doesn't let you edit the last post one submitted anymore. Also, we can't edit attachments on past posts. I can understand why text might be decided to be locked, but attachments should be able to be edited. The reason I say that, is because, for some reason licensing stuff was made mandatory with the composition repository, so this should somehow be able to be addressed with attached compositions as well. We can't add the same kind of license info to attachments. I'd also like to re-request that we're able to use whatever licensing we choose, instead of the forced drop down. In addition, the addition of the drop down/licensing, and lack of licensing for older stuff, implies that there isn't any kind of licensing, when it may be written in the composition, an additional txt file., or body of the post, etc. |
...thanks for the time, btw!
Edit functionality can only be done before a post has been replied to. I think this applies to both nodes and comments.
Yes, we will need to retroactively get license information on past compositions. We may need to collect this information.
Thank you.
Thanks Matthew.
Well, you know what, now I see edit again! I know that edit gets locked when someone replies, but I had no edit function, even right after hitting post, for the past week.
I don't know if the licensing thing is a big deal, but it occurred to me that maybe there should be some function for that? I may be impractical. It does seem like it would be nice to checkmark something that references an attached txt, or says that licensing info is in the composition, instead of one of the presets. Maybe it's just that I'm uncertain about some of the fine points of the CreativeCommons attributions.
For instance, NonCommercial-NoDerivs, says that "Attribution — You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work)." I don't really know where we should put that? Does this fall under what is considered "EULA"? (That seems like an ignorant question, but...). If so, it seems like so many software packages have distinct EULA's, not just one from what's in the drop down.
On this general note, when the composition repository started, it didn't necessarily have the kinemecore "import composition" function there, so it can be a bit weird to have some things present themselves as virtual patches in QC, if they weren't formatted with that in mind. (I've mentioned this, but just as "huh, that's interesting".)
I know that I removed a few compositions (a long time back) that seemed weird in that regard (if someone was to import it as with kinemecore, with the way it ends up in the patch list). I had a request not too long ago to put one back up. Maybe there could be some kind of tag to make it so things can't get imported via kinemecore, if the person submitting it has made it more as an example, and less for the purpose of being a virtual patch? Maybe this is a moot point if it doesn't work in Lion, but it's a thought if it gets redone.
I understand all of this stuff takes time, or maybe doesn't make sense for everyone. These are just some thoughts on what would seem nice.
We're investigating why your ability to edit un-replied posts is sometimes missing.
When you first reported the problem we logged in as you (not that we know your password, but admins can masquerade as other users) and your edit button was there. Today when you again couldn't edit we logged in as you and your edit button was gone.
Please let us know if you notice any patterns. For example, if you log out an log back in, does the problem go away?
Until this is fixed, anyone who's missing an edit button on un-replied posts can ask the moderators to make edits.
The November 22 update to one of the forum plugins we use broke the ability for users to edit their own comments without replies in some situations. I fixed it on kineme.net and submitted a patch upstream --- http://drupal.org/node/1356390. On kineme.net, it manifest as preventing users from editing their own comments if the comments were attached to a Forum post, but not if the comments were attached to a Composition Repository post or Wiki post, which I think explains why you were seeing it sometimes (and why we were having trouble reproducing the issue).
Let us know if you notice this issue again.
We just added an "Other" option to the Composition Repository's license drop-down. When adding a Composition with License "Other", please include either the full license details in the Composition's "Description" text field, or a link to the full license details.