Patagonia

[Patagonia]

Hi Abe,

could you add a list of changed files for the small update?,

Thanks!

[Patagonia]

Hi @Abe, so what will 1.51 bring, exactly?
you mention above:

– Mega menu functionality added with “add_theme_support” statement so it can be easily disabled in child theme

Will this mean a full megamenu, or still just links?
Thanks

[Patagonia]

See also the updated faq: http://wordpress.org/plugins/nav-menu-roles/faq/
KLeo team, it states:

Workaround #1

Shazdeh, the author of Menu Item Visibility Control plugin had the genius idea to not wait for a core hook and simply add the hook ourselves. If all plugin and theme authors use the same hook, we can make our plugins play together.

Therefore, as of version 1.6 I am modifying my admin walker to only adding the following line (right after the description input):

COPY CODE

<?php 
// This is the added section
do_action( 'wp_nav_menu_item_custom_fields', $item_id, $item, $depth, $args );
// end added section 
?>

I am then adding my fields to this hook. Ask your conflicting plugin/theme’s author to do the same and our plugins should become compatible.

So some work on your side might be needed.

[Patagonia]

It seems they changed it to have both plugins work together, see
http://wordpress.org/support/topic/does-this-work-with-nav-menu-roles-plugin?replies=13

Do they both work now with Kleo? Might need to test the dev version from github.

Cheers

[Patagonia]

Actually, still the same 6 hardcoded references to Open Sans & 2 references to Roboto are in the CSS (I checked my minified css, which is one large file), please remove them.

[Patagonia]

Good to see some more bugs getting fixed.

– Can you please fix the 2nd sidebar issue (it can’t be changed/chosen)
– there is still a hard-coded Roboto reference in bbpress.css
– The border between the left sidebar and the main section is only as long as the sidebar, not all the way down

Cheers

[Patagonia]

By the way, are background images automatically disabled when the browser-width is less than the container width? That would save it from being loaded for nothing. If not, please consider it a request.

Thanks

[Patagonia]

Sorry, was left-over custom css to fix bug that was fixed in 1.5. All works now.

[Patagonia]

Hi Inbloome,

I have no idea about the .htaccess, as I never edited this for the fonts, I just used the standard KLEO settings for fontello. It just seemed strange to me that on my theme the .woff is called (at least in FF), and on yours the EOT.

I am not sure if it is still the case, but before I think that FF was picky: the font files should be on the same domain and it should be woff, not eot. Again, this might have changed, I am no FF expert.

FYI, The icons on your site are still not showing up for me on FF.

Cheers

[Patagonia]

It worked fine for me, but note that the extra sidebar (on 3 column layouts) is not a regular sidebar and cannot be changed with any plugin or even through Kleo.

@abe, did you fix this for the 1.5 release?

Cheers

[Patagonia]

I just noticed this when viewing your site. I see that fontello.eot is called, not fontello.woff. Not sure if there is a specific reason or if it makes a difference. FireFox used to handle only woff, not sure what it does now (in my Kleo testing, always the woff gets loaded automatically)

Great site by the way!

PS: I test my site only in FireFox and never had problems, but use no CDN. Did you try with a different CDN or a free one like cloudflare?

[Patagonia]

In general most remaining problems are because Gravatar sucks 🙂
So unless you need them I would add a plugin that disables or at least caches them locally.

I used this code: http://bp-tricks.com/snippets/completely-disable-the-use-of-gravatars-on-your-buddypress-site/ but you can check plugins to cache gravatars as well.
Also it seems that your CSS is not minified, so either enable it in bwp-minify and/or install w3 Total cache. That is a good idea anyway, it will make your site faster. Or get a better host, as it takes about 2 seconds before anything starts loading, at that time my pages are already finished.

It also seems that you have some redirect from the www version to the non-www version, so check yoru general site settings in WordPress, they should be equal.

Veel plezier!

[Patagonia]

Hi Abe,

