Forum Replies Created
-
AuthorPosts
-
Perfect. I modified this a bit to force the images to be the same size at all screen widths and made the titles larger. This ticket can be closed. Thanks again!
figcaption.av-inner-masonry-content.site-background {
min-height: 130px;
max-height: 130px;
}.av-masonry-entry .av-masonry-entry-title {
font-size: 18px;
}Hi Ismael,
Thanks for your response. I did that, and it’s a lot closer to what we’re looking for but not quite there.
First – we would like the images to be the same height no matter what the screen size and not too short. Currently, at smaller screen sizes, some images end up taller than others and the height of the preview image can get rather small sometimes.
Second – we want the Blog headline text to be a little bigger, around 20px. When I try to apply that style, it affects the height of the images; to the point where sometimes the images are completely hidden.
See attached screenshot. Thanks.
Sorry for the delayed response. So, there are a couple things going on. I made some CSS adjustments that helped in “full screen” width but I had to hide the excerpt to get it to display the way I wanted.
If I adjust my screen width to a “medium size” on my desktop the post titles start to get covered up by the image – until the screen goes to a small size and the posts “stack” on top of one another. Even then, a small portion of the title gets covered up.
If I look at the site on my phone, that problem doesn’t exist – BUT the images aren’t as “tall” as we would like.
See screenshots and CSS currently applied to our Blog page in Private Content.
Thanks,
I did that and made a couple other CSS adjustments but it’s still not exactly what I want. I like the height of the image but now the excerpt portion is being covered by the images below it. How can I make each post preview taller?
Actually, I changed it from “Perfect Automatic Masonry” to “Perfect Grid” and now it’s behaving as I hoped.
My question now is – how can I force the images to all be the same height?
September 10, 2015 at 5:49 pm in reply to: Updated to WordPress Version 4.3 – Site Messed Up #501231Alright. Thanks Josue.
September 9, 2015 at 11:51 pm in reply to: Updated to WordPress Version 4.3 – Site Messed Up #500766I was experiencing the same issue. It appeared that they were all the same warning. There was probably 8-12 of them.
I updated to 3.3.1 and that helped clear most of the warnings, but I’m still getting one:
Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use
__construct()
instead. in /web/content/wp-includes/functions.php on line 3457I had to set WP_DEBUG in my wp-config.php file to ‘false’ to clear it. I’d prefer not to have to use this kind of workaround as a long-term solution. Any idea what I can do to clear that last warning?
That worked! There were some retargeting and call tracking scripts I forgot I had hard-coded in the child theme’s footer file. I moved those to functions.php, called them using the ‘wp_footer’ hook and it’s all working again. Thanks so much for your help. Topic can be closed.
Yes, those are the images. I followed the steps you listed and still have been unable to get those images to display. Should I be able to export the settings from my Child theme and import them into the Parent theme?
That’s strange. I’ve tried clearing the browser cache, all my history, cleared the site cache with WP Super Cache, hard-refreshed many times, and re-tested in Firefox, Chrome, Internet Explorer, and Safari. I’ve tested it on multiple desktops (at work, at home, co-workers) and my iPhone. The maps and CSS animations are still not working for me on any device.
Still seeing these 2 JavaScript errors in the Console as well:
ReferenceError: module is not defined avia.js:2016:1606
Error: Syntax error, unrecognized expression: unsupported pseudo: regex jquery.js:2:12716Okay, I tried that but did not see any change in results. I turned on WP_DEBUG in my wp-config.php file and saw 2 JavaScript errors in the Console.
ReferenceError: module is not defined avia.js:2016:1606
Error: Syntax error, unrecognized expression: unsupported pseudo: regex jquery.js:2:12716I activated the parent Theme for a minute, but this is for a client’s site and all styling, settings, etc. exist in the Child Theme, so I had to reactivate the Child theme. I can’t leave it with the parent theme activated.
I created a user account for you. Login info is in the Private Content. Can you go in and take a look please?
Hi Elliott,
I’ll give this a try. Just one question – does this mean all my current Enfold settings will be lost?
Hi Basilis,
We’ve tried this on multiple machines in multiple browsers, both mobile and desktop, and unfortunately, it’s not working perfectly for us at all.
I can find a workaround for the animations, but the fact that the Google maps won’t show up and the Accordions won’t expand is very concerning.
I’m going to post 2 URL’s in the Private Content below. Can you visit these 2 pages and send me screenshots of the maps you’re seeing and an expanded Accordion element please?
FYI – I’ve tried disabling all Plugins and that didn’t seem to help.
Just noticed Accordion elements aren’t expanding either.
Nevermind. I think I got it to work with the filter below. Does this look like the best way to do this?
add_filter( ‘the_content’, ‘featured_image_before_content’ );
function featured_image_before_content( $content ) {
if ( is_singular(‘post’) && has_post_thumbnail()) {
$html = ‘<style type = “text/css”>.big-preview { display: none !important; }</style>’;$content = $html . $content;
}return $content;
}I think that should work – BUT – the people who will be posting aren’t very technically savvy so making them post a piece of code in every post isn’t realistic. Is there a way to apply a filter in functions.php that will automatically prevent the featured image (.big-preview) from displaying in the post by default?
-
AuthorPosts