Hennessey Digital

Forum Replies Created

Viewing 15 replies - 16 through 30 (of 78 total)

  • This are called shortcodes: 

    [etheme_featured]
[etheme_new title="Latest Products" ]

    If you use these in your theme file directly, use them this way:

    <img src="<?php echo do_shortcode('[etheme_featured]'); ?>/images/assets/b2.jpg" alt="" />

    or

    <div class="clear"></div><?php echo do_shortcode('[etheme_featured][etheme_bestsellers][etheme_new title="Latest Products" ]'); ?>

    since your images directory is right inside your root directory, I would suggest using the following for calling images:

    <img src="<?php echo site_url(); ?>/images/siteart/logo_banner.png" width="780" height="180" >

    The result of which will always point to: https://jmdesantis.com/images/siteart/logo_banner.png

    Hi Brian,

    You could try editing the header.php file and looking for the following line:

    <h1 id="logo"><a href="<?php echo home_url(); ?>" rel="nofollow"><?php bloginfo('name'); ?></a></h1>

    Should be somewhere in the bottom third of the file.

    Change it to:

    <h1 id="logo"><a href="<?php echo home_url(); ?>" rel="nofollow"><img src="https://yoursite.com/logo.jpg" alt="Logo"></a></h1>

    NOTE: best practice way is to do your theme modifications via a child theme. This makes it so that any updates to the theme does not overwrite the changes you’ve made to the theme. Here are a couple resources for making child themes:

    https://wp.tutsplus.com/tutorials/theme-development/child-themes-basics-and-creating-child-themes-in-wordpress/
    https://codex.www.ads-software.com/Child_Themes

    or, you could use more specific selectors.. something like:

    body div#container_wrap{}

    but, yes, @alchymyth is right in that if the child theme is loaded right, you should have no problem using the same css selectors as the parent theme.

    @esmi,

    I’m not saying it’s the incorrect way. In fact, this is how I load stylesheets in my themes.

    But, my fault as I failed to elaborate how the parent theme could have messed it up. This would have happened if the parent theme referenced the stylesheet using:

    get_template_directory_uri() . '/style.css'

    instead of

    get_stylesheet_uri()

    So, if you child theme only has style.css file, then your child theme’s stylesheet would never load.

    That’s all I’m saying.

    And oh, would you agree that linking to the stylesheet in the <head> is how most themes do it? although it’s not the recommended way?

    Please post a link to your website.

    Try removing the function delicacy_page_menu_args() from your functions.php file in the child theme.

    One reason could be because the child theme’s style.css file isn’t being loaded. This may when the parent theme loads the stylesheet using wp_enqueue_style() instead of hardcoding it directly inside the <head> section.

    Try adding the following inside your functions.php file:

    add_action('wp_enqueue_scripts', 'spun_child_load_css' );
function spun_child_load_css(){
    wp_enqueue_style('spun_child_style', get_stylesheet_uri());
}

    Hi it seems like there is an error where it says:

    Error: report folder '/var/lightsquid/report' not contain any valid data which is where the post titles start to disappear.

    You might also wish to include link to this website on your future posts.

    Thanks

    regarding #3, actually it may be possible, but it would require convoluting the html to add graphic hooks for the css3 stuff. and even then, we’d still need some images (albeit smaller this time).

    Anyway, what grade did you receive in YSlow and Google page speed for the images?

    hi @drashok,

    oops! yes it’s living-journal not “live” ??

    #1. if you wish to call the parent stylesheet – style.css – using functions.php in the child theme, I would suggest the following code:

    function livingjournal_child_load_css(){
        wp_register_style('livingjournal_parent', get_template_directory_uri() . '/style.css');
	wp_enqueue_style('livingjournal_child_style', get_stylesheet_uri()', array('livingjournal_parent'));
}
add_action('wp_enqueue_scripts', 'livingjournal_child_load_css');

    no need to put @import in the child style.css file.

    #2. Inside the theme folder, there is a file called changelog.txt. This contains the summaries of the updates.

    #3. Thank you for the compliment. But, no, we can’t use css3 since the design we require cannot be duplicated using css3 alone.*

    before the theme was updated to v1.5.2, did you make a copy of the header.php file and after the update, copied the contents of the old header.php file to the newly updated one?

    I’m not sure what happened to your installations, but checking the source code in your website @lavishbride, the code that’s showing up is code that is in v1.5.1 where the search form is right below the site title.

    <div id="inner-header" class="clearfix">
<hgroup id="site-heading">
	<h1 id="site-title"><a href="<?php echo home_url( '/' ); ?>" title="<?php echo esc_attr( get_bloginfo( 'name', 'display' ) ); ?>" rel="home"><?php bloginfo( 'name' ); ?></a></h1>
	<h2 id="site-description"><?php bloginfo( 'description' ); ?></h2>
</hgroup>
<?php get_search_form(); ?>

    while on v1.5.2, the call to <?php get_search_form(); ?> is done after the main navigation and uses css to position it to the top right corner.

    This is why I thought you were using a child theme and copied the old header.php file from v1.5.1.

    Anyway, can you try switching to a different theme then switch back? see if that clears things? If you have a caching plugin installed, could you clear the cache too?

    To make your home page different, you can create a front-page.php file. Copy the contents of the single page to the front-page.php file and and take out the sidebar from there.

    Thing is, the differences in the code is due to the change in defining custom headers in WP3.4+. The code you currently have from 3.5.1 is the new (and correct) way of defining custom headers.

    This section:

    if ( ! function_exists( 'get_custom_header' ) ) {
		// This is all for compatibility with versions of WordPress prior to 3.4.
		define( 'HEADER_TEXTCOLOR', '' );
		define( 'NO_HEADER_TEXT', true );
		define( 'HEADER_IMAGE', $custom_header_support['default-image'] );
		define( 'HEADER_IMAGE_WIDTH', $custom_header_support['width'] );
		define( 'HEADER_IMAGE_HEIGHT', $custom_header_support['height'] );
		add_custom_image_header( '', $custom_header_support['admin-head-callback'] );
		add_custom_background();
	}

    is only there for compatibility with old wordpress version less than v3.4. If you notice, this is the old way and one that the tutorials uses. but this is out dated.

Viewing 15 replies - 16 through 30 (of 78 total)