Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/enebbe/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the visibility-logic-elementor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/enebbe/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the elementor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/enebbe/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the visibility-logic-elementor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/enebbe/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woo-product-feed-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/enebbe/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the insert-headers-and-footers domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/enebbe/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-paypal-payments domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/enebbe/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-paypal-payments domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/enebbe/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/enebbe/public_html/wp-includes/functions.php on line 6121
ENEBBE

No products in the cart.

Plum + White Chocolate Cheesecake

Serve:

6-8

Preparation:

Cook Time:

30-40 minutes

Ingredients

 

  • 250G SCOTCH FINGER BISCUITS
  • 150G BUTTER, MELTED
  • 3 TBSP BOILING WATER
  • 1 1/2 TSP GELATINE POWDER
  • 375G CREAM CHEESE, AT ROOM TEMPERATURE
  • 1/4 CUP CASTER SUGAR
  • 300ML THICKENED CREAM
  • 1/2 TSP VANILLA BEAN PASTE
  • 200G WHITE COOKING CHOCOLATE, MELTED
  • TOPPING:
  • 1 BOTTLE QUEEN GARNET PLUM NECTAR
  • 3 TBSP BOILING WATER
  • 1 1/2 TSP GELATINE POWDER

How To

  • Line a 20 x 30cm slice pan with non-stick baking paper, allowing the sides to overhang by 1 inch. In a food processor combine biscuits and butter until the mixture resembles fine breadcrumbs. Spread the crumb mixture over the base of the pan, pressing down firmly. Place in the fridge to chill.
  • Place boiling water in a small microwave safe dish. Sprinkle with gelatine and stir to combine. Microwave for 30 seconds, stir vigorously to ensure all the gelatine has dissolved – set aside.
  • Meanwhile, use a beater or an electric mixer to beat cream cheese and sugar until smooth. Add cream, vanilla paste and melted chocolate and beat until well combined. Add in the gelatine mixture and beat briefly to combine. Pour into the prepared pan and smooth over with the back of a spoon.
  • To make the Queen Garnet Plum topping, place boiling water in a small microwave safe dish. Sprinkle with gelatine and stir to combine. Microwave for 30 seconds, stir vigorously to ensure all the gelatine has dissolved – set aside to cool slightly. Add the Queen Garnet Plum Nectar and gelatine to a blender and blitz until combined. Pour plum mixture over cheesecake and set in the fridge for at least 3 hours. Cut into squares and serve.

Get In Touch

Shop

Navigation