Thanks so much, Ismael — glad you’re on the trail. No need to keep the modification on the dev site — I’ve downloaded that file so I can post it to the live site, if I want to implement that temporary fix for the client. Thanks again and Happy New Year!

Sorry, I think wpengine support may have deactivated the temp login plugin when they were troubleshooting. It should be working now, but here’s an actual user just in case. They also said the max on the hosting is 512, so even if you up it to 1024 it limits it to 512. But I run a bunch of Enfold sites with them and never had a memory issue like this — we shouldn’t have to up it that high, right? Maybe you’re just trying to do that temporarily to troubleshoot? Regardless, it doesn’t sound like they can do that for us, but I can double-check if you want; lmk. Thanks again for sticking with this!

Thanks, Ismael — sure thing, details in the PC below — and lmk if you need me to reach out to wpengine support.

Thanks, Rikard, but I increased the memory to wp engine’s max of 512MB, ran another test, and the issue seems to persist. The only things I see in the log since doing that are what look like my two times clearing the wp engine cache (once after increasing the memory to 256 and once after bumping it up to 512 — see below or https://crcamericadev.wpenginepowered.com/wp-content/uploads/crcamericadev-logs-2025-12-16T19_28_03.csv). Any other ideas? I’m including the temp login again in the Private Content field, in case you want to poke around. Thanks again!

{
“installName”: “crcamericadev”,
“environment”: “DEV”,
“type”: “error”,
“date”: “2025-12-16T19:24:37.000Z”,
“severity”: “notice”,
“client”: “24.24.164.87:0”,
“message”: “wpe_cache_plugin:info: event=clear-all-cache, referer: https://crcamericadev.wpenginepowered.com/wp-admin/edit.php?post_type=page”,
“uuid”: “8b6d00fd-38e3-44d3-903b-9166dbc7f21a”
}

{
“installName”: “crcamericadev”,
“environment”: “DEV”,
“type”: “error”,
“date”: “2025-12-16T19:17:43.000Z”,
“severity”: “notice”,
“client”: “24.24.164.87:0”,
“message”: “wpe_cache_plugin:info: event=clear-all-cache, referer: https://crcamericadev.wpenginepowered.com/wp-admin/media-new.php”,
“uuid”: “a746b3bf-7e06-48bd-994c-ce6d04e249d2”
}

min-height! why didn’t I think of that?! ;).

Thanks again, Ismael — that worked for desktop but not the phone, for some reason — removing the first class seemed to make it work for both, and I only needed about half the height:

.tribe-events-c-subscribe-dropdown {
   min-height: 175px;
}

Thanks again, as always!

Hmm, just when I thought I finally had that stuff wired ;). OK, thanks anyway! Feel free to close the ticket.

Awesome — sorry to pick faves, but you’re the best, Ismael ;)

Ah, I see, ok, thanks. And what about the flipboxes on desktop, further down on the home page of https://tortoise-tracks.org/ — I don’t suppose there’s any way to make those accessible via the focus? I mean, I can see the focus is indeed cycling through the links in those, but I don’t supposed that’d be enough to meet the accessibility standards, eh? Should I open a separate post about that?

Thanks again for the detailed explanation. Looks like the css “content” property is pretty well supported — https://caniuse.com/mdn-css_properties_content — good enough for me, I think! :)

Perfect, awesome, thank you so much! I also added my own class to the columns and added some css to adjust the height to taller than the max 500px allowed in the options (just in case this helps anyone else):

.taller .avia-fold-unfold-section .av-fold-unfold-container.folded {
    max-height: 1000px !important;
}

Thanks again!

Thanks Guenni — that’s cool — Do you know how to get the categories to show in the same line as the date (like on the single posts) or below the date?

OK, thanks anyway for trying all those things!

Thanks, but the code you posted there (pasted below) actually seems to be for the solution in this thread, so I think continuing here makes more sense. This is the thread asking if it’s possible to break the overlay/burger menu into columns — the other thread is asking if the 3-column mega menu can span the full site width. The code below refers to the burger menu, so I guess continuing here makes more sense, no?

Your code seemed to target one level too deep — maybe because I hadn’t actually changed this nav to a burger menu, yet (it was still a regular/text nav, set as a mega menu with everything nested under a “menu” button). So I switched to the burger and removed the last ul in your 2nd rule. Then I added a float: left, to get the lis/columns to layout horizontally. But the 4th column was sort of tucking up under the 3rd, so I added a “break” class to the 4th menu item and added a rule to clear: left on that item.

That seems to get me close enough — I think now I can just play with the theme options/styling and refine the css to make everything look better (and of course disable these columns on the phone version, since three columns won’t work there) — so, thank you! Unless you have any other comments, feel free to close this thread.

Your code:

#av-burger-menu-ul li.menu-item-86 {
  display: flex;
  flex-wrap: wrap;
}
#av-burger-menu-ul li ul {
  display: flex;
  flex-flow: column;
  flex-grow: 1;
  width: 33%;
}

My version:

#av-burger-menu-ul li.menu-item-86 {
  display: flex;
  flex-wrap: wrap;
}
#av-burger-menu-ul li.av-width-submenu {
  display: flex;
  flex-flow: column;
  flex-grow: 1;
  width: 33%;
  float: left;
}
#top #wrap_all #header #av-burger-menu-ul > li.break.av-active-burger-items {
    clear: left;
}

https://dtpc.wpenginepowered.com/

Thanks, Rikard — I get that; I just don’t understand why we’d have to subtract from the max height, and why it seems necessary to subtract more in order to get more scroll — like, why did I have to change that number from 20 to 120? But again, I’m just curious — it seems to be working, so don’t feel obligated to answer.

Sorry about that — here you go…