nosferatuscoffin

I ended up upgrading from WP 2.8.6 to 3.0.1 and the Update options button showed up again after not doing so under 2.8.6.

It appears that some of the code at the bottom of the admin page might require 3.0.x in order to function properly.

I went from WP 2.8.6 to 3.0.1 and the Update options button showed up again afetr not doing so under 2.8.6.

It appears that some of the code at the bottom of the admin page might require 3.0.x in order to function properly.

I am getting the same problem.

I notice that both your site and the site I am working with are running WP 2.8.x.

It is possible that the admin portion contains code that only runs under WP 3.x.

I finally got the slideshow thumbs to display properly in Safari.

The CSS was causing Safari to hiccup when loading the thumbs.

Changing the last line gallery-css.php from

#slider img { cursor:pointer; border:1px solid #666; padding:2px; -moz-border-radius:4px; -webkit-border-radius:4px; float:left !important; }

to

#slider img { cursor:pointer; width: 55px; border:1px solid #666; padding:2px; }

resolved it.

Safari seems to demand a hard-coded width for the thumb image. Setting width to auto or min-width does not seem to work properly. Also, as long as you have a clear at the end of page, (like in footer.php), the float:left does not seem to be needed in the #slider img declaration.

How are you generating the thumbs? Via Media or through the plugin’s own Manage Slides item? They generate thumbs differently.

Also, do you have an example URL that I could look at?

I have found that it is easiest to add images to a post/page gallery by simply using Add Media and then using the built-in WP 2.9.x image editor to create your own thumbs. Thereby bypassing the ones that the plugin would create when using Add/Manage Slides. (Which never seems to work properly when it comes to thumbs, anyway)

Also, it makes it a lot easier to sort your images in what order you want within the post/page. However, there seems to be a bug in the plugin that when the number of images reaches 25 or so, sorting the images after image #25 does not take. So you have to manually move some of the newer ones above slot 25 and then move them back down. That seems to work.

It is a great plugin, but it does have some problems and limitations.

What version of WP are you running? If you are running 2.9.x, you can just import the images using Add New Media, and using the new image editor, create the thumbs yourself. After that, just attach the images to a page, using the Attach link under Media.

Then, in the page/post just add the code [slideshow $post_id=postnumber]
where postnumber is number of the page/post you are adding the gallery to.

I can report that this slideshow does NOT work properly when the slideshow is first loaded under Safari for Mac, either. It works properly on IE 7 and 8 as well as Firefox. But not on Safari for Windows or OS-X.

This is on a WP 2.9.2 site that runs PHP 5.2.6-1 and the only other plugins that are installed are:

All in One SEO Pack
Exec-PHP
Google XML Sitemaps

none of which should interfere with the slideshow under Safari.

The site in question is . Go to the Media page and click either “Friends” or “Publications” and you will see that the slideshow does not load properly under Safari.

I posted a comment about this issue on the plugin’s blog page awhile back, but it was never approved and eventually was deleted. (Actually, no new comments have been approved there since late February). This is the third time I have posted either here or on the plugin’s site about this issue and I yet to receive any answer. No offense, but this is very poor support.

Are you still supporting this plugin and/or is there a fix in the works for this issue? If not, and as much as I hate to, I will need to go with a different plugin, as a good 30%+ of that site’s traffic come in from people using Safari.

BTW, I also increased the php memory_limit from 32M to 128M just to test and it did no good either.

I am having this same problem. In every image gallery that is created, it will always start duplicating once the gallery hits 25 images. Not only can you not change the sort order of the images, but all of the ones that are 25 or after cannot even be edited, such as changing the text description.

They can be moved and edited above #25, but that does no good if the image needs to be 25 or later.

This is a serious bug that needs to be looked into ASAP.

Try

[slideshow $post_id=87]

where $post_id is the post_id # of the home page.

This allows you to put different slideshows on different pages.

I went over the theme and see there was a function call that was reverting the timestamp back to the 1st of the month. Fixed easily.

Image rotation does not work properly in Safari for Windows. When the slideshow is first loaded only the first two thumbnails show up. When the page the slideshow resides on is refreshed, the slideshow then displays correctly.

I cannot say if it does this on Safari for Mac, so I do not have a Mac here to test it. But I have tested on Safari for Windows on two different PC’s, one running XP, the other Vista, and the same issue arises on both.

It works properly on IE 7 and 8 as well as Firefox.

That is what I figured was the problem. Thanks for checking it, Tac.

I would go ahead and just upgrade the upgrade the client’s site to 2.9, but I am also running into another, older recent posts plugin that has problems with WP 2.8+. I might just need to use a different one of those and then upgrade for Sociable to work. Ugh.

Actually, countermand that.

The plugin is still generating a wp_postmeta table value of “_sociableoff” whenever a post is either created or edited. Checking or unchecking the “Sociable off” checkbox in the post admin makes no difference, as the table value of “_sociableoff” is always generated no matter what. I have to manually go into phpmyadmin and delete those values everytime a post is created/edited. Otherwise, the post thinks that the plugin is deactivated for that particular post and will then not execute the plugin.

This is a major bug and one that needs to be addressed post-haste. I will keep digging around the code and see if I cannot find out what is causing it.