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
Pihak Pengurusan SUKMA Gagal Sediakan Template Kedudukan Pungutan Pingat – Independent

Independent

Pihak Pengurusan SUKMA Gagal Sediakan Template Kedudukan Pungutan Pingat

—

by

Admin
in
   
Reading Time: < 1 minute

Bahagian teknikal pengurusan SUKMA 2018 amat mengecewakan apabila mereka tidak dapat membantu kami untuk mendapatkan ‘kod html’ atau ‘widget’ untuk seksyen kedudukan pungutan pingat atau ‘medal standing’ seperti yang terpampang di dalam laman web rasmi SUKMA 2018 seperti dalam gambar.

Lebih memalukan apabila kami bercakap dengan pihak yang berkenaan, mereka mencadangkan menggunakan kaedah ‘tangkap layar’ atau ‘screen capture’ kemudian memasukkan ke dalam laman web kami. Adakah mereka sedang membuat lawak dengan memberi jawapan sedemikian?

Siapa yang tahu tentang pembangunan struktur laman web akan faham apa yang kami maksudkan ini. Untuk seksyen status pungutan pingat, ia bukanlah sesuatu yang boleh dibuat secara ‘screen capture’ kerana kedudukan pingat sentiasa berubah setiap masa. Adakah mereka mahu kami buat ‘screen capture’ setiap saat atau minit setiap kali kedudukan pingat berubah? Adalah amat melucukan menerima jawapan sedemikian dari pihak pengurusan SUKMA yang berada di pusat media.

Setelah menghubungi melalui telefon ke pejabat SUKMA, mereka gagal memberikan jalan penyelesaian, kemudian memberi kami nombor telefon Majlis Sukan Negara (MSN) untuk dihubungi. Cubaan kami untuk menghubngi nombor yang diberi berkali-kali telah gagal.

Maka dengan itu, kami ingin membuat kenyataan di sini bahawa untuk mengetahui kedudukan pungutan pingat, kami tidak dapat menyediakannya di laman web ini sebaliknya anda perlu perlu pergi ke laman web rasmi SUKMA iaitu di http://result.perak.gov.my

Diharap di masa akan datang, pihak yang berkenaan dapat membekalkan pakar dalam bidang IT untuk memberikan khidmat yang terbaik kepada pihak media seperti kami.