enollo

Hi Jeroen,

It works great! Thank you.

I’m curious, did you find out why it was Genesis specific?

Thanks,

Tamara

Hi Jeroen,

I’m actually developing a website for a client so it is quite normal that I see notices ??

Thanks for looking into this. Let me know what they say.

Cheers,

Tamara

Hi Sormano,

That’s unfortunate but understandable.

I ran into an issue with the Genesis framework, seeing the following notices:

NOTICE: UNDEFINED PROPERTY: STDCLASS::$TERM_ID IN /.../.../WOOCOMMERCE-PRODUCTS-PER-PAGE/OBJECTS/WPPP-DROPDOWN.PHP ON LINE 30

 NOTICE: UNDEFINED INDEX: BEHAVIOUR IN /.../.../WOOCOMMERCE-PRODUCTS-PER-PAGE/OBJECTS/WPPP-DROPDOWN.PHP ON LINE 32

NOTICE: UNDEFINED VARIABLE: ACTION IN /.../.../WOOCOMMERCE-PRODUCTS-PER-PAGE/OBJECTS/WPPP-DROPDOWN.PHP ON LINE 40

These do not show up with two other themes I have tested it with so I assume it might be Genesis specific. Either way, changing the if/esleif in wppp_create_object() a bit helped:

$action = '';
if ( isset($cat->term_id) && true == $cat->term_id && isset($this->options['behaviour']) && true == $this->options['behaviour'] && isset($cat->taxonomy) && 'product_cat' == $cat->taxonomy ) :
   $action = ' action="' . get_term_link( $cat->term_id, 'product_cat' ) . $query_string . '"';
elseif ( isset($this->options['behaviour']) && true == $this->options['behaviour'] ) :
   $action = 'action="' . get_permalink( woocommerce_get_page_id( 'shop' ) ) . $query_string . '"';
endif;

Cheers,

Tamara

All done, I kept the order the same as it is in the Stripe docs. You may wish to reorder it.

Thanks for the great plugin!

“payment_button_label” seems fine.
I’ll whip up a quick pull request (my username on GitHub is tamarazuk)

Actually, I got it wrong, you do not have the button label setup yet. ‘checkout_button_label’ is being set as data-panel-label (the button label on the checkout screen)

I’m hoping to customize the text to be shown on the default blue button ( “Pay with Card”)
Based on the Stripe docs, I assume data-label is the right attribute to pass them.
https://stripe.com/docs/checkout#integration-simple-options

Thanks.

Thanks for the quick update!
I’m manually adding the label attribute so I have access to it now. Is it safe to assume it will stay ‘checkout_button_label’?

I searched for the plugin on GitHub using “Simple Stripe Checkout”. Sorry I missed it ??

1) I’d like to see a ‘label’ shortcode attribute to allow the use to easily adapt the button label. You can use the data-label attribute provided by Stripe

2) GitHub (or similar) repo for easy contributions (I was looking for this so i can add the above)

Hi @primaltwins,

It really depends on the theme you are using and whether or not it alters the standard WooCommerce templates.

Even if your theme has altered the templates, if it is well coded then the below code should move the Wishlist button to right below your product image, at which point you can use CSS to absolutely position it.

function enollo_move_wc_wishlist_button($product) {
	if ( shortcode_exists('yith_wcwl_add_to_wishlist') ) {
		echo do_shortcode( "[yith_wcwl_add_to_wishlist]" );
	}
}
add_action( 'woocommerce_product_thumbnails', 'enollo_move_wc_wishlist_button' );

Make sure you select “Use shortcode” as the Position in the Wishlist settings tab.

Now is the fun CSS part.

in style.css or another css file add

.yith-wcwl-add-to-wishlist {
	position: absolute;
	right: 0;
	bottom: 0;
	z-index: 1000;
}

Oops, forgot the return. If anyone is looking to add this temporary solution here is the updated function to be placed in a custom plugin or functions.php

/**
 * Add 'full' image size to Cloudinary $sizes array
 */
function enollo_cloudinary_intermediate_image_sizes_advanced( $sizes ) {
	$sizes['full'] = array( 'width' => 9999, 'height' => 9999, 'crop' => false);
	return $sizes;
}
add_filter( 'intermediate_image_sizes_advanced', 'enollo_cloudinary_intermediate_image_sizes_advanced' );

Thanks for the patch!

I actually realized that I can hide items for logged in users right after I posted, but it seems a bit cumbersome to explain to clients.

I understand the logic is a bit messy and it might take a few tries to get it just right. In terms of UX, i feel something like my checkbox example above would be more understandable. Maybe even a way to show/hide the user roles checkboxes as they are not always needed. I can already imagine the emails from my clients if they try to edit the menus themselves ??

Thanks for a handy plugin!

Hey Nick,

Thanks for addressing this so quickly ??

Thanks ??
Just like you stated in the ticket, I was also concerned about the less techy people. Especially if WordPress continues developing features as plugins first (which is a great way to go), people with all sorts of backgrounds will stumble upon these plugins and they may not know what to do when an official release comes around. Automatic updates make it even harder to pinpoint the issue.

I agree, the plugins should be forced to deactivate on WP core update. I think the user shouldn’t be allowed to active it again, and an alert similar to the “update available” alert should inform the user that the plugin can be safely deleted.

I have fixed this myself before the most recent update which claims to have added this in.

I have not updated as I have made many modifications to the plugin and do not want to re-add them. If you’re still having issues I can take a look at what I did to fix this and give you the break down.

Let me know.

I had a similar issue

Open uninstall.php and comment out line 15 changing it from this

require_once( 'yith-wcwl.php' );

to this

//require_once( 'yith-wcwl.php' );

Poorly coded in my opinion. The issue is that this file they are requiring doesn’t exist and is apparently not needed because uninstalling works just fine without that line