Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp 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/joaomanu/magnumwineclub.com/wp/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/joaomanu/magnumwineclub.com/wp/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/joaomanu/magnumwineclub.com/wp/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/joaomanu/magnumwineclub.com/wp/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/joaomanu/magnumwineclub.com/wp/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/joaomanu/magnumwineclub.com/wp/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/joaomanu/magnumwineclub.com/wp/wp-includes/functions.php on line 6170

Warning: Cannot modify header information - headers already sent by (output started at /home/joaomanu/magnumwineclub.com/wp/wp-includes/functions.php:6170) in /home/joaomanu/magnumwineclub.com/wp/wp-includes/feed-rss2.php on line 8
Cremant – Magnum Wine Club http://magnumwineclub.com/wp Magnum Wine Club Aveiro Mon, 11 Mar 2019 15:53:47 +0000 pt-PT hourly 1 74084812 Magnum Wine Radio 232 – Veuve Ambal dá-se a conhecer http://magnumwineclub.com/wp/podcast/magnum-wine-radio-232-veuve-ambal-da-se-a-conhecer/ http://magnumwineclub.com/wp/podcast/magnum-wine-radio-232-veuve-ambal-da-se-a-conhecer/#respond Mon, 11 Mar 2019 21:30:12 +0000 http://magnumwineclub.com/wp/?post_type=podcast&p=1461

“Veuve” é a designação francesa para Viúva. E sim, parece ser normal que os vinhos se chamassem “viúva qualquer coisa” pois em Portugal, em Colares, também temos uma viúva, Gomes de seu nome. Em Champagne, a mais conhecida é a Veuve Cliquot, dos conhecidos champagnes com a mesma designação. Mas na zona da Borgonha, outra viúva desponta, uma marca com a bonita idade de 120 anos (feitos o ano passado) e que conta com vários domínios, grandes vinhos e uma marca forte de “Crémant de Bourgogne”: Veuve Ambal.

Jeannette Terras é a entrevistada deste podcast. A responsável pelas vendas europeias dá a conhecer a casa, o estilo e a forma de ser de uma empresa com número gigantes para o conceito português. Negócio puro e duro, com váriso domínios adquiridos e uma fortíssima presença na Borgonha. Para ouvir (em inglês) no programa!

]]> http://magnumwineclub.com/wp/podcast/magnum-wine-radio-232-veuve-ambal-da-se-a-conhecer/feed/ 0 1461