bbik

The API was not throwing any errors, or at least not outwardly. It was, however, reporting "No such dragon" for Thuwed codes -- despite listing those codes as parents for Thuwed offspring. It looks like it is properly returning dragon info for Thuwed codes again, though, so I presume the issues others were seeing have resolved themselves?

I don't know what the policy is for double posting around here, but AoND is working again, and some DC API bugs have been addressed in the process. Thanks T.J.! And thanks everyone else for your patience! Now to see if I have enough time to implement some of the fun new things rolling around my mind... 🤪

Hi everyone. Sorry about this. Yes, I am aware the site is down, and yes, it is related to the new API. Who knew it would be a bad thing to finally have a window of time to try to experiment with it a bit?! It was not supposed to have had any effect on the existing site. Clearly, that didn't work as intended. I'm still waiting to hear back about how to fix it, but I promise, as soon as I have a solution, I will get things running again! I emptied the ER manually last night to prevent (additional) sickness, but the daycare is too big of a task for manual management. You'll have to fog if you want dragons to stop receiving views instead, for now.

The scroll name problem should be fixed. Apparently, the fairly arbitrary and inconceivably large size limit I set up initially waaaaay back when this site started, was not actually inconceivable. Who knew AoND would become so popular and still be up and functioning all these years later?! Sorry it took so long to get it fixed. I noticed a weird error from the site a while ago, but didn't see anything posted here to test with, and didn't have time to investigate. By the time anything was reported here, I'd forgotten (and have still been super busy), so thank you MoonlitEevee for the PM! To everyone: In the future, if there are any bugs, please reach out to me directly -- I'm not particularly active anymore, but I'll do what I can to keep AoND running when core things come up. PMs at least get my attention, but email would be best, if you're willing -- bugs at allureofnds. That way I can quickly get your report, and reply when I've dealt with it, or ask if I need more information. Then you can let the thread know as well, when you've confirmed that it's fixed. 😀 As for any scroll statistics issues, those are going to have to wait. I would, someday, like to revamp it all and get it working again, but that will be a much larger undertaking, and I just don't have that kind of time these days. Darn that "real life" thing going and getting in the way of hobbies with a long list of time consuming end goals! 😆

Hi all! I'm still alive, but swamped with life stuff, even more than one would expect given this crazy past year. A few notes, though: The domain and hosting have been renewed for another three years. Previous donations covered about half the cost; I paid the remaining $150 out of pocket. If any of you are willing and able to help defray those costs and keep the site ad-free, I would appreciate it! I am working on a better way to track site improvements, starting with figuring out where I left off on ones already in progress. I am hoping this will make it easier for me to get them pushed out quicker in the future, but it's a long ways down the road right now. But in that vein: I'll make a note about the daylight savings issue and see if I can work that out for next year (I expect it's only an issue going in one direction, right now, given the observations posted). I know a few of you have reached out directly with suggestions and concerns. I haven't intentionally ignored you, but I please know that I have your items on my list, and they actually fit in very well with some other improvements I've been wanting to make. I'm debating a major overhaul, at least behind the scenes, but possible of the pages you all see, as well. Historically, AoND users have enjoyed the option to continue using the site with full functionality, even if JavaScript is disabled in their browser. It looks like many of the fansites no longer work that way, nor does much of the internet in general. How many people still use AoND without JavaScript, and/or would be upset if that ability were removed? I haven't made any decisions yet, but that is one option I could consider. In the meantime, if any of you notice issues with the site, or have any comments, let me know! I check this thread periodically. Alternatively, a direct message on this forum is the quickest way to make sure I see it, though odds are I won't reply immediately. Here's to at least three more happy years!

Certainly! Just don't you all forget to buy your sweethearts some candy or flowers for next week at the same time! The other option worth considering is to put ads on the site. I'm not sure if it would cover everything, but it ought to at least make a dent. The idea has come up before, but no one ever seemed too opinionated either way, and enough people have always been willing and able to chip in for it to be unnecessary. What is the prevailing mindset these days? Ah, yeah, I forgot about that one. That's one of the pages I ran out of time to update when I had to migrate the site, and I never did get back to it. I should probably get on that, seeing as it's still linked from the home page... There used to be a number of size, specificity, style, and color options. Another feature lost to the rushed migrate. Since it already exists, if with outdated logic, it shouldn't be too hard to get up and running again. I just need to find a solid block of time to work on all these things.

Latest update: The domain has been renewed for another four years, for a few pennies under $40. Hosting still has a year to go before it needs to be renewed, but it's going to cost several times that amount for the same time span. There was just about enough left in the account from the last fund raising to cover this domain renewal, but come hosting renewal, we'll be starting from scratch. If any of you want to try and preempt next year's big website notification, the "Support AoND" button at the bottom of every page on the site would be happy to help you out! And either way, we'll see where things stand when we get closer to the deadline. Thanks to everyone for helping make this site so successful; I couldn't have done it without all of you!

