Saya termasuk orang yang mengembangkan website tanpa pernah membuatnya dari nol. Maksudnya, saya tidak membuat komponen dari website itu secara manual satu demi satu. Mulai dari arsitektur website, komponen modul, file uploader, user access, image manager, dll. Biasanya semua dilakukan dengan menggunakan CMS yang OpenSource, seperti WordPress dan Drupal (jaman dulu juga termasuk PHPNuke). Biasanya memang saya melakukan modifikasi disana – sini agar website ini bisa bekerja sesuai keinginan. Umumnya akhirnya website tersebut akhirnya bisa berjalan sesuai harapan.

Tetapi kemudian datang masalah seperti berikut ini :

1. Website tersebut membutuhkan galery foto dengan fasilitas slideshow.
2. Website tersebut membutuhkan katalog produk.
3. Website tersebut ingin mengimplementasikan fasilitas social network.
4. Website itu ingin menyediakan fasilitas bagi membernya untuk bisa mengupload file MP3. Dan tiap member nantinya bisa mengatur level akses terhadap file MP3 yang dia upload.
5. Website tersebut ingin mempunyai form yang terintegrasi untuk arsip wawancara.
6. dll

Jika saya menggunakan CMS seperti Drupal. Mungkin hal ini masih bisa ditangani dengan ketersediaan modulnya yang sangat banyak. Atau jika memang modulnya belum tersedia, kita bisa membuat sendiri. Selain itu jika kurang puas, kita masih bisa melakukan oprek lebih dalam dengan menggunakan API yang disediakan Drupal. Dengan tujuan agar website ini sesuai dengan apa yang kita inginkan.

Tetapi, hal ini bisa jadi merupakan masalah baru. Tentunya kadangkala hal ini bisa menjadi solusi untuk satu masalah tetapi bukan tidak jarang malah menimbulkan masalah baru. Beberapa skenario yang sering terjadi :

1. Modul untuk CMS tersedia. Tetapi ada bagian yang tidak sesuai, bahkan mungkin ada bagian yang akhirnya malah terasa mengganggu. Misal modul e-commerce dari Drupal menyediakan begitu banyak fasilitas yang pada kenyataannya tidak saya butuhkan. Sedangkan untuk beberapa bagian justru masih belum sesuai harapan. Dan untuk bisa merubah modul ini, kita harus memahami hampir kesuluruhan struktur modul ini. Ditambah pengetahuan tentang API dari Drupal.
2. Terlalu banyak pilihan modul. Misal modul untuk upload gambar di Drupal. Secara default tidak ada. Kita masih bisa menginstal modul tambahan, sehingga nantinya upload gambar di Drupal akan semudah di WordPress. Tetapi ketika sampai di tahap theming, saya menyadari bahwa field untuk gambar hasil upload modul tersebut tidak bisa diakse langsung. Berbeda dengan image yang diupload menggunakan bantuan module Image Field (CCK).
3. Dengan API yang disediakan, kadangkala kita masih membutuhkan pengetahuan tentang API lain. Dan pada akhirnya mau tidak mau saya harus mempelajari banyak API, hanya untuk mengetahui bagian mana dari API ini yang tepat untuk solusi masalah saya.
4. Salah satu hal yang paling sulit adalah merubah alur kerja dari website ini. Misal jika user ingin register, tidaklah langsung ditampilkan ke halaman register, tetapi harus melalui satu halaman polling terlebih dahulu. Untuk bisa mengimplementasikan ini, secara tidak langsung kita harus tahu alur kerja (workflow) dari CMS yang kita gunakan.
5. Butuh field yang custom untuk tiap post (tidak hanya field TITLE dan POST saja). Secara default WordPress menyediakan fasilitas Custom Fields, tetapi penggunaannya masih belum senyaman CCK di Drupal. Untuk itu harus dibuat modul sendiri.
6. dll

Jika memang akhirnya saya ingin menjadi ahli dari CMS tersebut, saya rasa tidak masalah untuk mengikuti solusi yang saya berikan di atas. Tetapi jika saya hanya ingin menggunakan CMS ini sebagai bantuan, sepertinya effort nya terlalu besar.

Bahkan tidak jarang saya merasa, ketika mempelajari semua API, hook, templating, konvensi, dll dari suatu CMS, effortnya mungkin sama besarnya dengan jika saya membangun website tersebut dari nol.

Jadi apakah akhirnya membuat CMS dari nol?

Tidak. Bagi saya tetap tidak. Karena ada beberapa kemudahan di CMS yang tidak saya dapatkan jika saya harus membangun dari nol. Saya harus membangun kerangka / arsitektur dari website tersebut. Dan cukup banyak pula waktu yang tersita untuk membangunnya.

Jadi apa solusinya?

Framework. Bagi saya solusi di tengah – tengahnya adalah framework. Framework menjadi solusi yang tepat jika saya ingin mengembangkan website yang berbasis konten, tetapi dengan beberapa fasilitas yang tidak umum (seperti kasus di atas tadi). Dengan framework yang tepat, saya bisa membuat API saya sendiri, tetap mendapatkan fasilitas templating secara default, fasilitas layering untuk database, dan salah satu yang paling saya sukai adalah fasilitas URL Friendly secara default. Saya tidak tahu apakah semua framework menyediakan fasilitas tersebut, tetapi yang jelas Framework yang saya pakai (CodeIgniter) menggunakannya.

Pilihan framework yang cukup terkenal :

