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

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the gotmls 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/independ/public_html/wp-includes/functions.php on line 6170
PKPD Di Dua Daerah Bentong Dilanjutkan Hingga Awal Tahun Depan – Independent

PKPD Di Dua Daerah Bentong Dilanjutkan Hingga Awal Tahun Depan

Reading Time: < 1 minute

KUALA LUMPUR | Perintah Kawalan Pergerakan yang Diperketatkan (PKPD) untuk Pangsapuri Amber Court dan Pangsapuri Ria di daerah Bentong, Pahang dilanjutkan dari 24 Disember hingga 6 Jan 2021.

Menteri Kanan (Kluster Keselamatan) Datuk Seri Ismail Sabri Yaakob juga berkata PKPD untuk rumah kongsi Kampung Semaut di daerah yang sama pula akan berakhir esok.

Tambahnya, terdapat 381 kes positif Covid-19 di Pangsapuri Amber Court setakat ini sementara 85 masih menunggu keputusan.

“KKM juga telah melakukan 1.041 ujian saringan di Ria Apartment dan mengesahkan ada risiko jangkitan baru dikesan sementara ada hubungan dekat dengan kes positif yang perlu diuji,” katanya pada sidang media mengenai Perintah Pemulihan Pergerakan Pemulihan (PKPP) disini hari ini.

Beliau berkata, pemeriksaan yang dilakukan ke atas penduduk rumah kongsi Kampung Semaut mendapati hanya tiga yang mengalami simptomatik dan ujian antigen RTK yang dilakukan ke atasnya ternyata negatif.

Pada 9 Disember, ketiga-tiga kawasan tersebut ditempatkan di bawah PKPD dari 10 hingga 23 Disember setelah 55 kes positif Covid-19 dikesan di mukim, yang kebanyakannya melibatkan pekerja migran.