• strict warning: Non-static method view::load() should not be called statically in /home1/eangkasa/public_html/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home1/eangkasa/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home1/eangkasa/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home1/eangkasa/public_html/sites/all/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 149.
  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /home1/eangkasa/public_html/sites/all/modules/views/plugins/views_plugin_style_default.inc on line 25.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home1/eangkasa/public_html/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home1/eangkasa/public_html/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Non-static method view::load() should not be called statically in /home1/eangkasa/public_html/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home1/eangkasa/public_html/sites/all/modules/views/handlers/views_handler_argument.inc on line 745.
  • strict warning: Declaration of views_handler_filter_node_status::operator_form() should be compatible with views_handler_filter::operator_form(&$form, &$form_state) in /home1/eangkasa/public_html/sites/all/modules/views/modules/node/views_handler_filter_node_status.inc on line 14.
  • strict warning: Non-static method view::load() should not be called statically in /home1/eangkasa/public_html/sites/all/modules/views/views.module on line 879.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home1/eangkasa/public_html/sites/all/modules/counter/counter.module on line 136.
  • warning: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home1/eangkasa/public_html/sites/all/modules/counter/counter.module on line 159.
  • warning: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /home1/eangkasa/public_html/sites/all/modules/counter/counter.module on line 159.
  • strict warning: Non-static method view::load() should not be called statically in /home1/eangkasa/public_html/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_field_comment::init() should be compatible with views_handler_field::init(&$view, $options) in /home1/eangkasa/public_html/sites/all/modules/views/modules/comment/views_handler_field_comment.inc on line 50.
  • strict warning: Declaration of views_handler_field_comment_username::init() should be compatible with views_handler_field::init(&$view, $options) in /home1/eangkasa/public_html/sites/all/modules/views/modules/comment/views_handler_field_comment_username.inc on line 48.
  • strict warning: Non-static method view::load() should not be called statically in /home1/eangkasa/public_html/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /home1/eangkasa/public_html/sites/all/modules/views/views.module on line 879.

Code Igniter as an excellent PHP framework

For starter, i have been using Code Igniter for over a year and it was introduced by a friend of mine as he was explaining on how essential to have a PHP Framework to speed up your web development. I was doubt at that time, but after I tried it by myself for a couple of months, I was truly amazed on the fact that it does rapidly save your efforts and time.

Code Igniter is an open source PHP framework smilar to Zend and CakePHP if you know what i'm talking about. I would strongly recommend CI because it's lightweighted as compared to bloated Zend Framework. It introduces the idea of MVC (Model - View - Controller) approach in developing a website. For those PHP developers, you would normally put the whole HTML content, database connection and query, and PHP logic in one file with .php extension.

Now, what Code Igniter does, it separates the HTML content into "views" folder, database connection and query into "models" folder, and PHP logic into "controllers" folder. From my point of view, it gradually cleans up your code and makes it easy for web designers and developers to collaborate together, as a web designer should only need to modify the "views" folder, and there won't be any confusion in seeing PHP and/or MySQL code.

Fast rounded corners picture using Photoshop

A couple of months ago, i'm pretty much new in photoshop and experiencing difficulty in generating a fast rounded corners photo using Adobe Photoshop. After hours of researches, carefully selecting quite a few tutorials on the net, my choice would be on Matt Thommes article, his method is by far the quickest and easiest to learn for me, a beginner in photoshop around that time.

I have made up my mind to write my own tutorial version (based on Matt's idea of course), supposed to be much simpler and straightforward for Adobe Photoshop's starter:

1. As usual, create a new canvas by selecting from the top navigation menu, File => New

2. Select a rounded rectangle tool from the left side panel.

   

3. Create a random size (your pick) of rounded rectangle size as depicted on the screenshot below:

4. Insert your photo on the canvas by selecting File => Place, by now your photoshop canvas should look similar as below:

5. Click on Shape 1 layer (the rounded rectangle) and choose on the Paths.

Import large MySQL database (phpMyAdmin limitation)

I have encountered this issue about a week ago, when i'm exporting my database through phpMyAdmin tool, the export works very well and the output file is up to 10 MB in size. The main issue comes when i would like to import it back using phpMyAdmin, but guess what happened, a timeout occured.

 

I will kindly break it down for you, there are 2 limitations surrounding phpMyAdmin from importing a very large MySQL database:

1. A time out is divided into a server timeout and browser timeout. This basically means when a script is being executed for too long that it has eventually passed the time limit either on the server and/or browser, the script will cease to run. Simply put, the larger your file is, the longer it takes to be executed, the bigger chance it fails.

You could actually bypass the browser timeout by modifying the about:config setting if you are on Firefox, unfortunately for server timeout, if you are on shared hosting like me, you are unlikely to get access to modify the server config.

2. File size limit on certain web hosting companies. Normally, i would say a 10 MB filesize limit is being implemented by most web hosting companies, if your MySQL filesize is more than that, then you're out of luck. Fortunately, my hosting company (BlueHost) is generous by allowing me to upload up to 50 MB filesize.

Captcha form to secure against spam bots

Do you ever have a blog / forum / personal site where there are instances where your comment forms are filled with unnecesary advertisements, not mentioning horrible languages. For your information, this isn't done by a person, in most cases it will be spam bots automatically generated by a program.

Captcha is well known to prevent or reduce the amount of spams being posted on your blog / forum / sites, most open source PHP CMS such as Drupal / Joomla / Wordpress obviously have a captcha module or even integrated captcha by their own, so don't worry about them. How about free forum such as PHPBB and Simple Machines, they do have it as well, but there are certain tweaks and modifications needed to ensure your captcha is not being bypassed.

From my own experience, the phpbb captcha by default isn't very stricted and easily bypassed, you have to visit their official website to gain a better and stricter captha system. For those of you developing your own site from a scratch, i would strongly recommend using 3rd party captcha system from:

http://www.phpcaptcha.org/try-securimage 

http://www.recaptcha.net         

Generate htaccess password

Normally, we would protect our website that is currently under development, as we do not want any unauthorized access to the website, and we would like to prevent google from indexing our unfinished site.

Therefore, do you ever wonder how to protect your site with an username and password, most of web hosting companies do provide this capability out of the box. However, there is an easy way of generating the very same functionality using .htaccess, do visit this site to easily generate .htaccess password: http://tools.dynamicdrive.com/password/

Carefully pick your username and password, as well as providing your server's root directory. The password will automatically be encrypted during the process, so please do not forget your password. Afterwards, 2 files (.htaccess and .htpasswd) will be generated and transfer those 2 into your root directory, under public_html / httpdocs / www directory. Now, your site is well protected and ready to go.

Syndicate content