<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://docs.sandbox.joomla.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dukeofgaming</id>
	<title>Joomla! Documentation - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://docs.sandbox.joomla.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dukeofgaming"/>
	<link rel="alternate" type="text/html" href="https://docs.sandbox.joomla.org/Special:Contributions/Dukeofgaming"/>
	<updated>2026-07-07T22:53:24Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://docs.sandbox.joomla.org/index.php?title=Working_with_git_and_github&amp;diff=58278</id>
		<title>Working with git and github</title>
		<link rel="alternate" type="text/html" href="https://docs.sandbox.joomla.org/index.php?title=Working_with_git_and_github&amp;diff=58278"/>
		<updated>2011-05-20T01:27:04Z</updated>

		<summary type="html">&lt;p&gt;Dukeofgaming: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This document will provide a brief overview of working with the Joomla Platform repository on github.com for people who are interested in making code contributions and using eclipse as an IDE. Much will also apply for people who just want to follow development, but that is much simpler.&lt;br /&gt;
&lt;br /&gt;
Some preliminary information.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What is Git? ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Git is distributed version control software. Such software (another example is Mercurial while subversion and CVS are non distributed version control systems) allow many people to contribute code to a single project and also allow for well defined tracking of code changes and provide mechanisms for recording commit by commit records of changes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What is Github? ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Github is a host for git repositories. It is located at [https://github.com github.com]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What is the Joomla! Platform? ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Joomla! Platform also known as the Joomla! Framework is the set of libraries that are used to build the Joomla! CMS and other applications.&lt;br /&gt;
&lt;br /&gt;
The platform is managed separately from the CMS and has its own release cycle; each release of the CMS uses one specific version of the platform.&lt;br /&gt;
&lt;br /&gt;
The platform repository is located at: [https://github.com/joomla/joomla-platform  github.com/joomla/joomla-platform]&lt;br /&gt;
&lt;br /&gt;
== First steps: Github account ==&lt;br /&gt;
&lt;br /&gt;
First, you will need to register at git hub.  &lt;br /&gt;
&lt;br /&gt;
Once registered, you will probably want to go to [https://github.com/joomla/joomla-platform github.com/joomla/joomla-platform ]  and click follow. Then whenever you log in you will see the latest things that have happened in the repository.&lt;br /&gt;
&lt;br /&gt;
If you are going to code, you will also want to click on fork. This will give you your own copy of the platform to work with. You&#039;ll probably want to follow that too.&lt;br /&gt;
&lt;br /&gt;
== Second steps: Install git ==&lt;br /&gt;
&lt;br /&gt;
Now you will want to install git on your local workstation. Github provides excellent instructions on how to do this that will detect your operating system. Simply click on the Set Up Git button.&lt;br /&gt;
&lt;br /&gt;
You will need to set up SSH. As it says on the Github instructions &amp;quot; Setting them up is fairly easy, but does involve a number of steps.&amp;quot; Some will be specific to your operating system, so follow the instructions at github.&lt;br /&gt;
&lt;br /&gt;
You will also need to tell Git your user name and password so that it can connect to your repositories on github.&lt;br /&gt;
&lt;br /&gt;
== Third steps ==&lt;br /&gt;
&lt;br /&gt;
=== Command Line ===&lt;br /&gt;
If you like using the command line, git by itself provides commands to create a local copy of your fork at github. There are a number of tutorials and reference sites for git including:&lt;br /&gt;
* [http://git-scm.com/documentation  git-scm.com/documentation]&lt;br /&gt;
* [http://gitimmersion.com/ gitimmersion]&lt;br /&gt;
&lt;br /&gt;
Github itself has many documents about how to use git on its help site&lt;br /&gt;
*[http://help.github.com/ help.github.com/]&lt;br /&gt;
&lt;br /&gt;
=== Eclipse ===&lt;br /&gt;
&lt;br /&gt;
Git can also be used with Eclipse, a popular integrated development environment (IDE).&lt;br /&gt;
&lt;br /&gt;
Setting up Eclipse to work with git and github involves a number of steps.&lt;br /&gt;
&lt;br /&gt;
Important references are:&lt;br /&gt;
[http://wiki.eclipse.org/EGit/User_Guide wiki.eclipse.org/EGit/User_Guide]&lt;br /&gt;
and &lt;br /&gt;
[http://wiki.eclipse.org/EGit/GitHub/UserGuide wiki.eclipse.org/EGit/GitHub/UserGuide]&lt;br /&gt;
&lt;br /&gt;
First, you will need to install eGit and Mylyn. Mylyn is probably not really necessary but it will let you access other features of github. Note that Mylyn has dependencies and you will need to install them first (see the user&#039;s guide).&lt;br /&gt;
&lt;br /&gt;
To install eGit from eclipse, go to Help&amp;gt;Eclipse Marketplace. Search for git and click install.&lt;br /&gt;
&lt;br /&gt;
Follow the instructions to fill in your github account information to identify yourself, defaults and other settings.&lt;br /&gt;
&lt;br /&gt;
Once installed, if you click File&amp;gt;Import you should see Git listed as an option and projects from Git as a sub option.&lt;br /&gt;
&lt;br /&gt;
Note the following owes a lot to a number of sites including [http://blog.opsb.co.uk/getting-started-with-git-github-and-eclipse-p http://blog.opsb.co.uk/getting-started-with-git-github-and-eclipse-p].&lt;br /&gt;
&lt;br /&gt;
One important thing to note before starting is that we will be working with the fork you made in Step 1 (If you didn&#039;t make a fork then, do it now). Thus we will not be making a new repository. When reading help materials make sure not to follow instructions to create a new remote repository. &lt;br /&gt;
&lt;br /&gt;
Your fork on github will have a set of three links (ssh, http, git read-only) . You will need the http link.&lt;br /&gt;
&lt;br /&gt;
Click File&amp;gt;Import.&lt;br /&gt;
Choose Projects from Git, click next.&lt;br /&gt;
On the next screen, click Clone and add your http link. The other fields except your password will autofill. (If you haven&#039;t st up your username previously you will need this too).&lt;br /&gt;
&lt;br /&gt;
Click Next, select master (that is all you will have if this is your first time).&lt;br /&gt;
Set a directory.&lt;br /&gt;
Click finish and the files from git will be cloned which means they will be downloaded to your folder.&lt;br /&gt;
&lt;br /&gt;
Next Eclipse will want to create a project. Do not do it!! Instead, in a way that works for your operating system create a hidden file called .project.&lt;br /&gt;
&lt;br /&gt;
In the file put:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot; encoding=&amp;quot;UTF-8&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;projectDescription&amp;gt;&lt;br /&gt;
&amp;lt;name&amp;gt;joomla-platform&amp;lt;/name&amp;gt;&lt;br /&gt;
&amp;lt;comment&amp;gt;&amp;lt;/comment&amp;gt;&lt;br /&gt;
&amp;lt;projects&amp;gt;&lt;br /&gt;
&amp;lt;/projects&amp;gt;&lt;br /&gt;
&amp;lt;buildSpec&amp;gt;&lt;br /&gt;
&amp;lt;buildCommand&amp;gt;&lt;br /&gt;
&amp;lt;name&amp;gt;org.eclipse.wst.validation.validationbuilder&amp;lt;/name&amp;gt;&lt;br /&gt;
&amp;lt;arguments&amp;gt;&lt;br /&gt;
&amp;lt;/arguments&amp;gt;&lt;br /&gt;
&amp;lt;/buildCommand&amp;gt;&lt;br /&gt;
&amp;lt;/buildSpec&amp;gt;&lt;br /&gt;
&amp;lt;natures&amp;gt;&lt;br /&gt;
&amp;lt;nature&amp;gt;org.eclipse.php.core.PHPNature&amp;lt;/nature&amp;gt;&lt;br /&gt;
&amp;lt;/natures&amp;gt;&lt;br /&gt;
&amp;lt;/projectDescription&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
But change test to the name of your folder.&lt;br /&gt;
&lt;br /&gt;
Now your folder should appear on the list of projects. Select it and finish.&lt;br /&gt;
&lt;br /&gt;
You should now have a git local repository.&lt;br /&gt;
&lt;br /&gt;
== Getting to Work ==&lt;br /&gt;
&lt;br /&gt;
Once you have your repository you are ready to start working on code. &lt;br /&gt;
Whenever you have some code that you are happy with, you should commit it locally. Note that unless you commit, your local changes will not enter into version control. &lt;br /&gt;
To commit, you click Team&amp;gt;commit.&lt;br /&gt;
&lt;br /&gt;
To be continued ...&lt;br /&gt;
&lt;br /&gt;
== Reference ==&lt;br /&gt;
&lt;br /&gt;
* [http://progit.org/book/ Pro Git]&lt;br /&gt;
* [http://www.ndpsoftware.com/git-cheatsheet.html Git Cheatsheet]&lt;/div&gt;</summary>
		<author><name>Dukeofgaming</name></author>
	</entry>
	<entry>
		<id>https://docs.sandbox.joomla.org/index.php?title=Changing_the_site_favicon&amp;diff=26738</id>
		<title>Changing the site favicon</title>
		<link rel="alternate" type="text/html" href="https://docs.sandbox.joomla.org/index.php?title=Changing_the_site_favicon&amp;diff=26738"/>
		<updated>2010-04-18T03:35:52Z</updated>

		<summary type="html">&lt;p&gt;Dukeofgaming: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;# &#039;&#039;&#039;Create a 16x16 pixel image.&#039;&#039;&#039;  You may use graphic software such as [[wikipedia:Photoshop|Photoshop]], [[wikipedia:Gimp|Gimp]] or [[wikipedia:Windows_Paint|Windows Paint]] or an online tool such as http://antifavicon.com/&lt;br /&gt;
# &#039;&#039;&#039;Convert to ico format&#039;&#039;&#039; using free online sites such as:&lt;br /&gt;
#* http://converticon.com/&lt;br /&gt;
#* http://www.favicongenerator.com/&lt;br /&gt;
#* http://www.htmlkit.com/services/favicon/&lt;br /&gt;
#* http://tools.dynamicdrive.com/favicon/&lt;br /&gt;
#* http://www.favicon.cc/&lt;br /&gt;
# The file you created in this way will have the extension .ico. &#039;&#039;&#039;Copy the file&#039;&#039;&#039; to the /joomla/templates/&amp;lt;your template&amp;gt; directory and &#039;&#039;&#039;name it&#039;&#039;&#039; favicon.ico.&lt;br /&gt;
# Open a browser. Do you see your new icon? If so, congratulations. If not, that doesn&#039;t necessarily mean you did anything wrong. Browsers are designed to minimize data traffic, so they don&#039;t refresh the favicon every time they show a page. Even refreshing the page (F5) wont help. So you need to refresh more thoroughly:&lt;br /&gt;
#* &#039;&#039;Mozilla / Firefox / Safari&#039;&#039;: hold down Shift while clicking Reload, or press Ctrl-Shift-R (Cmd-Shift-R on Apple Mac);&lt;br /&gt;
#* &#039;&#039;IE&#039;&#039;: hold Ctrl while clicking Refresh, or press Ctrl-F5;&lt;br /&gt;
#* &#039;&#039;Konqueror&#039;&#039;: simply click the Reload button, or press F5;&lt;br /&gt;
#* &#039;&#039;Opera&#039;&#039; users may need to completely clear their cache in Tools→Preferences.&lt;br /&gt;
#* &#039;&#039;Chrome&#039;&#039;: Shift-F5&lt;br /&gt;
If this doesn&#039;t work you will need to delete the temporary internet files and the history and then open your page again.&lt;br /&gt;
&lt;br /&gt;
Some templates contain code that redirects the browser to another directory or another icon file. To determine where your new favicon should be, examine http://yoursite.com/templates/your_template/index.php and look for code that contains the text &amp;lt;link rel=&amp;quot;shortcut icon&amp;quot;. There you will find the directory and the name of the icon file. Copy your icon to that place and give it the the name that link is pointing to (you might want to backup the old file). Make sure you set the security correctly such that you webserver has access to that file. Look at the example below. &amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&amp;lt;link rel=&amp;quot;shortcut icon&amp;quot; href=&amp;quot;http://yoursite.com/templates/your_template/icon/favicon.ico&amp;quot; /&amp;gt;&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you don&#039;t want to just change the &#039;&#039;&#039;favicon.ico&#039;&#039;&#039; file in its respective template directory you can find the reference to the &#039;&#039;&#039;favicon.ico&#039;&#039;&#039; file in the &#039;&#039;&#039;html.php&#039;&#039;&#039; document. The path is &#039;&#039;&#039;&amp;quot;........\libraries\joomla\document\html\html.php&amp;quot;&#039;&#039;&#039;. This should prevent the icon from toggling if you use &lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&amp;lt;link rel=&amp;quot;shortcut icon&amp;quot; href=&amp;quot;http://yoursite.com/templates/your_template/icon/youricon.ico&amp;quot; /&amp;gt;&amp;lt;/source&amp;gt; &lt;br /&gt;
in the template html and you don&#039;t remove the favicon.ico file. (why call the icon twice?)&lt;br /&gt;
&lt;br /&gt;
From the html.php &lt;br /&gt;
&amp;lt;source lang=&amp;quot;php&amp;quot;&amp;gt;&lt;br /&gt;
// Try to find a favicon by checking the template and root folder&lt;br /&gt;
		$path = $directory . DS;&lt;br /&gt;
		$dirs = array( $path, JPATH_BASE . DS );&lt;br /&gt;
		foreach ($dirs as $dir )&lt;br /&gt;
		{&lt;br /&gt;
			$icon =   $dir . &#039;favicon.ico&#039;;&lt;br /&gt;
			if (file_exists( $icon ))&lt;br /&gt;
			{&lt;br /&gt;
				$path = str_replace( JPATH_BASE . DS, &#039;&#039;, $dir );&lt;br /&gt;
				$path = str_replace( &#039;\\&#039;, &#039;/&#039;, $path );&lt;br /&gt;
				$this-&amp;gt;addFavicon( JURI::base(true).&#039;/&#039;.$path . &#039;favicon.ico&#039; );&lt;br /&gt;
				break;&#039;&#039;&lt;br /&gt;
	&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&amp;lt;noinclude&amp;gt;[[Category:Templates]]&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Dukeofgaming</name></author>
	</entry>
	<entry>
		<id>https://docs.sandbox.joomla.org/index.php?title=Archived:Database_schema_standards&amp;diff=16543</id>
		<title>Archived:Database schema standards</title>
		<link rel="alternate" type="text/html" href="https://docs.sandbox.joomla.org/index.php?title=Archived:Database_schema_standards&amp;diff=16543"/>
		<updated>2009-11-04T00:31:44Z</updated>

		<summary type="html">&lt;p&gt;Dukeofgaming: /* Table Naming Conventions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Table Naming Conventions ==&lt;br /&gt;
&lt;br /&gt;
* Table names should always go in plural form, e.g.: users, sessions, usergroups, etc.&lt;br /&gt;
* Cross referencing table names should always reflect multiplicity, e.g.: 1 to N: user_sessions, M to N: users_usergroups&lt;br /&gt;
&lt;br /&gt;
== Field Naming Conventions ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Field Type Recommendations ==&lt;/div&gt;</summary>
		<author><name>Dukeofgaming</name></author>
	</entry>
</feed>