on my site (where I did not remove the logo) that CSS centers the menu, but the logo does not shrink anymore and the menu has moved down, so teh header is much larger.

(also the submenus & megamenu items have been centered, not sure if that can be remedied easily).

Cheers

[Patagonia]

http://lmgtfy.com/?q=batch+resize+images+wordpress 🙂

[Patagonia]

You need to optimize your homepage, it never fully loaded for me (slow connection, comparable to mobile).

See http://gtmetrix.com/reports/receptenmaker.nl/fdNxWhPB for a report.

You can save over 80% of bandwidth by using normal sized images and using plugins like BWP-minify and https://wordpress.org/plugins/remove-query-strings-from-static-resources/.

Cheers

[Patagonia]

Actually I would also like to know how to do this while keeping the logo 🙂

[Patagonia]

Hi Abe,

can you make sure that standard VC options are available in K-elements?
Right now there is not even an option to make 2 columns with a normal shortcode (not using VC).

VC is extremely limited in creating real content (not just flashy banners) and delays page loads.

Also, please update the documentation, so we know what K-elements actually (can) do 🙂

Thanks!

[Patagonia]

Make it easy for yourself:
http://wordpress.org/plugins/content-aware-sidebars/

[Patagonia]

More flexibility in sidebar configurations and widths.

– For example the 3 columns pages (2 sidebars) could have 2 sidebars of different widths
– also you can choose between 75%, 67% & 50% for the main column, that would be a great addition).

– Separate layout for the blog homepage (masonry) vs the blog articles. I want the blog homepage with one column, and the articles with two, but the only way to do that is to choose one for blog and change the layout for every article again.

Thanks!

[Patagonia]

Hi Abe,
thanks for your reply. Yes, I am talking about the lightbox for images in posts and pages (single images, galleries etc). If you could add the Magnific popup for that, that would be great. Would be even greater if some of the social icons would be available to share the images.

There are a lot of references to PrettyPhoto (and the CSS is loaded as well), so you might want to take all of these out as that is what confused me and what breaks the lightbox plugins if used.

Thanks in advance,
Cheers

[Patagonia]

Thanks. Please also note that in my stylesheets there are about 8 hardcoded mentions of Roboto and another 6 or so of Open Sans. (H2 headers in RTmedia, Date in posts etc).

Even though they are no longer called and thus not displayed, they fall back on ‘sans serif’, which is ugly and different than my chosen body & headings font.

Can you remove these hardcoded/fixed fonts and replace them with the choices for the Theme Options?

Thanks!

[Patagonia]

I solved 1) with a combination of function and CSS, not sure if this is optimal, but seems to work:

– To hide the time (the time will still pop-up as alt text when hovering over the date):
Add to child theme Style.Css:

COPY CODE

