I might take you up on that once I fix the queue to only show people who have actually accessed the site after first creating their profile. A lot of people create drive-by profiles and never come back. If someone makes a profile and never looks at the site again, they won't really be around to care if their profile is visible or not. :)
The short answer about why this happened is that there's a weird bug somewhere in the system (my guess is it's probably is a double form submit issue combined with a race condition) that causes duplicate items to be created that for some reason believe that they share the same URL alias (even though they don't). It's fairly rare and it would probably be difficult to hunt down and fix, so it's a fairly low priority at the moment. I can't even delete them unless I manually change the URL alias first, which is something that would be insecure to give everyone access to.
Anyway, sorry for the inconvenience. Let me know if it happens again.
I am, although I'm going to have to end up writing at least some custom code.
Specifically, there's a drupal plugin I'm using called Display Suite, which is responsible for formatting search results. Right now, I can hook into solr with display suite, but only in a very basic way that doesn't allow me to create multiple search interfaces for different types of posts (art, forum posts, blog posts, etc), so I'm going to have to code around that. Most likely I'll just do it the short way and write up some OGA-specific code rather than writing a generalized Drupal plugin for it. However, if you know someone with the time and inclination to undertake such a task, I'd be happy to explain the issue in more detail and help out however I can. :)
Ah, that happens sometimes and I'm not sure what to do about it. The short answer is no, but I can get rid of it for you. Which one do you want to keep?
Sorry about that. Thge forum moderation queue is kind of wonky in that even if a post is approved, it gets held in a weird state where it's "invisible" unless an admin edits and re-saves it. I've instructed people on this, but it's likely that someone approved your post and forgot this (non-obvious) step. I'll try to find it.
As for the user profile, I've got a huge backlog of them that I need to tackle. User profiles are where we get the majority of our spam, so I had to put the approval system in place, but there are just too many to be easily dealt with (there are about 900 right now).
There are a few possible solutions to this:
Make all user profile links "nofollow" and then make them public
Only put the profiles of active users in the approval queue (that is, users who have posted something other than a profile, or have at least logged in once after registering)
Build some sort of system where registered users can see a few profile links on the front page and flag them as either legit or spammy
I think I like the second option best. The first one is unfair to legit users and the third one is too random and inconsistent.
I like the results you're getting with your current generator and I don't feel that there's any need for you to change it drastically. However, I'm going to suggest a different approach just because I enjoy these kinds of conversations.
First off, start with a 2D grid (like you have now).
Randomly pick a bunch of points on that grid and designate them as "nodes". Optionally, make sure they're a minimum distance from all of the other points. Then, decide how each one of those nodes connects with the others.
For each node, pick a random number (perhaps with a minimum and maximum value specified by the user). Grow each node by one pixel in a random spot on the border of the node that many times (so essentially, you're making the node into a randomly-shaped room that's that many pixels in size. When you do this, you can either allow nodes to merge naturally or specifically exclude growth that would cause one node to merge with another.
For each connection between nodes, check if you can draw a straight line between them without hitting a wall. If not, dig a straight line from one node to the other, varying the width of the line (along with right/left offset) until you get to it.
Note that this is just off the cuff, so I can't guarantee how well it would work in practice. However, in theory, the advantage of it would be that you would be able to specify how many "rooms" the cave has, along with the general shape of the cave. If you make the nodes big and the connection width small, you could have a bunch of large rooms with small interconnecting passages. If you keep the nodes small but numerous and allow for some more variation in the connection width, you could have a cave that's made up of randomly winding passages. You could also tweak the connection generation to favor caves with lots of dead ends or a web of passages.
I might take you up on that once I fix the queue to only show people who have actually accessed the site after first creating their profile. A lot of people create drive-by profiles and never come back. If someone makes a profile and never looks at the site again, they won't really be around to care if their profile is visible or not. :)
Done. :)
The short answer about why this happened is that there's a weird bug somewhere in the system (my guess is it's probably is a double form submit issue combined with a race condition) that causes duplicate items to be created that for some reason believe that they share the same URL alias (even though they don't). It's fairly rare and it would probably be difficult to hunt down and fix, so it's a fairly low priority at the moment. I can't even delete them unless I manually change the URL alias first, which is something that would be insecure to give everyone access to.
Anyway, sorry for the inconvenience. Let me know if it happens again.
I am, although I'm going to have to end up writing at least some custom code.
Specifically, there's a drupal plugin I'm using called Display Suite, which is responsible for formatting search results. Right now, I can hook into solr with display suite, but only in a very basic way that doesn't allow me to create multiple search interfaces for different types of posts (art, forum posts, blog posts, etc), so I'm going to have to code around that. Most likely I'll just do it the short way and write up some OGA-specific code rather than writing a generalized Drupal plugin for it. However, if you know someone with the time and inclination to undertake such a task, I'd be happy to explain the issue in more detail and help out however I can. :)
No problem. This is another one of those things I'm going to have to address sooner rather than later.
I haven't actually seen this happen before, and I don't know why it would. If it happens again, leave it as-is and I'll take a look at it.
Ah, that happens sometimes and I'm not sure what to do about it. The short answer is no, but I can get rid of it for you. Which one do you want to keep?
Sorry about that. Thge forum moderation queue is kind of wonky in that even if a post is approved, it gets held in a weird state where it's "invisible" unless an admin edits and re-saves it. I've instructed people on this, but it's likely that someone approved your post and forgot this (non-obvious) step. I'll try to find it.
As for the user profile, I've got a huge backlog of them that I need to tackle. User profiles are where we get the majority of our spam, so I had to put the approval system in place, but there are just too many to be easily dealt with (there are about 900 right now).
There are a few possible solutions to this:
I think I like the second option best. The first one is unfair to legit users and the third one is too random and inconsistent.
At any rate, your profile is approved.
Nice work on these, thanks. :)
I like the results you're getting with your current generator and I don't feel that there's any need for you to change it drastically. However, I'm going to suggest a different approach just because I enjoy these kinds of conversations.
Note that this is just off the cuff, so I can't guarantee how well it would work in practice. However, in theory, the advantage of it would be that you would be able to specify how many "rooms" the cave has, along with the general shape of the cave. If you make the nodes big and the connection width small, you could have a bunch of large rooms with small interconnecting passages. If you keep the nodes small but numerous and allow for some more variation in the connection width, you could have a cave that's made up of randomly winding passages. You could also tweak the connection generation to favor caves with lots of dead ends or a web of passages.
These are really nice, and I like the palette. Excellent work. :)
Pages