Joe777

Thanks for your reply. And, thanks for BNFW. Sorry that I didn’t see that support thread before submitting this one. I searched and it didn’t turn up for me. I talked to fatcow before I submitted this question, and they told me that they don’t yet support PHP 8.0+. The link you gave me is not what I see on my fatcow interface. I think the link is in error. Here’s what I see: https://www.fatcow.com/help/article/scripting-how-to-switch-your-php-version, or https://www.fatcow.com/controlpanel/foundation/hosting, or this video starting at 1:40: https://www.fatcow.com/help/article/how-to-update-your-php-version-video. My opinion is that you jumped the gun a bit by requiring PHP 8.0+ too soon. BNFW is the ONLY plugin that requires it (that I use anyway). But, it’s your opinion that counts, not mine, and I appreciate your plugin, and I will just stay with BNFW 1.9.3.

I was wondering: what happens if I run 1.9.4 with PHP 7.4? Will BNFW just quit working, or will there be limited functionality?

BTW: Here is the quote that I got from fatcow: “I I understand your concern about more plugins moving to version 8.0. We are actively working on making version 8.0 available as soon as we can. We know it’s important to keep up with the latest plugin updates, and we are prioritizing the release of 8.0 to ensure our customers have access to the features and functionality they need. Please keep an eye out for our announcements regarding the 8.0 release timeline. In the meantime, let me know if there is anything else I can assist you with.”

That works! Thank you so much for your help!

Thanks for your reply. When I didn’t hear from you, I changed the lightbox back to one that works, since this is my live site. I have now changed it back to ARI Fancy Lightbox, so you can see what the problem is at the link I provided.

Since I wrote my post I have tried many things to get this to work, but without success. I can get the button background color to change, but the icons in the buttons (e.g. the start arrow, or the ‘x’ symbol to close the window, etc) don’t show up no matter what I’ve tried.

I really appreciate any help you can offer.

Thanks for your response. The email shows up OK in my email inbox. The problem is the inconvenience of copying and pasting the HTML in the ‘Visual’ tab to the ‘Text’ tab every time I want to view or change the email template.

Yes, that works! Thank you! Now the mystery to me is why the original code quit working. I spent a little bit of time on it, but no success. I can’t debug on my hosting company server (fatcow.com), but I can using Netbeans on my local computer (I have XAMPP). But, it works on localhost. I upgraded to php7.4 on the server in September, but didn’t see the problem then. My hosting server is at 7.4.10, and XAMPP is at 7.4.29. I don’t think that should matter.

Your code seems more straightforward, and it’s not clear to me what the advantage of the original code is.

I will use your code. If I ever download a updated version, I’ll have to remember to check this and make the change to the file if necessary.

Thanks very much for your help, and for your solution.

Thanks very much for your suggestion! I realize that you are busy, and that this problem isn’t caused by Easy Fancybox, so it is very kind of you to provide these suggestions. I didn’t take down my test site. I am curious to know how you found the missing file. I had CSS similar to what you suggested in my child theme styles, but, for some reason I don’t yet understand, it wasn’t showing up when I looked at Chrome Developer Tools. I manually put your lines in via Developer tools, and voila! I then put it in WordPress ‘Additional CSS’ and that worked. I then took it out of Additional CSS, commented out the code I had in my theme, and put yours instead, and waited for the cache to clear, and then the CSS showed up on the Developer tools! Here’s what I had in my CSS before:

.entry-content .ngg-gallery-thumbnail img {
height:auto;
margin: 0 0 18px 0;
width:auto;
}

I know the margins aren’t right, but I had that code in there for years.

A lot of things I don’t understand. But, the good news is that I have multiple columns now, and I can work in my leisure to make all three instances of my website the same.

Thank you very much for your help.

Thanks a lot for the tip! I really appreciate your looking at this even though it isn’t an Easy Fancybox problem. I checked the NextCellent (and Easy Fancybox) settings on all three instances, and they all seem to be the same. I also noticed CSS differences (using Chrome Developer Tools). Very strange – they should all be the same. I don’t see a way to determine exactly which style sheet is missing. I’ll get to the bottom of it. If nothing else, I can add the CSS to my child theme (a band-aide solution).

