Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-settings.php on line 186

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/backpress/functions.wp-object-cache.php on line 108

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/backpress/pomo/mo.php on line 171

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/functions.bb-l10n.php on line 484

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/backpress/class.wp-taxonomy.php on line 581
Hybrid version 0.8 discussion « Community

Welcome, guest!

Feel free to read the blog, browse for themes, or join the club.

The community forums are currently being phased out. At the end of February or early March 2012, you will no longer be able to post here. This is because the entire site is being restructured. Please use the main forums for discussions.

Hybrid version 0.8 discussion

  1. Would it be a bad idea to remove get_the_image() from all template files and instead hooking it to hybrid_before_entry()?

  2. Edit byline from Hybrid Settings
    Since the default byline will consist of shortcodes in Hybrid 0.8 it would be easy to let people build their own byline just like they build their own footer.

    The only problem is that while the footer is what it is, the byline is contextual. So there would have to be separate page and post byline inputfields.

    I do believe that this would make Hybrid more user friendly because many people on this support forum ask how to adjust the byline or disable certain parts of it.

  3. Off topic: I'd like the pagination on this forum to appear above the first post as well.

  4. Would it be a bad idea to remove get_the_image() from all template files and instead hooking it to hybrid_before_entry()?

    It wouldn't be a bad idea. In fact, it's a great idea and something I've given a lot of thought too. But, there's really no way to do it without messing up a lot of child themes, especially those with custom page templates. 1) Some custom templates already call get_the_image() and will now have two images. 2) Templates that shouldn't have get_the_image() have an image added.

  5. Since the default byline will consist of shortcodes in Hybrid 0.8 it would be easy to let people build their own byline just like they build their own footer.

    It's already possible in 0.7. I just want to cut back on code within Hybrid and use shortcodes as defaults.

    The only problem is that while the footer is what it is, the byline is contextual. So there would have to be separate page and post byline inputfields.

    This is the same issue with or without shortcode, which can mostly be handled with contextual hooks. Unless it's a custom setup that pulls different post types on various pages, singular pages and attachments are the oddballs:

    hybrid_singular-page_byline
    hybrid_singular-attachment_byline
  6. Off topic: I'd like the pagination on this forum to appear above the first post as well.

    With regards to that - I too would like to see it. A handy shortcut is to click Latest Reply in the TOPIC INFO box on the top right in the sidebar of this forum to jump to the latest posts.

  7. Reaction to previous post by Justin
    I'm not sure if you understood what I ment with my byline idea. My idea was too have an extra input field in the Hybrid Settings page just like the one for the footer. I like how basic the hybrid settings are right now, but one extra setting wouldn't hurt.

    Byline settings
    You can add custom HTML and/or shortcodes, which will be automatically inserted into your themes byline.

    <p class="byline">By [entry-author] [entry-terms taxonomy="category" before=" | "] [entry-comments-link before=" | "] [entry-edit-link before=" | "]</p>

    Shortcodes: [entry-author], [entry-terms], [entry-comments-link], [entry-published], [entry-edit-link].

  8. Another idea I've been thinking about is a new shortcode. One that allows logged in users to see a 'Delete this post' link depending on their role. [entry-delete-link]

  9. But, there's really no way to do it without messing up a lot of child themes, especially those with custom page templates.

    This will probably sound stupid, but is it not possible to check if a function has already been called for before executing it?

    The big disadvantage of having get_the_image() in template files is that I have to make and edit my own template files instead of making some small adjustments in my functions.php.

  10. I'm not sure if you understood what I ment with my byline idea. My idea was too have an extra input field in the Hybrid Settings page just like the one for the footer. I like how basic the hybrid settings are right now, but one extra setting wouldn't hurt.

    I'm trying to get rid of settings here! ;)

    I misunderstood though. I honestly have a few issues with an extra setting for the byline:

    • I don't want to run the risk of the slippery slope dilemma (one setting wouldn't do it, but that's how it starts).
    • Not all child themes have a byline, so the setting itself might confuse people when they see nothing showing up.
    • Your concern: How to best handle context.

    Plus, the next major version of the Hybrid Hook plugin will incorporate filter hooks and not all be based on action hooks. So, there'd be an option to change the byline from the admin.

    And, there's the Hybrid Byline plugin:
    http://wordpress.org/extend/plugins/hybrid-byline

    I'm mostly just a big fan of putting these types of things into a plugin and leaving things as open as possible for child theme developers.

  11. I loved your article about the slippery slope. You win.

    New idea:Template for multiple taxonomies
    Let's say I'm browsing the Pop Critics Movie Database and I'm looking for funny movies starring Brad Pitt. I get all funny movies when I select the Funny in the Genre taxonomy and I get all Brad Pitt movies when I select Brad Pitt in the actors taxonomy. Wouldn't it be cool if we could use custom taxonomies for narrowing down results?

  12. Integration of the new comment_form() function

    WP 3.0 will have a new comment_form() function to completely display the comment form. I was a bit angry because I just created the hybrid_get_comment_form() function in Hybrid 0.7, and this new functionality just erases all that work.

    There's some things I do and don't like about it, but it definitely needs to be used. Plus, I've already thought of some cool comment form plugin/functions.php tricks that could come in handy.

    So, we're deprecating hybrid_comment_form() and removing the comment-form.php template.

    This also means that the hybrid_before_comment_form and hybrid_after_comment_form hooks will have to go. I'm just not seeing any good way to add them in using this new method.

  13. Ability to have hybrid language files in child theme folder
    I have no idea if this possible, but having translation files for ThemeHybrid in my child theme's folder would be really nice. Maybe a hierarchy just like it works with templates? If translation not found in child theme folder, search the hybrid folder.

    Child theme translations could be called [childthemename]_en_EN.mo. The general translation would be called hybrid_en_EN.mo.

    Why? Because every time I upgrade to the latest version of Hybrid I loose my translation file. I could ofcourse update all my Hybrid powered websites manually. But that would mean ThemeHybrid is limiting the WordPress ease of use I love so much. Besides that: language files with self-explanatory filenames make life easier.

  14. RE: Ability to have hybrid language files in child theme folder

    Thanks for reminding me of this. I keep forgetting about figuring out a way to do it.

    I just committed some code changes that checks for the file in this order:

    • child/languages/$domain-$locale.mo
    • parent/languages/$domain-$locale.mo
    • child/$domain-$locale.mo
    • parent/$domain-$locale.mo

    For optimum results, you'd place your hybrid-en_EN.mo (for example) file in a /languages folder within your child theme.

    And, you must use the hybrid- prefix. This is the only way to keep from conflicting with a child theme translation. This steps a bit outside of the normal theme translation process, but it's okay. I just switched from using load_theme_textdomain() to dropping the file names into load_textdomain() myself.

  15. Navigation links for custom post types

    I know many of you will start using custom post types with WP 3.0, so this should be considered.

    Should the Next/Previous links be shown for singular views of custom post types? Currently, this is done for the posts but not pages. I'm kind of leaning toward not showing them, but I'm also a fan of having them in some scenarios.

    Off or on by default?

  16. Re: Navigation links for custom post types
    Off if you ask me. I'd rather enable this feature when I want it, than disable it for all the situations where I don't want it. This is my general opinion.

  17. Hello Justin and friends here.

    I'm putting in one feature request for the next release of hybrid theme framework

    Ability to disable all feeds in the theme setting page.

    Although, this could be or should be in childtheme
    but since hybrid already offers alternate feed address
    and also the option to direct category, author, tag, search to that address,

    So if it would be great to have one simple click to completely remove all feeds.

    A lot of websites using WordPress are not blog, they are simply static pages.
    This option will surely make it easier for user to disable feeds.

  18. My Snippet Body Class

    This may be more fitting for an update to the My Snippet plugin, but I figured it could go hand in hand with 0.8.

    When using My Snippet the body class changes from inactive-primary to active-primary. This works fine on any pages that have a snippet in place, but those that don't just have a smaller content area and blank sidebar.

    So I'm suggesting that when a page/post has a snippet a body class be added, like has-snippet. This way my CSS can look like this:

    .content ( width: 900px; }
    .has-snippet .content ( width: 600px; } .has-snippet #primary { width: 300px; }

    Of course there's more to it than that, but it paints the picture.

  19. It would be great if there is a class for the first and the last item of the top menu...or make it easy to add separators between the top menu items - maybe some kind of filter or something :)

  20. RE: Ability to disable all feeds in the theme setting page.

    I really see this as more as plugin territory. Plus, I want to shy away from adding any theme settings.

    but since hybrid already offers alternate feed address
    and also the option to direct category, author, tag, search to that address,

    This is mostly legacy stuff from the earliest Hybrid days. Honestly, I'd like to get rid of it too.

    Getting rid of feeds is an entirely different thing from changing a few URLs as well. There's a lot more code involved.

  21. RE: My Snippet Body Class

    Yep, this is something that should be done via the My Snippets plugin. I'll see about adding that to the plugin.

  22. It would be great if there is a class for the first and the last item of the top menu...or make it easy to add separators between the top menu items - maybe some kind of filter or something :)

    I agree about the first/last menu item classes (though it can be tricky with the "Home" link). We'll have to wait and see what happens with the menu management system as it moves along in WP.

    As for separators, It should be relatively easy to add those now.

  23. I agree about the first/last menu item classes (though it can be tricky with the "Home" link). We'll have to wait and see what happens with the menu management system as it moves along in WP.

    As for separators, It should be relatively easy to add those now.

    Yes it relatively is, I am doing it with this hack:

    add_filter('wp_page_menu','add_menuslash');
    
    function add_menuslash($menuslash) {
    
    	return preg_replace('/li><li/', 'li><li>/</li><li', $menuslash, -1); 
    
    }

    BUT it adds it also between the subpages in the dropdown :( (so I have to use only one level menu)

  24. Menu Separator

    Might it just be easier to add a separator using css? A background image of a slash or whathaveyou. I would think that would make more sense than altering your HTML for design reasons.

  25. Get the Image alt text

    If an attachment image is pulled (not custom field option), the post_excerpt field for the attachment will be used for the image alt text.

  26. Sitemap for Custom Taxonomies

    Unless it's a site-specific issue for me, the SiteMap Page Template doesn't include custom taxonomies and I think this would be an appropriate addition as the use of custom taxonomies becomes more common. (Thanks for the blog posts about taxonomies BTW - worked like a dream.)

    Kate

  27. Meta Description

    Regards the "Slippery Slope Dilemma" and the Hybrid's metadescription.

    I would like to know if this ( Hybrid's Meta) will be kept and supported ?
    How do you plan about it ?

    Will this be discontinued in the future at all ?

    as for me, I REALLY like this to be there forever !

    If you haven't had any plan on this , please consider keeping it.

    Thank You.

  28. Body Classes

    Just a very simple add-in - the auto generated body classes include (amongs others) eg: y2010 m02 d25 h15

    You gave me some nifty code for my functions.php to also deliver : w08

    How about including as standard - I can then reduce my functions.php a little...

    Cheers

  29. Intelligent Navigation Classes

    I'd like to have some conditional CSS classes in my navigation for more complex styling.

    Currently the classes output in the <li> are page_item, page-item-{ID}, and current_page_item.

    I'm proposing the addition of the class has-children when a page has child pages and a class specifying how deep the children go: depth-{levels}.

    So this navigation structure:

    • Home
    • About
      • Child 1
        • Grandchild 1

    ...would end up being:

    <ul>
    	<li class="page_item page-item-1 current_page_item">Home</li>
    	<li class="page_item page-item-2 has-children depth-2">About
    	<ul>
    		<li class="page_item page-item-3 has-children depth-1">Child 1
    			<ul>
    				<li class="page_item page-item-4">Grandchild 1</li>
    			</ul>
    		</li>
    	</ul>
    </ul>
  30. RE: Intelligent Navigation Classes

    I'm not sure how possible this would be from a theme in 3.0 because we'll be moving to the new Menus system.
    http://core.trac.wordpress.org/ticket/11817

    I would definitely throw this idea into that ticket for consideration.

Reply »

You must log in to post.

Topic Info