Forum Replies Created
-
AuthorPosts
-
September 3, 2017 at 7:39 pm in reply to: Whitespace Pro – How do I get post images to show on sites home page? #211073
bamajr
ParticipantBrad, I have used your suggested code a couple times and it works great. However, I'm not sure it is what the OP was looking for. Your suggested code maybe very well solve the OP's problem, but I'm going to ask the same question again, with a little added explanation, in case you may have another solution 😉
Whitespace Pro is an awesome looking theme (found here: https://my.studiopress.com/themes/whitespace/#demo-full) I'd like to see the post's featured images show up on the front/home page, in the post/grid display. I'd like the image to show without text and then, on mouse-over, show the post title and first part of the post.
Do you have an easy solution for that?
bamajr
ParticipantThank you Mr. Dalton.
I actually searched your website for a solution to this but never found the solution you linked.
bamajr
Participant@VictorFont This didn't work as expected, but I am much closer.
I have modified the script as follows:
add_shortcode( 'display_site_url', 'ms_display_site_url' ); function ms_display_site_url() { echo site_url(); } add_shortcode( 'display_site_name', 'ms_display_site_name' ); function ms_display_site_name() { bloginfo( 'name' ); } //* Change the footer text add_filter('genesis_footer_creds_text', 'sp_footer_creds_filter'); function sp_footer_creds_filter( $creds ) { $creds = 'Copyright [footer_copyright] · <a href="[display_site_url]">[display_site_name]</a> · All Rights Reserved · [footer_loginout]'; return $creds; }
...and it returns this:
HTTPS://TEST.CARETOPLAN.NET/7F011FF0-510D-450D-9BD1-2CD5D89A88E9ALZHEIMER'S SPEAKS (CTP) COPYRIGHT © 2017 · · ALL RIGHTS RESERVED · MY WEB MGMT CO. · LOG OUT
I figure I'm not escaping something correctly but trying to modify this has resulted in WordPress' beloved WSoD 😉
bamajr
ParticipantThank you @VictorFont. I think that will work!
bamajr
ParticipantThank you for chiming in @braddalton - always a pleasure.
Yes, I do know how to modify the script to display a specific Site-Name, on all sites within the multi-site network. However, I'm not able to make it dynamically change, with each new website on the multi-site network.
bamajr
ParticipantThank you Ginger for your response. My understanding of the REALTYNA solution is that it is both available with their themes, or as plugins to your own theme (I'm still trying to make sure that is the case, though). They seem to have developed a very nicely integrated system (WordPress, IDX/MLS, Dedicated Mobile App & etc), with very well thought out options.
Never heard of iHomeFinder, until you brought it up. Will definitely have to look into that.
Since you brought up iHomeFinder, does it work well with Agent Focused Pro?
February 14, 2016 at 2:41 pm in reply to: on mobile device the navigation menu lines are not showing #179047bamajr
ParticipantAre you asking about the "hamburger" icon, as seen here: https://developer.wordpress.org/resource/dashicons/#menu ?
bamajr
ParticipantOr...
If you'd like to do it in the functions.php file, check this out: http://www.studiopress.community/topic/shrink-in-centric-pro/
bamajr
ParticipantHad I known I could have done this with a pre-existing filter, I wouldn't have wasted so much time trying to construct a PHP DOMDocument Function. Either I or Google missed this filter, when I was searching for a solution.
Searching for what I thought was going to be PHP DOMDocument Function help, I stumbled across someone who knew the filter it needed (See: http://stackoverflow.com/a/33808160/5581540).
add_filter( 'genesis_attr_site-header', 'my_custom_genesis_header_class' ); function my_custom_genesis_header_class( $attributes ) { $attributes['class'] .= ' shrink'; return $attributes; }
Thank you @silver
bamajr
ParticipantI am able to accomplish my request using standard WordPress Functions (see below):
function custom_site_title() { echo '<h1 class="site-title" itemprop="headline"><a href="' . get_site_url() . '" title="' . get_bloginfo ( 'name' ) . ': ' . get_bloginfo ( 'description' ) . '">' . get_bloginfo ( 'name' ) . '</a></h1>'; }
...though I'm not sure I'm best utilizing Genesis' own Functions.
bamajr
Participant@braddalton - somehow I knew you'd be the first to weigh in. Thanks!
I have a working proof of concept, but I'm wanting to expand on it a little. Maybe you can help with the "expand on it a little" part ? ! ? Below is the code I'm able to accomplish my request with, though not exactly the way I want to do it.
remove_action( 'genesis_site_title', 'genesis_seo_site_title' ); remove_action( 'genesis_site_description', 'genesis_seo_site_description' ); function custom_site_title() { echo '<h1 class="site-title" itemprop="headline"><a href="http://bamajr.com/" title="SITE-TITLE: TAGLINE">SITE-TITLE</a></h1>'; } add_action( 'genesis_site_title', 'custom_site_title' );
This works, but does not correctly use the Genesis defined functions for SITE-TITLE nor TAGLINE. I'd like to echo a statement, which calls the SITE-TITLE & TAGLINE by their Genesis defined function(s) - so that any change to the SITE-TITLE and/or TAGLINE, from within the WordPress Admin, automatically changes what is displayed on the website.
Am I making any sense?
bamajr
ParticipantMaybe take a look at https://easydigitaldownloads.com/extensions/edd-purchase-gravatars/
bamajr
Participant@Summer - I'll be the first to admit, I'm probably not as seasoned in Genesis, as you, or many others, for that matter. I was even late to start using WordPress (started with 2.?). However, I have been developing websites and working on various web projects since the mid/late 90's. In the last few years, I've created several custom WordPress themes and probably just as many custom plugins, including one geo-plugin, which was overly complicated and doesn't currently work with Genesis. So, I understand Genesis does some things differently.
I can tell you, over the last 16-18 months, since starting to use Genesis, it has made my life much easier - though I've yet to convert my geo-plugin (I should really do that). It has made theme development easier. It has made theme customization easier. It has made theme management easier. And, their own plugins work great, and provide real value.
The developer IS experienced in WordPress Plugin development and pretty good at it. However until recently, he knew little/nothing about Genesis, except hear/say. While he is probably elbows deep in it by now, at the time, he had no proof of his claim, just a hypothesis.
Did he have a foundation for suspicion? Maybe - hear/say definitely helped him form a hypothesis.
Did he turn out to be right? I think we can all agree, he did!
Did he turn up with a solution? For the most part, yes!
How did he get to the solution? He had to develop for and test on Genesis, which I'm to understand a good samaritan provided to him. However, until he began testing and developing on Genesis, he was simply blaming someone else. Thus, I stand behind the statement you quoted.
bamajr
Participant@wendypchef the developer of this plugin has issued an updated version, which addressed this issue, beyond the fix, discussed above. If you want a little detail about the update I'm referring to, look at the last few comments here (http://bamajr.us/1bFSaVq) and here (http://bamajr.us/1bFTk3c). There was a "soft" update, which did not change any version numbers. However, I think there was a normal update since then, as well.
bamajr
ParticipantI didn't suggest they were crooks. The only thing even remotely close to that was:
I’m not letting anyone test and troubleshoot their sketchy plugin, on my website, when they refuse to set up a proper dev environment, of their own.
...and even that is a leap!
bamajr
ParticipantLook, I'll side with Copyblogger/StudioPress, 99 times out of 100 maybe even 999 out of 1000 when it comes to issues. Sure, developers are people and we all make mistakes, yes, including myself, however I don't get the blame game, from Copyblogger/StudioPress. They are a results driven organization and the effort they give, to provide a quality product, is second to none, in my book. So when a plugin developer's default response is to say it is a Genesis problem, because the StudioPress developers, didn't follow "WordPress Best Practices" when they created it and then citing a questionable article, that is two years old, I call B$! Which is exactly what I did.
I also call B$, when a plugin developer, with retail/premium add-ons, demands access to my production environment, to find a resolution, instead of buying Genesis himself. This is a sure sign, the developer puts zero weight in the product they have built and sell.
Finally, there is no way, I'm giving a no-name developer, from God knows where, admin or FTP access to my website. If the plugin developer doesn't believe in their product enough to test it on the most popular systems, then they deserve all the heat (or as you say, drama) I give them. I'm not letting anyone test and troubleshoot their sketchy plugin, on my website, when they refuse to set up a proper dev environment, of their own.
I would have had a completely different response to this guy, had he not come out of the gate, blaming Genesis. When, in his own context, he has ZERO idea if it is a Genesis issue, as he doesn't have a way to even evaluate the Genesis code - remember, he doesn't own Genesis, and isn't going to spend $100 to buy it (those were his words).
- - - - -
If you want to thank someone, for actually coming up with a temporary solution, you can thank Jennifer Baumann, a Technical Support Advocate, in Copyblogger Media Support. She presented the original option to me and I forwarded it to InboundNow.
However, even after you put this code in, you don't have to search hard, to find other display and functionality issues, which were also, immediately blamed on Genesis. Funny that this is the first plugin, in over a hundred I've used, which has had these types of problems. Other problems, maybe, but never once, did I hear them blame them on Genesis, before at least, taking the time to look into the problem, themselves.
bamajr
Participant...and if you want a little comedic banter, related to this specific plugin issue, and other issues, with the same plugin, check out https://twitter.com/bamajr/status/430897459607261184
I can't stand those who point fingers.
bamajr
ParticipantThe following code SEEMS to fix the title tag problem…
//* Genesis Theming Framework Fix for WordPress Landing Pages add_action( 'template_redirect', 'child_conditional_actions' ); function child_conditional_actions() { if( 'landing-page' == get_post_type() ) { remove_filter( 'wp_title', 'genesis_doctitle_wrap', 20 ); } }
Add this as the last line in your child-theme's function.php file. Whether or not this plugin is worth all the effort, is yet to be seen. So far, all I find is more problems, all of which the developer blames on Genesis.
bamajr
Participant@Dan must have...
I don't give much weight to the Brimsoft report and I'm not going to put this code in my Genesis Core, which is all I'm actually using right now. So many plugins, which have to modify the title, play nicely with Genesis, except this one. So, I find myself thinking this is more of a plugin developer issue, than a theme developer issue.
bamajr
ParticipantYes, I know I'm responding to my own request, but the developers at Inbound Now have suggested the following fix:
http://bamajr.us/1dZsn4I with an action & function titled "fix_bad_genesis_filter"
add_action( 'after_setup_theme', 'fix_bad_genesis_filter'); function fix_bad_genesis_filter() { // fix for genesis and catalyst framework $priority = ( function_exists( 'genesis' ) ) || ( function_exists( 'catalyst_activate' ) ) ? 6 : 50; add_filter('wp_title','wp_title', $priority, 3 ); }
Currently, I'm only using the Genesis core, on my website and David Wells (From Inbound Now) is suggesting I add this to my theme's function.php file.
I'm curious if this is the right way for their plugin to handle this issue and how Yoast may have handled this exact same problem.
-
AuthorPosts