1. Prado – PHP (contoh : website Univertias Indonesia) : Kalau tidak salah ini seperti menjadi ASP.Net pada PHP
2. CodeIgniter – PHP(contoh : OkeZone.com), Jujur saja, saya tahu CodeIgniter dari situs OkeZone ini, dan sampai saat ini paling nyaman menggunakan ini, karena framework ini terdokumentasi dengan baik.
3. Ruby On Rails – Ruby (contoh : SharingFoto.com) : Situs ini diklaim sebagai web aplikasi pertama di Indonesia yang menggunakan Ruby On Rails.
4. CakePHP – PHP (contoh : OwnCafe.com) : Salah seorang yang sangat aktif dalam edukasi CakePHP di Indonesia adalah Sunu Wibirama (alumni Teknik Elektro UGM). Situs lokal cake-php bisa dilihat di idcake.web.id
5. Symfony (PHP), Django (Python), dll

Saya sendiri masih penasaran dan menantikan Mambo CMS versi 5.0 yang akan menggunakan CakePHP sebagai basisnya. Dengan kondisi seperti itu, maka level kustomisasi bisa dilakukan dari tingkat yang paling dasar (langsung menggunakan framework),di lapis tengah (modul), maupun lapis akhir (theming).

Jika ada yang tertarik dengan framework – framework di atas, jangan lupa pahami satu istilah ini : MVC (Model View Controller)

source: http://okto.silaban.net/2008/02/website/menggunakan-cms-atau-framework/

ini, koleksi lama saya. Silahkan diDownload..

Beberapa ebook tentang Adsense..
http://www.4shared.com/file/100331427/114d84b5/106x.html
http://www.4shared.com/file/74295883/87b5163d/adehendra-tingkatkan-dollar-ad.html
http://www.4shared.com/file/73706907/c30c50b9/Blog__Google_Adsense.html
http://www.4shared.com/file/73709248/63e9779b/cara_menemukan_ide_untuk_tema_.html
http://www.4shared.com/file/74295534/f2fdc906/davidodang-movabletype.html
http://www.4shared.com/file/74295316/2a48b61a/Langkah_Gampang_Pasang_Adsense.html
http://www.4shared.com/file/74294528/5aecd309/Rahasia_berbisnis_Adsense.html

Freeware
http://www.4shared.com/file/87052604/26b1581e/firetune.html => Gampang nge-Tweak Firefox.
http://www.4shared.com/file/99585485/33f42096/ka_bah.html => aplikasi ini akan menampilakan foto ka’bah yang dapat dicontrol 360 derajat menggunakan mouse/keyboard.

Web programming..
http://www.4shared.com/file/99589970/8608e43d/Code_Igniter_Tutorial.html
http://www.4shared.com/file/136452378/946523cb/CodeIgniter_PRO.html
http://www.4shared.com/file/112963429/6eb2dc98/Memiliki_Blog_Canggih_dg_Modal.html

When we build a website using CodeIgniter (CI), we’ll know that CI provide some feature to help programmer to produce a good quality of website, one of the feature is “Scaffolding”. Scaffolding is the feature that we can do CRUD (Create, Read, Update and, Delete) from database easily.

First you must activate scaffolding feature in config/routes.php

// it used to activate the scaffolding feature

$route['scaffolding_trigger'] = “scaffolding”;

Then put the code below  in controller directory :

// Activate url helper

$this->load->helper(‘url’);

//Activate form helper

$this->load->helper(‘form’);

// Using scaffolding feature to add some data to employee table

$this->load->scaffolding(‘employee’);

Last, open your browser and type

http://localhost/parkir/index.php/park/scaffolding

• parkir can be changed, it depends on your directory on htdoc
• park can be changed, it depends on your name class in controller directory

• scaffolding used to show the feature

The result is

We can read, edit, delete, and add easily…

Last year I encountered an issue while supporting some code I hadn’t written. The issue was that random session data was randomly disappearing. I consulted with the original author of the code who was adamant that nothing with their code would be responsible for the issue. Recently, I was revisiting the code and had a revelation. They had used the CodeIgniter session library instead of PHP native sessions. After some research I discovered that the CodeIgniter session library uses cookies and as a result limits data to 4kb. This was the cause of the issue. I switched CodeIgniter to use database storage and the issue was resolved.

Hoy quiero hablar de la inclusión de la librería PHP NuSOAP en el framework de desarrollo CodeIgniter, dado que hace unos días me vi en la necesidad de realizar esta integración. En este artículo me centraré en la integración de la librería para consumir servicios web ofrecidos por un sitio externo a nosotros.

<?php if (!defined('BASEPATH')) exit('No direct script access allowed');
class nuSoap_lib{function Nusoap_lib(){
    require_once(BASEPATH.'libraries/NuSOAP/lib/nusoap'.EXT);
}
?>

class Client extends Controller {
    function __construct() {
        parent::Controller();
        $this->load->library("nuSoap_lib");
    }

