any thoughts on why? Sorry for delayed responses; getting ready for work.

: At work here, so I know what you mean. The filesystem seems to be in place: http://www.subetalodge.org/cron/update-prices-last-item is there along with the forums, but I can't get in through cPanel either.

It looks though like someone's working on the SSL certificate -- when I look at it, I get this:

Issued On Friday, April 7, 2017 at 5:38:02 AM Expires On Saturday, April 7, 2018 at 5:38:02 AM

[edit] Following up -- Someone was in this morning and rewrote the .htaccess file and the entire contents of cgi-bin. Do you know anything about that?

[edit]Following up some more -- the cron stopped running just before 3am this morning. Has someone been working on Subetalodge today?

I don't would that be related to the ssl work? I KNOW SO MUCH ABOUT THIS STUFF! How are you seeing this?

And how recent of a backup do we have?

Got to leave but will be at work and back online around 11

I can get in to the cpanel

[edit] I've got the main page loading by bypassing memcache. There may be some features that don't work with memcache bypassed.

[edit]10:37 am: Yup, there's a problem. The item detail page won't load.

[edit]10:42 am: I've bypassed memcache on that page (this will make the site run more slowly, but it's better than not running at all.) Unfortunately, I'll be in class from 11:00-2:15, so if there are any other problems, it'll be a while before I can get back to them.

[edit]10:57am: I think they're working on the SSL -- the new certificate is by Let's Encrypt, which is the place I recommended. Doug said they'd need to upgrade some things first, and I'm guessing that one of the upgrades interfered with memcache. (Memcache, by the way, keeps a track of frequently-accessed items and makes then available outside the MySQL database, reducing load on the server. That way, for example, when a brand-new item comes out, and hundreds of people are trying to toggle that item in their collections, we wouldn't have to hit the database every time one of them tried to load the item page. With memcache down, we're hitting the database every time, which will slow things down when new items get released, but it's not fatal to us while we try to figure out what's gone wrong.)

: I'm in the cPanel too -- what I've been doing is going through the code a few lines at a time and verifying that everything's loading.

Here's what I notice -- and you can try it yourself if you want:

Go into /public_html/includes/connect.php

and look where it says

$cache = new Memcached; $cache->addServer('localhost', 11211);

Put a line in front of that that says

echo "begin!";

and one after that says

echo "end";

Then visit Subetalodge. You'll see the 'begin' message, but not the 'end' message, which tells me that memcached isn't loading correctly and the script is crashing at that point.

If it looks like they are still working on it then we should probably not change anything for the time being

: I had already changed a few things before I figured out what was going on, but all the memcache code is still there -- I just commented it out in places, so that we can put it back in when the time comes.

The site seems to be working fine for me now so I'm assuming whatever y'all were doing fixed it (I tried to understand but I really and truly do not haha)

: Short version -- SubetaLodge was using a third-party service to speed up the more frequently-accessed parts of the site. Something caused that service to go down last night. I've commented out the code that used that service in order to get the site back up, but it means that we're not getting any speed benefits from it anymore.

Ah damn =/ I'm assuming it was an issue on their end right? So nothing much we can do until they sort it?

Did you see the latest email?

: Just answered it.

thanks. just want to get this (#&$HASD(@$ fixed. argum!

Also, I am ready to be not at work anymore

I'm doing what I can on my end -- most users shouldn't notice that we're running at reduced capacity right now.

Oh! Oh, no! I know that you are! I'm sorry! I didn't mean to imply that you aren't! Forgive me, please.

: That's okay -- I knew what you meant.

So, where are we on things getting fixed up? Are costume trunks all sorted?

: Cron is running again; memcache is still out. Profile widgets are working again.

: My understanding is that costume trunks are done. With vast, tremendous appreciation to everyone who slogged through that chore.