Forum Replies Created

Viewing 15 replies - 151 through 165 (of 272 total)
  • Plugin Author Firelight

    (@firelightwp)

    I’m going to go ahead and resolve this thread on the assumption it is now fully resolved. Obviously, if you still find some issue, I’ll continue to work on it. Thanks!

    Plugin Author Firelight

    (@firelightwp)

    Hi, I just wanted to follow and let you know I pushed a fix for Fancybox2 + Vimeo player links in version 2.2.8. On the assumption the issue is resolved, I’m going to mark this thread resolved. But please feel free to update and let me know if you are still having issues.

    Plugin Author Firelight

    (@firelightwp)

    Hi @sonicgyn – I have good news and bad news.

    Your note compelled me to fully review the plugin’s integration with NextGEN Gallery. There were actually a few different issues, and I’ve resolved them. So that’s good.

    The downside is that the fix for ajax pagination, specifically, is in Pro. A lot of the third party integration code, including NextGEN code lives there. So I kept the code there.

    I assume you are a free-only user. It seems not-quite-right for me to fix an issue you reported in a plugin which you cannot access. Given that, if you reach out at firelightwp.com/contact, I’ll arrange to get you a copy of Pro with a 6 month license.

    Thanks again for the report.

    Plugin Author Firelight

    (@firelightwp)

    @newsarena – I just pushed a release (2.2.8) that fixes some known issues with a few settings not saving. It also ensure a success message shows when settings are saved so you can tell action was taken. If you are up for it, please feel free to try updating and let me know if you’re still having issues. Thanks.

    Plugin Author Firelight

    (@firelightwp)

    @ukandrzej – Just pushed a release (2.2.8) that should resolve remaining issues with this batch of settings that haven’t been saving correctly. Please feel free to update, test, and let me know if you have any additional issues.

    Plugin Author Firelight

    (@firelightwp)

    Hi, so I think I understand what is happening. It is an issue with the core Fancybox 2 code. Fancybox2 comes with some media helpers that help with certain media types, especially videos. Those helpers actually adjust/change the vimeo url. The changes they make are fine for the vanilla vimeo links (vimeo.com/123456), but they break player links (player.vimeo.com/123456).

    I will include this in the next release, but if you would like to try the fix on your site in the meantime: access your website via FTP, go to wp-content/plugins/easy-fancybox/fancybox/2.2.0/helpers/jquery.fancybox-media.js, and change line 96 as below.

      Change it from this:

      matcher : /(?:vimeo(?:pro)?.com)\/(?:[^\d]+)?(\d+)(?:.*)/,

      to this:

      matcher : /(?<!\.)(?:vimeo(?:pro)?.com)\/(?:[^\d]+)?(\d+)(?:.*)/,

      You are adding an extra (?<!\.) right after the first /.

      If you get a chance to test it before release, please let me know if it works. Otherwise just let me know after the release is out and you update.

      It’s unusual that we are fixing vimeo by adjusting lines that Fancybox itself specifically added to make vimeo work.

      Plugin Author Firelight

      (@firelightwp)

      Just wanted to confirm I can duplicate this locally. The link works/opens with Fancybox Legacy and Fancybox for Fancybox Classic Reloaded, but not Fancybox V2. So it must be something about player links + V2 only. I’ll see if I can figure it out.

      Plugin Author Firelight

      (@firelightwp)

      Hi – sorry for delayed response on your earlier reply. Looking at this now. I can duplicate the issue on your link. I’m wondering if it has to do with the type of link. We usually anticipate standard Vimeo share links like https://vimeo.com/181645979, while yours is a vimeo player link.

      I’ll investigate with this particular link, and see if I can duplicate and fix. Will reply again when I have an update.

      Plugin Author Firelight

      (@firelightwp)

      Hi,

      In my last post, I asked if you could double check whether ALL settings won’t save, or just some. I ask because there’s another thread specifically about the Link To and Group Galleries settings not saving. Those settings have their own issues that I’ve resolved and will be in the next release.

      https://wordpress.org/support/topic/no-next-and-back-arrows-in-galleries/

      For now, I’m assuming your issue is broader and affecting all settings.

      Plugin Author Firelight

      (@firelightwp)

      Hey @ukandrzej – Thanks for the detailed follow up. There is a lot in your reply.

      1) On documentation. I actually agree. Easy Fancybox has complex settings that are hard to understand, and the documentation needs a major overhaul. Related to this, many of the options could use in-line explanatory notes directly on the settings page. Working on both of those.

      2) On the Choose Lightbox setting, I must admit I this one was clear. It’s just ‘which lightbox do you want’. It may be confusing because Fancybox Legacy vs Classic Reloaded vs V2 are nearly the same. I’ll consider adding a small explanatory note. I’m also considering adding an additional, free, non-“Fancybox” lightbox like PhotoSwipe.

      3) Good to here the Automatically group images setting is working.

      4) On the ‘Apply to’ setting, I didn’t realize that wasn’t saving too. That was working like 2 weeks ago, so not sure what I did, but I can duplicate. I’ll start on a fix tomorrow morning, and will include it in the next release.

      Thanks again for your diligent reporting.

      Plugin Author Firelight

      (@firelightwp)

      Just wanted to follow up and after reviewing the 2.2.2 release, I don’t see any other obvious troubleshooting steps to suggest.

      To clarify, when you click the save settings buttons, does anything happen at all? Does the page pop back to the top? Also, if you’ve only been testing with 1 or a couple settings, can you try some others and see if it depends on the setting.

      To do more, I really need to be able to see or duplicate the issue. If you reach out directly, we can coordinate that.

      Plugin Author Firelight

      (@firelightwp)

      I just prepped a fix for this and pushed it to the main code base. It will go out with the next release. Given that, I’m going to go ahead and mark this as resolved. Thanks again.

      Plugin Author Firelight

      (@firelightwp)

      Lol. I guess that’s been there since we added the new settings page a few month ago. It was missed because it doesn’t show on the visible page, only on the browser tab. We’ll update in the next release. Thanks for taking the time to come here and report!

      Plugin Author Firelight

      (@firelightwp)

      Ok, that’s good information. So it sounds like it was a change in 2.2.2 that broke things for you. I’ll review changes in that version and see if I have thoughts on possible causes.

      Plugin Author Firelight

      (@firelightwp)

      One more follow up – I noticed you reverted to 2.0.6. To confirm, the immediate prior version 2.2.5 was working for you? I’m wondering why you reverted so far back.

      I ask because if it is 2.2.5 vs 2.2.6, that obviously narrows down where the issue could be. In that case, I could try sharing one or more slightly adjusted versions of the plugin that reverse or comment out changes in 2.2.6. At the least, that would allow us to narrow down which code might be causing issues in your environment. If you’d prefer to try that (vs reaching out directly), let me know.

    Viewing 15 replies - 151 through 165 (of 272 total)