    function index() {

        $this->nusoap_client = new soapclient("http://url.servidor.soap");

        if($this->nusoap_client->fault)
        {
             $text = 'Error: '.$this->nusoap_client->fault;
        }
        else
        {
            if ($this->nusoap_client->getError())
            {
                 $text = 'Error: '.$this->nusoap_client->getError();
            }
            else
            {
                 $row = $this->nusoap_client->call(
                          'funcionEnElServidor',
                           array(parametros)
                        );
                ...
            }
     }
}

Kali ini saya membandingkan enam PHP Framework berbasis MVC (Model View Controller) yang populer. Keenam framework itu adalah CakePHP, CodeIgniter, Kohana v2 dan v3, Yii, dan “new kid on the block” DooPHP. Semua menggunakan versi terbaru saat ini (2009-11-22) kecuali Yii. Berikut informasi detail mengenai versi yang di-test:
- Cake PHP 1.2.5
- Code Igniter 1.7.2
- Kohana 2.3.4
- Kohana 3.0.1.2
- Yii 1.0.10
- Doo 1.2

Mesin yang digunakan
Acer Aspire 4520
AMD Turion 64 X2 TL-58 1.9 GHz
RAM 3 GiB

Software yang digunakan
- Windows 7 Ultimate
- Apache 2.2.12
- PHP 5.3

Hampir semua framework konfigurasi-nya tidak diubah sama sekali (kondisi default). Kecuali Cake PHP yang sudah dimatikan konfigurasi session, cache, database, log, dan debug.

Metode test yang digunakan mencetak tulisan “Hello World!” lalu langsung exit;.

Hasil yang didapat adalah nilai rata-rata dalam satuan rps (request per second). Berikut dari yang terlambat hingga yang tercepat:

- CakePHP ==> 19.72 rps
- CodeIgniter ==> 71.23 rps
- Yii ==> 73.68 rps
- Kohana v2 ==> 76.31 rps
- Kohana v3 ==> 103.39 rps
- Doo ==> 200.32 rps

Terlihat Doo buatan negri tetangga adalah yang tercepat dalam test “Hello World!” ini.

Tapi dalam memilih suatu framework, bukan mana yang tercepat. Tapi yang paling nyaman anda gunakan sehingga mempersingkat waktu developing dan meningkatkan produktivitas anda.

Berikutnya akan ada tambahan dari PHP Framework berbasis MVC lainnya seperti Symfony, Zend Framework, dan APF, Solar Framework. Dan agar lebih fair, semua session, cache, database, dll akan di-non aktifkan. “Hello World!” juga akan dicetak pada view, bukan pada controller lalu exit.

Nb: Konfigurasi module dan extension yang sedang berjalan pada Apache dan PHP tidak diikutsertakan dalam tulisan ini.

CodeIgniter Development

NetTrackers has been using CodeIgniter to develop small and large scale applications for the last 2 years. The biggest advantage of using CodeIgniter is that it leaves a small footprint and allows our developers to code applications rapidly in a secure environment.

The CodeIgniter development team at NetTrackers has gone through full life-cycle development with different project sizes. Our developers use CodeIgniter for Rapid Application Development taking full advantage of it’s MVC framework. We have used CodeIgniter to build up a large and stable codebase that our developers are comfortable using and extending upon. The advantage of working with our CodeIgniter Developers is evident in our rapid response for changes or extensions to existing code.

CodeIgniter allows our team to build rapidly without compromising on code effeciency and code base sizes. The basic memory foot print is relatively small and allows scaling to larger sizes. Our work with CodeIgniter has allowed us to extend it to be used with a number of external providers such as the Amazon Web Services and Javascript toolkits such as DoJo and jQuery.

We always challenge our knowledgebase against new technologies to develop our skills and REALLY make the most of what the web can do. Our frequent use of AJAX based solutions creates websites and services that are not just completing tasks, but actually bringing a degree of pleasure in terms of use.

We provide, customized CodeIgniter Programming solutions if you are looking for developers in CodeIgniter. CodeIgniter Programmers in our office will cost $10 per hour or if you want to hire on a monthly basis,you would pay $1000 per month for a minnimum of 21 days of work. We provide daily reports, access to our managers for no charges, chats over Phone, Instant Messenger and email. Mixed with our strong management skills NetTrackers delivers stable and reliable applications that are tailor cut to your custom requirements at competitive prices.
codeigniter development

Primul gand pe care l-am avut cu totii in echipa a fost “in ce codam”. A fost usor sa trecem prin cei cativa termeni, care ne mai trecusera pe la ureche, si sa alegem Metoda aia *usoara* prin care tot ce era desenat pe hartie si gandit, sa devina realitate… web. La fel de usor a fost sa incercam sa scriem primele linii de cod mai complicate ca sa ne dam seama ca trebuie sa si gusti inainte sa mananci. Si ca sa trecem in planul concretului ne-am gandit la 3 metode de a face paginile sa fie dinamice (adica sa integram o comunitate, sa avem pagini context sensibile) : un framework, un cms sau php de la 0.

La capitolul framework, am constatat ca este destul de popular codeigniter (http://www.codeigniter.com) si dupa vizionarea a exact doua tutoriale video cu tot cu incercat cod, am fost convinsi ca si noi putem sa dezvoltam un intreg website in 20 de minute (precum video-ul arata un blog gata in tot atatea minute). Problema cu un framework este dificultatea de a intelege cum lucreaza bibliotecile, ce trebuie sa incarci si ce module fac ceea ce zic ca fac. O problema cu care m-am  confruntat personal a fost o simpla logare. In primul rand nu exista modulul gata facut de autentificare ci trebuie supraincarcate anumite clase. In al doilea rand, voiam sa ma folosesc de cunostintele, de baza, de PHP, insa constatam ca pana si sesiunile sunt vazute altfel. Concluzia noastra este ca un framework se studiaza intai. Avantajul, totusi,  al unui astfel de framework este modelul MVC care personal mi s-a parut intuitiv si foarte aplicabil.

Frameworkul Zend a fost inca o propunere, laudat fiind si pentru ca php are module zend, insa nu am reusit sa trecem de configurarea acestuia.

Punctul doi in aceasta discutie, ar fi un Content Management System. Din pacate, tema aleasa nu se preteaza la o astfel de abordare. Sigur ca putem scrie module php pentru CMS, dar intervine si aici problema studierii sistemului. Am fi mers ori pe Joomla ori pe WordPress, care vin si cu un design gata facut si customizabil (mai putin la WordPress).

Solutia numarul 3 ne avantajaza cel mai mult, php de la 0.  Cateva minute pe w3schools si doua trei exemple de lucru cu baza de date face ca PHP sa nu para o necunoscuta. Exista mii de linii de sample code utilizabil si customizabil, apoi reutilizabil in cadrul aceluiasi proiect. Suntem obisnuiti sa codam in C, Java, Scheme, Haskel, Prolog, CLIPS chiar si Verilog, limbajul nu este o problema.  De asemenea partea de control (administratorul) nu trebuie sa fie extrem de complex, noi construim sistem, stim cum merge. Singurul dezavantaj este securitatea care s-ar putea sa ne dea batai de cap.

Cam atat pe partea de programare pe server.

CodeIgniter Development

NetTrackers has been using CodeIgniter to program small and large scale applications for the last 2 years. The biggest advantage of using CodeIgniter is that it leaves a small footprint and allows our programmers to code applications rapidly in a secure environment.

The CodeIgniter development team at NetTrackers has gone through full life-cycle development with varied project sizes. Our developers use CodeIgniter for Rapid Application Development taking full advantage of it’s MVC framework. We have used CodeIgniter to build up a large and stable codebase that our developers are comfortable using and extending upon. The advantage of working with our CodeIgniter Developers is evident in our rapid response for changes or extensions to existing code.

CodeIgniter allows our team to develop quickly without compromising on code effeciency and code base sizes. The basic memory foot print is relatively small and allows scaling to larger sizes. Our experience with CodeIgniter has allowed us to extend it to be used with a number of external providers such as the Amazon Web Services and Javascript toolkits such as DoJo and jQuery.

We constantly challenge our knowledge against new technologies to extend our skills and REALLY make the most of what the web can do. Our regular use of AJAX based solutions creates websites and services that are not just completing tasks, but actually bringing a degree of pleasure in terms of use.

We provide, customized CodeIgniter Programming solutions if you are looking for developers in CodeIgniter. CodeIgniter Programmers in our office will cost $10 per hour or if you want to hire on a monthly basis,you would pay $1000 per month for a minnimum of 21 days of work. We provide daily reports, access to our managers for no charges, chats over Phone, Instant Messenger and email. Mixed with our strong management skills NetTrackers delivers stable and reliable applications that are tailor cut to your custom requirements at competitive prices.
codeigniter developers

Hallo Teman-teman pemula CodeIgniter !!
Saya juga seorang pemula, mari kita memulai pelajaran dasar CodeIgniter :

1. Downloadlah CI (CodeIgniter) di http://codeigniter.com/download.php (saat tutorial ini ditulis, versi yang saya download adalah CodeIgniter_1.6.0.zip)
2. Ekstraklah file CodeIgniter_1.6.0.zip di folder yang bisa diakses web
3. Akses web di mana CI berada, secara default akan tampil halaman welcome.

Ok mari kita ganti halaman welcome dengan halaman yang kita buat sendiri :

1. Bukalah file routes.php di folder CodeIgniter_1.6.0/system/application/config
2. Ganti $route['default_controller'] = “welcome”; dengan $route['default_controller'] = “pemula”;
3. Buatlah file pemula.php di folder CodeIgniter_1.6.0/system/application/controllers/
4. Isi file pemula.php seperti berikut :

<?php
class Pemula extends Controller {
	function Pemula()
	{
		parent::Controller();
	}
	function index()
	{
		$this->load->view('pemula_view');
	}
}
?>

5. Buatlah file pemula_view.php di folder CodeIgniter_1.6.0/system/application/views
6. Isi file pemula_view.php sebagai berikut :

<html>
<head>
<title>PEMULA</title>
</head>
<body>
<h1>Saya benar-benar seorang pemula</h1>
</body>
</html>

7. Akseslah folder CodeIgniter_1.6.0 dengan browser Anda, Mamamiaaaaaaa…… Anda benar-benar seorang PEMULA !!!

Bersambung ……

Hoy en día, somos muchos los desarrolladores que disfrutamos de las bondades de este muy buen framework, pero siempre se ha tenido el problema para quitar esa porcion de url “index.php” de nuestros proyectos.

Bien, pues luego de investigar, buscar y preguntar… y demas cosas, encontre un modo de retirar ese “index.php”, el cual lo trabaje en una distro de Linux.

Pues comencemos:

• Como sabran, se necesita activar el mod_rewrite en la configuracion de nuestro servidor Apache. Pues se puede hacer manualmente accediendo al archivo de configuracion o simplemente ejecutando el siguiente comando:   sudo a2enmod rewrite
• Una vez activado el mod_rewrite, procederemos a quitar las restricciones en el archivo:  sudo gedit /etc/apache2/site-enable/000-default , donde reemplazaremos todos los “AllowOverride None” por “AllowOverride All“.
• Una vez terminado esto, procedemos a reiniciar el servicio de Apache con: sudo /etc/init.d/apache2 restart .
• Si al reiniciar el servicio de Apache, por casualidad les aparece mensaje como: apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName , no se preocupen, se soluciona agregando la siguiente linea: ServerName localhost en el apache2.conf.
• Es hora de comprobar que en nuestro archivo de configuracion  ”system/application/config/config.php” , esté ya modificado la opcion del index page, de modo que quede así:  $config['index_page'] = “”;
• Ahora viene lo más importante, y es crear un archivo: .htaccess con el siguiente contenido, en la carpeta donde se encuentra nuestro proyecto, es decir donde se encuentra la carpeta “system”:

        ErrorDocument 404 /index.php

        DirectoryIndex index.php.

        <IfModule mod_rewrite.c>
        RewriteEngine on
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^(.*)$ index.php/$1 [L,QSA]
        </IfModule>

Y con esto ya tenemos podemos trabajar sin el poco querido: index.php , es decir, si nuestra url era: http://localhost/proyecto/index.php/controlador ahora sera simplemente http://localhost/proyecto/controlador.

Espero les haya servido este post, ya saben que cualquier consulta, pueden hacerla dejandonos un comentario, y nosotros gustosamente responderemos. Gracias.

Hehehe… Walaupun baru mencoba, boleh kan berbagi ilmu…, bagi para expert, mohon comment-nya ya apabila ada kekurangan atau kesalahan..,wong saya cm otodidak kok.. Nuwun….

Okey,,let’s begins…

Sejak lama saya menggunakan EditPlus sebagai editor tools dalam menulis kode-kode program php. Kemudian beralih ke NotePad ++ beberapa tahun terakhir ini. Sepanjang satu dasawarsa beberapa editor pernah saya gunakan, seperti MS FrontPage, DreamWeaver, UltraEdit dsb. Kali ini saya ingin menjajal menggunakan Eclipse PDT.

PDT yang saya gunakan adalah versi GanyMede (lihat tulisan saya sebelumnya tentang instalasi Eclipse). Baru sekitar satu tahun ini, saya menggunakan framework PHP yang bernama CodeIgniter. Gunanya menggunakan framework untuk mempermudah dan mempercepat pekerjaan koding.

Untuk menggunakan Eclipse dan CodeIgniter ada beberapa cara yang mungkin bisa anda gunakan.

CodeIgniter

1. Download CodeIgniter, dan ekstrak filenya

2. Lalu salin/copy folder CodeIgniter ke folder baru misalnya c:\CI

3. Di dalam c:\CI ada folder system. Di dalam folder system ada folder application. Cut folder application lalu paste ke folder system. Kira-kira hirarkinya seperti ini:

application/
	config/
	controller/
	errors/
	....
system/
	codeigniter/
	database/
	fonts/
	.....
index.php
.htaccess

4. Lalu edit file index.php dengan notepad. Carilah baris $application_folder = “application”;
dan ubahlah menjadi $application_folder = “../application”;

Eclipse

1. Jalankan Eclipse dan buat File New PHP Project. Isi nama proyek dengan CI_CORE dan pilih Create Project from existing source. Browse dan pilih ke c:\CI\system. Folder system merupakan sumber utama kode-kode Codeigniter.
2. Buat lagi New Project dengan nama CI_APP, dan arahkan ke c:\CI\application. Folder ini akan berisi kode-kode proyek yang akan kita kerjakan. Kemudian kita sertakan pula Project Path untuk dimasukkan ke CI_APP, masukkan CI_CORE seperti gambar ini:

Masukkan CI_CORE sebagai bagian dari proyek

Hasilnya kira-kira seperti ini:

Tampilan CodeIgniter dengan Eclipse

Nah ketika kita akan ketik-ketik koding di Eclipse. Kita akan dimudahkan dengan AutoCompletion seperti gambar ini:

Semoga meng-koding jadi lebih mudah dan menyenangkan.

Hi Coderz,
Sheet-1 is a list of library functions with parameters.
Sheet-2 is for helpers functions & CodeIgniter reserved names etc.
Save the images and keep it as an easy reference.

Hi Coderz,
These are some tips for increasing the performance of CodeIgniter. Please have a look.
1. Move application directory outside of the system folder

Application directory doesn’t require residing inside system directory all time.
You can move this anywhere according to your convenience.
So, you don’t need to dig deeper into the system directory every time to access a controller or model.

After moving the application directory, you can simply update the new path in “$application_folder” variable of the main index.php file. And another happy new is, if you put the application directory & the system directory in a same folder, you don’t need to change anything.

2. Remove ‘index.php’ in the URLs using htaccess

By default CodeIgniter includes the index.php file in your URLs. To create friendlier & search engine optimized URL, remove the ‘index.php’ from your URLs using htaccess. Add the below code in an htaccess file & upload to your server and it will remove the ‘index.php’ from URL.
RewriteEngine on
RewriteCond $1 !^(index\.php|images|robots\.txt)
RewriteRule ^(.*)$ /index.php/$1 [L]

3. Use routes.php to remap or redirect URLs

Use regex pattern or wildcards with $route array to remap a URL to a new location.
Instead creating a function for each redirection, this will help you to save time & resources.

4. Use Autoload whenever required

Use $autoload array to load resources (libraries, helpers, plugins etc) rather than loading in each function.
If it is required for a specific controller only, then load them in the controller’s constructor method.
It you use $autoload for everything, it will slow down your site & affect perfomance, so use it whenever necessary.

5. Try to keep all configuration in the config directory

Instead setting configuration values in each function, you can use a separate file to include all config options.
For example, you can use a form_validation.php file under ‘application/config’ folder and you can keep all validation rules for the total application in a single array.
In this manner you can create a separate file for every library.
Initially it may take some extra time, but in the long run it will help you to save many hours.

6. Filter all user input before adding them to DB

If your application heavily depends on user input, then set $config['global_xss_filtering'] = TRUE in config.php file.
Don’t forget to filter & escape user input for better security.

7. Don’t use pure PHP, if there is a CI alternative

Before using any native PHP function or code, double check if there is any CI function is available.
CI functions are created to help you to decrease your workload & to increase performance.
Always when you use CI, use CI functions.

8. Delete unnecessary libraries and helpers to save server space

Usually, We don’t use all the libraries and helpers in every application. But keeping them in the server requires more space and cause extra cost.

Once we complete our development, when we move to hosting server its better to delete unused libraries & helpers. It will help to reduce hosting space usage. But be careful & make sure before deleting any file that it is not used anywhere.

9. Create a library or helper for frequently using functions

Try to create a library or helper with all reusable functions to avoid repeated coding of the same thing over and over.
For example if we need to check for user authentication, instead checking their authenticity in every function and redirecting them to login page (if the user doesn’t have permission) we can create a logincheck() function in authentication library and can simply call the function to check for permission.

10. Avoid .php extension when loading views

When loading view files, avoid using .php extensions. It is not necessary to use, unless if you use different extension like .html etc.

And one more : Cache output files to decrease server load

Repeated requests to a function that returns the same results every time can cause unnecessary load on the server.
It can be easily avoided by using the CoedIgniter’s cache() function.
Caching all the pages has no meaning, if they are dynamic pages.
If you use dynamic pages like stock ticker then there is no meaning of caching. Because its value changes every minute & it can display wrong information to the users.
So, use output cache wisely.

Pada dasarnya framework Codeigniter membuat aturan agar developer dapat memilih tipe2 file apa saja yg bisa di upload, tujuannya sangat baik
Tapi dalam beberapa masalah diperlukan agar semua file bisa di upload dengan berbagai macam alasan kebutuhan.

Capek juga kalau harus memasukan list ekstension tersebut dalam config

$config['allowed_types'] = ‘gif|jpg|png|ods|xls|…|…|…’;

Setelah dicari maka didapat salah satu teknik yg dapat menyelesaikan masalah tersebut, yaitu dengan membuka file Upload.php pada path /system/libraries .
Pada function is_allowed_filetype() langsung saja dibuat return nya menjadi TRUE.

function is_allowed_filetype()
{
/*
if (count($this->allowed_types) == 0)
{
$this->set_error(‘upload_no_file_types’);
return FALSE;
}

foreach ($this->allowed_types as $val)
{
$mime = $this->mimes_types(strtolower($val));

if (is_array($mime))
{
if (in_array($this->file_type, $mime, TRUE))
{
return TRUE;
}
}
else
{
if ($mime == $this->file_type)
{
return TRUE;
}    
}        
}

return FALSE;
*/
return TRUE; //dillah yg nambah, tadinya yang diatas…
}

Ormai si sà lo sviluppo di applicazioni su facebook è diventato un MUST per molte aziende che vogliono aumentare il fatturato e la propria visibilità.

Un aiuto durante lo sviluppo può essere dato dal Framework PHP CodeIgniter. Tuttavia l’interazione tra i due sistemi (Facebook Platform e CodeIgniter) non è così immediata e intuitiva.

Ecco come fare

Download della Facebook Platform

1. Scaricare la PHP Facebook Client Library
2. Copiare tutto il contenuto della cartella /php della facebook platform nella cartella ./system/plugins di CodeIgniter
3. Rinomina  facebook.php in facebook_pi.php (./system/plugins/facebook_pi.php)

AutoLoad Facebook Plugin

Eventualmente puoi fare in modo che la Facebook Platform venga inizializzata automaticamente ad ogni caricamento. Per farlo è sufficiente modificare ./system/config/autoload.php e modificare questa riga

$autoload['plugin'] = array('facebook');

Altrimenti ti basta inserire questa riga in tutte le pagine che verranno richieste da Facebook

$this->load->plugin('facebook');

Configura la tua applicazione

A questo punto dovrai configurare la tua applicazione affinchè possa essere eseguita in Facebook.

Modifica ./system/application/config/config.php in questo modo:

$config['uri_protocol'] = "PATH_INFO";
$config['base_url'] = "APPLICATION_URL";

N.B. Se stai eseguendo l’applicazione in localhost in $config['base_url'] devi inserire http://127.0.0.1/path_applicazione

Modifica della Classe Controller

Se tutti i controller della tua applicazione dovranno essere eseguiti in Facebook allora dovrai modificare questa classe

Perciò vai in ./system/libraries/Controller.php e modifica il metodo costruttore Controller() in questo modo

function Controller()
{
parent::CI_Base();
$this->_ci_initialize();
log_message('debug', "Controller Class Initialized");
$secret = 'LA TUA SECRET KEY';

$api_key = 'LA TUA API KEY';

// Previene la notifica'Undefined index: facebook_config'
$GLOBALS['facebook_config']['debug'] = NULL;
parse_str($_SERVER['QUERY_STRING'],$_GET);
// Crea un nuovo oggetto Facebook
$this->facebook = new Facebook($api_key, $secret);
$this->uid = $this->facebook->require_login();

}

In questo modo in tutti i controller (che per definizione devono estendere la classe Controller)  potrai utilizzare le API di Facebook.

Tutte le chiamate dovranno essere fatte sull’oggetto $this->facebook e $this->uid corrisponde alla USER ID dell’utente loggato in sessione Facebook.

Ad esempio per ottenere la lista amici dell’utente loggato

$friend_list = $this->facebook->api_client->friends_get();

jQuery Uploadify là một plugin cho phép upload nhiều file lên server cùng một lúc. Bạn có thể tải Uploadify tại đây.
Do Uploadify dựa vào Flash để upload file, kiểu file gửi lên server bao giờ cũng là application/octet-stream, còn CodeIgniter lại chỉ hỗ trợ cơ chế kiểm tra file upload thông qua kiểu mimes để đảm bảo tính bảo mật của website, nên khi nhúng Uploadify vào CodeIgniter, chương trình sẽ không chạy theo ý mình.
Để sửa lỗi này, có 2 cách thường được dùng:
1 – Sửa lại CodeIgniter Upload library để nhận kiểu file thông qua file extension thay vì mime types.
2 – Sửa lại file config/mimes.php trong ứng dụng, thêm vào kiểu “application/octet-stream” vào các kiểu file cho phép upload.
Ngoài ra, ta có thể mở file .fla đi kèm với Uploadify và sửa lại nội dung file này để gửi kiểu file đúng cho CodeIgniter.
Đối với cách 1, nếu người dùng cố tình đổi đuôi file (vd, từ .png thành .exe), chương trình sẽ lập tức từ chối, không cho phép người dùng upload lên (vì sai đuôi). Cách 2 tối ưu hơn cách 1, nhưng giả dụ bạn có 1 trang chỉ cho phép upload văn bản .txt, một trang cho up ảnh .png, vậy bạn phải sửa lại config/mimes.php 2 lần liền. Như vậy khá là mất thời gian ngồi sửa từng dòng của config/mimes.php
Một cách trung gian là vẫn ứng dụng phép kiểm tra mimes của CI, nhưng thêm kiểu file “application/octet-stream” vào cho mỗi kiểu file được phép upload lên.
Ta thực hiện phương pháp này bằng cách viết phần mở rộng application/libraries/MY_Upload.php:

<?php
    class MY_Upload extends CI_Upload
    {
         var $allow_flash = FALSE;

/* End of file : application/libraries/MY_Upload.php */
/* Author: Nguyen Dinh Trung <nguyendinhtrung141@gmail.com> */

Giờ ta có thể thực hiện việc upload thông qua Uploadify bằng các Controllers và View sau:

Controller : application/controllers/upload.php

<?php
class Upload extends Controller
{
    function Upload()
    {
        parent::Controller();
        $this->load->helper('form');
        $this->load->helper('url');
    }
     
     
    /*
    *    Display upload form
    */
    function index()
    {
         
        $this->load->view('form');
    }
     
    /*
    *    Handles JSON returned from /js/uploadify/upload.php
    */
    function uploadify()
    {
       
        $config['upload_path'] = APPPATH . 'assets/uploads/';
        $config['allow_flash'] = TRUE;
        $config['allowed_types'] = 'csv';
        $config['max_size']    = '100';
        $config['max_width']  = '1024';
        $config['max_height']  = '768';
        $this->load->library('upload', $config);
        if (! $this->upload->do_upload('Filedata')){
            echo ($this->upload->display_errors());                       
        } else {
            echo json_encode($this->upload->data());                   
        }         
    }
     
}
/* End of File /application/controllers/upload.php */


View: application/views/form.php

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>jQuery Uploadify Demo</title>
<link rel="stylesheet" type="text/css" href="<?php echo base_url();?>js/uploadify/uploadify.css" />
<script type="text/javascript" language="javascript" src="http://ajax.googleapis.com/ajax/libs/swfobject/2.2/swfobject.js"></script>
<script type="text/javascript" language="javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script>
<script type="text/javascript" language="javascript" src="<?php echo base_url();?>assets/js/uploadify/jquery.uploadify.v2.1.0.min.js"></script>
 
    <script type="text/javascript" language="javascript">
        $(document).ready(function(){
                                         
                    $("#upload").uploadify({
                            uploader: '<?php echo base_url();?>assets/js/uploadify/uploadify.swf',
                            script: '<?php echo base_url();?>upload/test',
                            cancelImg: '<?php echo base_url();?>assets/js/uploadify/cancel.png',                             
                            scriptAccess: 'always',
                            multi: true,
                           'onError' : function (a, b, c, error) {
                                 if (d.status == 404)
                                    alert('Could not find upload script.');
                                 else if (d.type === "HTTP")
                                    alert('error '+d.type+": "+d.status);
                                 else if (d.type ==="File Size")
                                    alert(c.name+' '+d.type+' Limit: '+Math.round(d.sizeLimit/1024)+'KB');
                                 else
                                    alert('error '+error.type+": "+d.text);
                                }
                            'onComplete' : function(a,b,c,response,e) {
                                $("#notify").html(response);
                             }
                    });                                          
                                 
        });
    </script>
</head>
 
<body>
<h1>Uploadify Example</h1>
     
    <?php echo form_open_multipart('upload/index');?>
    <div id="notify"> </div>
    
    <p>
        <label for="Filedata">Choose a File</label><br/>
        <?php echo form_upload(array('name' => 'Filedata', 'id' => 'upload'));?>
        <a href="javascript:$('#upload').uploadifyUpload();">Upload File(s)</a>
    </p>
    
    
    <?php echo form_close();?>
    
</body>
</html>


Ganti :
$config['sess_cookie_name'] = ‘ci_session’;
ke
$config['sess_cookie_name'] = ‘cisession’;

atau

$config['sess_expiration'] = 7200;
ke
$config['sess_expiration'] = 72000;

Làm sao để tạo một form Ajax với jQuery và thư viện Form_validation của CodeIgniter?
Trước hết, ta tạo một controller như sau:

class Devel extends Controllers
{
function index(){
       $this->load->library('form_validation');
      # Đặt các luật kiểm tra cho Form.
       $this->form_validation->set_rules("username", "Tên đăng nhập", "required|trim|xss_clean|max_length(20)");
       $this->form_validation->set_rules("password", "Mật khẩu", "required|trim|xss_clean|max_length(20)");
       $this->form_validation->set_rules("password_again", "Nhập lại Mật khẩu", "required|trim|xss_clean|max_length(20)|match(password)");
      if ($this->form_validation->run()){
            # Form kiểm tra ok!
            echo "<div class='success'>Đã kiểm tra form, không có lỗi gì hết!</div>";           
      } else {
            # Form chưa kiểm tra, hoặc chưa chạy.
            if ($this->input->post('uniqueid')){
                  # Form đã khởi tạo và được chạy ít nhất 1 lần. Trả về mã lỗi kiểm tra form
                  echo "<div class='error'>".$this->form_validation->error_string()."</div>";
            } else {
                  # Chưa khởi tạo form.
                  $default['username'] = 'username';
                  $default['password'] = '';
                  $default['password_again'] = '';
                  $this->load->helper('string');
                  $default['uniqueid'] = random_string('unique');
                  $this->load->view('form', $default);
            }
      }
}
}
/* End of class Devel */
/* Author : Nguyen Dinh Trung <nguyendinhtrung141@gmail.com> */

Tiếp đó tạo view như sau:

<html>
    <head>
        <title>Example Form</title>
        <script type='text/javascript' src='<?= base_url(); ?>assets/js/jquery.js'></script>
    </head>
    <body>
        <form id='myform' method='post'>
            <div id="notify"></div>
            <fieldset><legend>Xác nhận mật khẩu</legend>
                 <input type='hidden' name='uniqueid' value='<?= $uniqueid; ?>'>
                 <label for='username'>Tên đăng nhập</label>
                       <input type='text' name='username' id='username' value='<?= set_value('username', $username); ?>'>
                 <label for='password'>Mật khẩu</label>
                        <input type='password' name='password' id='password' value='<?= set_value('password', $password); ?>'>
                 <label for='password_again'>Mật khẩu</label>
                        <input type='password_again' name='password_again' id='password_again' value='<?= set_value('password_again', $password_again); ?>'>
             </fieldset>
             <fieldset>
                  <button type='button' id='submit'>Gửi</button>
                  <button type='reset' id='reset'>Nhập lại</button>
             </fieldset>
        </form>
        <script type='text/javascript'>
              $(document).ready(function(){
                   $("#submit").click(function(){
                          $.post("<?= current_url(); ?>", $("#myform").serializeArray(), function(response){$("#notify").html(response);});
                    });
               });
        </script>
    </body>
</html>

Với jQuery, ta có thể gửi form dễ dàng với phương thức POST bằng 1 dòng như sau:

$.post("url", {"username":1234, "password":4567}, <callback>});

Trong đó callback là hàm xử lý dữ liệu mà server trả về. Như trong file view ở trên, tôi lấy toàn bộ chuỗi văn bản mà server trả về, đem nhét nó vào trong vùng <div id=”notify”></div>.
- Khi mới truy cập đến trang devel/index, do form chưa được khởi tạo nên không có giá trị gì trong biến $this->input->post(‘uniqueid’). Sự kiện này báo với controller rằng hãy hiển thị form và view với các thông số được chọn. Chuỗi uniqueid là một chuỗi ngẫu nhiên được tạo nhờ string helper của CI.
- Sau khi người dùng bấm vào nút Submit, jQuery sẽ gửi dữ liệu lên Server. Dữ liệu được gửi chính là nội dung Form lấy được nhờ lệnh $(“#myform”).serializeArray().
- Tại server, CI nhận thấy có trường uniqueid, nên thay vì tạo form thông qua View, CI chỉ gửi lại thông báo lỗi (trong trường hợp Form không chạy), hoặc thông báo thành công (trong trường hợp kiểm tra thành công).
- jQuery nhận được bản tin từ server và chèn chuỗi nhận được đó vào trong div id=”notify”.

I recently spent some time to do some research on different php frameworks. I know there are a lot of PHP MVC (Model View Controller) frameworks out there. But I tried checking only three of them – CodeIgniter, CakePHP and Zend framework. All these frameworks are Open Source. I’m not going to give you a detailed review of each and every point of each framework, as you can find lot of detailed reviews out there. This is just a conclusion on review of those.

CodeIgniter

CodeIgniter is really a framework with very small footprint, as they claim it. It has all the MVC structure, scaffolding and all. Even though I don’t think scaffolding can be used for production purpose in it. CodeIgniter is basically a structure and some libraries and easy to learn compared to the other two frameworks I think. If you are about to start a project straight away and you want to use an MVC framework, then CodeIgniter is best option as the learning curve is small. And its also flexible, not strict on the MVC rules, as you have the option not to use models in the MVC structure and code around different ways you like to achieve the result you want.

CakePHP

CakePHP is also a very robust framework. I think we can define it as CakePHP is to PHP is more like what Rails is for Ruby (Correct me if I am wrong, as I’m not too much familiar with rails). The problem with CakePHP is the learning curve is more than that of CodeIgniter, and most importantly you need to code exactly how they want you to code. i.e. you have to follow exact naming conventions, even follow it in database field naming too. Even a missed underscore or a different name (than what they expect) for an object can pop up as an error. For example, if the model object name is “User” then the Controller object name for it has to be UsersController, exactly the same model object name in plural form. And this is a must and CakePHP will show errors if they don’t find the object. But the good part of that is if follow the conventions correct in CakePHP, everything falls in correct automatically. In addition to this the scaffolding feature of CakePHP is also brilliant.

Zend Framework

I really didn’t got a chance to try too much in it, mainly because the learning curve far more bigger than the other two frameworks. Zend has a massive objects library (yeah I mean really BIG library). You can understand it by just by seeing the download file size of Zend framework, its around 12 MB whereas other frameworks mentioned above are only around 1.5 MB. Zend framework is not very strict in their conventions and coding compared to CakePHP I think. I would say its just a massive library in the MVC structure that can be used it whichever way we want it to be used for projects. But I’m still not familiar with Zend compared to the other two frameworks, so I may be wrong about. (Feel free shed some light on my review if you know more about Zend framework).

Conclusion: To me I would pick CodeIgniter or CakePHP. I really can’t pick between these two. CakePHP needs some getting used to also, but I think it will help to standardize the coding as every coder has to follow same rules.

Feel free to post your comments about your experience with these frameworks.

Prabhul Sankar
www.southoceansolutions.com