How To Get The Wishlist URL From YITH Wishlist Plugin

YITH Wishlist Plugin is one of the most popular plugin for Woocommerce to add a Wishlist to your WordPress website. The good thing about this plugin is they make it very simple to add the wishlist button to the product page. If you are a regular user, there isn’t many things else to do. However, if you are a developer, you may wonder how can you get the wishlist URL so you can integrate to your own plugin or theme. That’s exactly what I’m going to show you in this post.

How to get the add to wishlist URL of a particular product

If you need nothing else but a working add to wishlist button, you can put this in your code:

do_shortcode('[yith_wcwl_add_to_wishlist product_id=your_product_id]');

Make sure you replace your_product_id with actual ID.

However, YITH wishlist plugin only provide you with the text link like this:

add to wishlist yith button

What if you want to remove the text and get just the heart?

Well, this is how you can get only the URL of the add to wishlist button of YITH wishlist plugin:

esc_url( add_query_arg( 'add_to_wishlist', $your_product_id ) )

What you get from this code is an URL. When you go to that URL, the product will be added to their wishlist.

Pretty easy, isn’t it.

However, I would recommend you send an ajax request to that url instead of open it. That would improve the visitors’ experience greatly.


One final warning to plugin developers and users of wishlist plugin alike, don’t use multiple wishlist plugins on your site. The reason is because, for example, you installed and activate two wishlist plugin called A and B. There are times you add a product to A’s wishlist and try to view the B’s wishlist page. You will see things that you may not expected. So, remember not to use two different wishlist plugin on one site.



Accessing Media Files (Audio, Video, Images…) From DigitalOcean Spaces Using Java

Recently, I need to upgrade my English learning app on Android to use multiple servers. Previously, I used two servers already. However, the way I manage media files caused me a lot of headache. So, I decided to switch to DigitalOcean since they have servers around the world and the pricing is good ($5 for 250GB storage and 1TB monthly transfer, which is good).

The initial problem with DigitalOcean spaces

Coming from old-school servers, I thought I can upload the files to DigitalOcean spaces using FTP and access the files directly as I usually used. However, the first problem is you cannot upload to spaces using FTP and the second problem is in order to make a file accessible to public, you need to set it permission to public. If you have one or two files, that wouldn’t be a problem.

I have more than 18,000 files.

The solutions to uploading multiple files

It turned out that DigitalOcean spaces use Amazon s3 technologies. So, in order to upload to spaces, you need to have FileZilla Pro (paid) or CyberDuck(free). I chose FileZilla Pro because it allows you to resume failed transfers while CyberDuck doesn’t allow that (or I couldn’t find where is that option).

The solution to accessing files

As my app used by thousands of people, the media files need to be accessible to all of the users. Actually, it is very easy to generate a public accessible URL for any files (they are called objects) using the aws-android-sdk. In case you need a working sample code, here it is:

public class DigitalOcean implements MediaServer{

    private static final String KEY = "YOUR_KEY";
    private static final String SECRETS = "YOUR_SECRETS";

    private String endpoint, bucketName;
    private AmazonS3Client s3Client;

    public String getEndpoint() {
        return endpoint;

    public String getType() {
        return "s3";

    public DigitalOcean(String endpoint, String bucketName)
        this.bucketName = bucketName;
        this.endpoint = endpoint;
        AWSCredentials myCredentials = new BasicAWSCredentials(

        s3Client = new AmazonS3Client(myCredentials);


    public String getMediaURL(String objectPath)
        GeneratePresignedUrlRequest request = new GeneratePresignedUrlRequest(bucketName, objectPath);
        URL objectURL = s3Client.generatePresignedUrl(request);

        return objectURL.toString();


As you can see, I created an object to generate URL to any files(objects). For example, here is a sample space url:

Accessing Media Files (Audio, Video, Images...) From DigitalOcean Spaces Using Java 3

The bucket name would be data-sample.

If your file, let call it song.mp3 located at /data-sample/media/song.mp3, the objectPath would be: /media/song.mp3.

If you run the method getMediaURL(), you will get the path to the file that is accessible to your users but you don’t have to mark the file public.