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
Status Pulau Sembilan Ditentukan Tidak Lama Lagi – Independent

Status Pulau Sembilan Ditentukan Tidak Lama Lagi

Reading Time: < 1 minute

Kedudukan Pulau Sembilan sama ada akan dibuka semula atau ditutup akan ditentukan dalam masa terdekat.

Menurut Pengerusi Jawatankuasa Pelancongan, Kesenian dan Kebudayaan negeri, Tan Kar Hing, kertas kerja mengenai perancangan masa depan pulau itu sedang dalam proses dan akan dibentangkan kepada kerajaan negeri tidak lama lagi.

Pulau Sembilan telah ditutup sejak April tahun lepas kepada semua aktiviti pelancongan ekoran keindahan pulau tersebut terancam akibat aktiviti komersial yang tidak terkawal. Pengusaha pelancongan tidak menghormati peraturan dan kawalan yang telah ditetapkan oleh kerajaan telah mengakibatkan kerosakan ekosistem alam di sepanjang pantainya. Pulau Sembilan terkenal di kalangan pelancong dan pencinta alam kerana pasir pantai yang bercahaya biru pada waktu malam akibat tindakbalas cahaya phytoplankton yang bersifat bioluminescent.

“Sama ada Pulau Sembilan kekal ditutup atau dibuka kepada orang ramai akan ditentukan oleh kerajaan, kita perlu tunggu selepas kertas kerja siap sepenuhnya,” katanya kepada pemberita selepas menghadiri Majlis Jamuan Hari Raya Aidilfitri anjuran Tourism Perak di Ipoh malam tadi.

Menurut Tan, beliau berpuas hati selepas lawatannya ke pulau tersebut untuk melihat kerja-kerja pemuliharaan oleh JKR.

Pulau Sembilan terletak kira-kira 17 kilometer arah ke Selatan dari Pulau Pangkor seperti dalam peta.