Considered and affirmatively executed. And don’t spam me, bro. I’m probably behind the times, but I actually only follow people whose tweets I care to read, and actually read them. I don’t understand how people can legitimately follow 100+ people other than for “follower farming” for lack of a better term. There must be bots that under configurable conditions follow accounts and unfollow them X days later in the hope the user will follow them back and then not realize they’ve be unfollowed. People are just evil, I guess.
Not to confuse the crap out of you, but I think there may be two types of articles being posted that affect the “follow-up” and “new posts” email notification functionality. This article doesn’t have the “Subscribe” option near the top-right, but has both the “Notify me of follow-up comments by email” and “Notify me of new posts by email” options just below the editor. The editor here also doesn’t use plain text, so the issue may be related to when the posts were made relative to the forum cross-posting feature, if that’s what you have implemented. Let me know if you’d like to debug the site privately since it’s obviously in a state of transition. I need to work on Sylph anyway and my beer count is inversely proportional to how successful I’ll be at doing so. 🙂
Another tidbit for use in debugging or the process of elimination is that the articles (I’m assuming using the latest state of the site) with the plain text, BBCode editor automatically update the poster information to reflect their current account information (as opposed to being cached from their account state at the time of posting), while this article shows my two posts as “Sanctimonia” and “Boolean Dragon” respectively.
I can look into that. If need be, I can pseudo-merge accounts by deleting one. Or I can look at renaming one, or assigning it a nickname so that it looks outwardly the same.
I’ve got three accounts of my own, actually. One is for main admin, one is for remote edits, and one is for testing the user experience.
Not a big deal, just something I thought might help in the migration/modification. In debugging (game code in my case) the more known symptoms the easier it is to deduce the root cause.
If forum comments can’t be bulk-enabled for old articles, once enough new articles are posted no one will notice the discrepancy.
I like the new site work. I’ll check out the forums later to see how they jive with the comments on the articles. For now I absolutely have to try to get some work done on Sylph. I’ve been trying to get planetary atmospheres rendering properly in perspective (as opposed to faking it with orthogonal) and it’s been busting my moonstones.
It’s not that they can’t be bulk-enabled, strictly speaking. There’s a button I can press to do just that.
But I’ve a feeling that I’ll blow past the global PHP execution time limit on the server if I try and do that for thousands of articles and over ten thousand comments! Nor am I particularly keen on dialing up the global PHP execution time to something absurd, because damn but that’s a security hole.
So…I don’t quite know how to proceed. I might hit the button one day and see what it does. But I may just accept the imperfect solution and run with it. And then remember to implement the new commenting on ALL new articles, rather than leave stragglers like this.
Considered and affirmatively executed. And don’t spam me, bro. I’m probably behind the times, but I actually only follow people whose tweets I care to read, and actually read them. I don’t understand how people can legitimately follow 100+ people other than for “follower farming” for lack of a better term. There must be bots that under configurable conditions follow accounts and unfollow them X days later in the hope the user will follow them back and then not realize they’ve be unfollowed. People are just evil, I guess.
Not to confuse the crap out of you, but I think there may be two types of articles being posted that affect the “follow-up” and “new posts” email notification functionality. This article doesn’t have the “Subscribe” option near the top-right, but has both the “Notify me of follow-up comments by email” and “Notify me of new posts by email” options just below the editor. The editor here also doesn’t use plain text, so the issue may be related to when the posts were made relative to the forum cross-posting feature, if that’s what you have implemented. Let me know if you’d like to debug the site privately since it’s obviously in a state of transition. I need to work on Sylph anyway and my beer count is inversely proportional to how successful I’ll be at doing so. 🙂
Yeah, I forgot to enable forum comments for this post. Oh well…
Another tidbit for use in debugging or the process of elimination is that the articles (I’m assuming using the latest state of the site) with the plain text, BBCode editor automatically update the poster information to reflect their current account information (as opposed to being cached from their account state at the time of posting), while this article shows my two posts as “Sanctimonia” and “Boolean Dragon” respectively.
I can look into that. If need be, I can pseudo-merge accounts by deleting one. Or I can look at renaming one, or assigning it a nickname so that it looks outwardly the same.
I’ve got three accounts of my own, actually. One is for main admin, one is for remote edits, and one is for testing the user experience.
Not a big deal, just something I thought might help in the migration/modification. In debugging (game code in my case) the more known symptoms the easier it is to deduce the root cause.
If forum comments can’t be bulk-enabled for old articles, once enough new articles are posted no one will notice the discrepancy.
I like the new site work. I’ll check out the forums later to see how they jive with the comments on the articles. For now I absolutely have to try to get some work done on Sylph. I’ve been trying to get planetary atmospheres rendering properly in perspective (as opposed to faking it with orthogonal) and it’s been busting my moonstones.
It’s not that they can’t be bulk-enabled, strictly speaking. There’s a button I can press to do just that.
But I’ve a feeling that I’ll blow past the global PHP execution time limit on the server if I try and do that for thousands of articles and over ten thousand comments! Nor am I particularly keen on dialing up the global PHP execution time to something absurd, because damn but that’s a security hole.
So…I don’t quite know how to proceed. I might hit the button one day and see what it does. But I may just accept the imperfect solution and run with it. And then remember to implement the new commenting on ALL new articles, rather than leave stragglers like this.