beargfr

I checked the log (I don’t have to ask, I can enable/disable it myself). There are no php errors being logged.

Looks like no one at Updraft is interested in working on this or responding. On the other thread, they asked for information, which I provided. It’s been silent ever since. In

I covered this in the other thread. No, there aren’t any plugins that I can do without and still keep the site usable for my users. Besides, say I disable one and find out that corrects the problem. What then? Keep it disabled? Why should another vendor be responsible for something that Updraft isn’t capable of coexisting with?

Why is this marked “resolved” when it’s not?

I do see an error in the js console:

Direct link to the image, because the above only shows “This image has an empty alt attribute”

https://photodump.garrettfamily.us/updraft.jpg

Yes, it is. Necessary that is. I have wordpress instances that are running behind a proxy and are also running inside containers on various servers inside my local network. So unless I include HTTP_X_FORWARDED_FOR in the settings for Trusted IP Origins all logins appear to originate from the IP address of the proxy instead of the true origination point. These IP addresses will always have a port number on them because that’s how the front end proxy directs inbound traffic to the appropriate wordpress instance/container, and your is_ip_valid function as shipped does not handle them correctly.

Yes, I have removed and reinstalled multiple times. I’ve also manually gone into the wp database and deleted all of the updraft_ records in the options table because apparently, Updraft does not “clean up after itself” during the deactivation/remove process, even if one uses the advanced option to wipe out all settings. It also does not delete the ../wp-content/updraft directory upon removal.

Suggesting that I disable all plug-ins is not helpful. This site uses a significant number of other plugins, all of which are needed, so disabling them would render the site non-functional for all users. I’ve not added any new plug-ins to the site in a very long time. Auto-update is enabled for most so it’s possible that an “undesirable” conflict has been created “somewhere” as a result. Even if I were to disable all others and identify a causing plug-in, what then? Leave that one disabled? Wait for that provider to code a fix just so that they don’t cause a problem with someone else’s plugin? I can’t tolerate my site being non-functional while I’m waiting for them to decide if they’re even willing to alter their code to fix someone else’s problem.

What would be helpful would be directing me to the specific routine(s) responsible for creating the icons in the output web page so that I can attempt to diagnose what’s going on myself.

Seriously? The set of plugins I’m running are plugins that I need in order to deliver our service. Likewise, for the theme. Let’s say I do what you ask and it works. Are you then going to tell me I have to run the site that way? Well, I can’t and I won’t. I’m open to the idea that the cause might be coming from something other than the Nextgen Gallery plugin, but it would be much better to have a way to diagnose where the problem is instead of just randomly guessing at things.

No, disabling that plug=in does not correct the problem.
I’m able to edit the gallery.

While we’re on the topic of documentation, how about providing a similarly comprehensive document that provides details of all the available filters that can be used to augment the plug-in?

No, that page is not at all helpful. What is so difficult about providing a comprehensive reference list that details all supported shortcodes and includes a complete description of all the options/parameters that each one supports? There should be one document that details all of that information in one location, not a collection of disjointed videos.

For example:
[short code 1] == summary of what it does
[parameter 1] == required/optional == syntax, description, acceptable values
[parameter 2] == required/optional == syntax, description, acceptable values
…
[parameter n] == required/optional == syntax, description, acceptable values
usage examples
[short code 2] == summary of what it does
[parameter 1] == required/optional == syntax, description, acceptable values
[parameter 2] == required/optional == syntax, description, acceptable values
…
[parameter n] == required/optional == syntax, description, acceptable values
usage examples

I’ll bet you could write that document in a fraction of the time it takes to make just one of those videos, and it would be infinitely more useful.

This experience has prompted me to “shop elsewhere” and I’ve very glad that I did. I found and have installed WP Photo Album Plus and so far, I love it. It works. The import from folder function loaded all the files that Nextgen couldn’t handle and never missed a beat. It’s much more configurable, I like the way that it presents thumbnails in posts and pages much better, and the built in slideshow function rocks. It’s full function, there are no extra ‘pro’ features that you have to pay for, although the author does accept donations.

Thanks tanvirdave123, I’ll try that method on one of the problem posts and see what happens. Hopefully if it works, I’ll be able to figure out why and find a different way to correct that problem on the others.
I’m wondering if perhaps it could be a theme problem. I know the one that this site has is ancient – more than 12 years old – and it’s no longer offered in the theme repository so there’s a good chance it’s missing updates to be compatible with the current version of wordpress.

• This reply was modified 6 years, 4 months ago by beargfr.

I’m not sure how many times I’m going to have to say this: I will *not* be permitting you to log into my site to mess with things. Period. For you to even ask for that sort of access is beyond belief.
A potentially long-running process such as your import function should always maintain some sort of log or trace so that it problems happen, there is a trail to help debug the issue. That’s the most basic software 101 sort of idea. Even something simple, such as writing messages to a log file that say “I’m starting to work on this file now” would at least give people a clue of where to start looking when there are problems.
I honestly do not care how many -other- users your plugin works for. All I know is that it doesn’t work for me, and also does not provide any sort of diagnostic help when there is a problem. I know that it’s difficult to anticipate all of the possible permutations of configuration that you might encounter “out in the wild”. That’s all the more reason to build in robust diagnostic capabilities into your code – which obviously you have failed to do.