Jon Boss

Thanks so much for the update on this one, 10-4.

Hi Amanda,

While this is certainly possible to do using some custom hooks – we are also planning to release a new premium version of the plugin shortly that will give you control over features like this! You will be able to set the button location yourself. Currently there is no way built into the plugin that allows you to display the button on the archive page without some custom coding. Be sure to check back when the premium version is available, as it sounds like it might help you out!

Cheers,
Jon

Hi Josef,

You can use the two lines of code above to change the position of the button to anywhere on your product page! You’ll just want to know exactly which hook you’d like the button to appear on. You can take a look at the templates/content-single-product.php file for a list of those hooks!

We will also be releasing a pro version of the plugin soon, which will give you the ability to easily adjust the button positioning through your admin panel!

Cheers,
Jon

Hi Amanda,

Thanks for using the plugin! This is a notice you’re seeing and not an error. It is correct though – there is a line in the plugin that shouldn’t be accessing a property directly – but through it’s ‘get’ function. I’ll be sure to update that with the next push. However for now – you may want to disable these types of notices from appearing on your site directly. The plugin will still work correctly – its just that you’re in debug mode and printing notices out on the page.

To avoid that, I would recommend:

In your site’s wp-config.php file, you can update your settings for debug mode. Your probably have something like this:

define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_DISPLAY’, true );

What I normally do is log any errors to a debug file so I can see them easily, but they don’t print out on my page, like this:

define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_DISPLAY’, false );
define( ‘WP_DEBUG_LOG’, true );

You’ll certainly want that for a production site anyway – if not your local environment! But again – perfectly legitimate notice, and I’ll make sure this gets updated.

Jon

@albinholmlund

Can’t thank you enough for helping to debug this one – great catch. I’ve just pushed an update for you Patrick – that will fix this compatibility issue with PHP < 7.0. You can update and this should be taken care of as suggested above.

Thanks again, will mark this one resolved.

Hi,

Thanks for reaching out – glad you like the plugin! We actually are currently working on a paid, ‘PRO’ version of the plugin that will contain additional features like this – and it will be released soon! I will be sure to post back here with a link to purchase our paid extension as soon as its available.

Cheers,
Jon

Hi Jason,

So the actions used in the plugin have changed with the newest update. To make way for some new features and upgrades we’ve updated the structure somewhat – you can still easily change the position of the button if you like, what you’ll want to do is replace those two lines:

remove_action(‘woocommerce_after_single_product’, array( ‘SWF_Favourites_Button’, ‘display_button’ ), 10);
add_action(‘woocommerce_before_single_product’, array( ‘SWF_Favourites_Button’, ‘display_button’ ), 10);

And that should put the button location back to where it was before! Let me know if that works for you.

Hi Patrick,

Glad to hear you like the plugin, thanks for reaching out. What version of the plugin do you have installed? It looks like there must be something wrong with that file – is it possible it was edited accidentally? That line declares a function ‘print’ – it looks like maybe something is missing. Would you be able to download the latest copy of the plugin and let me know if the issue persists?

Hi John,

Thanks for the link above. I reviewed the conversation between yourself and the Woocommerce devs – it looks like you’ve found a good solution to this. I’m running the latest copy of both plugins, but it doesn’t look like this change has been made yet – is that right? I’m still having the same issue. If not, any idea when this will be implemented?

Thanks a lot.

Great – thank you!

Hi Steven,

Just had a quick question RE: 4.8.7. I had a site also auto-update today to this version. What it looks like to me is this was released retroactively to fix the same vulnerability addressed in 4.9.7, and auto-update sites that may not be current.

Is that correct? I can’t find any more info on this version.

Hi Calymond,

Thanks for the message – we’d like to expand the plugin and add language support at some point in the future for sure. Currently, however – the plugin is built English-only, and will require some updates. My time is unfortunately limited! In the future, when we do offer language support – I’ll be sure to get in touch.

Cheers,
Jon

Hi Dave,

Apologies for the late reply on this one. I think you’re right on the money in thinking this is a caching issue. When you switch browsers – everything updates properly, which tells me your favourites are being updated in the database correctly, and the data is being pulled and displayed properly. The issue is that your cache is loading a generated HTML file, rather than regenerating the HTML to display. This can greatly help with speed, but is an issue for dynamic content like this. What I would first try is: disable WP Super Cache and see if the problem persists.

If that fixes the problem, WP Super Cache does offer support for disabling caching for certain pages! If you simply disable page caching on the favourites page – that should solve your issue.

Let me know if I can be of further help!

@keithpickeringkmg

Unfortunately not just yet. The issue I describe above I’ve contacted support about – essentially they have not implemented this as an option for the reasons I stated.

I’m waiting to hear from a client to determine if I’ll continue and find a custom solution to get this working – If I do come up with something I’ll be happy to share it with you!

@aecorn,

Thanks once again for pointing this out for me. That shortcode definitely should have been returning rather than echoing – that has been updated in v 1.4 as well. Thanks a lot for your insights.