[torb]

I will manually download and overwrite the theme with the latest version from Themeforest, if you are not able to confirm you do not see the badges. If you do not see them, it of course has to be something wrong with my browsers.

[torb]

This reply has been marked as private.

[torb]

Thank you, I sometimes go blind in the settings – they are everywhere 😉

[torb]

Yes, thank you! What settings? I would like to know, so I know what to do next time 🙂

[torb]

Icon

Attachments:

You must be logged in to view attached files.

[torb]

This reply has been marked as private.

[torb]

Like in your demo shop four: http://cardinal.swiftideas.com/demos/#shop_four

[torb]

I am quite sure it is styled like the cart and wishlist icon in your demo, when set to “show only on hover”?

[torb]

I have been thinking the same; “I would like it open by default. It’s currently closed by default.”

But – would it be possible to use the ordinary description where the short description is? Would it not be more natural to use the standard description field in WP for the description?

[torb]

This reply has been marked as private.

[torb]

It is not the cache on the iPad, because it is flushed through the system settings…. and I have no caching yet on the server. Can you have a look? Or is there anything I can do to make sure the data served is fresh?

[torb]

OK, they do display on my screen. A better approach than hiding them could be to put them somewhere else, so they don’t occupy the same screen area. Maybe in the opposite corner, or as a rectangular badge at the bottom of the image. You do want to display items on sale or new even on smaller screens 🙂 The world is moving towards tablets 🙂

[torb]

You will find examples on the bottom of the front page.

[torb]

This reply has been marked as private.

[torb]

It is the latest version of the theme, as far as I know (1.71)

But I do also have problems with styling of Quickview ( http://support.swiftideas.net/forums/topic/quickview-not-styled/ ) so it could be related issues.

I did however receive a preliminary release to solve a immediate problem, but I have later upgraded in “the normal way” through wp-admin.