Download button disappeared

Hello @trainmaniac,

In version 1.2.6 icons classes were changed for the compatibility sake.

So yes, some users faced this issue in two cases:

1. If you’re using custom template for the PDF Light Viewer, please refer to the template which included in your plugin version. Classes prefix is now “slicon-” instead of default “icon-“
2. Some users with PRO Addon upgraded only free plugin version and didn’t upgrade the PRO Addon

You could also share example link so I could test it by myself.

Hello.

Link: https://portugalferroviario.net/wordpress/article/trainspotter-070-junho-2016/

So if I understood correctly I need to change template files to reflect that change on classes prefix?

Thanks

Hello.
I have this problem but i don’t use custom templates

As far as I can see the issue is not in the icons.
If you’re using custom template for the plugin then yes, please make diff with code comparing software (something like meld) between your version and plugin’s template version to see what was changed.

There were also template changes in version 1.3.0 ( https://github.com/antongorodezkiy/pdf-light-viewer/commit/2a7d7ea3c77c106f39f0664edc6fbe3f75304f23 )

Hello @xapnder,

Please add more information about your case. Example preview page also could be helpful.

Hello
Link: https://archivoorotava.es/blog/libro-1/

I have sent screenshots of the PDF settings to support two days ago

@trainmaniac, so are you using custom templates? If no, then could you please show me screenshot of the PDF editing page? Wanted to know is it issue with download button or with some others too.

@xapnder, sorry, didn’t recognize you at first. Will answer you in https://support.wp.teamlead.pw/q/full-screen-and-download-icons-missing-2/

ok thanks

Hello,
I’m using Colormag template: https://pt.www.ads-software.com/themes/colormag/

screen: https://portugalferroviario.net/screen.PNG

We’ve found the issue, emergency release will be published in hour or two on wordpress. For Codecanyon it will take some time for approve.

Great news, thanks for your support.

The issue should be fixed in 1.3.3, just released.