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
Pengusaha Ladang Ayam Diwajib Guna Reban Tertutup – Independent

Pengusaha Ladang Ayam Diwajib Guna Reban Tertutup

Reading Time: < 1 minute

IPOH | Pengusaha ladang ayam di negeri ini akan diwajibkan menukar reban ayam daripada reban terbuka kepada reban tertutup sebagai langkah mengatasi masalah lalat.

Exco Infrastruktur, Kemudahan Awam, Pertanian dan Perladangan, Dato’ Abdul Yunus Jamhari berkata, arahan menggunakan reban  tertutup seratus peratus dengan kelulusan pihak berkuasa negeri itu akan dilaksanakan dalam tempoh yang akan ditetapkan setelah pindaan terhadap enakmen berkuatkuasa.

“Langkah mewajibkan beban tertutup merupakan antara perkara-perkara yang akan ditambah baik diambil kerajaan dalam memastikan masalah lalat ini dapat diselesaikan,’’ katanya pada sidang media di bilik media Bangunan Perak Darul Ridzuan, Ipoh pada Khamis.

Selain itu  menurut Yunus, pengusaha ladang penternakan ayam diwajibkan mengguna baja kompos mengikut Akta Baja yang sedang disediakan oleh Jabatan Pertanian.

“Kerajaan akan mengenakan kadar penalti yang lebih tinggi terhadap kesalahan-kesalahan yang berkaitan dengan pengurusan sisa unggas,’’ katanya.

Abdul Yunus berkata, penyelesaian jangka pendek dan panjang yang akan dilaksanakan oleh Jabatan Veterinar, Pejabat Daerah dan Tanah Manjung serta Majlis Perbandaran Manjung juga telah mengenal pasti beberapa langkah berkesan yang perlu dilaksanakan dalam masa terdekat.

Katanya, antara cadangan itu termasuklah penubuhan satu pasukan penguatkuasa khas oleh Jabatan Vetarinar dengan bantuan daripada agensi-agensi penguatkuasa di daerah Manjung.

Di samping itu, katanya, tindakan tegas perlu diambil kepada mana-mana pengusaha ladang yang gagal menepati  atau melanggar mana-mana peraturan yang telah digariskan setelah notis atau tindakan remedi gagal diikuti.

Beliau mengulas masalah lalat yang dihadapi oleh penduduk di kawasan berhampiran ladang ternakan ayam di Segari, Manjung telah berlarutan sejak sekian lama.

Baru-baru ini pada 4 November 2019, masyarakat setempat di Segari telah mengemukakan aduan kepada Jabatan Perkhidmatan Veterinar melalui NGO Rakan Gabungan Segari.

Aduan dan rintihan penduduk ini juga telah mendapat liputan daripada pihak media dimana lebih 20 tahun masalah lalat ini mengganggu aktiviti dan kehidupan seharian penduduk.