Blogging–by me, anyway–will be almost non-existant till the very end of March or early April. The move to the Davis area is upon us at last!
Those who have the keys to the virtual orchard are invited to plant (as Alan did earlier today). I will be checking comment threads now and then; if your comment lands in the moderation queue, it may take longer than usual for me to spot it and clear it.
Twice this week, we have had the return of orchard gremlins. It had not happened for a while, but now and then the blog software automatically re-sets all comments to off, and tells readers they must be “registered and logged in to comment”.
This is not a setting I am doing1; I have no idea why it happens, and no one ever needs to register or log-in to comment at F&V. Whenever I catch this having happened, I will reopen comments.
I also never close old threads. F&V works best when readers remember and locate an old thread and post a comment when something new has happened that is relevant to the thread.
There will be times now and then when I am unable to check for a day or two to make sure that comments are, in fact, open.
Thank you for you patience and for your comments.
First time commenters will have their comment put in the moderation queue until I can confirm it. [↩]
The blog seems to have taken Shabbat off. And why not?
For some reason, readers could not post comments yesterday. When I went into the Word Press “dashboard” this morning, I found that the option “users must be logged in to comment” was checked. I had never checked it.
We’ve had this problem before, and I have no idea how to prevent it. But I was able to uncheck the setting, and everything should be open for business again.
No comments had appeared for a couple of days, at least. And not even spam. That always makes me suspicious. Sure enough, the settings for “users must be registered and logged in to comment” and “administrator must always approve a new comment” were checked again. I did not check them.
So, even with the changing of passwords, upgrading to new Word Press, and stripping out of some suspicious code, something is still amiss.
I should know that when even the spammers stop “commenting,” as they did sometime last week, something is wrong.
I just checked the Word Press settings and found that the box that says that one must be “registered and logged in” in order to comment was checked. I did not check it.
How can a setting check itself? The answer, the previous of several times this had happened, seemed to be a hacker. I changed my password and made other fixes (with help of some of this blog’s greatest supporters). And yet this has happened again.
As of the moment, all recent posts should be open for comments. Older ones are still automatically shut down. I hope to insert some code in the near future that will automatically re-open them.
As always, thanks to my readers for their support and patience as we work out the bugs.
Bugs can be the downfall of any orchard, including the virtual kind.
I am in the process of updating Word Press, which powers this blog.
Some features may be disabled for a bit.
Update (to the update): The new version of Word Press is installed, but at the moment you need a direct link to get to any post other than this one. This process may not be complete today, but please be patient.
Further update: It seems things are back in order. (Thanks, Steven!) There remain various other things to be done before the virtual orchard is completely back in business.
Espen sends this note, which may be of use to folks trying to get around the latest spontaneous combustion of the virtual orchard:
To access comments, chop off the last bit of gibberish which as of now is included in the links. It seems all posts have gotten new addresses, namely date, title, and something like the following:
This needs to be taken off to get to a post. Of course, most of them will say that the “soil has been over-planted”, including the latest update on comments (Blog problem update). Also, fruitsandvotes.com now leads directly to that last post.
Again, I have no idea why these things are happening; I have not tinkered with settings or installed any new plug-ins.
FURTHER UPDATE: It looks as if the standard links are working again, as of Friday mid-afternoon (Pacific time zone in the USA). It wasn’t anything I did, that’s for sure. So, if it can fix itself, it could just as easily break itself again…
It seems that links within F&V work so long as “/blog” is in the URL, but not without it. Up to now, URLs have worked with or without “/blog”.
URLs for navigating around the blog do not routinely have /blog in them, but adding them gets you to the desired page–including the comment form.
For instance, if you wanted to comment on the recent entry on Afghanistan’s elections, the default for the comment form is http://fruitsandvotes.com/?p=4274#respond. This will not work. But the following modified URL will open up the comment form: http://fruitsandvotes.com/blog/?p=4274#respond
If by my laws you walk, and my commands you keep, and observe them,
then I will give-forth your rains in their set-time,
so that the earth gives-forth its yield
and the trees of the field give-forth their fruit.
--Vayikra 26: 3-4