@caeles: Sorry about that. I just made it possible to permanently toggle using the rich text editor in your user profile. While this doesn't fix the bug itself, it should at least serve as a work-around.
@MoikMellah: I don't own an iDevice (and can't really afford to go buy one at the moment), so I'm not sure how to go about testing and fixing this. I've disabled a Drupal setting that minifies and caches the theme css and javascript, so it should be easier for people to poke and prod at them now. If someone can submit a fix that doesn't break anything else, I'll add it.
@surt: Fixing that is going to involve a lot of effort and testing. I know it drives some people crazy, but unfortunately the fix will involve some major changes site theme. For the record, the page used to extend outward as wide as the browser would go, and while I get occasional complaints about it not doing that now, I got a flood of complaints when it did, because the blog, forum, and comment text widened as well, and that made it difficult to read. If I'm going to fix this, I'll need to be intelligent about how the layout works so that I can avoid those issues. I'll see what I can do about the wide images, though.
@riidom: The blocks needed to be reorganized a bit, and your suggestion spurred that on. All the blocks now show up on the latest page if you scroll down enough. I also removed the superfluous donate block.
@JaidynReiman: I Tweaked the page headers so they shouldn't do that anymore. Let me know if you see some that I missed.
@Botanic: Just added a fix. Hopefully it doesn't break everything else. :)
@catmanjan: When I come up with a "hotness" algorithm for arts, popular will link to a different page.
This site exists because of Drupal. As for whether I've ever considered rewriting OGA from scratch, the answer is absolutely not. I don't have the time.
Also, you what you don't see here are people talking about the hundreds of things on this site that just work because of Drupal. Things that I would have had to code myself (and likely never would have gotten around to in many cases).
For the record, I'm aware that searching is broken. I am planning on addressing it in a big way, and that involves a major rework of the search system. If I have to write the code for that part of it myself, I'm prepared to do that. Drupal is nice in that way -- it's pretty simple to drop in your own code.
In essence, the reason that I don't rewrite the site from scrach is the same reason that I'm not rewriting the little parts of it that don't work very well -- I haven't been able to find the time to do that. Regardless, getting rid of everything because other people don't like Drupal isn't the solution.
Off the top of my head, I can think of two ways to go about it. The easiest way is just (like you said) to make a new entry. Link to the original very clearly in the description and in the copyright notice.
The other way, if you can get a hold of the artist, is to have them add you as a collaborator on their art, which will allow you to edit it in place. Collaborating is the better option, but obviously it will only work if the artist agrees to it.
We run on Drupal. I find it very developer friendly, but only after you get past the learning curve, which can be pretty substantial. A lot of my initial time with open sourcing OGA will likely be spent coaching people and tweaking submitted code to make sure everything is done in a consistent way.
As for the LPC hairstyles, I'm looking forward to seeing them. :)
@ace491:
The duplicates in art browsing is a known bug. A complete rewrite of the search function is planned.
I like the idea about automatically stopping other playing music. I'll see if I can fix that in the next day or so.
@caeles: Sorry about that. I just made it possible to permanently toggle using the rich text editor in your user profile. While this doesn't fix the bug itself, it should at least serve as a work-around.
So, quick update on this stuff:
@MoikMellah: I don't own an iDevice (and can't really afford to go buy one at the moment), so I'm not sure how to go about testing and fixing this. I've disabled a Drupal setting that minifies and caches the theme css and javascript, so it should be easier for people to poke and prod at them now. If someone can submit a fix that doesn't break anything else, I'll add it.
@surt: Fixing that is going to involve a lot of effort and testing. I know it drives some people crazy, but unfortunately the fix will involve some major changes site theme. For the record, the page used to extend outward as wide as the browser would go, and while I get occasional complaints about it not doing that now, I got a flood of complaints when it did, because the blog, forum, and comment text widened as well, and that made it difficult to read. If I'm going to fix this, I'll need to be intelligent about how the layout works so that I can avoid those issues. I'll see what I can do about the wide images, though.
@riidom: The blocks needed to be reorganized a bit, and your suggestion spurred that on. All the blocks now show up on the latest page if you scroll down enough. I also removed the superfluous donate block.
@JaidynReiman: I Tweaked the page headers so they shouldn't do that anymore. Let me know if you see some that I missed.
@Botanic: Just added a fix. Hopefully it doesn't break everything else. :)
@catmanjan: When I come up with a "hotness" algorithm for arts, popular will link to a different page.
Indeed.
This site exists because of Drupal. As for whether I've ever considered rewriting OGA from scratch, the answer is absolutely not. I don't have the time.
Also, you what you don't see here are people talking about the hundreds of things on this site that just work because of Drupal. Things that I would have had to code myself (and likely never would have gotten around to in many cases).
For the record, I'm aware that searching is broken. I am planning on addressing it in a big way, and that involves a major rework of the search system. If I have to write the code for that part of it myself, I'm prepared to do that. Drupal is nice in that way -- it's pretty simple to drop in your own code.
In essence, the reason that I don't rewrite the site from scrach is the same reason that I'm not rewriting the little parts of it that don't work very well -- I haven't been able to find the time to do that. Regardless, getting rid of everything because other people don't like Drupal isn't the solution.
Off the top of my head, I can think of two ways to go about it. The easiest way is just (like you said) to make a new entry. Link to the original very clearly in the description and in the copyright notice.
The other way, if you can get a hold of the artist, is to have them add you as a collaborator on their art, which will allow you to edit it in place. Collaborating is the better option, but obviously it will only work if the artist agrees to it.
Actually, that was kind of a silly oversight in my part. Also very easy to fix. It's in there now. :)
Yup, there was. Your credits display correctly now. :)
Ah, I think that's because it's trying to strip HTML tags out of a field that's actually plain text. Hopefully there's an easy way to fix that.
True, but that's also a function of how popular and widely used it is. :)
We run on Drupal. I find it very developer friendly, but only after you get past the learning curve, which can be pretty substantial. A lot of my initial time with open sourcing OGA will likely be spent coaching people and tweaking submitted code to make sure everything is done in a consistent way.
As for the LPC hairstyles, I'm looking forward to seeing them. :)
Pages