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/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

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/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

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/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

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/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

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/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

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/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085

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 `init` 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/mpafbwbr24jp/public_html/wp-includes/functions.php on line 6085
Somalia strongly condemns assassination attempt on Sudan PM - Al Jasiira News
Site icon Al Jasiira News

Somalia strongly condemns assassination attempt on Sudan PM

Al Jasiira- News
Somalia strongly condemns assassination attempt on Sudan PM

The Federal Government of Somalia has strongly condemned the assassination attempt on Prime Minister of Sudan, Abdallah Hamdouk on Monday.

Sudan’s prime minister survived an assassination attempt after an explosion went off near his convoy in the capital of Khartoum, Sudan’s state media said.

In a statement issued on Monday by Somalia’s ministry of Foreign Affairs and International Cooperation condemned the attack, and expressed its stand and solidarity with the Sudan government in its fight against violence and extremism.

Prime Minister Abdallah Hamdouk has on his part assured the attack will only strengthen the wheel of change in the country.

“I would like to assure the people of Sudan that I am safe and in good shape. Rest assured that what happened today will not stand in the way of our transition, instead it is an additional push to the wheel of change in Sudan.” He said.

Officials from Khartoum have also confirmed that no one was hurt in the attack.

“An explosion hit as Prime Minister Abdalla Hamdok’s car was driving by but thank God no one was hurt,” Ali Bakhit, the prime minister’s office director, said on Monday.

Exit mobile version