wpress2010

Thank you.

The logic is: a Pod can belong to many categories. I want to display those that are simultaneously in the category of ‘HB’ but also are NOT in the category of ‘Sold’

So, f’rinstance, there are 6 Pods who have the category of ‘HB’

Of these 6 Pods, only 3 do NOT also have the category of ‘Sold’

So, I want to display those 3 only.

Thank you. I tried this statement, and it does not correctly recognize the NOT IN category part of the code.

Here’s the way it is set up:

The Pods can have multiple categories. So, as an example, a Pod is in the categories ‘HB’ ‘other’ and ‘different’. So the statement should NOT return this Pod in the results. But it does.

Code:

[pods name=”property” where=”category.name IN ( ‘HB’ ) AND category.name NOT IN ( ‘Sold’ )” template=”HB For Sale” orderby=”post_date DESC”]

Thank you! I had looked around in the Pods documentation for a while and did not find this type of conditional statement.

Is it similarly possible to combine this logic using AND:

where=”category.name IN( ‘HB’, ‘other’ )” AND where!=”category.name IN( ‘different’ )”

Same thing, same fix. Phew!

Same issue: I can add image files to both Image and Gallery fields, but on Update, they are not saved. Pods 2.8.3

Thank you so much for your analysis! There is an ongoing “issue” with this website, as a previous developer somehow insisted on NOT using HTTPS – had something to do with SEO – I am still trying to puzzle that one out. So yes, you are right – there is obviously mixed content if FooGallery is trying to load its CSS file via HTTPS.

My current plan is to get the SSL certificate and convert the site over to HTTPS. That ought to take care of the problem. Oddly enough, on another page in the site there is a very large FooGallery, and that one shows the correct thumbnail sizes throughout.

Neither that second gallery page, nor the one I referred to originally, has anything on it save for the gallery and a bit of other text preceding it.

Thanks. Upon actually going in and configuring a set of hotspots, I have found that this is actually a pretty simple plug to use. Also needed (maybe it’s in the Pro version, I don’t know):

An easy way (without having to go and find the particular element and either hide it or have its child element (the image itself) cleared, via CSS) to remove the title of the image, the h2 element. In my particular case, it took up space to the left of the image, pushing the image itself out of alignment, to the right.

I meant a really good UI

I think it is a matter of what I do not see as a really UI here. I was able to add the Image through the box on the right. But once this is done, nothing appears anywhere to show that this image is now available for mapping.

I finally figured out that the Hotspot Areas “Clickable Area #1” link is where one needs to click to add/edit hotspots, but this link doesn’t suggest that it is a clickable thing when you hover over it – it just looks like static text – with an obvious “x” to remove it.

After thinking about this for a while, the Pro version shown on the tutorial video – since it permits more than one image per site – has an Images menu choice in the admin panel. The free version, even if you configure the single permitted image – never shows the Image list. So it is never obvious that you have any Images to edit, in the free version.

Well, obviously something is not right with the auto-updater feature. It’s usually possible to do the update manually, once on the server, with WP-CLI. I guess the entire point of having the auto-update is that it doesn’t require any “intervention”. The ambiguity of the error message is something that can and should be addressed, I think.

FWIW, just as I suspected, it was indeed the PHP version being out of date that had blocked the update. Once I reset the PHP version and went back to the site, the update went through without incident.

Thanks. I am fairly certain that the plugins and the theme are not the source of this error. I inherited the management of this site from someone else; there are only a few plugins – all registered on the repository and up to date, and the theme is a standard one from a major developer, also up to date.

I majorly overlooked the Site Health tool: the PHP version for this site is out of date! I would expect that this is the actual source of the problem, but until I get access to the server, can’t do anything about it.

Yup. Since FooGallery will generate the extra-res thumbnail images, maybe the Retina feature should be “on” by default.

WordPress, of course, generates all of the additional image file sizes it needs from the largest original file you upload. But Retina resolution images, AFAIK, all need to be generated with the @2x type of suffix appended to the original filename. So, what FG is going is taking f’rinstance, a file named “myimage.jpg” and using it create a thumbnail (i.e. smaller size) file, doubling the thumbnail size, and then appending the suffix, like this:

Original file, myimage.jpg = 600×800 px
Thumbnail of same file, myimage-150.jpg, 150×200px (what WP would create…)
Retina 2x file, 300×400px, [email protected] (FG creates this)

Not intuitive, like I said – but really nice, as thumbnails are very sharp.

I figured that out! Not intuitive, though: perhaps you could add a note in the UI with the Retina checkbox that mentioned that FG generates the Retina images.

Thank you.

Just for fun, I enabled 2x Retina images, and although there are NO @2x image files in the Media Library, this is what apparently fixed the problem!