Forum Replies Created
June 11, 2015 at 1:19 pm in reply to: Formidable Pro Security Fix Disables 3rd Party Shortcodes #155886
Thanks for working that out, Victor. I love Formidable!October 28, 2014 at 12:18 pm in reply to: Genesis (or Winning Agent) Custom Menu widget only Home Page? #129623
I love this community!
Brad--I didn't know about that plugin. I'll need to remember that!
Jackie--Yes, that was exactly the kind of code solution I was looking for but much more elegant than what I had in mind. It works great!
Thank you both!
You beat me to the punch! I was going to ask if Denali got delayed because Brian decided to evolve it into something better.
Really glad we have a Genesis-based parallax theme to add to the arsenal.
Any ETA on Denali Pro? I have a new account that dropped into my lap that I would LOVE to put it on!
Ditto. I had it earmarked for one of my clients but I think we have to move forward with another child theme at this point. Not the worst fate in the world, but still...
My glass-half-full view is that it is being held up to make it super-amazing!
I'm bumping this just in someone has come across a solution.
Executive summary: Using the Ayoshop theme, wherever I have a main menu with a subitem dropdown and there is an embedded YouTube video underneath, the video frame immediately covers up the dropdown only for people using Windows Google Chrome.
No other browsers seem to be affected. As you can see in the thread above, I've done all the usual fixes. I just can't find the class/ID/z-index combination that will fix this, if that is indeed the way to do it.
Here's the example. Hit the link and then mouseover "collections." If you're using Windows Chrome, the problem will occur MOST of the time.
Thanks for all insights!
SO happy to learn about Manual Control! Thanks for the tip.November 14, 2013 at 5:40 pm in reply to: Do I edit a purchased child theme's files, or edit a child of that child theme? #73026
I'll be the contrarian, I guess. I think it's a good practice to routinely make child-of-a-child themes, or grandchild themes, or whatever you'd like to call them--even if it's only a custom css file.
First, it's a trivial thing to do. Second, it may be Studiopress's unofficial practice but not a stated policy to rename its themes when they update them. There's no guarantee that they won't find a reason to correct a few things in, say, Magazine Pro from v3.0 to 3.1 tomorrow and push that out.
More important, StudioPress isn't the only company that makes Genesis themes. I recently build a site using Ayoshop, which updated while I was in development. No problem, though--all my changes were tucked into a grandchild theme folder.
Finally, it makes it easier for me to deal with an extensively-changed site knowing that 100% of my changes are in one place and that 100% of the code in a particular file are changes I've made. I just think it's faster and more efficient.
Or maybe I'm just really anal-retentive, One or the other.
Interesting theory. I may grab my partner's Mac and try. I have the same problem on PC and I just keep hammering each drop down until it "takes" my option.
If Nick has given up on the plugin, I do hope someone takes ownership of it. It is SO useful!
Ha! Definitely different strokes..., etc. I took one look at Magazine Pro and said, "there's my next blog." I'm going to break it out as soon as I finish my current project.
@Landon Well, I'll be darned. It looks like I almost fixed it.
Since I've been working on the problem, I've only been checking the results in Chrome. My best guess is that when I changed the php code from wmode=transparent to wmode=opaque in the plugin I referenced, it fixed the problem in all other browsers. You're right--I've checked in IE, FF, and Safari and the menu drops down just fine.
However, in Windows Chrome the problem seems to persist. Sometimes the menu will drop down OK, but on most occasions it will disappear behind the frame. I wonder why that browser is different and what fix I would need for that?
@emasai Thank you. However, as my original post and above reply implies, the iframe always had wmode=transparent. I changed the code to wmode=opaque which has apparently fixed 90% of the problem. The problem with Windows chrome remains.
Go, Brian, go!
@sssv--I'm trying, but my CSS, etc. skills consist of banging on the keyboard like a happy monkey until something works. I'm not sure that's the prescribed method.
@Summer--I hope some Genesis themes with a little voodoo come our way some time. However, DenaIi--I love that!
And if you use Woo Commerce with Genesis and have the Genesis Connect Plugin working to help that, those things have a little contention with Genesis Simple Sidebars, which I had to investigate and solve – just an FYI!
Ah, well it turns out that I am! So maybe that was a contributor as well. I'm using the Ayoshop theme, which has been very good so far--although, yes, I've had to be resourceful a few times!
What was tripping me up was not selecting Blog as the template. It seems like all three of those things--correct template, correct sidebar, and unselected Settings->Reading option need to be in place before the excerpts show up with the correct sidebar! I have them now. Thanks again.
I appreciate the advice!
I'm probably being overly careful. Still, I would argue that the "child theme of a child theme" makes sense in the Genesis case, since the child theme is the one we're operating on. I'd argue that whatever logic makes it a good idea in the rest of the WordPress world, holds up here. The child theme I've been using (Ayoshop) has updated itself on occasion, and it would be annoying if my code got overwritten in the process. My custom CSS is safely off in another directory while the original style.css is pristine.
However, the second problem may not be as easily solved. What I think I've learned up to this point is that WP is going to load and try to execute that separate, child-of-a-child functions.php first, before the parent functions.php. Because of that, It doesn't know how to execute any functions it finds there and that's why it aborts. Therefore, even though the include statement works, it doesn't!
Since this is a nice-to-have and not something I'm desperate for, I think I'll just keep putting whatever functions I need in the parent file for now and make sure it's backed up so i don't get caught by an update.