Download webERP SugarCRM Integration Component for Joomla

webERP - SugarCRM Integration Joomla component allows clients captured in SugarCRM to be imported from SugarCRM to webERP. Creates a Debtor Master record and a Customer Branch record in webERP.

The pro version allows import from webERP to SugarCRM also and allows you to connect accounts that already exist in both. All you do is click just one and submit to include it in the other list. Click one of each list and submit and you get both cross referenced with the others id.

For Demo - Click Here

To Download SugarCRM Bridge webERP Joomla! v1.5 (free) - Click Here

To Download SugarCRM Bridge webERP Pro Joomla! v1.5 (free) - Click Here

Facebook Comments Point (FCP), Ajax Comments WordPress plugin Free Download

Facebook Comments Points (FCP) is an AJAX/JQuery powered comments WordPress plugin. It will allow you to completely customize your comments system layout. It looks same as facebook wall's comment system. People can "Like/Unlike" any comment and they can also share any comment on twitter as tweet. So if want a flexible comments system for your WordPress blog, this is perfect choice.

Enabling and Customising our own custom Theme in Magento

In my previous post, I have explained about How to build a custom own theme in Magento. In this Post I will explain about the following things.

  1. How to Enabling our Package/Theme in Magento 1.4?
  2. How to Creating a template file?
  3. How Customising the default Magento theme?

Building your own custom Magento Theme


In this article I will be showing you how to create your own custom theme for Magento 1.4. Rather than creating a totally bespoke theme, we will create a theme based on the default theme. However, by doing this, you will have all of the information needed to create your own totally bespoke Magento 1.4 custom theme.

Directory Structure

The first part of creating your custom theme is to create your directory structure. To understand this, first we need to learn about themes and packages.

Package & Theme: What's the difference?

Look at the directory structure below and see whether you recognise it.
  • app/design/frontend/default
  • app/design/frontend/default/default
  • app/design/frontend/default/default/layout
  • app/design/frontend/default/default/template
  • app/design/frontend/custom-theme/default
  • app/design/frontend/custom-theme/default/layout
  • app/design/frontend/custom-theme/default/template
The above directory tree is the template structure used in Magento 1.3.2.4. Notice the folder default has a sub-directory also called default? In this scenario, the first folder called default is the package being used while the sub-directory called default is the theme. Also notice that the default package has another sub-directory called custom-theme. This is where the majority of developers would previously put their new theme. While this works, this is not the correct way to structure your themes.

In the above scenario, the default package houses 2 separate themes. In theory, a package can contain as many themes as you like. The beauty of this system is that as well as having your base theme, you can create new themes which simply enhance your base theme. This allows you to reduce the amount of code you need to write and maintain!

The Directory Structure in Magento 1.4

  • app/design/frontend/base
  • app/design/frontend/base/default
  • app/design/frontend/base/default/etc
  • app/design/frontend/base/default/layout
  • app/design/frontend/base/default/template
  • app/design/frontend/default
  • app/design/frontend/default/default
  • app/design/frontend/fishpig/default
  • app/design/frontend/fishpig/default/layout
  • app/design/frontend/fishpig/default/template
  • app/design/frontend/fishpig/fish-theme
  • app/design/frontend/fishpig/fish-theme/layout
  • app/design/frontend/fishpig/fish-theme/template
You'll notice that the directory structure is identical apart from the addition of the folder called base. This package contains a theme named default, which contains all of the base template files needed for a Magento theme. The base package serves as the final fall back package. Let's discuss fall back so we can understand exactly how to structure our package.

Template Fall Back in Magento 1.4

This subject almost deserves an article of it's own, however, I will try and condense it here without stripping too much out. In the above directory structure, there are 3 packages:

  • base - contains the theme default
  • default - contains the theme default
  • fishpig - contains the themes default and fish-theme
Using the above structure, let's pretend we have configured Magento to use the fish-theme in the fishpig package. If we were to navigate to a product page, Magento would attempt to load the file package/theme/catalog/product/view.phtml. In our scenario, Magento would first look in the fish-theme theme. If the file could not be found here, it would next check the default theme inside the fishpig package. If the file wasn't found here it would then look inside the default theme inside the base package. If this file could not be found Magento would throw an exception saying it could not find the template file needed and execution would stop.

When trying to access view.phtml, Magento would access the following files until either the page was found or an exception was thrown.
  • app/design/frontend/fishpig/fish-theme/catalog/template/product/view.phtml
  • app/design/frontend/fishpig/default/catalog/template/product/view.phtml
  • app/design/frontend/base/default/catalog/template/product/view.phtml
What the above basically means is that to create a new theme, you don't have to recode the whole of Magento!

We are now presented with two options:

  1. Allow our theme to fall back to base/default
  2. Copy over base/default files to fishpig/default and use that as our fall back
Both options are valid and each have their own advantages and disadvantages. For this tutorial, I will be leaving all of the core files in base/default and falling back to that. I will be doing this mainly because it will be easier and require less work from you at this point.

Skin folders

Just like the template and layout folders, the skin folders operate using base/default as a fall back. While templates can be vary similar cross-theme, CSS will most likely be entirely different. Because of this, the default CSS and JS are stored in default/default rather than base/default.

