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/1153080.cloudwaysapps.com/cprprqfuzz/public_html/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/1153080.cloudwaysapps.com/cprprqfuzz/public_html/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/1153080.cloudwaysapps.com/cprprqfuzz/public_html/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/1153080.cloudwaysapps.com/cprprqfuzz/public_html/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/1153080.cloudwaysapps.com/cprprqfuzz/public_html/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/1153080.cloudwaysapps.com/cprprqfuzz/public_html/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/1153080.cloudwaysapps.com/cprprqfuzz/public_html/wp-includes/functions.php on line 6131
DIOS CON NOSOTROS – Impacto Evangelístico
Deprecated: Creation of dynamic property OMAPI_Elementor_Widget::$base is deprecated in /home/1153080.cloudwaysapps.com/cprprqfuzz/public_html/wp-content/plugins/optinmonster/OMAPI/Elementor/Widget.php on line 41

DIOS CON NOSOTROS

Cuando el ángel se presentó a José en sueños, le dio ciertas indicaciones cuando naciera el niño. Una de ellas era el cumplimiento de lo que ya había sido establecido por Dios mismo, alrededor de setecientos años antes, cuando habló por medio del profeta Isaías (Is. 7:14).

2 Min lectura

Por Rev. Ramón Aponte

Entonces había hecho el anuncio que llegaría al mundo a través de una virgen y que su nombre sería Emanuel. En el Nuevo Testamento, que estaba escrito en griego y no en hebreo, se aclara “que traducido es: Dios con nosotros” (Mt. 1:23). Hablar de que aquel niño llegaría a ser “Jesús”, es describir al Dios que vino al mundo con poder y acción para derrotar al demonio y a la muerte, sufriendo la consecuencia de los pecados. Pero para que ello llegue era necesario que Dios estuviera con nosotros. De ese modo, “Emanuel” es la descripción más amplia de lo que significó la encarnación. Cristo nuestro Salvador es la misma presencia de Dios en este mundo, a nuestro lado ( Jn. 14:8-10).

TODOS PODEMOS SENTIRLE CERCA

Para los paganos, que habían llegado en algunos casos, como Platón o Aristóteles, a vislumbrar la posibilidad de un Dios único, este era un ser lejano y ausente del mundo. Para los mismos judíos, el temor supersticioso a la posibilidad de ver a Dios tenía su raíz en la conciencia de que “Dios está en los cielos, y tú sobre la tierra” (Ec. 5:2). Continúa leyendo en https://bit.ly/3pb1JUJ

[ruby_related total=3 layout=6]