444

[Admin]

In reply to: Upgrading to 1.4.1 leads to loop.php error

#16051

What files do you have in your child theme (if you’re using one)?

[Admin]

In reply to: Home Page Sidebar

#16045

You still can. Just target the CSS to the front page elements only by prefixing every selectors with the .home class. Example:

.home #sidebar1 {}

instead of just:

#sidebar1 {}

[Admin]

In reply to: Thanks!

#14973

@Orlik,

Wow…you really transformed the theme! I wouldn’t call it “a bit of editing in the CSS” 😀

[Admin]

In reply to: How to remove shadow (or strong?) on menu's item ?

#16054

You can do this:

#header-menu > li > a > strong {

font-weight: normal;

}

[Admin]

In reply to: Bug: 'read more' buttons – filters in code

#16040

Thanks for the heads up on the typo!

However, I can’t seem to reproduce the bug you mentioned. It works just fine when Itried with these settings:

1. Show excerpts on front page

2. Give a post a manual excerpt (tried both long and short excerpts)

3. Enable Read More link for manual excerpts

[Admin]

In reply to: Home Page Sidebar

#16043

You can do this if you’re using a Static Front Page. Otherwise, you can use CSS to swap the positioning of the sidebar.

[Admin]

In reply to: Mobile Issues

#15993

Quote:

Regarding the sticky posts order, I believe they are ordered by their last update timestamp instead of their published date. Would be nice if you use their published date for the order so they follow the ordering of the other recent non-sticky posts.

I still couldn’t reproduce this bug. I just tried updating one of the sticky posts in my dev site for the theme and the sticky posts order still follows the Published timestamp, and not the Updated timestamp.

In any case, the theme itself doesn’t modify the order in which posts are displayed on the front page. It just uses the WordPress default order, which is chronologically according to the published date in descending order.

[Admin]

In reply to: Theme images set to expire headers how?

#16038

Hurm..from what I know, the expiration not set problem usually occurs when the static content is served from another server or domain, hence the expire headers on your server’s .htaccess files are not served from them.

I have the same plugin W3TC applied on the theme’s demo page, and all of the theme’s static contents have the proper expire headers set, so it shouldn’t be an issue with the theme. Perhaps you can try clearing your browser cache (CTRL+F5)?

[Admin]

In reply to: Theme images set to expire headers how?

#16036

Are you using any CDN with W3TC? Also, I can’t seem to access your website. It’s forever “Waiting for wowmobilemadness.com…”

[Admin]

In reply to: did I delete the five small buttons on slider?

#16034

Okay, first of all, there’s no such thing as display: fancy; in CSS. It doesn’t exist. You can’t use it 🙂

Secondly, did you modify the theme’s style.css file? If you did, it’s a bad way to customise the theme cause you’re gonna lose those changes next itme you update the theme, and you’re gonna have to restore the part that you have accidentally deleted to get those small round buttons again. It’s probably this chunk:

.slider_nav a,

.slider_nav a:visited {

background: url(images/sprite_master.png) -80px -37px no-repeat;

display: inline-block;

margin-left: 3px;

width: 12px;

height: 12px;

}