541

[Admin]

In reply to: in focus @ stillworx.com

#11872

I believe it’s due to Firefox’s CSS rendering engine not being optimised for CSS3 yet. The new look utilises quite a lot of CSS3 to enhance the visuals with the highest flexibility,

That’s also the reason why in Firefox, the container doesn’t have a drop shadow. Try viewing it in Chrome or IE, and the drop shadow will be there, but you probably won’t notice it in your website since it has a dark background. It looks better with the drop shadow, but I have to scrap it off for Firefox or the slider will be noticeably slow.

[Admin]

In reply to: Is there a way to roll back latest update?!

#12529

Which blue header are you referring to? And which navigation column are you referring to that the blue header is not spanning the entire width?

There’s actually a lot more going on in the latest update besides the cosmetic changes, so I don’t recommend rolling back to the previous update. You might want to take a look at the changelog before rolling back. And if after that you still decide to roll back, here’s the link to version 1.1.3.1: http://wordpress.org/extend/themes/download/graphene.1.1.3.1.zip?nostats=1

Also, on a side note the cosmetic change of the sidebar is necessary to prepare the theme for future updates which will add more layout options that will allow the user to choose between different configurations of one-, two-, and three-column layout. Especially with the three-column layout, the width of the content area will be small, so the sidebar styling has been changed to remove wasted layout space and allow for the content area to be expanded.

In the next update, the theme’s total width will be expanded to 960px from the current 900px, so definitely there’ll be some disruption to current theme users who have been using custom header images. But all that are necessary to accommodate a more flexible layout options, and also to have increased content area width, which can’t be bad.

But if the current version has been working fine for you, and you have no use for the new features implemented in 1.1.4 and the planned features ahead, then by all means you can continue to use the current version 1.1.3.1.

[Admin]

In reply to: gravatar image cut off

#12527

Yep, noticed that as well and will be fixed in the next update.

[Admin]

In reply to: Saved custom edits

#12525

The best and recommended way to go is really to use a child theme.

[Admin]

In reply to: Saved custom edits

#12523

The only way is to use a child theme for complex edits. For purely CSS edits, you can use the new Custom CSS feature in the theme’s Display options page. It should be obvious that editing the theme’s files directly (even by using the WP editor) will cause the changes to be lost when the theme is updated.

[Admin]

In reply to: Text wrap around

#12512

Align the image to the left or right?

[Admin]

In reply to: Latest theme

#12237

The XHTML validates just fine.

The warning in the options page has already been fixed and will be made available in the next update.

As for the cosmetics, you can always change it to however you like it using custom css.

If you don’t like the new version, you can always revert back to the previous version: http://wordpress.org/extend/themes/download/graphene.1.1.3.1.zip?nostats=1

[Admin]

In reply to: Pages who don't appeared in my menu

#12303

In the Custom Menu options page, slide the menu item that you would like to appear as the second level a little bit to the right.

[Admin]

In reply to: rtl/arabic

#12091

Hurm..it seems that you have done everything right, but somehow WordPress is not loading the child theme’s rtl.css file.

In that case, just add this line right after the @import url("../graphene/style.css"); line in your child theme’s style.css file:

@import url("../graphene/rtl.css");

It’s a hack, and adding that means that your child theme will always load the rtl.css file, regardless of the language being used.

[Admin]

In reply to: Help with Changing Colors

#11942

In the theme’s Display options page, insert this code into the Custom CSS section:

.featured_slider{

background: -moz-linear-gradient(left top, #333, #aaa);

background: -webkit-gradient(linear, left top, right bottom, from(#333), to(#aaa));

background: linear-gradient(left top, #333, #aaa);

-pie-background: linear-gradient(left top, #333, #aaa);

}

.sidebar h3{

background:#3C9CD2;

background:-moz-linear-gradient(#aaa, #555);

background:-webkit-gradient(linear, 0 0, 0 bottom, from(#aaa), to(#555));

background:linear-gradient(#aaa, #555);

-pie-background: linear-gradient(#aaa, #555);

border-bottom:1px solid #444;

}