[David Chu]

Naiara,
¡Que bien! Me alegro.

Hasta la próxima vez,

Ciao,
Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Hola Naiara,
Es un problema interesante. 😉 It sounds like your plugin requires that your theme use the Customizer for the header image.

Previously Genesis themes used a proprietary setting for the header image. Your theme may be doing that now. I don't have that theme, but it may not be prepared to use the Customizer for the header image.

Pero todavía tengo una idea pequeña para Vd. It's done with CSS. Hay un ejemplo aquí.

.site-title a:lang(eu) {
    background: url(http://itsasargia.com/wp-content/uploads/2015/06/imagen-nueva.png) no-repeat !important;
}

Por supuesto mi ejemplo tiene un imagen imaginario. 😉 First you'll want to upload your image for Euskera somewhere on the server. Then make a note of the path to the file, and use it to replace the file path above. Then add the code to your CSS. Appearance.... Edit.

Yo diría la respuesta completamente en castellano, pero no tengo un vocabulario técnico muy grande. 🙂 I hope my solution is understandable.

Un saludo,
Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Hi Bjorne,
I also don't like the "You are here" either, even though I speak English. I just get rid of it completely. Nor do I like the overly colloquial "Speak Your Mind" on a comment screen, but that's another topic. 🙂

Here's a code example that shows what you can do to replace or delete it.

Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Hallo!
Wonderful. I have visited Curacao, and I was thinking about it when I looked at your site. Such a great place. Sigh! 😉

Best, Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Hi!
That's a very good question. I didn't know the answer immediately myself. After looking into it, for some unknown reason, Genesis handles this differently from other themes. You can display the Category Description on a Category page, but it takes a small amount of coding.

Genesis has an extra field you can fill in to do pretty much the same thing. Go to Posts... Categories. Click on your category. Then instead of filling in Category Description, under Category Archive Settings, try putting your text into one of the two fields there, Archive Headline or Archive Intro Text.

Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Hi,
I think I see what you're referring to. Try commenting out or getting rid of this line:

@media only screen and (max-width: 600px) {
.responsive-menu {
display: block;
}
}

Cheers, Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Super! That fix is good for a variety of problems that result in busted links, such as when there's some plugin cache that isn't behaving well.

Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Hi,
You're definitely on the right track. That should work great. You could put that command into any CSS file, including the normal style.css of your theme. If it's not working, you may need to get more specific with your CSS command, or check the syntax of your code addition.

Tables are always a chore, although Tobias' killer plugin does do a great job taming them. You could get a similar effect by using column classes (which your theme probably has) and DIV's. But that's something for another day.

Hope that helps,
Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

I would suggest re-saving your permalinks. Settings... Permalinks... Save Changes.

Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Hi,
As far as I know, they don't announce that, they just slowly get to them. But Associate, wow, that's not even being sold anymore, so I'm going to guess that the answer is no. I had completely forgotten about that theme.

It's certainly possible for a competent developer to make an old theme responsive even if they won't. That being said, it's old enough that you may be better off getting a new one.

Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Hi,
I see your slider sitting there, but there are no slides in it. 🙂 So if you're running it via some selection criteria, either via some slider setting, or a widget setting, I'd suggest you check those spots and re-make your selections.

Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Detroit,
Very nice idea! That could cure Webkit.

Speaking of that, Angela, maybe you already did this, but you'll probably want to test in that nutty IE as well. 😉

Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Hi,
It's a good example of how fonts do vary in appearance, and very skinny ones really stand out as tricky. I can't comment specifically because I don't have a link, so my comments will be very general.

Given what you're saying, this font probably causes some issues for Webkit, which is the engine for those browsers. With any very skinny font, I've found that if you use the smallest size possible, you may have this type of trouble.

Again, I can't see your code, so it may be the font-weight, the font-size, letter spacing, even color, or something else.
If it were me, I would just try bumping up the font size by 1 or 2 pixels, and that would probably get more clarity. The viewers with non-perfect eyesight would applaud, too. 😉

Good luck,
Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Emmtre,
A very clever way around it. Nice job! It's a great example of how there are nearly always multiple solutions for such problems.

Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Hi,
Please keep in mind that I can't see your HTML code or site, so I'm only guessing exactly what you're looking for. 🙂

I'm afraid the ultimate answer is to study the code carefully in markup.php. I found what I call the "wildcard" in this function: genesis_parse_attr

Investigating and testing that will be instructive. The articles you cite do look legit (and similar). Because I used the wildcard bit I was able to stick attributes on things that aren't in their lists! 🙂 But as I said, I could not get any attributes on anything with a non-unique class, or on repeating structures such as 10 ARTICLEs in an archive. I don't know right now, but I suspect this has something to do with array processing, and I don't have time to dig further right now.

I did just do a test with a widget that I coded myself, somewhat like what you have. I tested, but could not alter its attributes, either. So that might be a dead end.

The bottom line: markup.php, while very helpful, is limited.

If I were faced with a dead end in markup.php, and couldn't get the attribute I wanted, I'd "go native" and hand-code a template to make the code bend to my will. 🙂

Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Howdy,
I got curious about this, and cracked the code for quite a few "wildcard" attribute items.

I had a hunch and tested it a bunch. [got to work that into some poem]. Since many types of markup items do seem to respond to a command like yours above, it occurred to me that if there's more than one on a page, the command throws up its hands, essentially, and doesn't work. widget-area may actually work if you just have one on a page!

There are some items that work great, such as site-inner, content, site-container, etc. Even nav-primary works because there's only one (unless you code your theme to have 2 of those, I've done that for submenu coding to have them both styled the same).

