Your comments

Thank you for contacting us and I am sorry to hear that there were some problems getting the Connect coins correctly assigned to your account.  I spoke to the team at InMotion and have adjusted the coin balance of your key to the expected amount.  The coins are assigned to the Connect key ending in '8e1e' and any website that is using that key should show the correct balance.

We apologize for any inconvenience this has caused you and please let us know if there is anything else that we can do to help!

Thank you for contacting us and providing your feature suggestion!

I have created a GitHub issue with our development team to review this improvement for an upcoming release and you can subscribe to that thread to get updates on this as soon as they occur.

Thank you for helping us improve BoldGrid and please let us know if you ever need anything in the future, we are always happy to help!

I am glad to hear that worked for you!  Thank you for pointing out that styling problem as well, I will review that behavior and let our development team know.

Thank you for contacting us.


I am sorry to hear that there are some problems with the display of Blog titles on your page and our team is happy to help in any way we can.


I took a look at the website associated with your Connect key and I believe that I have determined the source of the problem.  The actual title for your Blog page is being correctly hidden but the titles for the individual blog posts are still visible, even though the title is also contained in the body of the post content.

We can fix this display issue by using custom CSS to hide the Post titles in the Blog feed and I believe this will provide you with the display you are looking for.  Below is the CSS snippet you will need to add to the Custom CSS area of your Customizer to hide those titles.

.blog article .entry-title {
    display: none;
}

I have also created a feature request with our development team to consider adding the option to hide post titles in the blog feed for an upcoming release.

I hope that this information helps you get your blog styled to your liking and please let us know if there is anything else that we can do to assist you.

Thank you for contacting us and reporting this bug.

I have created a bug report for this issue in our public GitHub repository for our Development team to review.  If you would like, you can subscribe to the thread there to get live updates on our progress as we move towards a permanent fix.

Thank you for helping us improve BoldGrid and please let us know if there is anything else that our team can do to assist you.

Hi lauriewinestocksings, thank you for contacting us.

Apple mobile devices have some trouble utilizing the CSS rule background-size: cover and it leads to some strange behavior. However, we can correct this by using the custom CSS option is your website's Customizer to make it behave how we want. Below I have provided some code that you can copy into that section that should address the problem you are experiencing.

@media (max-width: 991px) {
    body.custom-background {
        -webkit-background-size: auto !important
}

This code uses a media query to target screen resolutions for mobile and tablet devices and changes the background size option from cover to auto, which will help the image display correctly for the appropriate screen size. I also added in the -webkit tag to ensure that only devices that utilize the Apple Webkit framework will use this new rule.

This information will be included in WordPress 5.2 ("/wp-admin/site-health.php?tab=debug"). We decided not to include features that will be in current or near-future releases of WordPress.

Thank you for providing that information and I have reported this bug to our development team for further review.   I hope that we can release a fix for this problem in an upcoming release and thank you again for helping us improve BoldGrid.

Thank you for contacting us.

If possible, can you provide us a link to one of your pages where the background images are tiling?  I am currently unable to replicate the problem on my end and any additional information you can provide us will help narrow down the source of this bug.