For this example I'm going to create a package called fishpig and a theme called fish-theme. Start by creating the following folders:

  • app/design/frontend/fishpig
  • app/design/frontend/fishpig/default
  • app/design/frontend/fishpig/default/layout
  • app/design/frontend/fishpig/default/template
  • app/design/frontend/fishpig/fish-theme
  • app/design/frontend/fishpig/fish-theme/layout
  • app/design/frontend/fishpig/fish-theme/template
  • skin/frontend/fishpig
  • skin/frontend/fishpig/default
  • skin/frontend/fishpig/fish-theme
Now that you have created the necessary folders, copy over the contents of skin/frontend/default/default to skin/frontend/fishpig/fish-theme.

Now that we have created a custom theme, it is time to enable it in Magento.

In my next post I will explain about the following things

  1. How to Enabling our Package/Theme in Magento 1.4?
  2. How to Creating a template file?
  3. How Customising the default Magento theme?

Check Username/Email availablity using jQuery and Ajax in Codeigniter

This tutorial will helps you to check live availability of username or email using Ajax in Codeigniter. Using this tutorial you can also understand how can we send a jQuery Ajax request to server living in Codeigniter.

In your "view", where you have created form include jQuery library and put the below code there.

In header section:

$(document).ready(function() {     
 /// make loader hidden in start     
 $('#Loading').hide();            
 $('#email').blur(function(){   
 var a = $("#email").val();   
 var filter = /^[a-zA-Z0-9]+[a-zA-Z0-9_.-]+[a-zA-Z0-9_-]+@[a-zA-Z0-9]+[a-zA-Z0-9.-]+[a-zA-Z0-9]+.[a-z]{2,4}$/;        
 // check if email is valid   
 if(filter.test(a)){                 
  // show loader     
  $('#Loading').show();    
  $.post("<?php echo base_url()?>controller_name/check_email_availablity", {     
  email: $('#email').val()    
 },
 function(response){                         
  //#emailInfo is a span which will show you message     
  $('#Loading').hide();     
  setTimeout("finishAjax('Loading', '"+escape(response)+"')", 400);    
 });    
 return false;   
} 
}); 
function finishAjax(id, response){   
 $('#'+id).html(unescape(response));   
 $('#'+id).fadeIn(); 
}

In body section of your form:

<div>   
 <label>E-mail</label>   
 <input id="email" name="email" type="text" value=""  />   
 <span id="Loading"><img src="loader.gif" alt="Ajax Indicator" /></span>  
</div>

In "controller" add this function:

function check_email_availablity()  {   
 $this->load->model('My_model');   
 $get_result = $this->My_model->check_email_availablity();      
 if(!$get_result )   
  echo '<span >Email already in use. </span>';   
 else   
  echo '<span >Email Available</span>'; 
}

Suppose you have a model called my_model.php and a table tbl_members or what ever you named. This table should have a field named "email" of type varchar [200].

Add this function:

function check_email_availablity()  {         
 $email = trim($this->input->post('email'));   
 $email = strtolower($email);       
 $query = $this->db->query('SELECT * FROM tbl_members where email="'.$email.'"');      
 if($query->num_rows() > 0)   
  return false;   
 else 
  return true; 
}

Thats it, this function will return a message against email field that whether it is available or not. This is not for only email, you can use it to check any field. Also this is client side check so you also need to use this model function in server side so that email can also be verified when form has been submitted with disabling javascript .

Download JE Effective Lead Management System - Joomla module and component

JE Effective Lead Management system is a lead Management solution for Joomla websites to manage the leads or contact us Emails. This is kind of very tiny CRM for a sales person who follows up with leads. This best fits of someone who is looking for simple and effective solutuion. If you are small company with few sales guys, this works better, Doing a complete integration of other complex softwares to handle the leasds is a overkill sometime.

Features of JE Effective Lead Management system:

  1. Customizable form for submitting leads.
  2. Captcha field for preventing spam.
  3. Displays all custom field created by Admin.
  4. Supports ajax Form validation.
  5. Admin can Manage Leads(ADD/EDIT/DELETE) from the back end.
  6. The leads has been assigned to the salesperson by Super Admin.
  7. Those who belonged to the Manager & Administrator user group are the salesperson.
  8. Sales person handle the leads that has been assigned by the Admin.
  9. Admin can change the status and weightage of the lead and write remarks about every leads.
  10. Salesperson can change the status and weightage of the lead and write remarks about the leads.
  11. Salesperson can update their daily status and next action to be taken.
  12. Colorful Dashboard with shortcuts for all controllers and list of remainders by Sales person.
  13. Display leads information based on the country and date.
  14. Ease to maintain documents uploaded by users.
  15. Admin can generate his own customfields and set parameter for every fields via backend.
  16. Customizable mail template from the backend.
  17. Unlimitted number of Sales persons can be added in backend.
  18. Admin can restrict the users to upload particular files(.doc, .txt, etc).
  19. Statistical information will be displayed based on the country, weightage, status, date and the sales person.
  20. Support languages English, Swedish, French, Spanish, Dutch, German, Arabic, Norwegian, portuguese, etc ..
  21. Quick Icon in Admin section [only for Joomla 2.5]
  22. Module for Listing Reminder,Latest leads,Leads Report by country in control panel(Admin section) [only for Joomla 2.5]

Admin Demo - Click Here

To download files - Click Here

Screenshot Images

Writing a first code to your own custom theme in wordpress

In the previous post we have discussed about "Building your own theme in Wordpress". At this post, we try to show a article at front page. So, we will write simple code.

Open "index.php", enter following code:

Wordpress_own_theme_code

Open your browser. Point to http://localhost/wordpress.

Now, we will try to loop and show all posts:

Wordpress_own_theme_code