iNexi

It does appear that the original poster’s issue was resolved, as the EGS is up and running on the link provided.

Can the recent posters provide example links?

It appears you have images inserted into your page there.

There is no need to insert images on a post/page, only the need to attach images to a post/page.

Basically if you edit the page, and remove the images from the body of the page, it will appear as you desire.

Under Help > Advanced Options, you can choose to disable TimThumb resizing. Then images will be used as is. This may be a direct fix for your issues.

Sorry for the quick response, but I figure that’s better than none.

Not in this version. Future releases will accommodate this feature.

Not included yet. Next update most likely.

The option before “Order slides by” is “Randomize slides”… Is that checked?

If you’re using conditional style sheets, why not include rules for the container the slider’s in (like #post), or the slider’s div itself (div.easygalleryslider)?

I agree there needs to be control over cropping for “larger” images.

Look for it in the next update.

That’s a great feature. Look for it in the next release after 0.6.6.

What event or situation do you want to trigger what change?

This is a responsive slider that adjusts to the size of the container it’s in, or respects the max width/height settings.

You could set the “.easygalleryslider” div to a fixed height (or min-height) in your own CSS.

This is now on schedule for future releases. Would you want to see a minimum height, that would get stretched if images were larger? Or fixed?

I’m sorry the nav option wasn’t easy to turn on. I’m sure it can be resolved by CSS. Are you able to implement some styling?

This is an area that hasn’t yet received a lot of attention.

Interesting. Do you have a link for me to check out? (You can send by email or web)

Is this on the home page or blog page?

Thanks.

The next version will address this use on the homepage/blog list.

I know of no such bugs with this plugin. Did this happen immediately after deactivation? Had you deactivated and reactivated it previously? Does reactivating it solve the problem?

The plugin is pretty non-invasive, I’d suspect another plugin is to blame.