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 6131

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 6131

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 6131

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 6131

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 6131

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 6131

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 6131

Warning: Cannot modify header information - headers already sent by (output started at /home/joaomanu/magnumwineclub.com/wp/wp-includes/functions.php:6131) in /home/joaomanu/magnumwineclub.com/wp/wp-includes/feed-rss2.php on line 8
http://magnumwineclub.com/wp Magnum Wine Club Aveiro Fri, 12 Jan 2018 21:26:24 +0000 pt-PT hourly 1 74084812 http://magnumwineclub.com/wp/podcast/magnum-wine-radio-117-temos-que-pensar-mais-nos-consumidores-normais/ http://magnumwineclub.com/wp/podcast/magnum-wine-radio-117-temos-que-pensar-mais-nos-consumidores-normais/#respond Fri, 12 Jan 2018 21:30:12 +0000 http://magnumwineclub.com/wp/?post_type=podcast&p=616 Hoje é dia de opinião. Pensar que a comunicação dos vinhos está pouco centrada no consumidor normal. Não falo da publicidade mas de tudo o resto. A opinião, livre como habitual.

]]> http://magnumwineclub.com/wp/podcast/magnum-wine-radio-117-temos-que-pensar-mais-nos-consumidores-normais/feed/ 0 616 http://magnumwineclub.com/wp/podcast/magnum-wine-radio-113-como-avaliar-a-critica-como-julgar-como-criticar/ http://magnumwineclub.com/wp/podcast/magnum-wine-radio-113-como-avaliar-a-critica-como-julgar-como-criticar/#respond Wed, 03 Jan 2018 21:30:47 +0000 http://magnumwineclub.com/wp/?post_type=podcast&p=601 Isto de começar o ano com dúvidas existenciais é complicado. Mas ao mesmo tempo serve para analisar o mundo dos vinhos. Onde ouvimos todas as verdades e todas as mentiras do mundo. E esta questão passa, também, pela minha área profissional, da comunicação. O melhor é ouvirem e tirarem as vossas conclusões que eu, em breve, voltarei ao tema!

]]> http://magnumwineclub.com/wp/podcast/magnum-wine-radio-113-como-avaliar-a-critica-como-julgar-como-criticar/feed/ 0 601