Forum Replies Created
-
AuthorPosts
-
March 14, 2015 at 7:56 am in reply to: How to build custom widget area for recipes above related posts #144389WhiteleyDesignsMember
Actually that seems like it would be the perfect solution. Great idea.
https://wordpress.org/plugins/widget-logic/
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberVery interesting feedback. I've had probably 50+ please give me feedback and readability has not come up once. Plenty of other feedback, positive and negative, but not once has readability been mentioned.
I'm not sure what "the wood effect through transparent does my eyes in when scrolling" means either. It hurts your eyes to scroll the page because there is an opaque box over a wood texture? Again, very interesting feedback and I don't see an issue.
I appreciate you taking the time to look and you're certainly entitled to your opinion. Cheers.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressMarch 13, 2015 at 4:54 pm in reply to: How to build custom widget area for recipes above related posts #144336WhiteleyDesignsMembersingle-recipe.php would create a template for a post if she had a CPT (custom post type) called 'recipe'. She is trying to accomplish this based on if the post has a category of 'recipe'.
She would have to use category-recipe.php to do that...but she would have the same issue...she would still need to create multiple widget areas to enable the widget to be placed where she wants it since she wants it between widgets that are all in one sidebar.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberIt can be accomplished via CSS. This article from CSS-Tricks is the code-base I use when styling blockquotes...it should be a good starting point:
https://css-tricks.com/snippets/css/simple-and-nice-blockquote-styling/
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressMarch 13, 2015 at 9:16 am in reply to: How to build custom widget area for recipes above related posts #144296WhiteleyDesignsMemberThe problem is you want to inject the widget between a bunch of other ones all in the same area, so there is no way to wrap the specific widget in something like has_term so it conditionally shows up based on whether the post has the term you are targeting.
You could register a new sidebar area and wrap it in a conditional to accomplish that, but that would be below all your widgets.
The other approach would be to create 2 new sidebars so you would have one that holds all the widgets above the conditional one (you could use the current one for that), the first new one would be specifically for the recipes widgets, which you could wrap in a conditional to display only on posts that have the term you're targeting, then the 2nd new widget you would move all the other widgets into so they show below it.
Then when you aren't on the recipe pages it would look exactly like it does now...but would technically be two separate sidebars stacked on top of each other, and when you are on the recipe post pages it would show as you'd like.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberAhh...I always use page_customname.php - I use an underscore, not a hyphen. That makes sense. Same as when I do a custom archive or single page is is always single-customname.php or archive-customname.php.
So - if you want to have the word page in front you could use an underscore instead and do page_design.php.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberHmm...that's a bit odd that you had to change the page names to get it to work - that shouldn't make a difference.
Anyhow, yes, you'll want to call the sidebar directly in the page template OR you'll want to use the sidebar.php and use conditionals. You'll need to include the sidebar.php file in the page template somewhere, then in the sidebar.php you can use conditionals based on what you want to show on specific page templates.
I hope that makes sense...
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberSo do you have a design page template as well (like page-design.php)? It should look something like this:
<?php /** * Template Name: Design Page * * A custom page template for the about page. * * @package Kim_Schwede */ get_header(); ?> <?php dynamic_sidebar( 'sidebar-design' ); ?> <?php genesis(); ?> <?php get_footer(); ?>
And then, of course, you would need to select that page template when editing the page in WordPress.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressMarch 10, 2015 at 2:43 pm in reply to: How to build custom widget area for recipes above related posts #143947WhiteleyDesignsMemberMy approach, and there may be a better solution, would be to add the widget to all posts, hide it completely with CSS so it doesn't show up at all, the add some jQuery to check if the post being viewed has the class you're targeting, and if so, show the widget.
After adding the widget and hiding it with CSS the jQuery would look something like this:
<script> jQuery(document).ready(function() { if ( jQuery('article.post').hasClass('enter-category-class') ) { jQuery('enter-widget-id').show(); } }); </script>
If you add the widget and let me know what the category you want to target is I can give you a more accurate snippet.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberYou can use rgba on the background of the menu - something like this:
.nav-primary .genesis-nav-menu .sub-menu a { background-color: rgba(0,0,0,0.8); }
The first three numbers are the RGB color code (0,0,0 is black) and the last value is the opacity (0.8 is 80%). Adjust as needed.
This is not supported in some older browsers but has very good support overall and in all modern browsers.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressMarch 10, 2015 at 2:17 pm in reply to: Can Home-Top images and Sliders from Home Page used on other pages? #143943WhiteleyDesignsMemberWithout looking at any of your code, your best bet would be to create a new page template and add in the code to display the Home-Top widget or the call to the slider, then apply that page template to any pages you want to display that stuff on.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberMaybe post the entire code from your page templates so we can see it. As Brad describes, you shouldn't need an about-sidebar.php based on what you're describing since you're pulling in a registered widget directly in the page template.
Or as Brad described...you should include the sidebar.php file, but inside of that wrap each widget call in a conditional statement to pull based on the page template.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberThis post from Bill Erickson pretty much sums up exactly how I migrate from Dev to live:
http://www.billerickson.net/migrating-wordpress-websites/
The key is using the WP DB Migrate plugin which allows for a find/replace on export...so if you're exporting from a dev site you can do a find/replace on the dev URL and replace all instances of that URL with the live site URL.
I develop all sites on my development urls (whiteleydesignsdev.com) as a sub directory, then once the client approves I migrate it using this process.
To sum up:
Move wp-content folder to new host via FTP with a new name (ie wp-content-new) - DO NOT copy over current wp-content folder
Export database and do find/replace to ensure URLs are correct
Import database into new database on new/live host
Update wp-config to point to new database (comment out old DB User, DB Name and DB Password in case you need to roll back)
Change name of wp-content (on live site) to wp-content-old
Change name of wp-content-new to wp-contentIf it breaks for any reason you can simply change the folders back to what they were and put the wp-config back to what it was and it will revert to the old version while you troubleshoot.
Hope that helps...
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMember.page-template-page_landing-php h1.entry-title { text-align: center; }
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberTo center the logo on the landing page add this to your CSS:
.page-template-page_landing-php #title-area { width: 100%; text-align: center; }
The simplest way to stop the link from working on the landing page would probably be to add this to your landing page template:
<script> jQuery(document).ready(function() { jQuery('.page-template-page_landing-php #title a').click(function(e) { e.preventDefault(); }); }); </script>
So your new landing page template code would look like this:
<?php /* Template Name: Landing */ // Add custom body class to the head add_filter( 'body_class', 'add_body_class' ); function add_body_class( $classes ) { $classes[] = 'custom-landing'; return $classes; } // Remove header, navigation, breadcrumbs, footer widgets, footer add_filter( 'genesis_pre_get_option_site_layout', '__genesis_return_full_width_content' ); remove_action( 'genesis_before_content_sidebar_wrap', 'eleven40_page_title' ); remove_action( 'genesis_before_loop', 'genesis_do_breadcrumbs'); remove_action( 'genesis_before_footer', 'genesis_footer_widget_areas' ); remove_action( 'genesis_footer', 'genesis_footer_markup_open', 5 ); remove_action( 'genesis_footer', 'genesis_do_footer' ); remove_action( 'genesis_footer', 'genesis_footer_markup_close', 15 ); genesis(); ?> <script> jQuery(document).ready(function() { jQuery('.page-template-page_landing-php #title a').click(function(e) { e.preventDefault(); }); }); </script>
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberThis would remove the navigation on the page (add to your CSS):
.page-template-page_landing-php ul#menu-primary { display: none; }
I gotta run now but can get back to you later about removing the link from the logo.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberSomething like this should help you out:
@media (max-width: 1023px) { .header-image .title-area { width: 100%; text-align: center; } .header-image .site-title a { width: 450px; float: none; display: inline-block; } }
It is a bit tougher working with that logo in the header as it is set as a background image on the anchor tag. You may need to fool around with this at different screen sizes, but this should be a good starting point.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberA simple CSS solution for the navigation would be this:
.home #header .widget_nav_menu { display: none; }
A better way would be to go into the template that controls the navigation and wrap it in something like this (in a child theme of course) so it doesn't even load the menu (slightly better for performance but not a big difference:
<?php if( !is_home() && !is_front_page() ) : ?> put your navigation stuff here <?php endif; ?>
You could use a similar method of wrapping the anchor tag in the if statement to remove the link from the main logo - but it is probably un-necessary...leaving the link there doesn't hurt anything really.
Sorry I don't know the exact template files for the theme you are using or I would be more specific.
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMemberI certainly appreciate the feedback and you are definitely entitled to your opinion and I'm open to all opinions.
I disagree with a few things - I think the 5 boxes explaining some of the key things I offer and work with are very important and need to be prominent on the home page.
Thanks for the feedback on the Portfolio section on the landing page, I think it turned out pretty nice. I, personally, don't really care what a site looked like before I worked on it as the finished product is the key. Whether it looked good already and just needed a better code-base, or if it was created from scratch and is a new site, or if it was an ugly site that now looks great doesn't really matter to me in the end-game; I simply want the final product to be the focus.
Thanks for the feedback! I take it all, positive or negative, and try to learn from it!
Matt Whiteley – WhiteleyDesigns, GitHub
Designing, Developing & Creating with WordPressWhiteleyDesignsMember -
AuthorPosts