joefryfoto

You’re right – the .tmb is being written due to another plugin. Thanks again for the help and a great plugin!

Server-state issue in Wordfence seems a false alarm. It looks like it appears because Freesoul creates a directory .tmb outside the normal WordPress installation, even though it is within the WordPress root directory. To prevent getting a Wordfence server-state warning flag, you must go to All Options / Scan Options, check “Scan files outside your WordPress installation” and save.

Jose, does the fact that this folder is 777 make it risky in a multisite scenario? (It’s empty, but I don’t know if it gets used).

Jose, that worked – thanks much for the quick fix! Is it possible my other site worked on 2.2.7 because I installed 2.2.6, got in the door, so to speak, and then when I upgraded to 2.2.7, the presence of Network:true didn’t matter? If so that would explain everything. Another question: around the time I was installing and reinstalling, I had a Wordfence Server-state warning crop up. Any chance this could have been related, or unlikely?

Thanks again for the great product and quick fix!

Jose everything you stated is correct. I thought I’d made a breakthrough and the problem was cookie-related, but I think I read something wrong, so I edited this comment.

• This reply was modified 5 months, 4 weeks ago by joefryfoto.

Added info: installation writes nothing into mu-plugins, which seems otherwise sound. Could some earlier backfire have written something into db to prevent this? Also, I went back to a previous working prototype to see that the subsites were all of format: *.example.com – that is, there were no subsites having their own domain name like my current site. I’ll try to test that out when I can.

• This reply was modified 5 months, 4 weeks ago by joefryfoto.

Thanks for the quick response. I do suggest this as a feature enhancement – some sort of hook “at the top” that could signal a disabling of discounts that a user could trigger with his own coded criteria upon opening the product page.

I have a few hundred images that can be sold as one product. The url to product takes the form https://mysite.com/master-product?img=123. I have custom values indicating sale-status in my image attachments. After a customer selects variations, the img-id is written to the cart object, but before this, there is no reference I can use in the product as a criterion to indicate sale and discount.

So I’d like to use the sale field in the attachment referenced by the query var as the condition to trigger implementation of rule(s) from your plugin. I need a hook to accomplish this.

This is a follow-up after further discussion with the plugin support team. They responded quickly, affirming that the routine is indeed visited twice. I’ll dare to call it a bug-feature – something they did to help with backwards compatibility.

I want to correct my notion that it slowed things down. Based on Query Monitor, performance difference is negligible with the plugin enabled. And this is without any caching add-ons – I’m purposely going with none during development. Any perceived slowdown is due to my option filtering alone.

So false-alarm on a performance hit, and thanks again to the team for a quick solid response; the plugin is great!

@fizanzvai – This is the beginning of my snippet filter for my variation attributes dropdowns:

add_filter( ‘woocommerce_dropdown_variation_attribute_options_args’, ‘filter_dropdown_variation_args’, 10, 1 );

function filter_dropdown_variation_args( $args ) {

echo (‘variation attribute args routine<br>’);

… }

###

The rest of the filter routine is a rather complex “unsetting” of some options for the first attribute; the other attributes are skipped using an if statement reading wc_attribute_label( $args[‘attribute’] ) – but I don’t think any of that should matter.

With your plugin enabled, it prints out “variation attribute args routine” twice above each attribute on my product screen, meaning that somehow, the routine is called twice? The attribute buttons themselves are not duplicated, but I guess that’s to be expected because this routine is only for setting options $args?

https://pasteboard.co/SfDPSHGAmRem.png

When I turn off your plugin, “variation attribute args routine” only prints once.

https://pasteboard.co/BqDNGSLEM1le.png

I am wondering if this has anything to do with swatches, which I am not currently wanting to use – at least for now, all I want is the button action. Is there something I might need to turn off?

I hope I’ve been clear here.; I’d send you a vid, but I’m shy about showing my site/code to the rest of the world ??

To help clarify – I need no inventory stock control, so any use of variants in this regard is unnecessary.

You’re welcome, happy to help.

I suspect Jordy would agree that good simple design philosophy means not creating needless design dependencies. Thus, the Lightbox can’t, and shouldn’t see what is “outside” of each particular image. In this case, it’s Meow Gallery, but it could be any gallery. Or it might not be a gallery, it might be a certain type of page, or section, or anything.

So, setting up a simple trigger-mechanism in this way lets you choose where it operates.

To complete the logical circle…
The anti-selector could be used if you wanted a certain gallery not to be lightboxed. You’d have to determine a unique identifier for that gallery and put that class name in the anti-selector slot.

In Meow Lightbox settings, there’s a slot for selector and anti-selector. I put only “.mgl-gallery” (without the quotes) in selector and leave anti-selector blank.

If you don’t use Meow Gallery, you’ll have to find the class selector used by your gallery. This should be all you need – the selector tells Meow Lightbox to only work on gallery images. No need to use the anti-selector in your use-case.

I ended up doing a hack that looks pretty decent.

.mgl-item figcaption background set to 0% (I guess I could have just specified no captions, doh!)

Then I wrapped my title text in a span, class=’title-txt’ and set its background to around 50%. Added some padding to give it the same height as the shopping cart button floated right in the caption frame. I’m still working on neatening things up to deal with truncated titles on smaller mobiles.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<aside>
So I managed to create a workable WooCommerce gallery using Meow Gallery “naturally”!
(I made it easy to create a link by matching my attachment title to the WooCommerce product title.)

As soon as I clean up my spaghetti code I intend to document it on my blog, along with the many trials and tribulations trying to set up a separate WooCommerce tiled gallery. In some sense I think this could be a game-changer of sorts, as WooCommerce advanced gallery solutions are few and far between.

Jordy, a future request would be to allow user input for a set space below the image, and allow the user to specify in Meow Gallery the name of the boolean custom field in the attachment that would turn it on or off as the gallery is assembled, if that makes sense.
</aside>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jordy, again many thanks for a superb product!

I’d like a solution for this, too.

Here’s what what I think could be an easy-to-implement feature that could help a lot of people. Create a field, let’s call it aspect. When the main image is selected for Product, examine it. For height>width, then “portrait”. For height<width, “landscape”. And for height=width, “square”.

This aspect value can then be written as a selector to the product image wrapper and we can then use it to style with CSS as desired.

For extra credit, allow the user to enter any string value in place of the computed one, to allow for even more detailed control.

For me, the first issue was not activating individual images. Duh!