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
Feri Pulau Pinang Akan Dijadikan Produk Pelancongan – Independent

Feri Pulau Pinang Akan Dijadikan Produk Pelancongan

Reading Time: < 1 minute

Menteri Pengangkutan, Dr Wee Ka Siong berkata bahawa perkhidmatan feri Pulau Pinang tidak dimansuhkan pada tahun baru 2021 ini.

Wee berkata kerajaan persekutuan hanya berusaha meningkatkan perkhidmatan feri ke tahap yang lebih baik.

Beliau mendakwa kerajaan Pakatan Harapan sebelum ini pernah mencadangkan feri Pulau Pinang diganti dengan catamaran.

Beliau memetik kenyataan oleh Senator Lim Hui Ying pada 17 Dis bahawa penggantian feri berusia puluhan tahun itu adalah “pemodenan yang tidak dapat dihindari”.

“Bukankah menggantikan feri yang terdedah kepada kerosakan dengan catamaran merupakan langkah yang lebih praktikal untuk melindungi keselamatan orang Pulau Pinang dan lebih bermanfaat bagi industri pengangkutan Pulau Pinang?” soalnya di laman Facebook beliau.

Dalam jangka pendek, dua kapal penumpang berkapasiti tinggi akan mula beroperasi pada Hari Tahun Baru untuk mengangkut pejalan kaki dengan kecepatan hampir dua kali ganda dari apa yang dapat dikendalikan feri sedia ada.

Terminal feri yang ada di pulau dan di Butterworth juga akan ditingkatkan supaya pengangkut kenderaan dapat berlabuh di terminal.

Peningkatan ini dijangka memakan masa 12 hingga 18 bulan.

Selepas itu, feri Pulau Pinang yang terakhir akan ditukar menjadi muzium terapung, restoran dan tarikan pelancongan lain.