• 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.

The appropriate location of any custom modules/themes in Drupal

To begin with, for most people a standalone drupal doesnt give you much option to do, however its plugins/modules from the drupal community can expand that functionality into a much wider scope. Your own version of modified theme can also be installed to change how drupal essentially looks.

Now, all contributed modules or themes should be placed in:

'sites/all/modules/' for custom modules and 'sites/all/themes/ for custom themes, the exact location should be in (well, this's the case if you installed drupal on your root) 'public_html/sites/all/modules' and 'public_html/sites/all/themes'

Perhaps, you are wondering why we should need such work, that's simply because once you upgraded your site to a better version of drupal (let's say from 6.6 to 6.7) then the Drupal 'Upgrade.txt' instructions specifically say that we should backup our 'sites' folder since all other folders will be overwritten during the upgrade.

So, do not ever put your contributed modules/themes outside 'sites' folder otherwise you may have lost it during the upgrade. Well, some of you may comment, sometimes we do need to alter the core drupal module to change how forms looks and such.

Difference between Zone Rates & Zone Table Rates in Zen Cart

I have come across this question before and for some time i was confused what would be the difference between Zen Cart preinstalled Zone Rates and this plugin "Zone Table Rates" available at here.

Alright, this is a brief summary of each purpose:

Zone Rates allows to define multiple shipping rates based on countries only, so you can setup let's say 3 (as the default) shipping rates with different countries attached to it.

Meanwhile, Zone Table Rates allows to define multiple shipping rates based on "Zone Definition", for those who doesnt know zone definition means, it is where we can setup a zone area down through states/provinces. So, for example you want to setup zone 1 covering Indonesia in Jakarta & Bali combined with USA in California & NY, we can do that easily.

Once we setup our zone definition, then we can define our own shipping rates using Zone Table Rates and attached our predefined Zone Definition to it, and you're done.

Welcome to eangkasa - second life

Hi everyone, this site is dedicated to be my personal website which I have developed over a month for professional purpose. This site will hold out my current portfolios, services, resume, and many others to be offered. I'll also post my own articles related to the web and database development as my current expertise, such as drupal, code igniter, mootools, zen cart and many other web technologies.

Feedback and comments are greatly appreciated as I would like to hear your opinion on how am I going with the site, and any constructive suggestions on improvement / reports on website bug would be excellent. Last but not least, enjoy your stay in here, and welcome to eangkasa.com - second life.

Syndicate content