But wait, that's not all! It also works on some unique HTML elements, too, such as BODY and HEAD. Some things did not work even though unique, such as HTML and FOOTER. ARTICLE worked on a single page, but not on an archive page, which does make sense, as there are many ARTICLES on an archive page.

Here are examples.

It also possible that regular WordPress filters may help, too. I know that stuff on the HTML tag can be dealt with that way.

Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Hi,
That's an interesting question. I tried your code and a couple variants, but didn't get it to work. As you may have seen, there is a spot in the code that uses a wildcard; it may work with further investigation.

In the meantime, I was able to get something similar to what you're asking for, I think, applying it to the Primary Sidebar, and the secondary can also be done this way, as well as the footer widgets area.

I didn't set itemscope, as it seems to default to true, but it wouldn't hurt to have that. I also added a class, taking care to concatenate it, not just assign it.

Here's the code.

Hope this helps,
Dave, aka Mr. Attribute

PS: great job on finding the funky schema parts in the Genesis update!

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Great idea, Victor!
Besides who can resist font advice from you, obviously? I also like that plugin a whole lot.

You're the man,
Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Interesting. Good luck!

Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

Deb,
I had not seen FontAwesome For Menus before just now. I think I may have found a symptom, if not the cause.

I looked at your Webworks site, and saw some funky icons. Examining the code, I noted that the CSS generated looked incomplete, without explicitly naming a font-family. When I put that in in the Chrome Inspector, the icons showed right up. Below is an example. Your CSS didn't have the font-family line.

.fa-home:before {
    content: "\f015";
    font-family: "FontAwesome";
}

Since things were working before, I imagine the font-family "got through" before somehow. Maybe something in Genesis 2.2 crunched some of the minified CSS, or put something else out of sync.

I did update my homepage to Genesis 2.2, and did not have any problem with Font Awesome, presumably because I hand-coded all my CSS for it.

Sorry, definitely not a solution, but at least it's part of the scenario. I think you're right in waiting for the 2.2.1 version to see if that helps.

Here's a very random idea you could try - it's probably bunk, though. That plugin allows you to change the source of its CSS to a CDN source. Your site is using the plugin's code on your server.

Good luck,
Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[Author]

Posts