I finally heard back. Sure enough, AoND had its API access blocked, presumably due to the sickness check, which does not go through the API since that information doesn't even exist in the API. As such, I have disabled that option. I also requested that information be added to the API (I know people have done so before, in various fashions, as well, including at least one thread in the Suggestions subforum -- if someone could find and link it so it can get bumped with fresh requests, maybe that would help!), because clearly people want it, if so many of you used the option on AoND that it triggered the API access being blocked! Hopefully API access is re-instated soon. Once it is, everything should "just work" again. Except the sickness check. Edit: Found a couple threads, but they don't seem to be what I'm vaguely recalling... We'll see what others turn up, and maybe tomorrow I can do a better check myself. * Possible API Improvements, Ideas for TJ to maybe implement * Add the new features to the API * Ways to Reduce Viewbombing Attempts, Fansite API Login +more Edit 2: It's also possible that what I'm remembering wasn't its own thread, but rather a collection of posts in the Cave Feedback thread. But if so, I definitely don't have time to go through all of that to quote and bump (or start a new thread with) the relevant posts.

Not much in the way of an update... The host says it's not on their end (none of their other servers have this problem, only the one AoND lives on). I contacted TJ and we confirmed that the IP I thought was AoND's wasn't blocked, but it turned out that IP wasn't quite right, and I haven't heard anything back about the updated IP. So I'm stuck waiting for someone to tell me what's changed and why, just as much as all of you are.

I noticed it early yesterday, but was too busy to start investigating until late last night, sorry! I was hoping it was just a temporary hiccup that would resolve itself... I'm looking into it at this point, but it might take a bit still, so I'll at least clear out the ER so those dragons stop getting pummelled.

I think there was one at one point. But given how low priority it was (it basically said "what you see is what you get"; scroll name, dragon codes, selected API-provided info, and completely separately IP addresses for 5 minutes to count users online), it probably fell by the wayside with the server migration. Much like the other fansites have responded, this is a site to raise dragons, not to collect personal information, as evidenced by the complete lack of personal information that is even requested.

The host had to reboot the server that AoND is on in order to resolve some instability issues. They are hoping it will be back up soon. I, however, need to get to bed, so I am hoping that when it comes back, it does so without causing site errors. If that is not the case, I will look into things ASAP, but may not have time until I get home from work tomorrow. Cross your fingers that it doesn't come to that!

It looks like my host had an issue with their provider again for about 10 minutes a couple times today, and their provider will be doing maintenance tonight from 11pm-3am EST, with some amount of downtime expected. For those curious, my host has a post about these and the previous downtimes here.

It looks like there was a particularly bad issue at a data center where my host (among others) store the servers. Here's the analogy my host made, for those who are curious: That said, the downtime still never should have happened, and my host is working on getting an explanation from the data center for why it did.

Yeah, I do still plan to add it (and everything else that existed previously) back into AoND. But with plans and life being what they are... Sorry it's taking so long!

Yay host! In regards to what happened, it sounds like one of the issues that came up during the host's original hardware migration a couple weeks ago cropped up again. I'm checking with them about why that happened, but at least they knew how to fix it! As always, let me know if anything seems amiss. Hopefully we're good to go, but we all know how technology can be sometimes...

It's the nature of the beast. But thanks, Cireth! I am actually really busy today but I know exactly what happened, just not why. I have contacted the host to look into it. Hopefully we will have an answer soon! (Gosh typing on a phone sucks!)

There were a few extra blips in the host's migration/upgrade process throughout the weekend, and one other quirk yesterday evening. Those are all resolved now, so hopefully, from here on out (plus the past 24-ish hours!), we're free and clear! As before, let me know if you see anything odd, but I don't expect there to be major issues at this point.

Yeah, it shouldn't be doing that. Until I know the cause, I don't know if the results are trustworthy or not, but I would suggest double checking just in case. I'm not sure if I'll have time to look into this one before tomorrow evening, but if I have a chance, I'll try! Thanks for pointing it out.

It should be fixed fully now (for the past hour, actually). Please let me know if you see any other weirdness.

There's a timezone issue on either the server or the database. That should be a quick thing to fix, at least! I've contacted the host again. That said, until it is fixed, this is a suitable workaround:

Sorry guys! I can immediately see what the problem is, but I have no explanation for why, since everything I can see shows no changes that would cause it. I have sent an email to support asking them what's up; we'll see what they say! Edit: They're looking into it. We've narrowed it down to part of the server settings not migrating properly, so once they get that fixed, we should be back in business. Until then (and/or tomorrow morning, whichever comes first!), it's going to have to remain broken, because making the changes needed to work around the settings problem would be significant, and I need to get some sleep! I'll update again in the morning once I determine the current status.

Just a head's up, I received notice from the host that they will be upgrading the hardware starting Friday night. They are not expecting any downtime, but in case anyone sees a blip, that's probably why!

I like anon editting (I used to do some cleanup myself, but gave up when I realized it'd been disabled, because I couldn't be bothered to make an account for the tiny changes I had been making), but as a compromise, does Wikia have an option to protect certain pages only, like Wikipedia does? Maybe during a release/event, you could make related pages (currently being released, new breed, etc.) non-anon, but leave the rest of the wiki open to anon editting, and reduce vandalism without dramatically reducing useful edits?

Interesting. I tried both the filter and the sort, and the results were the same (as they should be!). It's sounding like something did indeed go wonky with my scroll, because all of my Alt Black adults are listed in a single group, and they most definitely were not all from sitting hatchlings. In fact, I basically gave up even collecting Alt Blacks a while back, because all I ever seemed to get was sitting males (8m, 1f, 2009, 2012-2014) and curled females (2m, 6f, 2009-2010), and I was getting sick of the imbalance growing ever larger. So the data was supposed to have been saved. It does still beg the question, though -- if it got confused on my scroll, did it on others' as well? If it did, that could explain the seemingly huge imbalance in sitting vs curled adults.