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
Pemakaian Pelitup Muka Di Tempat Awam Diwajibkan Mulai 1 Ogos – Independent

Pemakaian Pelitup Muka Di Tempat Awam Diwajibkan Mulai 1 Ogos

Reading Time: < 1 minute

KUALA LUMPUR | Penggunaan pelitup separuh muka akan dikuatkuasakan di kawasan awam yang sesak dan di dalam kenderaan awam bermula 1 Ogos ini.

Keputusan itu diambil oleh kerajaan berikutan peningkatan kes Covid-19 sejak 3 hari lalu serta ketidakpatuhan orang ramai terhadap SOP, menurut Menteri Keselamatan, Datuk Ismail Sabri Yaakob pada sidang media di Bangunan Parlimen hari ini.

“Kementerian Kesihatan melaporkan 50 peratus mereka yang menjalani kuarantin di rumah tidak mematuhi SOP,” katanya.

Sebelum ini kerajaan tidak menguatkuasakan peraturan penggunaan pelitup separuh muka kerana akan membebankan golongan berpendapatan rendah tambahan pula ia perlu ditukar setiap 3 jam walaupun penggunaan 1 pelitup muka sehari dibenarkan.

“Bagaimanapun, Pertubuhan Kesihatan Sedunia telah menetapkan bahawa orang ramai boleh menghasilkan sendiri pelitup muka dengan mengikuti syarat-syarat spesifikasi yang ketat.

“Kementerian Kesihatan Malaysia akan mengeluarkan spesifikasi untuk pelitup muka buatan tangan tidak lama lagi, “katanya.

Beliau turut mensarankan orang ramai mula memakai pelitup muka dari sekarang memandangkan tidak lama lagi cuti perayaan Hari Raya Haji akan bermula.