Tagged: cornerstone
-
AuthorPosts
-
February 14, 2017 at 7:50 am #1370426
Hi,
I have a two-up block grid item for which I want to change the break point. The Cornerstone default is stacking the two block grid items when iPhone portrait size is reached.
I would like it to stack at tablet/ipad portrait size – can you help with the CSS for that?
Many thanks!
February 14, 2017 at 9:03 am #1370505Hi there,
Thanks for writing in! It would be possible with some CSS. To make sure it won’t affect other elements, you can add a custom class to the element or the container (section/column). Update us with your URL after adding the class and point us the element so that we can tailor some code for you.
Cheers!
February 14, 2017 at 9:10 am #1370511This reply has been marked as private.February 14, 2017 at 11:55 am #1370773Hi there,
Thanks for writing back! You can add this under Custom > CSS in the Customizer.
@media only screen and (max-width: 979px) { .x-block-grid.two-up > li { width: 100%; margin-right: 0; } }
Hope this helps.
Cheers!
February 14, 2017 at 12:11 pm #1370803Perfect thanks!
February 14, 2017 at 12:46 pm #1370830You’re welcome.
February 16, 2017 at 1:02 pm #1373950Hi again,
I need to re-open this topic, as the css Rupok gave me here has stopped working properly.
The two-up grid items in question now don’t fill the screen width to 100% – the image above the video is sitting over to the left at the specified media width. I tried changing the code to:
@media only screen and (max-width: 979px) { .x-block-grid.two-up > li { width: 100%; margin-right: 0 !important; } }
It didn’t help.
In addition, the four-up block grid further down the page (CAST section) has started misbehaving. When it gets to a certain media width, the default behaviour should be two images side-by-side at 100% width. Now it looks like there is padding either side!
I’ve tried everything to fix the layout, but I’m really lost as to what’s causing this, especially as it was all looking great before!
Many thanks.
February 16, 2017 at 10:34 pm #1374515Hello There,
Thanks for updating this thread. This could just be a caching issue. Since you have installed a caching plugin WP Super Cache, please clear your plugin cache before testing your site. This can cause the changes to not take place on the front end. It will eventually show up when the cache regenerates, but it’s not ideal if you’re looking to see your changes immediately. Caching plugins are best to turn on only when you’ve finished building the site.
Please let us know how it goes.
February 17, 2017 at 1:59 am #1374687Thanks for your help – the cache had indeed been cleared for testing purposes before I posted my reply, and WP Super Cache switched off.
However this seems to have resolved itself overnight, so I guess something must have remained in the cache, even though it had already been cleared.
I will keep an eye on it and report back if I have any further issues.
Thanks again.
February 17, 2017 at 3:11 am #1374730Hey There,
You’re welcome! We are just glad we were able to help you out.
Thanks for letting us know that it has worked for you.Cheers.
February 17, 2017 at 8:38 am #1375014On further inspection, I’ve discovered this was not a caching issue.
The problem is related to Jetpack Photon. When Photon is turned on, it breaks the layout in the way described in post #1373950 above. Evidently one of Themeco’s support agents must have switched Photon off when inspecting the site, hence fixing the problem.
Any idea why Photon might be causing this? I’ve turned Photon off for the moment, but perhaps this is something to submit to your development team, as so many people use it?
Many thanks.
February 17, 2017 at 3:46 pm #1375586Hi again,
Regretfully, we cannot provide support for third party plugins or scripts as our support policy in the sidebar states due to the fact that there is simply no way to account for all of the potential variables at play when using another developer’s plugin or script. Because of this, any questions you have regarding setup, integration, or troubleshooting any piece of functionality that is not native to X will need to be directed to the original developer.
Thank you for your understanding.
February 19, 2017 at 4:06 am #1376923Thanks – yes of course, I do understand that.
However, Jetpack is an extension provided by Automattic, the developers of WordPress, and is so frequently used that it has almost become a default part of WordPress itself.
I was just suggesting that it might be something for your development team to look at, bearing in mind how embedded it has become in so many WordPress installations.
February 19, 2017 at 5:38 am #1376977Thanks for your feedback. I’ll forward your concern. Please bear in mind though that supporting Jetpack or Jetpack features is not a requirement so we could not promise an integration for this.
-
AuthorPosts