wpgloe

Thank you for your request and sorry to hear that it does not work as expected.

I will look into it and see what can be done.

Thanks for the feedback, good to hear that you managed to make it work.

Hi, and thanks for using the plugin.

The plugin uses the standard WordPress approach for handling plugin options. Do you see any messages after pressing Save in the options page? If you have not turned on WP_DEBUG (see wp-config.php) it could be an idea to do so, at least temporarily. After having done so, try again the Save button and look for error messages.

If you have other plugins installed, are you able to save options from those plugins?

Are you able to save other general settings, like the WordPress settings below General, Writing, Reading etc. without any problems?

It could be an idea to try to delete the plugin and then re-install it again if the above does not take you anywhere.

Thank you for the feedback and good to hear that it works as expected!

There is now a new version 5.2 published. It has some imrovements that I suspect may be related to your issue. You may try it out.

As I have no access to your site, I have again uploaded a development version to the same location and hope you can help out with a solution the recent issue. A logging option added in System settings. Turn that on, and check console.log when you click and image on a page to start the viewer. If you have the possibility to reply with the output for the first item logged it would be great. You may of course obfuscate any information you do not want to reveal.

Also, when you click and image in the thumbstrip, there will be a message logged in console.log which can reveal some useful information.

Another option is added – Fall back to currentSrc. When checked, you should be able to see the images as you did with the pre-5.0 version. But this is a temporary development solution.

Noted. It may (this may not be the case here) be related to the existence of the url specified as the src for the img element. In 5.0 it uses currentSrc property rather than the src property. I will look into it at the earliest, meanwhile I hope you can use 5.0.

Version 5.1 published.

Thanks for the feedback and your patience. I will publish a new version omitting the System settings options and always load directly from file to avoid the discouraged file_get_contents.

As a mean to check whether the loading of the SVG has some issues, I have added an additional option page System settings in the plugin admin interface where the loading of the SVG definitions can be controlled. If you could dowload a development version at https://image-projector.com it could be worth a try. The download link is at the bottom of the landing page.

All the svg icons comes with the plugin and is stored in ip-svg-sprite.svg below the includes folder of the plugin. The content of this file is inserted at the bottom of the page, it can be seen in the developer view of the browser. Assume the console does not have any related messages?

I will see if the icons can be loaded in another way and keep you updated. Sorry for the inconvenience.

OK, understood. Could you try to increase the z-index for the pluging? You can find this on the bottom of the Appearance page. Try to increase it significantly (e.g. 10000), so there are no other page elements with a z-index higher than that number which may obscure the plugin.

Also, if you use bright background, are they still hidden?

Another thing you could try is to uncheck ‘Fade out buttons’. That is found in the Controls page.

If you also have another browser available – could you try that as well to see if there are any differences?

Hi and thank you!

I have difficulties recreating the problem that you describe – do you have a link to a page where this is happening?

Thanks for reporting back and contributing to improving the plugin.

Good luck to you too!

Note typo above, this works better: if(src !== "" && (typeof src !== 'undefined')) {

It appears that there are several IMG elements with incomplete attributes (no src attribute) on the page. This is causing the abnormal behaviour and is handled in the new version 4.7 that is now available. There should be no need for manual editing if you install this version.

• This reply was modified 2 years ago by wpgloe.
• This reply was modified 2 years ago by wpgloe.
• This reply was modified 2 years ago by wpgloe.