Category Archives: hybrid elephant


the latest about aparajita:

no good news, i’m afraid. i’m down to my last two boxes of aparajita, and then i am COMPLETELY OUT… for retail sale.

(my “personal stash”, of around a kilo, is the exception, of course.) 😉

HOWEVER, i am cautiously optimistic. an email i sent on 12th april has JUST been responded to by mavana’s representative in india, a guy named arun, with whom i have dealt extensively, in the past… 15 to 20 years ago…

he didn’t respond to any of my direct questions regarding aparajita, he asked how i was getting along in these times of global pandemic…

the global pandemic is fine, and all that, but I WANT MY APARAJITA, GODDAMNIT!

and it’s not JUST for me: i’ve got two other retailers who are breathing down my neck for it, and, just a couple of months ago, i had to PREVENT some unknown miscreant person from swooping in and buying ALL my remaining stock, just prior to ravi shankar’s birthday celebration — the only reason he wasn’t successful is that the first of his two credit cards was declined, which gave me the chance to go in to the web site and make the changes necessary to prevent him from doing so again — so i KNOW the demand is out there.


since monday, 200608, i have gotten SEVENTEEN new incense orders, which works out to 3.4 new orders a day, in 5 days. 🤨

under ordinary circumstances, i get 3 or 4 new orders A MONTH. 😖

someone must have mentioned my web site on their podcast, or something.

also, it may be that someone mentioned my web site on a podcast about ravi shankar or the beatles, because by far and away the most incense i have sold since 200608, has been aparajita. now there are approximately 35 boxes left before i run completely out. 😒

ahhhh! now we find out…

my newly redesigned site uses the enfold theme, which has faulty (under certain circumstances) caching and optimisation routines, so we use lightspeed cache, which doesn’t have those (particular) faults, and works better (under certain circumstances).

except, last year, prior to my site being redesigned (when i was still using the avada theme), i was told (by SOMEONE) to disable lightspeed cache, because it had some sort of incompatibility with… something…

so, i went through the site redesign with a disabled lightspeed plugin. no problem, until i put in the enfold theme, and whatever circumstances that cause the caching and optimisation routines to fail, were happening, which was the cause of the first go-round.

turning on the lightspeed cache fixed the first go-round, but whatever incompatibility i was trying to avoid by having the lightspeed plugin disabled, took effect, which was the cause of the second go-round.

which was further confused by the fact that part of my routine for fixing the first go-round was good enough that it fixed the second go-round well enough that i didn’t find out about it until it was too late.

what i found out, today, via my web developer, is that the people who make the lightspeed cache and webhost python (my host provider) have their own battle going on: on webhost python’s servers (which include mine), the lightspeed plugin causes expired transients to multiply and duplicate. lightspeed says it’s python’s fault. python disagrees…

on the record…

OFF the record, python agrees that there is a bug in their system that they haven’t found yet… compounded by the fact that it was THEIR ERROR which caused the third go-round… 😠 but it’s not for me to say “i told you so”, especially with my already somewhat precarious position with this particular host provider…

and so, i’m caught in the middle. 😒

apparently, for the time being anyway, the plan is to disable the caching modules on both enfold AND lightspeed, keep an eye on the database (which hasn’t blown up since implementing this plan), clear the expired transients manually, and examine other options for a cache.


oy! why won’t this just go away?

at midnight (which was 3:00 in the morning, florida time), i got a message saying that the database was blowing up again. they said it was 183 GIGABYTES

because of the fact that i was asleep (thankfully), i didn’t actually read the message until 7:00 my time (10:00 florida time). i immediately logged into my web server, and discovered that the MySQL disk usage was lower than i have ever seen it before, which is to say 253 MEGABYTES

what this tells me is that there’s something else going on besides this whole “enfold-theme-not-caching-correctly” horseshit.

which is bad.

it also tells me that, whatever it is, we haven’t actually found it… we may have found another problem, but not the one for which we’re looking… yet…

which is bad, but not as bad as it could be.

it also tells me that, whatever it is that is going wrong, the cronjob that we put in place to solve the problem, works, REGARDLESS of the actual problem.

which is good.

but, when it comes right down to it, it is not good for me to be so stressed out about something over which i have very little control.

which is bad.

something has to be done. this is ridiculous.