Category Archives: hybrid elephant

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.

oh, but it couldn’t have ended there, now, could it?

and the answer is, a big, fat, OF COURSE NOT! 😒

i woke up this morning, and couldn’t log in to my web site… at, like, SEVEN in the fucking morning, i was wide awake because i couldn’t log in to my web site.

at NINE, the web designer gets back to me. he can’t login either. apparently the host provider has disabled the config file that makes everything work — i login using SSH, and there’s the file… everything LOOKS okay, but… the host provider apparently did SOMETHING to my web site. as far as i can tell, everything works, sort of, until you get one or two pages deep, at which point it gives me a “unable to connect to database” error.

😠

so, i file a ticket with the host provider. a couple hours later, (all the while, i’m sweating bullets) they get back to me, apparently, the database blew up AGAIN. they disabled the config file so that nobody could use the web site, because the database was growing by gigabytes A SECOND.

😠😠

eventually (seriously, they took most of the day to UN-disable the config file), the web designer went in and turned off everything having to do with the built-in, screwy, does-not-work, enfold caching and optimisation routines, turned OFF “store transients”, and set a cronfile to delete three rows of a table in the database, every hour.

😠😠😠😠‼‼‼

this better be the last of it for a while, because i’m just about ready to throw in the towel.

database update

the database is fixed. 😌

what happened? that’s complex.

recently, i had my web site redesigned. the new design uses the “Enfold” theme, which uses a lot of what they call “transients” to maintain the look and feel of the site, regardless of the platform on which it’s being viewed. “transients” are sort of like cookies, except that you can’t opt out of them, and they don’t contain any personally identifying information. some of these “transients” expire immediately when a person leaves the web site, and others persist, for a few minutes to several days. they persist on your computer AND on my server… in the one of the tables in the database…

the “Enfold” theme has automatic caching and garbage collection routines that are supposed to handle these expired “transients”, but, because it’s a wordpress theme, it doesn’t do all the jobs very well… or, sometimes, at all… which is why i also use a caching plugin that actually, you know, works ALL the time, and not only some of the time… 😒

except that, for some reason, prior to my site upgrade, “someone” (and i have yet to identify who, but it was either my web designer or my host provider) recommended that i disable the caching plugin, because of some issue with the new version of wordpress… or something like that… as i said, i don’t remember. i distinctly remember disabling the plugin on someone’s recommendation, i just don’t remember exactly who, when or why. 😖

one way or the other, my caching plugin was disabled, which meant that, when i installed the new theme, it was relying on the not-working-the-way-it-should, internal cache… which, basically, didn’t work, causing the table in the database to expand beyond my disk space allocation. 🤯

it didn’t show up in my cPanel because i wasn’t looking at the SQL disk space, which is “below the fold” of my browser, and i just didn’t scroll down far enough to see it. 😕 during the nightly automatic backup, it was overwhelming the server for everybody, not just me. i had to pay my web designer for two days of poking through piles of arcane SQL code and deleting bits and pieces of it. it was not fun.

the solution was to enable the caching plugin(!), and to install a “transient manager” plugin, so that i can delete the expired transients from the wordpress dashboard, and not from the SQL database,… which requires A LOT more “knowing what to look for” and “knowing how to delete stuff without damaging other stuff” than i have on board, personally.

aparajita

ravi shankar’s 100th birthday was the 7th of april.

ravi shankar’s favourite incense was aparajita.

at this point, i believe i am responsible for THE ONLY retail store in the united states which sells aparajita, online.

i am aware of several local retail stores which sell aparajita in their store, but not online. i’m fairly sure that there are others, in other cities. i am also aware of at least two retail stores (i won’t give them the satisfaction of a link) who say that they sell aparajita online, but they’re either perennially “out of stock”, or flat out rip people off, and hope that nobody notices. i have no doubt that there are others of that sort out there, as well.

recently, i had to prevent a guy from los angeles from buying ALL of my aparajita. he said he was working with ravi shankar’s family and the ravi shankar foundation on a special 100th birthday celebration. problem was, his credit card failed stripe, and the order was automatically cancelled… and then i learned how to set an item limit, so that people like him can’t just swoop in and buy all of my stock…

i’ve actually had this happen before: a few years ago, i stocked an incense that was made for the theosophical society by shroff agarbathies, that shroff called “Adyar Meditation Incense”, but the theosophical people called it “Leadbeater Incense”, and it was fantastic, rose, agar, and sandalwood, and i was the ONLY agarbathiwala outside of the theosophical society that carried it… but then the government of india put some sort of restrictions on the export of sandalwood, and shroff stopped making it. i found out about it when someone from florida (i suspect a theosophist, actually) bought TWO KILOS of adyar meditation incense, in 100 gram packages, and when i tried to order more, i couldn’t.

fortunately, i held back some for my own, personal “stash”, but since then i have been very wary of people who buy a huge quantity of one particular incense.

and, the fact is, i’ve been having some trouble locating a supplier of aparajita… AGAIN… 😒

my contact at mavana stopped responding to my emails, the mavana web site died, both of the suppliers (one in florida, one in new york) that carried it have gone out of business, and all of the other suppliers i’ve talked to say that they won’t carry it because aparajita smells too “medicinal”, whatever that means… 😟

my only hope is the fact that, in india, it is still popular enough that it’s being “copied” by at least two incense manufacturers… they haven’t got the recipe for the incense, but their labeling and package artwork is a direct rip-off of the authentic aparajita.

so, i guess i may have to actually travel to india eventually… 😒