Jesse Owens

Hi Anne-

Thanks for reaching out! The easiest way to accomplish this is to simply hide the metadata using CSS.

Navigate to Customize > Advanced > Custom JS & CSS and paste this line into your Custom Theme CSS:

.entry-meta { display: none; }

That will hide it from your visitors, but it will still show up in the source code and be visible to search engines (this is usually good for SEO).

If you’re interested in modifying that PHP code, you’d need to set up a Child Theme for Resolve, and then override the pluggable function boldgrid_posted_on in the Child Theme’s functions.php file.

If you’re interested in using a theme that gives you control over your Post Metadata without using any code, I recommend checking out our Crio WordPress Theme for Business, which includes controls to remove the Author Byline, Date, or customize the metadata to your preference.

Hi Andrew-

I can spot a few things you can do to improve your background image on mobile devices.

First, I’d recommend editing your source image to remove this white gap at the top of the image:
.

Next, one reason you’ve found a few different answers for different people trying to solve this issue is that iPhone’s Safari in particular does not support the “Cover Page” size very well, and different CSS tricks work best for different individual images.

The technical reason for that is because iOS Safari uses the full height of the entire webpage to determine the “cover” size, rather than the height of the phone’s viewport, which results in the background image looking extremely zoomed-in. You can see the difference side-by-side here:

My favorite solution for this tricky issue so far is the following Custom CSS, which makes sure that the image is the right size on mobile devices, as well as centered:

@media (max-width: 991px) {
    body.custom-background {
        background-size: auto !important;
        max-height: 100vh;
        background-position: center top !important;
    }
}

By using the max-height: 100vh; rule, we make sure the image stays at 100% of the “View-height.”

Hi Andrew-

Thanks for reaching out! I’m sorry to hear about the frustration trying to fix that left-side gap.

It looks like you’ve got a negative margin set up on your logo in your Customize > Site Title & Logo > Horizontal Margin setting. When that negative margin is used together with a Right-to-Left font, it causes that gap.

I’d recommend setting that back to 0 to avoid this issue.

Hi Barbara-

Thanks for reaching out, we’re happy to help you change your menu color.

I checked out your site, and it looks like you’re using the Above Header menu position. Because of that, the code to change it is a little different than the Primary Menu location.

Navigate to Customize > Advanced > Custom JS & CSS and paste this line into your Custom Theme CSS:

