Hmm maybe all those linebreaks are confusing the poor old IE 8. I don’t believe it’s the length that matters as we use quite lenghty lines in our themes.
Try stripping all unnecessary spaces and line brakes on css output.
/\* there are no custom styes \*/Shouldn’t it be like this:
/* there are no custom styes */
Just discovered something new, if you use WP 3.5, then do wp_enqueue_script( ‘media-models’), then you have a convenient wp.media.ajax available for use, and you don’t have to specify the admin ajax-url anymore. The only drawback is that this is only compatible with WP 3.5+
Why would you want to support < 3.5 in your new products, just a hassle.
Everyone should upgrade to the latest WP version.
Nope, regular licence will do in such situations.
XanderRock saidI’m all for standarization but stuff like this is not a good idea.
I’ve listened the radio show a few days ago. Couldn’t listen from the beginning but there were a discussion about shortcodes. The problem was when a user switches to another theme, all of the shortcodes of the old theme will be garbage. Nonsense texts. I was keep asking the main reason of these changes. If this is the main reason of the shortcode changes. I’ve got this idea ;
How about, if we make a shortcode list. That all of the authors will be using the same shortcode with same attributes. For example a map shortcode could be something like ;[googlamap lat="" long="" type="" zoom="" scroll="" width="" height=""]If the reason of the changes is to keep the user based content, then user will be able to use his/her content with the new theme with different style. But ofcourse these shortcodes must be organized very well. I’m sure I’m missing a few more attributes on this example map shortcode. But with a good research we can have a shortcode list that will be useful for everyone.
1.) You limit everyone to the same list of shortcodes 2.) You are making everyone (even those that don’t use shortocdes in their themes) to support those shortocdes 3.) You can’t affect marketplaces other than TF
Also used Chrome, no problems.
Done, when do I get my survey ninja badge?
I actually love your theme design very much. I’m a big fan of minimal designs like yours so high five.Issues in my opinion:
- Images in homepage carousel are not resized (you load full version instead of cropped ones) causing unnecessary long page loading
- Contact form button is an image (how are users supposed to translate that?)
- Contact page is too simple and does not look as good as the rest of the layout (maybe incorporate google map somewhere, that’s pretty much standard these days).
- Button shortcode (first in line, the grey one) has white text on hover making it impossible to read the button text
And my last sugestion would be to implement few more layouts for blog/portfolio, for example with single column ot three columns.
OriginalEXE saidMy theme has a static width, and that’s the point, not every user knows about row-fluid so it won’t be just switching themes to make the plugins portable.
nagaemas saidWhy don’t you use row-fluid?
You’ll get a mess, for example Bootstrap columns on Twenty Eleven won’t fit in its main container as a row on Bootstrap is 1200px, the columns will overflow/vertically stacked.
I understand but can’t you still use row-fluid?
It’s not like .row is deciding on your container width so switching it for row-fluid should change nothing.