Tyler Tork

This is exactly what I came here to ask. I can display or hide based on whether a particular category is selected, but I see no generic way to hide the “Categories” heading if there are no categories selected. I expect I can use {has_category_X} and list all the categories, but this will break if the list of categories changes.

Perhaps I didn’t explain clearly enough. There’s a checkbox that says “no location”. I check that box and it still insists I enter a location. It insists I enter values in fields which are hidden because I checked the box. This is a bug.

I suppose I’ll have to for now, but meanwhile you “may want to” fix the bug.

As shown here, the thing I object to is still there.

Workaround confirmed. Thank you!!!

I offered to debug the JavaScript for you if you would send me the un-munged-up version, but you didn’t, and I needed the site working.

Setting up a new, fresh site as you suggested, doesn’t solve my problem. We already put in a ton of work on the existing site. If we get your plugin working on a new site, yay, but then what? Manually re-create the entire site, including hundreds of timestamped blog entries? Or use a migrator tool to copy it all over, probably including whatever database data are causing the problem, so we just have the same issue on the new site? Seems like a waste of time. And if that did solve it for us, that still does zero to track the cause of the problem to help others who may encounter it.

Please pay attention to the information I already gave you. You’re still saying it could be the theme or a plugin, after I already told you I switched to Twenty Sixteen theme and deactivated every plugin but yours and still had the problem.

No doubt your code is breaking based on something in the database, or in the .htaccess, or something else that doesn’t involve a theme or plugin. But to find out exactly what, we need an environment that reproduces the problem, and the ability to debug. I have the environment, but I don’t need your help anymore. If I work on it further, it would just be to help you.

If you update the plugin to include un-munged JavaScript source, or better error trapping to display more information than “t.style is undefined”, I might then be willing to do more. Please let me know.

I couldn’t get it to work, but I decided to use a different plugin that does work, so it’s resolved in that sense.

I tried installing plain old Twenty Sixteen theme, with all my plugins deactivated (except yours). Your code still fails in the same way.

We mainly use Firefox, but I’ve also tried Chrome, and three different people are having the same issue. I have FB Purity and Adblock Plus installed, but the latter is disabled for our own site. I use LastPass extension but others having the same problem do not.

I agree there must be something special about our site, but it’s apparently not the theme or plugins and I don’t know what it might be.

If you feel like poking around yourself, I can give you an account.

I disabled every plugin except yours and still have the same problem. I am using Graphene theme, latest version.

After reactivating the plugins, I tried installing plain old Twenty Sixteen theme, with all my plugins activated. Your code still fails in the same way.

Perhaps you could trap errors and display a slightly more useful error message? Or if you would supply a version of the plugin where the JavaScript source code isn’t smushed, I could debug it myself and tell you exactly what’s going wrong. I’m an IT professional and quite used to debugging JavaScript code.

• This reply was modified 5 years ago by Tyler Tork.

TypeError: t.style is undefinedapp-3-14-0.js:1:244549

I don’t think it’s legitimate for you to hide notices put up by other plugins. If people don’t want to see them, they can choose to dismiss them, and then you’re not exposing yourself to the risk of your stuff not working at all.

If you really feel you must, I suggest you use CSS rather than JavaScript to try to make your stuff visible, e.g. add to the style #metaslider-ui, a display:block !important

Same here

I do not understand. Why, when you have the whole window to play with, wouldn’t you offer the option to display every piece of information about the image, including the text I’ve specifically chosen to type? Not all descriptions are short enough that they’re appropriate to display on a thumbnail.

Even though you didn’t write the code that makes them appear, you did supply the URLs that they try to use. This is not out of your control. You could override those, or make those controls do something useful, or at least display a message to the effect that the preview and view functions are not supported. Everyone else seems to manage to do something reasonable to prevent these links from giving 404 errors. It’s sloppy and makes me lose all confidence in the plugin.

OK but the preview function and permalink don’t work at all. If there’s a control on your editing screen, you need for it to work. When I create a gallery, and I click Preview and just get a big fail, what it looks like to me is that the developer was very sloppy and that the thing probably doesn’t work at all in the latest WordPress version. Why should I try various things to get it to work when there are obviously big holes in it?

You can’t assume thumbnails are square. That’s an option in the media settings panel. And then even if you assume thumbnails are square, you’re not displaying them square. So you either have to distort them, or crop them further to make them fit your rectangle.

It almost makes sense to make a square thumbnail. It doesn’t make any sense to make a rectangular thumbnail that’s the opposite of the original image’s orientation. You’re saying that if there’s a tall image, and the thumbnail settings are the default crop to square, you’re just displaying a tiny slice from the middle of it? How are people supposed to tell what it is?