Extension Types in Joomla!

Component

• Complex extensions with two parts: admin and fornt end
• Always one component should be running 
• Components are triggered by menus

Module

• Can be more than one module per page
• Usually placed around the components

Joomla! tips

How to upload files more than 2MB to Joomla

• Go to Apache x.x/bin and open php.ini file with a text editor
• Find 'upload_max_filesize' (i.e. ctrl+f)
• Give a higher value you want
• Save and DO restart the server.

Changing the text displayed in Joola! admin login

Use the following fie to customize the login.
\administrator\language\en-GB.com_login.ini
\administrator\language\en-GB.ini

Removing adsmanager footer

components/com_adsmanager/helpers/general.phpdelete only...

echo '<div style="text-align:center !important;"><a href="http://www.joomprod.com/" title="classifield ads">Classifield Ads</a> - AdsManager 2.6</div>';

Spring Security in the simplest possible way!

Spring security has support for almost all the security protocols being used today. Here is the introduction and list of technologies supported by Spring. In addition it supports OAuth 1.0 and 2.0 !!!

In this article, I describe Spring security at very basic level: how to implement a simple client-server authentication using Spring security. So lets take a look at the steps to do this.

• Including Spring security libraries in your classpath. If you are using eclipse put these .jar files into  WEB-INF/libs folder and add them to the build path.

 Note: These are the required srping security libraries

• spring-security-core
• spring-security-config
• sprng-security-web

• Creating the Spring security configurations file, say spring-security-context.xml. and configuring the namespaces.

my spring-security-context.xml file

Loading ....

• Adding the  spring-security-config.xml to the web.xml file so that it can be loaded as a part of the spring application context.

• Adding spring security filters

my web.xml file

Loading ....



Advanced Stuff

• SecurityContextHolder, to provide access to the SecurityContext.
• SecurityContext, to hold the Authentication and possibly request-specific security information.
• Authentication, to represent the principal in a Spring Security-specific manner.
• GrantedAuthority, to reflect the application-wide permissions granted to a principal.
• UserDetails, to provide the necessary information to build an Authentication object from your application's DAOs or other source source of security data.
• UserDetailsService, to create a UserDetails when passed in a String-based username (or certificate ID or the like).
  
  

Power of HTML5!

..

OAuth makes life easier and safer!

This is the best explanation I found so far.

My Objective

This is my way of tracking what I've learnt by experience and sharing it with you so that  you wouldn't have to go through a hard time to connect the pieces of information that you collect from here and there into a single topic. I'll try to keep keep everything as simple as possible. Because;

"Simplicity is the key to brilliance" - Bruce Lee 

Anyone is welcome to share ideas and improve the content.