article .article-meta .post-meta a.post-time:after {
  content: none;

To remove author, I added the entire function to child theme functions.php and deleted the author part:

COPY CODE

	function kleo_entry_meta($echo=true, $att=array()) {
	
		$meta_list = array();
		
		// Translators: used between list items, there is a space after the comma.
		$categories_list = get_the_category_list( __( ', ', 'kleo_framework' ) );

		// Translators: used between list items, there is a space after the comma.
		$tag_list = get_the_tag_list( '', __( ', ', 'kleo_framework' ) );

		$date = sprintf( '<a href="%1$s" title="%2$s" rel="bookmark" class="post-time"><time class="entry-date" datetime="%3$s">%4$s</time></a>',
			esc_url( get_permalink() ),
			esc_attr( get_the_time() ),
			esc_attr( get_the_date( 'c' ) ),
			esc_html( get_the_date() )
		);

		$meta_list[] = '<small>'.$date.'</small>';

		
		$cat_tag = array();
		
		if ( $categories_list ) {
			$cat_tag[] = $categories_list;
		}
		
		if ($tag_list) {
			$cat_tag[] = $tag_list;
		}
		if (!empty($cat_tag)) {
			$meta_list[] = '<small class="meta-category">'.implode(", ",$cat_tag).'</small>';
		}
		
		//comments
		if (!isset($att['comments']) || (isset($att['comments']) && $att['comments'] !== false)) {
		$meta_list[] = '<small class="meta-comment-count"><a href="'. get_permalink().'#comments"> '.get_comments_number().' <i class="icon-chat-1 hover-tip" 
			data-original-title="'.sprintf( _n( 'This article has one comment', 'This article has %1$s comments', get_comments_number(), 'kleo_framework' ),number_format_i18n( get_comments_number() ) ).'" 
			data-toggle="tooltip" 
			data-placement="top"></i></a></small>';
		}
		
		if ($echo) {
			echo implode(", ", $meta_list);
		}
		else {
			return implode(", ", $meta_list);
		}
		
	}

And made a lot of CSS and template changes as well.

Still it would be a bit more userfriendly to have the option in the backend about which meta parts (not) to show.

I would appreciate advice re question #2 above.

Thanks!

[Patagonia]

Some observations:
– When I enable the prettyphoto plugin, the underlying KLEO lightbox is not Prettyphoto, but Magnific.

– When uncommenting all prettyphoto scripts in Functions (2x css, 2x js), it still does not work without a plugin to ‘push’ it.

– When enabling a Magnific plugin (like IW magnific popup), the magnific script works, kinda: the popup appears, though there are no navigational buttons (and the arrow keys do not work), so you cannot move to next photo in the post/page.

I don’t really care whether Magnific or Prettyphoto s used, as long as it works properly and preferably with some options:
– Social share buttons (would be nice if they are in the regular KLEO post style)
– Some skins/styling options
– Navigation + swipe for mobile
– Title and/or caption to be displayed.
– Popup to 100% screen width, with button for full size (if full size is larger).

Thanks for considering.

[Patagonia]

edit: the RT plugin actually is responsive as well, just not when resizing the browserwindow and it seems to have fixed sizes, not 100% width images. It has a nice option to be able to click through to true full size as well.

[Patagonia]

ps:

– The KLEO CSS is better because it is responsive and I like the navigation arrows better.
– The Royal Prettyphoto CSS/plugin is better because it has the photo title, miniatures of the pictures on the page and twitter/FB share buttons. And the CSS is loaded anyway.

I hope you can use the best of both worlds, ideally with options in the KLEO back end such as http://wordpress.org/plugins/rt-prettyphoto offers (though I hate that you cannot switch off Google fonts in that plugin).

Thanks

[Patagonia]

I tried to enable the following plugins:
– PrettyPhotomedia, but it did not do anything
– Royal Prettyphoto: this seems to work, but suddenly I get two image overlays.

It seems that the prettyphoto.js scripts is not called in KLEO, is that correct? (even though it is in the themefiles, under js/plugins). I tested it with BWP minify switched off.
It also seems that the prettyphoto CSS is included, is that correct? (That’s why I see two lightboxes when the external plugin is enabled?)

If so, then KLEO should either have an option to enable prettyphoto (and load the script), or to disable it (so thatthe CSS is not loaded). Currently it is either not working or working ‘twice'(when using a plugin.

Thanks.

[Patagonia]

Thanks Robert, much appreciated. Are you expecting to put out a theme update soon, or should I patch it temporarily?

Thanks.

[Patagonia]

Hi Abe,

thanks for your reply. On my home page (which is nearly empty at the moment) the 2 css (Roboto & Opensans) are requested from Googlefonts, even though I have disabled the custom fonts.
On the blog pages, the font themselves (open sans + roboto) + the 2 CSS files are requested/

These are useless and time consuming requests which are not needed. Even though the files are small, they often keep the pages from loading. When I disable the Google fonts, I do not want any calls to google, can you fix this?

Thanks!

[Patagonia]

Please do check how (and how many times) the fonts are called/included. As far as I could see, even if I use only one Google font (just the body for example), then still multiple instances of both default custom fonts are called.

For now I turned off all custom fonts and use Helvetica instead, but:
1- On a regular page, still 2 Google CSS’s are called (open sans & Roboto). PLease remove these if not needed!
2- On a BuddyPress page (I tested Groups, turned off all custom fonts and purged all caches) still the fonts are included and called (and the CSS as well). Is the Roboto font hard coded in BP pages? I cannot seem to be able to change and not include it?

3 by the way, is it standard to call the Google fonts with a huge random string? The advantage of the popular Google fonts like Open Sans is normally that the browser of the visitor might have cached it already as they have visited other pages. But with these random strings attached, that won’t happen, will it?

Many thanks

[Patagonia]

I noticed the same and added the following to the child’s theme CSS:

COPY CODE

body {
	background-image: none !important;
    background-repeat: no-repeat;
}

This overrides the CSS calling it, so the next theme update won’t replace it on the site.

I don’t see any difference, not sure why the file is called?
Cheers

[Patagonia]

Never mind the avatar: I reckoned that as an Admin and group Admin I would have access, but apparently I must enable the BuddyPress settings to allow all users to upload avatars, else the group avatar is no option either. Very strange setting, it would be better if the siteadmin and/or group admin had more privileges.

The problem as reported is true, now new groups work, existing ones don’t. Still deleting groups from the front end does not work (I have all cache and other plugins off at the moment).

[Patagonia]

ps: also deleting a group does not work, can only do this from the back end. When deleting from the front end it just waits a bit and then does noting and the group is not deleted.

[Patagonia]

I think I am going crazy, but where can I actually upload or edit a group avatar?
When creating a group there is no option and when administrating one neither, see screenshot.

I also do not have the group location/hierarchy settings I see on the screenshots.

Is there a special setting somewhere? Which script(s) is responsible for this, maybe it is minified or so?

Thanks!

Attachments:

You must be logged in to view attached files.

[Patagonia]

Not marked as solution

[Patagonia]

Not marked as solution

[Patagonia]

Big feature: true responsive images.

Currently resizing of the screen makes the uploaded and displayed image resize to fit the screen. That is nice, but it means that somebody that checks my site on a mobile phone will still download the large image (which will be resized).

It would be much better to have the (more or less) correct size served, based on screen size, instead of loading a 1200px image for a 367px display. This saves bandwidth/costs/time for both the visitor as well as the server.

There seem to be several solutions out there already as well as some plugins. Would be a great selling point for KLEO if this were to be supported out of the box!

[Patagonia]

On a related note:

1) Do you have some tips for which theme Js scripts can be loaded in the footer?

2) On a completely empty (home)page, 4 Carousel scripts (“carouFredsel”) are loaded and probably some others as well that are not needed (BPpress etc). Is there a way to optimize the theme so it only loads the scripts that are actually needed?

[Patagonia]

I just noticed that some basic shortcodes are missing from the K-elements plugin:
– Columns
– Tables
– More?

The first (columns) Likely because it is in VC.
First of all I (and many with me) don’t like to use VC. But more importantly: all plugins that use Tiny MCE for editing don’t even have the option to use the composer (for example Global Content Blocks and all other custom post types editors).

So even though we have the K-elements plugin, the columns & tables and other basic stuff (?) is not there. Can we have that functionality in the K-elements button? So we don’t have to add yet another plugin (that will likely conflict) to be able to use the built in functionality? Thanks!

[Patagonia]

Thanks Robert. Not sure if you are just adding the default ones or if you are actually editing them. If it is the latter, then I would request a feature that allows not only styling, but also to replace the default percentage (%) with regular numbers or text (i.e. to display a grade from 1-10, easy to hard etc).

Thanks!

[Patagonia]

Thank you, that is a helpful overview. Is there a preferred way to add/define custom icons? Either from other sources or home-made?

Thanks.

[Author]

Posts