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
Orang Ramai Diingat Berwaspada Terhadap Kehadiran Buaya – Independent

Independent

Orang Ramai Diingat Berwaspada Terhadap Kehadiran Buaya

—

by

Editor
in ,
   
Reading Time: < 1 minute

JOHOR BAHRU, 17 Dis – Jabatan Hidupan Liar Johor menasihatkan orang ramai supaya berwaspada terhadap ‘buaya tembaga’ yang mungkin didapati di sungai-sungai banjir di sembilan daerah di negeri ini.

Pengarahnya Salman Saaban berkata ini berkemungkinan berlaku memandangkan terdapat populasi buaya di sembilan sungai di negeri ini.

Sungai-sungai ini adalah Sungai Batu Pahat, Sungai Jemaluang dan Sungai Endau (Mersing), Sungai Lebam dan Sungai Sedili (Kota Tinggi), Sungai Muar (Muar), Sungai Pulai (Pulai), dan Sungai Johor dan Sungai Skudai (Johor Bahru).

“Tempat-tempat di mana buaya boleh tersasar adalah longkang-longkang dan terusan.

“Ia akan mencari dan memakan bangkai haiwan yang tenggelam semasa banjir,” katanya kepada Bernama ketika dihubungi.

Salman berkata sesiapa yang menemui reptilia ini harus menjauhkan diri daripadanya dan memaklumkan kepada jabatan.

“Jangan memprovokasi atau panik kerana ini boleh menyebabkan mereka menjadi agresif.

“Berhati-hati dengan persekitaran untuk mengelakkan pertemuan dengan buaya ini,” katanya.

Banjir baru-baru ini telah menjejaskan lebih 9,000 rumah penduduk di daerah Mersing, Kota Tinggi, Segamat, Kluang, Batu Pahat, Pontian, Johor Bahru, Muar dan Kulai.

– BERNAMA