kallym

I contacted EDD and here is there reply:

This is a bug in the Groups plugin. For example, in the first error you mention they are doing the following:
if ( !isset( $post_types_option[$post_type][‘add_meta_box’] ) || $post_types_option[$post_type][‘add_meta_box’] ) {

They are checking for a post type that they do not have in their array of post types they control. There isn’t anything EDD can do to correct this.

What can I do to prevent these warning messages?

This has happened to us, too, on several sites. I set the home page to not be cached in W3TC, but, don’t think this is the best solution, so would appreciate a response from WordFence also, as I imagine it could happen on any page. Did you contact W3TC?

I don’t use JetPack so can’t help there. Do you need JetPack?

Ah yes, I also adjusted the .wrap css styles.

Again, I”m still experimenting with sizes, so just experiment with both the function and the styles to get what you want.

Compare this to your current CSS:

 @media screen and (min-width: 48em) { /* 768 px */
.wrap {
    max-width: 700px;
    padding-left: 1em;
    padding-right: 1em;
}
 } 
 @media screen and (min-width: 75em) { /* 1200 px */
.wrap {
    max-width: 1400px;
    padding-left: 3em;
    padding-right: 3em;
}
.single-post:not(.has-sidebar) #primary, .page.page-one-column:not(.twentyseventeen-front-page) #primary, .archive.page-one-column:not(.has-sidebar) .page-header, .archive.page-one-column:not(.has-sidebar) #primary {
    margin-left: auto;
    margin-right: auto;
    max-width: 1140px;
}
 }

This worked for me, it is only slightly different, I’m still playing around with the sizes so use your own.

function remove_parent_filters(){ //Have to do it after theme setup, because child theme functions are loaded first
    remove_filter('wp_calculate_image_sizes', 'twentyseventeen_content_image_sizes_attr', 10);
}
add_action( 'after_setup_theme', 'remove_parent_filters' );

function child_content_image_sizes_attr( $sizes, $size ) {
	$width = $size[0];

	if ( 740 <= $width ) {
		$sizes = '(max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px';
	}

	if ( is_active_sidebar( 'sidebar-1' ) || is_archive() || is_search() || is_home() || is_page() ) {
		if ( ! ( is_page() && 'one-column' === get_theme_mod( 'page_options' ) ) && 767 <= $width ) {
			 $sizes = '(max-width: 767px) 89vw, (max-width: 1000px) 85vw, (max-width: 1071px) 700px, 1020px';
		}
	}

	return $sizes;
}
add_filter( 'wp_calculate_image_sizes', 'child_content_image_sizes_attr', 15, 2 );

Thank You!

Thank you!

This is a whole row of round buttons above each slide – one for each slide. And the surrounding div is called bwg_slideshow_dots_container, so it seems that these are definitely slideshow dots. So I think I am misunderstanding you and you are saying that the control button option is for next/previous and the slideshow dots can only be disabled if I purchase the premium plugin. Is that correct? If so, I guess display:none is my only option for now. Thank you!

Thank you!! ??

Thanks Spinaker, but the plugin was just updated in the last 24 hours. The version I downloaded a few days ago had 150 instead of 120. ie. $i = $i + 150. So my code shows 150. It doesn’t matter, I just changed the function to 0, 120, 240, 360, 480 and 600 and it still doesn’t work.

RockyReasoner, yes, it looks like the plugin is loading 6 different stylesheets for 150 Google Fonts, and those stylesheets are loading the fonts.

The number of fonts involved is causing GTMetrix to report that I should minimize request size and says: The requests for the following URLs don’t fit in a single packet. Reducing the size of these requests could reduce latency.

You can see from the following example that this is ridiculous and this is just for 120 – there are 6 in all. We are forced to load Google Fonts we don’t need. I checked the updated options and there is no where to disable this and the standard methods for creating child theme functions to over ride these are not working for me. I ended up commenting out code in the plugin itself, but this will be overwritten the next time there is an update, so not an acceptable solution!

Can the Photo Gallery moderator please comment on this?

example for 120:

<link
rel='stylesheet' id='bwg_googlefonts_120-css'  href='https://fonts.googleapis.com/css?family=Carrois+Gothic+SC|Carter+One|Caudex|Caveat+Brush|Cedarville+Cursive|Ceviche+One|Changa+One|Chango|Chau+Philomene+One|Chela+One|Chelsea+Market|Chenla|Cherry+Cream+Soda|Chewy|Chicle|Chivo|Chonburi|Cinzel|Cinzel+Decorative|Clicker+Script|Coda|Coda+Caption|Codystar|Combo|Comfortaa|Coming+Soon|Concert+One|Condiment|Content|Contrail+One|Convergence|Cookie|Copse|Corben|Courgette|Cousine|Coustard|Covered+By+Your+Grace|Crafty+Girls|Creepster|Crete+Round|Crimson+Text|Croissant+One|Crushed|Cuprum|Cutive|Cutive+Mono|Damion|Dancing+Script|Dangrek|Dawning+of+a+New+Day|Days+One|Dekko|Delius|Delius+Swash+Caps|Delius+Unicase|Della+Respira|Denk+One|Devonshire|Dhurjati|Didact+Gothic|Diplomata|Diplomata+SC|Domine|Donegal+One|Doppio+One|Dorsa|Dosis|Dr+Sugiyama|Droid+Sans|Droid+Sans+Mono|Droid+Serif|Duru+Sans|Dynalight|EB+Garamond|Eagle+Lake|Eater|Economica|Eczar|Ek+Mukta|Electrolize|Elsie|Elsie+Swash+Caps|Emblema+One|Emilys+Candy|Engagement|Englebert|Enriqueta|Erica+One|Esteban|Euphoria+Script|Ewert|Exo|Exo+2|Expletus+Sans|Fanwood+Text|Fascinate|Fascinate+Inline|Faster+One|Fasthand|Fauna+One|Federant|Federo|Felipa|Fenix|Finger+Paint|Fira+Mono|Fjalla+One|Fjord+One|Flamenco|Flavors|Fondamento|Fontdiner+Swanky|Forum|Francois+One|Freckle+Face|Fredericka+the+Great|Fredoka+One|Freehand|Fresca&subset=greek,latin,greek-ext,vietnamese,cyrillic-ext,latin-ext,cyrillic' type='text/css' media='all' />

Thanks for getting back to me on this. I’m sorry you won’t be able to continue your plugin.

Wonderful! Thank you!

Thanks for your quick reply! But, too bad. That won’t work in this case as I need the description to show below the title on the form itself.

Example:
SIGN UP (title)
..for our mailing list (description)

Thank you! This will work really well for me and I think will be a welcome addition to the plugin for a lot of your users. Thanks again!

Thank you for the quick response and willingness to modify your plugin. I really appreciate that!
Also I modified the code to use the thumbnail size rather than the uploaded image size as my clients were uploading all different sizes of images. Could that be an option also?
For my purposes I changed the_post_thumbnail( ‘url’ ) to the_post_thumbnail( ‘thumbnail’ )
Thank you!