Forum Replies Created

Viewing 40 posts - 1 through 40 (of 92 total)
  • Author
  • in reply to: Shortcodes in template files #175097
     Patagonia
    Participant

    Thanks for your reply. It did not work in this specific case, but that is a very useful solution to keep in mind for other template changes.

    in reply to: Header background image per category, body class outputs #174749
     Patagonia
    Participant

    Thanks! That works fine, much appreciated.

    in reply to: Header background image per category, body class outputs #174396
     Patagonia
    Participant

    PS: I wasn’t sure how to call the category as body class output, but did try two variations to get the top-parent ID. I added these variations to the theme’s functions.php

    COPY CODE
    /* Get the Page Slug to Use as a Body Class, this will only return a value on pages! */
    $class = '';
    /* is it a page */
    if( is_page() ) { 
    	global $post;
            /* Get an array of Ancestors and Parents if they exist */
    	$parents = get_post_ancestors( $post->ID );
            /* Get the top Level page->ID count base 1, array base 0 so -1 */ 
    	$id = ($parents) ? $parents[count($parents)-1]: $post->ID;
    	/* Get the parent and set the $class with the page slug (post_name) */
            $parent = get_post( $id );
    	$class = $parent->post_name;
    }
    

    (from WordPress codex, this didn’t work)

    And I tried

    COPY CODE
    add_filter( 'body_class', 'dc_parent_body_class' );
    function dc_parent_body_class( $classes ) {
        	if( is_page() ) { 
            	$parents = get_post_ancestors( get_the_ID() );
    			$id = ($parents) ? $parents[count($parents)-1]: get_the_ID();
    		if ($id) {
    			$classes[] = 'top-parent-' . $id;
    		} else {
    			$classes[] = 'top-parent-' . get_the_ID();
    		}
    	}
     
    	return $classes;
    }
    

    Which also did not work. Neither did add the top-parent ID, not sure why not as your code does output all kinds of body classes?

    in reply to: Sticky menu mobile padding #121614
     Patagonia
    Participant

    Sorry, I never saw you answered me.
    I am not sure how to explain it better: Is there a way to have it minimized, like on the normal menu? So when you scroll down, the logo gets smaller.

    Under theme options -> header options this is called “Resize logo on scroll* – Enable or disable logo resizing when scrolling down the page”, which is enabled by default and ysed widely.
    But it does not work on mobile while exactly on mobile you need the extra space it creates.

    Thanks in advance.

    in reply to: Sticky menu mobile padding #108000
     Patagonia
    Participant

    For me it works in the stylesheet as well.
    Is there a way to have it minimized, like on the normal menu? So when you scroll down, the logo gets smaller etc.

    Cheers.

    in reply to: Sticky menu mobile padding #106963
     Patagonia
    Participant

    Could this be made into a theme option?
    Especially for mobile a (minimized) sticky menu is very usable.

    Thanks in advance.

    in reply to: floating contact form #106932
     Patagonia
    Participant

    Also: the selected option/placeholder does not get sent in the email.

    in reply to: floating contact form #106931
     Patagonia
    Participant

    Sorry, your code did work, when posted in functions.php

    I noticed that the form is defined in lib/themefunctions.php

    However, it does not show the refferring page, i.e. from which page the form was sent from, as per the original request (and mine) above. How/where could we add this?

    Thanks in advance.

    in reply to: floating contact form #106921
     Patagonia
    Participant

    Hi, I was just looking for this, especially as I want to know from which page the form was submitted.

    I added the code above (tried both version), to my child theme’s functions.php but see no difference, just the standard form. Does this code still work with Kleo 4? Where is the contact form defined as it is not in the main Kleo theme’s functions.php?

    Thanks!

    in reply to: Add referring page to floating contact form? #106913
     Patagonia
    Participant

    Well, that is the first time I ever received such a useless reply from anybody at 7thqueen. @abe or @sharmstr, could you help out?
    Cheers.

    in reply to: update change log? #106535
     Patagonia
    Participant

    And what is new/changed in 4.0.1?

    in reply to: Designated fonts no longer working #105237
     Patagonia
    Participant

    Thank you @abe. Note that the changes in itself did not fix it, I had to change all Headings and Body fonts to some other font first, save changes and then back again to Trebuchet, save changes again before they actually changed.

    Cheers.

    in reply to: Designated fonts no longer working #104435
     Patagonia
    Participant

    This is Trebuchet and how it looked before:

    Attachments:
    You must be logged in to view attached files.
    in reply to: Designated fonts no longer working #104434
     Patagonia
    Participant

    Hey Sharmstr, thanks for your swift reply.

    The example you posted has the same problem: it is not Trebuchet MS, but some other -serif- font (Trebuchet , Helvetica ans sans serif are all, well, sans serif 🙂

    in reply to: Select User Role at Registration #102412
     Patagonia
    Participant

    @romanzy, did you figure this out?


    @Sharmstr
    , I have a similar question, which I think does involve KLEO:

    For ‘basic’ memmbers the Kleo Facebook registration should be enough, quick and painless. But for other member types I want them to fill out more field (either at registration or later).

    – Is there a way to differentiate this at sign-up, based on user role (they can choose themselves)?
    – is there a way to remind people/roles to complete (parts of) their profile, for exampl if they only signed up with FB?

    Welcome any input you might have, thanks.
    Cheers

    in reply to: How to create a buddypress overall template ? #63347
     Patagonia
    Participant

    Ah, ok, yes that might work. I am ok with making more templates, but the problem is I want to edit the part that is not covered by the templates. There is no template that goes between general-before-wrap & general-after-wrap I think.

    So the only choice is to make a complete new page type like content-edited.php in the child theme root, and a real new template which then calls get_template_part( 'content', 'edited' ); which calls new page parts. Just seems a bit impractical and was a big puzzle for me.

    This also mean I cannot set this as a default template as far as I can see.

    in reply to: Testimonials: how to show them? #63345
     Patagonia
    Participant

    Ah, now I do see the featured image, though very small and it does not link to anything. Still I would like to see it limited to x words/characters, for the widget etc.

    Thanks!

    in reply to: Testimonials: how to show them? #63344
     Patagonia
    Participant

    Thank you, I tried VC and could edit some basics, but did not find a way to answer these questions:

    – with or without featured image (all are without, vc offers no image option? Where does the featured image go?)
    – Display first xx characters/words only (or excerpt, but there is no excerpt field in the editor), with a link to the full testimonials or a specific page?

    Thanks!

    in reply to: How to create a buddypress overall template ? #63336
     Patagonia
    Participant

    Why can’t you use !bp_is_blog_page()?

    I don’t know because I do not know what you mean with that 🙂

    in reply to: How to create a buddypress overall template ? #63302
     Patagonia
    Participant

    Hi Laura,

    no, what I want to do is make a page template with some extra code within the loop (underneath the featured image).

    It seems that the only way to do this is to make a whole new page type, as the page templates do not cover the main part; if I change content-page.php, then all pages (including the mentioned BP ones) have the change, which is what I don’t want.

    So now I have solved it by creating a new template which calls a new content type: content-edited-page.php, not sure if this is the way to go. Just a bit different code should not warrant a new content-type?

    Cheers

    in reply to: Issues With Kleo theme after Update #63297
     Patagonia
    Participant

    I am getting different errors when updating to 3.01 on Xampp/localhost:

    COPY CODE
    Updating Theme Kleo (1/1)
    
    Downloading update from https://s3.amazonaws.com/marketplace-downloads.envato.com/files/137970596/kleo.zip?AWSAccessKeyId=AKIAJYG5ROGJ6X7Z3M6Q&Expires=1434488463&Signature=0P%2FF1vK9pngNA%2Fv1Yn2wBZjEum0%3D&response-content-disposition=attachment%3B+filename%3Dthemeforest-6776630-kleo-next-level-wordpress-theme-wordpress_theme.zip…
    
    Warning: touch(): Unable to create file C:\Users\Harry\AppData\Local\Temp/kleo.zipAWSAccessKeyIdAKIAJYG5ROGJ6X7Z3M6QExpires1434488463Signature0P%2FF1vK9pngNA%2Fv1Yn2wBZjEum0%3Dresponse-content-dispositionattachment%3B-filename%3Dthemeforest-6776630-kleo-next-level-wordpress-theme-wordpress_theme.tmp because Invalid argument in E:\XAMPP\htdocs\site\wp-admin\includes\file.php on line 164
    
    Warning: unlink(C:\Users\me\AppData\Local\Temp/kleo.zipAWSAccessKeyIdAKWIAJG5ROGJ6X7Z3M6QExpires1434488463Signature0P#3FF1vKartgNA%2Fv1Yn2wBZjEum0%3Dresponse-content-dispositionattachment%3B-filename%3Dthemeforest-6776630-kleo-next-level-wordpress-theme-wordpress_theme.tmp): Invalid argument in E:\XAMPP\htdocs\site\wp-admin\includes\file.php on line 464
    
    An error occurred while updating Kleo: Download failed. Could not open handle for fopen() to C:\Users\me\AppData\Local\Temp/kleo.zipAWSAccessKeyIDAKWIAJG5ROGJ6X7Z3M6QExpires1434488463Signature0P#3FF1vKartgNA%2Fv1Yn2wBZjEum0%3Dresponse-content-dispositionattachment%3B-filename%3Dthemeforest-6776630-kleo-next-level-wordpress-theme-wordpress_theme.tmp
    
    Disabling Maintenance mode…

    I have fopen ‘on’ in php.ini.

    Cheers, Harry

    in reply to: Testimonials: how to show them? #62701
     Patagonia
    Participant

    + some more options needed:

    – Display first xx characters/words only (or excerpt, but there is no excerpt field in the editor), with a link to the full testimonials or a specific page?

    – A page with x testimonials, limited by tags etc.

    Thanks!

    in reply to: Add LinkedIn sharing, make options #41403
     Patagonia
    Participant

    No, I did not; it should be part of the frame work, so maybe @abe can add it?

    in reply to: Problem with tags for pages #39644
     Patagonia
    Participant

    Thank you, Abe & Sharmstr!

    in reply to: Problem with tags for pages #39391
     Patagonia
    Participant

    Thanks; Yes, that seems to work with the KLEO widget (only), though the BBpress widget is more useful as it does not show the date for the topics.

    in reply to: Problem with tags for pages #39388
     Patagonia
    Participant

    Scrap the previous post: the side effect does exist as described, the correct version was still cached, but clearing the caches creates the problem on all pages.

    in reply to: Problem with tags for pages #39387
     Patagonia
    Participant

    Strangely enough this side-effect seems to have been temporarily (?). It’s ok now, maybe a cache-ing issue.

    in reply to: Problem with tags for pages #39386
     Patagonia
    Participant

    Hmm, it does have a strange unwanted side effect: in both the latest posts widget (Kleo Latest post, with “post type =post” defined), as well as in the bb-press latest post widget, the latest pages now appear instead of blog posts and forum posts…

    in reply to: Problem with tags for pages #39385
     Patagonia
    Participant

    Thank you very much, Sharmstr, that fixed it for now. Please make a reminder/trac or something for Abe. so I don’t have to change it after every update 🙂

    in reply to: Problem with tags for pages #39372
     Patagonia
    Participant

    Thanks for looking into this. Yes, it’s 2.3 now, so not sure if the problem was introduced with 2.2 or 2.3.

    in reply to: Open Sans font loaded repeatedly? #31944
     Patagonia
    Participant

    Thank you sharmstr. Though your first link mentions it was a theme issue, the 2nd link pointed me to this plugin:
    https://wordpress.org/plugins/disable-google-fonts/

    Which seems to take care of it.

    You might want to apply for the 7thqueen job openings 🙂
    Cheers.

    in reply to: Open Sans font loaded repeatedly? #31941
     Patagonia
    Participant

    It is not public yet, but here is the section of the source that is loading it, with the previous and next stylesheet:


    rel=”alternate” type=”application/rss+xml” title=”Website » Forums Feed” href=”http://7summits.ws/forums/feed/&#8221; /><link
    rel=’stylesheet’ id=’open-sans-css’ href=’//fonts.googleapis.com/css?family=Open+Sans%3A300italic%2C400italic%2C600italic%2C300%2C400%2C600&subset=latin%2Clatin-ext&ver=4.0′ type=’text/css’ media=’all’ /><link
    rel=’stylesheet’ id=’dashicons-css’ href=’http://website.com/wp-includes/css/dashicons.min.css?ver=4.0&#8242; type=’text/css’ media=’all’ /><link>’

    (I changed the website URL/title above).

    in reply to: Open Sans font loaded repeatedly? #31892
     Patagonia
    Participant

    Thanks for your reply. I have admin bar (and RT Media) on all pages, but it only loads on KLEO pages that have BBpress enabled (I use the plugin manager plugin, that lets me disable plugins selectively).

    The CSS that comes with BBpress does not include the Google fonts reference, so it must be in the KLEO CSS.

    Thanks.

    in reply to: Open Sans font loaded repeatedly? #31863
     Patagonia
    Participant

    Hi there,

    I am updated to the latest KLEO version, use no Google fonts, but still there is a reference somewhere:
    ‘@import “//fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,700italic,400,300,700”;’

    It is not needed, lowers page rank/score and gives a 404.

    Can you take this out in teh next update and let me know where to find it, so I can remove it for now?

    Thanks!

    in reply to: Editing of thumbnails makes Kleo ignore them #30884
     Patagonia
    Participant

    Never mind, it does not seem to be a KLEO-specific problem as when activating another theme, the problem remains. Will keep on searching elsewhere.

    in reply to: Editing of thumbnails makes Kleo ignore them #30882
     Patagonia
    Participant

    ps: ignore the part of the w=150 addition, that is created by the Bj-lazyload plugin. But even with that switched off, it still uses the 300px non-square version and the problem remains.

    in reply to: Where are uploaded image sized defined? #24798
     Patagonia
    Participant

    I noticed that the problem lies in this part of kleo/functions.php:

    COPY CODE
    	/* This theme uses a custom image size for featured images, displayed on "standard" posts. */
    	add_theme_support( 'post-thumbnails' );
    	set_post_thumbnail_size( 672, 9999 ); // Unlimited height, soft crop 
    	add_image_size( 'kleo-full-width', 1038, 583 );
    

    If I change the last line to 900,999, then the 900pxx version is used.

    Of course I should not edit the Kleo/functions.php, can I just add the above function to the child’s functions.php? Or just the last line?

    Thanks

    in reply to: Where are uploaded image sized defined? #24795
     Patagonia
    Participant

    Hi, coming back to this with a related request:

    I have prepared images to be used as featured images, they are exactly 900px wide. I changed my theme/css so that the featured image/container is this width as well.

    However, after selecting one of these images, a smaller version (that I did not define, for example 769px wide) is selected which is upscaled, which degrades the image quality. If I delete that version, no image is shown, so KLEO is looking for a smaller version, it does not pick a larger version.

    How can I be sure that the full-size version / 900px version is being used as the featured image? Of course I want to use smaller versions for the masonry etc.

    Thanks in advance!

    in reply to: Lightbox not styled for RT-media? #24444
     Patagonia
    Participant

    Fixed it. It seems that somehow the option to use RT media’s layout was switched off in
    /wp-admin/admin.php?page=rtmedia-settings#rtmedia-custom-css-settings

    When I switched that on, the problems went away..

    in reply to: Lightbox not styled for RT-media? #24442
     Patagonia
    Participant

    This did not work for me, not only is the lightbox similarly unstyled (and it has no closing button, only ESC closes it), but also the album lists, images etc.:

    1 The options/upload buttons are behind the upload container (which is always visible) when in initial media mode.
    2 When in Album mode, the list is vertical and with a list-style dot. Options button is now visible, but clicking results in something appearing to the left of the container.

    See screenshot for 1 & 2.

    It’s still on a dev server, so I cannot give a login at this point.
    ps: I switched BWP minify off for this page, but no change.

    Thanks in advance

    Attachments:
    You must be logged in to view attached files.
Viewing 40 posts - 1 through 40 (of 92 total)

Log in with your credentials

Forgot your details?