Thanks again for your help. I’ll mark this issue as resolved, since it isn’t an Easy Fancybox problem.

Thanks for your response. You’re right. Sorry to bother you about this. I don’t use NextGen, but rather NextCellent (the NextGen legacy plugin), since the NextGen rewrite broke my site. I thought the only difference between the three versions of my website (live site, test site, and localhost site) was Easy Fancybox. But, I have now updated all three to version 1.9.5, and the problem is still there. All three versions have a different gallery display. Yikes! This is a new development, and I don’t know what caused it (browser update? plugin update? OS update?). I’ve spent the morning searching and haven’t yet found the problem. However, as you said, it’s doesn’t seem to be Easy Fancybox that’s causing the problem.

Thanks again.

Thank you for your reply. Can you tell me what algorithm is used to select which Admin the notification is sent to? For example, does it choose the first Admin in alphabetical order?

Yes, you’re right, it’s an old theme. It uses the old thematic framework theme, so I have a child theme. It’s on my list to update it, probably using the Astra theme and the Elementor plugin, but I don’t know when I’ll get to it. Until I do, maybe I could add the viewport meta tag. I wasn’t familiar with that until you mentioned it. I’ll look into that.

I tried the ‘Legacy’ setting. You can see it at the test site: thelesters.net/tlntestsite. It works fine, except that swipe doesn’t work. ‘pinch-to-zoom’ does work. So, I guess if I want ‘pinch-to-zoom’ and not swipe I can use legacy (rather than reverting to version 1.8.19), and for vice versa, I can use ‘Classic Reloaded’. I’m hoping you find a real easy way to get them both working on Classic Reloaded ?? (if (two fingers) { use native;} – I know I’m over simplifying and don’t know what I’m talking about).

Thanks again for your help.

Thanks. Now I remember seeing that option. I tried it. The ‘pinch to zoom’ still doesn’t work. And it has another problem. On my mobile, when I select a photo from the gallery, it is very small – thumbnail size. This problem isn’t there on the desktop computer. And, this problem isn’t there with the ‘Classic Reloaded’ version. You can see what I mean on my test site, where I have selected the fancyBox 2 version. My test site is here: thelesters.net/tlntestsite.

Sorry for the dumb question, but how do I download fancyBox 2? I searched in github, but couldn’t find anything with that label. I also looked on WP plugin site. Is fancybox 2 the same as the 1.9.1 version at github?

Thanks for letting me know. I hope you don’t mind, but I want to make sure I understand. Are you saying that we should expect the fatal error message when upgrading from version 11.2, and that future releases will always have that fatal error message when updating from version 11.2? So, we should go ahead and update, even thought we know that the fatal error message will occur? Of course, I know we shouldn’t expect the error in subsequent upgrades e.g. from 11.3 to 11.3.1.

As a software developer myself (now retired) I understand the complexities of doing upgrades, and I am thankful and appreciate of all your efforts. I won’t pretend to know all the obstacles you are facing, but I must say it seems strange that you couldn’t update the software so that it doesn’t tell users that a fatal error occurred during an upgrade, when there really is no problem. I understand what you’re saying about conflicts between the new and old software, but I would think that there are ways for the software to detect this problem, and not throw a fatal error.

However, my opinions don’t really matter. If you tell me it’s perfectly safe to upgrade despite the error message, then I’ll do it on all my sites.

Thanks so much for your response to my questions.

Thanks for the reply! From what you say, this fatal error won’t impact the upgrade, or operation after the upgrade. That’s good (though kind of strange that there’s a fatal error but no consequence). However, out of an abundance of caution, I won’t update Jetpack in my other sites until this is fixed.

Thanks again.

Your version fixed the bulk delete problem! I should have checked that when I was trying your version for the ‘Sort gallery’ problem. This time, I will leave your version installed, instead of the one from WordPress.

Thanks very much for all of your help, and for your patched NextCellent version!