Forum Replies Created

Viewing 15 replies - 1 through 15 (of 32 total)
  • Thread Starter cmerrick

    (@cmerrick)

    It took a while to get back to this but I tried adding this code to wp-config.php and it didn’t seem to do anything. I changed the numerical values, and tried clearing my cache before reloading the site, but there was just no effect at all.

    Also it’s kind of weird that this has to go in wp-config.php instead of being able to put something in functions.php, but for now I’d settle for just getting it to work.

    Any thoughts on what’s wrong?
    Thanks!

    Thread Starter cmerrick

    (@cmerrick)

    That plugin did what I needed, thanks very much!

    Thread Starter cmerrick

    (@cmerrick)

    Cool, thanks for the info!

    Thread Starter cmerrick

    (@cmerrick)

    Hi Judith, thanks for writing back but what I mean is can I change the pixel values of the breakpoints? They default to something like tablet view at 976px and mobile at 767 (roughly). What I want to do is change the tablet breakpoint to, say, 1140px. I interpreted “Ability to modify breakpoints” as being able to do this, but I can’t find anyplace in the interface for it.

    Thanks!

    Thread Starter cmerrick

    (@cmerrick)

    Hello everyone, OP here letting you know I’ve been working with WP Stackable support on this issue and we have found the cause. From their most recent email to me:

    “You’re right that the issue is with the Content Vertical Align setting, and it seems to happen with any setting (Align Top, Align Center, Align Bottom). We can confirm that this is what’s causing the issue as we were able to replicate it on our end as well. Apologies for missing this and for taking some time.

    We informed our dev team already, and they also filed this issue and marked it as priority. We will be working on a fix for this to release in the upcoming update, but for the meantime, you can turn that setting off first so that the issue won’t persist.”

    Turns out the bug is in the columns settings, not in the Accordion block at all. If you experience this problem look in the individual column “style” settings for Content Vertical Alignment and turn off any alignment setting (at least until the issue is fixed).

    Thanks to the WP Stackable for looking into this and keeping me in the loop.

    Thread Starter cmerrick

    (@cmerrick)

    Thanks for the response. It would be ideal if the Convert to Container function could implement the tablet settings I’d already chosen, rather than have to manually do the same correction again and again for every 2-column set. But it’s good to know how to do it.

    The default row-padding in the Container I find completely baffling. At the very least, something converted from Advanced Columns (where there was no such setting) should default to zero.

    I understand you can’t test for every possible scenario, but “I have a deprecated but totally normal two-column layout that I need to convert to a Container” does not strike me as an edge case.

    Thanks again for responding, I do appreciate it.

    Thread Starter cmerrick

    (@cmerrick)

    Ha, you’re right, I’ve dodged that. I had to use Divi once and it put me off builders forever. Good point on the skills, half my problem is now I’ve gotta learn a new interface to do the same thing, and who’s got time for that?

    If ACF ever screws me, I’m just gonna fold up shop and try raising alpacas instead.

    Thread Starter cmerrick

    (@cmerrick)

    I’m hoping that as well!

    You’re right it’s a risk we take but in 15+ years of WordPress design I’ve never had the rug pulled quite like this. I have to wonder, if they’d been charging for it all along, would they have released something that breaks this many sites? I would have paid for a Pro version. And then I’d be even more angry 🙂

    But I will be keeping as many sites on version 1.x as possible until this is resolved in the hope that genuine backwards compatibility gets added to a future release.

    Thread Starter cmerrick

    (@cmerrick)

    Thanks for the reply CGS, that does help some but honestly they’ve lost my trust at this point. I have so many blocks I have to convert now! I’m hoping this gets fixed anyway, for now I’ve notified all of my clients to not update from 1.x until they hear back from me.

    Thread Starter cmerrick

    (@cmerrick)

    Hi, I checked the same site and reactivated Blockmeister, and it works correctly now. As part of the stuff I was doing before, I turned on auto-updates, so it was running 3.0.5. But I definitely remember updating to the latest version when I saw the error (I updated WooCommerce as well) and still getting the error; now I wonder if there was a caching issue or something. At any rate, the current version works.

    I have another nearly identical site that still had Blockmeister 2.0.8 installed, and I did get the critical error there, which went away after I updated it.

    So I guess nothing left to do, thanks for looking at it.

    Thread Starter cmerrick

    (@cmerrick)

    Update: It appears the problem is related to the Admin Menu Editor plugin. When the plugin is active, the links appear as they should. When it’s deactivated, the CPTM link disappears for both me and the client, and the Staff custom post type link disappears for the client only. (The Staff CPT is set to Public -> True, Show in UI -> True, and Show in Menu -> True).

    I have submitted a ticket to the AME developer for guidance.

    Thread Starter cmerrick

    (@cmerrick)

    Thanks for the reply! I ended up doing it the other way around, since I’m 99.9% sure we won’t be using the description on the front end. I explained what I did to the next poster in this support forum, since they’re trying to do the same thing I am 🙂

    This is exactly what I’m trying to do (I’m one post back in the support forum). What you need to do will depend in part on what your category names are. If your category names have spaces in them, as mine do, it will be hard to use them. So what I did was use the category descriptions to hold a class name. E.g., the category may be “Good Canine Citizen Workshop” but the description is just “workshop”. Then I used the event description to put the category into the calendar event link as a class. To do that, go to Settings –> Calendar and in the last field, called “Full calendar events format” (assuming you’re using the full calendar) put this:

    <li class=”#_EVENTCATEGORYDESCRIPTIONS”>#_LINKEDNAME

    If your categories are just one word each, you could do

    <li class=”#_EVENTCATEGORIES_CSS”>#_LINKEDNAME

    If you do that and check your calendar page code, you’ll see your event links look like this:
    <li class=”yourcategory”><a href=” etc….

    Then you can target .eme-calendar-table li.yourcategory a in your css, e.g.
    .eme-calendar-table li.yourcategory a { color: #009; }

    You may have to write a more specific rule depending on the rest of your code.
    Hope that answers your question!

    Thread Starter cmerrick

    (@cmerrick)

    I could but we may want to display category names on the front end, so that would look weird. Since the slug is by definition unique, machine-friendly, and devoid of spaces, it seems like a better choice for a CSS hook.
    Thank you for the reply!

    Thread Starter cmerrick

    (@cmerrick)

    Thanks! I was looking in the “documentation” area of the site. This is super helpful, I’ll be sure to point my clients at this article as an explanation of how GDPR may affect their site.

Viewing 15 replies - 1 through 15 (of 32 total)