delwinv

Any news on this? I am getting this exact same situation – needing to publish a second time to actually get it published

A bit more information: The two types of embed that work – pasting the slideshow URL (e.g. https://www.slideshare.net/khoslaventures/project-rifle) on a line by itself in the editor and including the iframe HTML directly in the editor (e.g. <iframe style="border: 1px solid #CCC; border-width: 1px; margin-bottom: 5px; max-width: 100%;" src="//www.slideshare.net/slideshow/embed_code/key/hwtKQyW5Vuj5Gv" width="425" height="355" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" allowfullscreen="allowfullscreen"> </iframe>) – produce an iframe with src attribute set to (for a test slideshow) https://www.slideshare.net/slideshow/embed_code/key/hwtKQyW5Vuj5Gv and //www.slideshare.net/slideshow/embed_code/key/hwtKQyW5Vuj5Gv, respectively (the later simply implying the protocol from that which the browser used to load the page)

The WordPress shortcode (e.g. [slideshare id=49610449&doc=khosla-ventures-project-rifle-150619175300-lva1-app6891]) produces an iframe, for the same slideshow, with a src attribute set to https://www.slideshare.net/slideshow/embed_code/49610449.

So there appears to be a different backend mechanism generating the two different references to the slideshow, the shortcode method not producing an allowfullscreen attribute in the iframe tag.

NB: when not used in an iframe (e.g. by clicking on the above links from here, thereby opening them in their own window), the full-screen option seems to work in all cases.

I would suggest trying another plugin for this task at this stage. I believe there is a commercially supported (yet free) plugin out there.

Sorry,
Delwin

It does indeed have much in common with DNUI – I mainly just changed the interface and corrected a couple minor bugs. That said, version 1.04 was a simple version update with a minor bug fix that only would make it work on more servers. Behaviour was in no way changed, and seeing that DNUI is also not working for you, I really don’t know what could have happened.

I would suggest trying another plugin for this task at this stage. I believe there is a commercially supported (yet free) plugin out there.

Sorry,
Delwin

Unfortunately I cannot help without seeing exactly what is going on with your particular installation (that is, on the server).

Actually, I would suggest looking at other plugins at this point. I believe there is a commercially supported (yet free) plugin out there that would get a lot more attention to issues. I simply don’t have the time to continue development of this plugin. It’s basically the old DNUI plugin with an updated interface, and were I to work on this, I’d completely redo it.

Delwin.

Please make sure that the number of displayed images per page is a reasonable number (around the default of 20). Otherwise a long delay and/or timeout might occur, not allowing a scan.

Hope that helps!

Delwin.

The plugin deletes no image automatically an lists what it thinks are unused images for you to verify before you delete them. Image Gallery plugins typically do not reference the images in the same manner as WordPress does and so this plugin cannot recognize those images as being in-use. As noted, use with care and verify that the images aren’t used before deleting. This is simply a tool to help in that deletion for images used in Pages, Posts and Pods (not including usage of shortcodes).

Very large databases of images will still cause a lot of headaches for you to delete. You shouldn’t increase the number of images displayed per page to much more than 20 for this plugin, since for each image it has to make a database call and retrieve information. This takes time and increasing that number beyond 50 causes very slow response. Increasing it even more can cause PHP timeout errors. So looking through a library of 20k images is still going to be painful with this plugin.

This plugin is also a simple modification and amelioration of two other plugins and I have not done much with optimising database access, so there are issues.

You’re best trying another plugin for your purposes.

Delwin

The plugin deletes no image automatically an lists what it thinks are unused images for you to verify before you delete them. ProPhoto does not reference the images in the same manner as WordPress does and so this plugin cannot recognize those images as being in-use. As noted, use with care and verify that the images aren’t used before deleting. This is simply a tool to help in that deletion for images used in Pages, Posts and Pods (not including usage of shortcodes).

Can you provide more details? Version of WordPress, version of plugin, what isn’t working, what is being reported to you by the plugin, etc.

Thanks,
Delwin.

Closing topic

This has been changed in version 1.04 of the plugin

Closing topic…

Closing topic

Closing topic