Hey schoenj!

I suggest to use the free Codestyling plugin to translate the theme or to change the content of the current translation. Install the plugin ( http://wordpress.org/plugins/codestyling-localization/ ), go to Tools > Localization and select “Themes”. Then search for “Enfold” in the list and select your language and click the “create po-file” button. Click on “Rescan” to search for all text strings. Afterwards click on “Edit” and translate the required strings from the “avia_framework” textdomain. At least click the “create mo file” button next to the “Textdomain” selection dropdown (top left corner). Search for “Leave a Reply” and “Want to join the discussion?”, etc to translate the comment text strings.

Cheers!
Peter

Hey!

1) I think it’s easier to solve the issue by setting a background for the entire page.

The reason for the white background instead of the background image applied universally is because when I apply the background universally, no color sections apply a new color or background image.

Please apply the background universally and post a link to a color section which doesn’t work. I’ll investigate the css code and check why the color section doesn’t work.

2) Kriesi uses the “large responsive” layout (with 1210px width). You can configure it on the theme option page ( Enfold > General Settings). If you want to stretch the forum content area to 100% insert this code into the quick css field:

#top .forum-archive .entry-content {
width: 100%;
margin-left: 0;
}

3) I’m not sure if Kriesi uses a custom widget or a standard bbpress widget for the login area. I’ll tag this thread for him and ask him to comment on it.

Cheers!
Peter

Hi!

Ja, bitte, da ohne Test Account der Fehler schwer zum testen (und beheben) ist. Ich konnte den Fehler auf der Demoseite nicht reproduzieren ( ). und auf deiner Seite sollte dieser Code funktionieren:

.avia-msie-8 #top .header_bg{
background: #fff;
filter: ;
}

Ich konnte diesen aber nicht testen, da das dynamische Stylesheet diesen nicht übernommen hat.

Regards,
Peter

I’m not even sure if this is a good idea because of potential downsides, but I may have a suggestion to improve the mega menu editing interface. It’s probably one of the least important things possible to worry about, but hey, might as well post it.

I actually think what you have now is really great and very functional, but it’s a little odd from a UX standpoint. You can tell it’s engineered to get around WordPress’ limitations (which is not your fault of course). Check a box to make a mega menu, and suddenly pages or custom links turn into columns. Drag them in a level deeper, and they’re pages and custom links again. Check another box, and now the description is a thing you can use to put custom content in. Not bad, just kind of weird.

Some months ago, a little-known plugin was released called Big Voodoo Mega Menu & Related Links Menu. While it falls flat in its front-end implementation, the back-end is pretty good. Here’s a look at it. Columns and what Enfold calls text blocks are their own separate elements, with their own properties, and I think it works well.

Downsides vs. the current Enfold way are:

• It’s not as easy to link to a page from a column heading (since you can’t just make a page also a column with this method)
• Pages and text blocks can be on the same level as columns, which would be layout chaos
• There’s nothing stopping you from making a column or text block a top level item, which would also be layout chaos.

But maybe there’s a clever way to solve those issues, like still doing the “page becomes a column” thing if a user is absolutely insisting, and a JavaScript check to keep columns inside the second level and text blocks inside the third level (although what do you do about adding them to the menu initially?). And, on the other hand, maybe it’s not a big deal, and users will use the tools as intended.

Anyway, I think it’s more intuitive, but a lot easier to break, so I’m not sure if it’s a useful suggestion. I’ll let you decide.