.palette-primary .secondary-menu li a { color: #5e17eb !important; }

Hi Todd-

Since your WordPress website is hosted with one of our premium WordPress Hosting partners, you can hide that link in your Customize > Advanced > Footer Settings menu.

If you don’t see the option to hide the Special Thanks link, make sure that you’re using your Premium BoldGrid Connect Key from InMotion Hosting. Log into your InMotion Account Management Panel (AMP), and and navigate to Install BoldGrid > I already have a WordPress Site > Download BoldGrid Plugin and you’ll find your Premium key.

Once you have your key, head back to your WordPress Dashboard and navigate to Settings > BoldGrid Connect > Change Connect Key and paste your premium key into the field there.

Hi Dan-

This is happening because whenever the visual editor is initialized, it runs a scan of all the content you entered into the Text editor and checks it for “valid” HTML markup, sanitizing elements that aren’t included in the HTML5 standards.

Since your custom <dpc> tag isn’t a standard HTML tag, it strips them out. This is built into the TinyMCE editor in WordPress, not specifically the BoldGrid Post and Page Builder. I can think of two ways you can solve this.

First, you could solve it with pure CSS. I checked out your blog, and it looks like you’re mainly using the drop-cap on the very first letter of each post. If that’s consistent, you could accomplish the same thing with the following Custom CSS (I copied these styles from your <dpc> element):

body.single-post .entry-content p:first-of-type:first-letter {
    line-height: 33px;
    font-size: 50px;
    font-family: Georgia;
    color: #222222;
}

This code targets:

• Just blog posts (not pages) with the body.single-post class
• Just the post content with the entry-content class
• And finally, the first letter of the first paragraph, with the p:first-of-type:first-letter pseudoclass.

If, on the other hand, you’d like to be able to use your <dpc> tag in more places throughout your posts, you can add it to the allowed tags for TinyMCE. This will take a little bit of custom code. I recommend using the Code Snippets Plugin to manage custom code snippets.

Once you’ve installed the plugin, you can use a filter like the one found on this StackExchange Post to add the tag:

add_action('init', function() {
    global $allowedtags;
    $allowedtags['dpc'] = array();
});
add_filter('tiny_mce_before_init', function($a) {
    $a['extended_valid_elements'] = 'dpc';
    return $a;
});

Hi Kevin-

Thanks for reaching out! I’m sorry to hear about the problem with your menu not being clickable. I updated the title to your post to say “clickable,” because the word “responsive” generally means “not mobile-friendly” in web design terms.

It looks like what’s going on here is that the top row of your homepage has a large negative margin, which effectively puts it “on top” of your menu, preventing your users from clicking it.

In order to fix that, edit your homepage, and look for the yellow Edit Row icon (because of the negative margin, it will show up a little ways above your page content. Click on Advanced Control, and then Margin.

Here, you’ll see that the top margin is set to -89 Pixels. Change that to 0, and your menu will work properly:

Hi Richard-

Thanks for reaching out, I’m sorry to hear about Comodo’s ModSec WAF rule affecting your site.

The first thing about this error log that jumps out to me is that it matched “-C” with a font (.woff) file. I checked your website’s file against the current version of that font asset and I can confirm that they’re identical, so your plugin files haven’t been modified or compromised.

Since you noted that your website is running PHP 7.4, and the vulnerability that this rule is checking only applies to PHP 5.4.2 and lower versions, my first instinct would be to disable this rule for your site.

You can do this by adding the following line to your .htaccess file:
SecRuleRemoveById 220030

Your web host might also be able to help disable that rule, since most modern web hosts don’t include PHP 5.4 in their shared hosting platforms.

Hi Susan-

Thanks for reaching out! I’m sorry to hear you no longer need your subscription.

This is a public support forum, so we can’t change or discuss your subscription or billing here, but you can easily find out and cancel your renewal directly through your WordPress Dashboard, in the Performance > Support > Billing section, or by contacting our billing team directly.

Hi James-

Thanks a lot for the clarification, I see what you mean now that the Label for the variations was the light color.

Here’s a Custom CSS rule you can use in your Customize > Advanced > Custom JS & CSS menu:

.woocommerce div.product form.cart .variations label {
    color: #333;
}

The color #333 is based on the text in the paragraph just above the selection box, but you can change that according to your taste. Once you have that CSS rule in place, you can change your background color back to white.

Hi Gerard-

There isn’t a BoldGrid theme that would accomplish this out-of-the-box, but you could likely create it with any of our Themes, put together with using Anchor Links together with a plugin like Easy Smooth Scroll Links.

Hi Grace-

The extra space is actually coming from your site’s “Tagline,” or Site Description.

When you have a logo enabled, as you do, the tagline is made invisible, but it’s still there for SEO purposes and for users of accessibility devices like screen readers. Since yours is rather long, it takes up a lot of vertical space on mobile devices (again, even though it’s invisible).

Here’s one way you can fix this. Navigate to Customize > Advanced > Custom JS & CSS and paste this line into your Custom Theme CSS:

@media only screen and (max-width: 767px) {
    h3.site-description.invisible {
    font-size: 0px;
    margin: 0px;
    }
}

Hi James-

Checking out your site, it looks like you may have already solved this issue over the weekend? When I check out variations, for example the wine option, it looks correct like black-on-white text.

Did you already solve this, or am I looking at the wrong area?

Hi Shawna-

Sorry, there was a typo in that last post that didn’t let it finish.

Right now, in the link for your button, you’re pasting the embed code from JotForm, not a link to the form. It’s in a <script>…</script> element, which won’t work as a button. You’d paste that into your page if you wanted the form to be embedded on your page, not link to it externally.

Putting that script into a button link would probably explain a lot of the weird behavior you’ve been experiencing as well.

Look for the Direct link of your form option when you’re logged into your JotForm account:

Glad to hear it, Lotte! Our developers are working on getting that bug fixed once and for all, and it should be updated shortly.

Hi Alexander-

Thanks for reaching out, I’m sorry to hear about the issues using W3 Total Cache and Elementor.
From what you’ve described, it sounds like Elementor’s CSS assets aren’t being added to the Minify Cache. One solution for this is to exclude Elementor’s CSS files from minification, by adding them to the Never minify the following CSS Files in your Performance > Minify > Advanced.

Hi James-

It should be safe to re-enable Minify in your General Settings menu now that you’re set to combine only.

Hi Kris-

Thanks for reaching out, I’m sorry to hear about the issues with Post and Page Builder.

Most of the time, the behavior you’re describing comes from a JavaScript error, most often caused by a conflict with another plugin. I checked out your site, and I didn’t spot any from the front-end that conflicts with Post and Page Builder, although I couldn’t test out the Mixone theme or the Mixone Toolkit plugin since they’re commercial.

One way to troubleshoot would be to deactivate your plugins one-by-one, starting with those you might have installed at about that one-week mark, and see if the issue continues.

Another thing that might help us to narrow down the cause would be to check your browser’s error console while you use the Post and Page Builder. If you can copy any errors you see there and paste them here, we can take a closer look.

Here’s a quick video showing you how to check the error console.

Hi Thierry-

Thanks for letting us know about that bug! I’ve let the developers know so that we can get that fixed as soon as possible.

Your CSS is almost right, you’ll just need to add an !important flag to the rule:

body h1 {
font-size: 24px !important;
}

Hi James-

Thanks for reaching out, I’m sorry to hear about the issues with your product images.

I checked out your site, and your product pages don’t look the way that they normally do in the Hydra theme. Normally, a smaller image would be displayed, with the 600-pixel full size only shown as a “preview” when the user hovers over it.

I’m curious if the normal image display is being affected by your Minify settings in W3 Total Cache. Can you disable minify temporarily in your Performance > General menu, and see if that makes your product page look correct? That might also explain the behavior you saw when the Customizer changed, but the front-end of the website did not, if the cache had not been cleared when you checked the page.