<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://docs.moodle.org/dev/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Net-buoy</id>
	<title>MoodleDocs - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://docs.moodle.org/dev/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Net-buoy"/>
	<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/Special:Contributions/Net-buoy"/>
	<updated>2026-11-17T16:40:02Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.5</generator>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=User_talk:Helen_Foster&amp;diff=23157</id>
		<title>User talk:Helen Foster</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=User_talk:Helen_Foster&amp;diff=23157"/>
		<updated>2009-03-09T23:44:27Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* &amp;quot;experimental:&amp;quot; prefix */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Creating new FAQ pages ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
I have successfully created a stub for a XML FAQ page (https://docs.moodle.org/en/XML_FAQ) but how do I get it promoted on https://docs.moodle.org/en/Category:FAQ ?&lt;br /&gt;
&lt;br /&gt;
I also would like to create an Import/Export FAQ for collecting all the information regarding Moodle import and export which is scattered in different forums.&lt;br /&gt;
&lt;br /&gt;
Regards,&lt;br /&gt;
[[User:Frank Ralf|Frank Ralf]]&lt;br /&gt;
&lt;br /&gt;
:Hi Helen will have to answer the Import/Export question.  I jumped in and added &amp;lt;nowiki&amp;gt;[[Category:FAQ]]&amp;lt;/nowiki&amp;gt; to the bottom of the page, which anyone can do. And took your hint and added a &amp;lt;nowiki&amp;gt;{{stub}}&amp;lt;/nowiki&amp;gt; template at the top.  Thanks for the XML work. Best --[[User:chris collman|chris collman]] 14:16, 3 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
::Hi Frank, thanks for your offer - an [[Import and export FAQ]] page would be great, thanks! --[[User:Helen Foster|Helen Foster]] 04:12, 4 December 2008 (CST)&lt;br /&gt;
:::Thanks to both of you! Helen, how did you get that nice Contents menu on your Import and export FAQ page? I couldn&#039;t figure that out from the source. --[[User:Frank Ralf|Frank Ralf]] 05:30, 4 December 2008 (CST) Problem solved, just found the documentation ;-) --[[User:Frank Ralf|Frank Ralf]] 05:43, 4 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
== Suggestion that is probably total overkill ==&lt;br /&gt;
&amp;lt;onlyinclude&amp;gt;&lt;br /&gt;
# Create a new FAQ namespace.&lt;br /&gt;
# In this namespace, create one page for each frequent question, where the contents of the page is the answer.&lt;br /&gt;
# Use our new knowledge of transclusions to build the FAQ lists by just pulling in pages from the FAQ namespace.&lt;br /&gt;
&lt;br /&gt;
The benefits of doing this are&lt;br /&gt;
* The same FAQ can appear in more than one list without copying-and-pasting.&lt;br /&gt;
* Each question gets a unique URL that so in the forums, we can point people to a page that just answers their specific question.&lt;br /&gt;
&lt;br /&gt;
Disadvantages&lt;br /&gt;
* Editing FAQ lists becomes incomprehensible to anyone who is not a MediaWiki geek.&lt;br /&gt;
&lt;br /&gt;
If we went this way, I would like to use B to build a new FAQ page: &amp;quot;Troubleshooting FAQ&amp;quot;. Might be a good idea anyway.&lt;br /&gt;
&amp;lt;/onlyinclude&amp;gt;&lt;br /&gt;
I hasten to say that I am not recommending this approach. The disadvantages could easily outweigh the advantages. I am simply pointing out a technical possibility that may be worth considering either now, or in the future.&amp;lt;onlyinclude&amp;gt;--[[User:Tim Hunt|Tim Hunt]] 07:11, 4 December 2008 (CST)&amp;lt;/onlyinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:Just added [[MoodleDocs:Transclusion]].  Good thing I had my first cup of coffee, Tim&#039;s thoughtful post got me rubbing the sleep out of my eyes.  I wonder if I can get the partial transclusion of this section to work in Sandbox then in [[MoodleDocs_talk:Transclusion]]. Definitely a tool to be used with care. But Wowie Zowie ! --[[User:chris collman|chris collman]] 06:49, 5 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
:: Hello Tim, I think your suggested solution would indeed be overkill and would make maintaining FAQ too difficult. I see FAQ as an intermediary step between the unorganised kind of &amp;quot;documentation&amp;quot; which is provided in the forums towards &amp;quot;real&amp;quot; documentation. Therefore the ease of editing is crucial in my opinion. What about using Moodle&#039;s &#039;&#039;&#039;autolinking mechanism&#039;&#039;&#039; to automatically link to FAQ pages, e.g. if there is a mention of grades in the forums that would create an automatic link to Grades FAQ. I am quite new to Moodle, but couldn&#039;t that be done with setting up a kind of FAQ Glossary? --[[User:Frank Ralf|Frank Ralf]] 02:44, 16 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
::: Hi Tim, thanks for your suggestion, though I think it&#039;s overkill too!  The current FAQ pages have nice short titles which are easy to find and to include in forum posts. Having a page for each FAQ would result in really long URLs. Also, I think that when we point people to an FAQ page, and they have to look through it to find the answer to their question, they may well find answers to other questions they have. As other people have suggested, I think FAQ pages work well as start pages with links to lots of other pages i.e. they&#039;re kept fairly short, for example [[Contributed code FAQ]]. --[[User:Helen Foster|Helen Foster]] 04:49, 18 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
::: Frank, regarding autolinking to FAQ pages, have you come across the Moodle Docs filter on moodle.org? Please see the [[Moodle.org FAQ]] for more details. --[[User:Helen Foster|Helen Foster]] 04:49, 18 December 2008 (CST)&lt;br /&gt;
::::Helen, thanks for the hint. But isn&#039;t that the usual &#039;&#039;manual&#039;&#039; way of wiki linking? But on second thought that might really be the best way of linking to FAQ pages as it keeps getting the forums cluttered with too many (automatic) links. In fact, it just might be a matter of good practice to put advice of lasting value from the forums into a more structured form of documentation and nothing which could or should be done in an automatic and technical way... --[[User:Frank Ralf|Frank Ralf]] 05:11, 19 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
== Security Notification registration ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
It was suggested to me through the #moodle channel on freenode that I raise this concern with you.&lt;br /&gt;
&lt;br /&gt;
I&#039;m developing a moodle installation behind a firewall on a non-public URL and am interested in subscribing to security updates (prompted to check this after seeing a moodle vulnerability mentioned on Bugtraq). I had previously attempted to subscribe by registering our installation through the admin pages, however that registration was rejected as the site was located behind a firewall and not accessible.&lt;br /&gt;
&lt;br /&gt;
Due to that rejection, I wasn&#039;t subscribed to security updates.&lt;br /&gt;
&lt;br /&gt;
I now find myself in the unfortunate position where I cannot subscribe to security updates without having a public facing site (which I can&#039;t reasonably know is secure as I&#039;m not receiving security updates through your mailing list).&lt;br /&gt;
&lt;br /&gt;
The burden for those of us who have an internal site they&#039;re developing (or perhaps is in production) is that we must now create a public facing site to register for the sole purpose of receiving security updates. If the thought is that only parties interested in maintaining a moodle site should have access to those messages, perhaps a different measure could be put into place (a code that appears once moodle is installed, for example).&lt;br /&gt;
&lt;br /&gt;
I&#039;ve tried subscribing through sympa@lists.moodle.org, however that method does not work either.&lt;br /&gt;
&lt;br /&gt;
Could you please provide a process for folks like me to get on the security updates list without having to install moodle on a public web server first?&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
- P.&lt;br /&gt;
&lt;br /&gt;
:Hi Paul, how about subscribing to the [http://moodle.org/mod/forum/view.php?f=996 security announcements forum], where all important security issues are published. --[[User:Helen Foster|Helen Foster]] 04:34, 18 December 2008 (CST)&lt;br /&gt;
== Unseen (not hidden) activities==&lt;br /&gt;
Hi Helen (This is partly my attempt at practising here by the way!) I&#039;ve posted several times recently about the concept of &#039;unseen&#039; topics with resources that can be linked to on the course page where hidden ones wouldn&#039;t work. is there documentation about that somewhere here ? If so, where? Then I can point Moodlers to it next time.If not, shall I write it? Thanks - [[User: Mary Cooch|Mary Cooch]]&lt;br /&gt;
&lt;br /&gt;
:Hi Mary, I&#039;ve just had a quick look and can&#039;t find any documentation about unseen topics, so it would be helpful if you could write some, perhaps here: [[Course homepage]]. Thanks in advance :-) --[[User:Helen Foster|Helen Foster]] 17:20, 19 December 2008 (CST)&lt;br /&gt;
:Helen - please can you check what I have done as you know I&#039;m still a novice and don&#039;t want to put the wrong thing in the wrong place! Also, if you look on my usertalk Chris Colman said it might be useful on the html linking page? [[User: Mary Cooch|Mary Cooch]]&lt;br /&gt;
&lt;br /&gt;
== Downloading Moodle Core ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
I came across Moodle just this morning, and read a little about its design, and loved it, it is perfect for the project Im starting.&lt;br /&gt;
&lt;br /&gt;
Ive gone to the download page, to download the Moodle core zip package, but when I click on the link to download I get the following message;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;A server error that affects your login session was detected. Please login again or restart your browser.&#039;&lt;br /&gt;
&lt;br /&gt;
( Continue )&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I had a look around the FAQ pages, to see if there was anything on there, but it only mentions about people who already have moodle and are having this difficulty,&lt;br /&gt;
&lt;br /&gt;
Please could you send me an alternative link, &lt;br /&gt;
&lt;br /&gt;
Kind Regards&lt;br /&gt;
Andrew&lt;br /&gt;
:Hi Andrew, I left a comment on your [[User_talk:Andrew_Abel|user comment page]], just in case you were in a hurry to play with Moodle. --[[User:chris collman|chris collman]] 07:40, 1 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
::Hi Andrew, I hope you&#039;ve been successful in downloading Moodle by now. Chris, thanks for your helpful comments :-) --[[User:Helen Foster|Helen Foster]] 01:21, 2 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;experimental:&amp;quot; prefix ==&lt;br /&gt;
&lt;br /&gt;
[[User:Marc Grober|Marc Grober]] 12:00, 12 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
We started using experimental: as a prefix because there was some confusion about the use of Development: as a prefix.....&lt;br /&gt;
&lt;br /&gt;
In the Moodle docs, Development: appears to cover Moodle developer documentation, not docs under development,  so we wanted to use a prefix that connote that the docs were, as we suggest, &amp;quot;experimental&amp;quot; (i.e. not ready for prime time).   I had not come across [[Experimental|Experimental]] as the search is a bit temperamental and searching for the root, experiment, produced no result.....&lt;br /&gt;
&lt;br /&gt;
Perhaps we need a different topic name?&lt;br /&gt;
&lt;br /&gt;
I have encouraged AT to ask you to move these pages out of the experimental: topic but I think she feels they are not quite ready and I want to respect hre wishes on this.&lt;br /&gt;
&lt;br /&gt;
We also have some experimental pages under development with respect to gradebook &amp;quot;cases&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
I would encourage you to discuss the progress on all these pages with AT.&lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:Marc, thanks for your comments. The use of experimental: as a prefix is fine by me. Alternatively you could use a [[MoodleDocs:Templates|Moodle Docs template]] to add a message saying that the page is experimental. --[[User:Helen Foster|Helen Foster]] 02:41, 13 January 2009 (CST)&lt;br /&gt;
::Marc and Helen, something new to me.  I found 7 pages when I searched on &amp;quot;experimental:&amp;quot; and found 7 Article title matches.  6 started with &amp;quot;experimental:&amp;quot; and of course &amp;quot;Experimental&amp;quot;. Wondering if an alternative draft to Main Page should be done that way with the Experimental template.  :)--[[User:chris collman|chris collman]] 06:00, 13 January 2009 (CST)&lt;br /&gt;
:::Helen, thanks for moving some of the experimental: pages.  The page here, however, has yet to be moved: [https://docs.moodle.org/en/experimental:Getting_Help_Installing_and_Managing_Moodle]. Vis-a-vis topics/categories, I think it makes sense to have a category that is not searched by default so that users do not find materials that is not ready for prime time.  By the same token,  I think, as I mentioned above,  that Development: is problematic because it confuses as far as whether it is a topic for Developers or addresses material under development, which are really two different areas.  Likewise, as long as there is an Experimental page the use of experimental: could cause confusion.    I would argue for three distinct categories.... [[User:Marc Grober|Marc Grober]] 12:16, 24 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
::As I understood your (Helen&#039;s) comment (posted I don&#039;t recall where) you (Helen) were I think suggesting that what I was really suggesting was a new name space such that folks could develop documents that were not included in a default search.....  which I think is exactly what I was looking for....  So the question becomes can and should we do such a thing..... --[[User:Marc Grober|Marc Grober]] 23:44, 9 March 2009 (UTC)&lt;br /&gt;
&lt;br /&gt;
==Talk:Helen&#039;s page is over 32k==&lt;br /&gt;
FYI: I got that warning.  Maybe a subpage for the older stuff and a link, so we don&#039;t loose some stuff. Of course alternatively, if I deleted all my comments/questions, that would shorted it a lot :)  --[[User:chris collman|chris collman]] 06:04, 13 January 2009 (CST)&lt;br /&gt;
::Seriously, I would be happy to edit my posts here down to a nub or nothingness.  I think some of the language requests for help could be put in one heading and shortened, without losing anything.    --[[User:chris collman|chris collman]] 06:13, 13 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
:Chris, thanks for creating [[User talk:Helen Foster/1]]. I think it&#039;s a good solution :-) --[[User:Helen Foster|Helen Foster]] 02:51, 14 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[User talk:Helen Foster/1]] for older comments&lt;br /&gt;
&lt;br /&gt;
== Registered Users Bug with Mediawiki ==&lt;br /&gt;
&lt;br /&gt;
Hi, [[User_talk:David_Scotson#Moodle_Docs_stats|Way back in 2006 you mentioned]] a work-around for a bug resulting in registered users stats on [[Special:Statistics]] not updating properly. I think I am encountering this same bug on my internal wiki now. I know that was a long time ago, but do you remember what you did to fix it/what the work-around mentioned was?&lt;br /&gt;
Thanks,&lt;br /&gt;
--[[User:Adrian Archer|Adrian Archer]] 11:02, 4 March 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
:Hi Adrian, here are Eloy&#039;s workarounds (easy to do with phpMyAdmin):&lt;br /&gt;
&lt;br /&gt;
:# To refresh the count of pages, if it&#039;s not working: table: site_stats, field: ss_total_pages, setting it to -1 should force recalculation of pages&lt;br /&gt;
:# To refresh the count of registered users, delete the contents of the &amp;quot;cached statistics&amp;quot; table&lt;br /&gt;
&lt;br /&gt;
:Thanks to Eloy for recalling them :-) I hope you are able to upgrade to a newer MediaWiki version soon. --[[User:Helen Foster|Helen Foster]] 09:01, 5 March 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
::Thanks so much for the quick response, that sounds like it should work. I&#039;m actually using Version 1.13.3, so I guess the bug still exists. --[[User:Adrian Archer|Adrian Archer]] 09:17, 5 March 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
:::Hmm, Moodle Docs is actually using version 1.11.2, though we&#039;re hoping to upgrade very soon (MDLSITE-657). --[[User:Helen Foster|Helen Foster]] 09:35, 5 March 2009 (CST)&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=User:Marc_Grober&amp;diff=21241</id>
		<title>User:Marc Grober</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=User:Marc_Grober&amp;diff=21241"/>
		<updated>2009-03-03T19:27:47Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: New page: Yes......&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Yes......&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=Talk:Messaging_2.0&amp;diff=27874</id>
		<title>Talk:Messaging 2.0</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=Talk:Messaging_2.0&amp;diff=27874"/>
		<updated>2009-02-06T00:45:29Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: New page: Could you add some info about server configuration? Does the current work intend that a jabber daemon will be included in Moodle 2? If not, will an admin be able to select a jabber daemon ...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Could you add some info about server configuration? Does the current work intend that a jabber daemon will be included in Moodle 2? If not, will an admin be able to select a jabber daemon to use? If the intent is to just provide jabber client service, what about config requirements beyond jabber ID? By way of example,  if we assume that one is already running jabberd for example, how will the new subsystem interface with that server&lt;br /&gt;
&lt;br /&gt;
[[User:Marc Grober|Marc Grober]] 18:45, 5 February 2009 (CST)&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=User:Eric_Hagley&amp;diff=21199</id>
		<title>User:Eric Hagley</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=User:Eric_Hagley&amp;diff=21199"/>
		<updated>2009-02-03T19:34:57Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://moodle.org/user/view.php?id=13907&amp;amp;course=5| Eric Hagley&#039;s ] Moodle Profile.&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=User_talk:Eric_Hagley&amp;diff=23901</id>
		<title>User talk:Eric Hagley</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=User_talk:Eric_Hagley&amp;diff=23901"/>
		<updated>2009-02-03T19:31:48Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: Thanks for cpanel video links&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Thanks for cpanel video links ==&lt;br /&gt;
&lt;br /&gt;
Thanks for the links on cpanel added to the selecting web hosts pages.  I have moved your bits about a little and have added a link to your user page so folks can use the Talk feature with you....&lt;br /&gt;
&lt;br /&gt;
[[User:Marc Grober|Marc Grober]] 13:31, 3 February 2009 (CST)&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=User:Eric_Hagley&amp;diff=21198</id>
		<title>User:Eric Hagley</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=User:Eric_Hagley&amp;diff=21198"/>
		<updated>2009-02-03T19:28:22Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: New page: .&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;.&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=User_talk:Helen_Foster&amp;diff=23152</id>
		<title>User talk:Helen Foster</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=User_talk:Helen_Foster&amp;diff=23152"/>
		<updated>2009-01-24T18:16:34Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* &amp;quot;experimental:&amp;quot; prefix */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Creating new FAQ pages ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
I have successfully created a stub for a XML FAQ page (https://docs.moodle.org/en/XML_FAQ) but how do I get it promoted on https://docs.moodle.org/en/Category:FAQ ?&lt;br /&gt;
&lt;br /&gt;
I also would like to create an Import/Export FAQ for collecting all the information regarding Moodle import and export which is scattered in different forums.&lt;br /&gt;
&lt;br /&gt;
Regards,&lt;br /&gt;
[[User:Frank Ralf|Frank Ralf]]&lt;br /&gt;
&lt;br /&gt;
:Hi Helen will have to answer the Import/Export question.  I jumped in and added &amp;lt;nowiki&amp;gt;[[Category:FAQ]]&amp;lt;/nowiki&amp;gt; to the bottom of the page, which anyone can do. And took your hint and added a &amp;lt;nowiki&amp;gt;{{stub}}&amp;lt;/nowiki&amp;gt; template at the top.  Thanks for the XML work. Best --[[User:chris collman|chris collman]] 14:16, 3 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
::Hi Frank, thanks for your offer - an [[Import and export FAQ]] page would be great, thanks! --[[User:Helen Foster|Helen Foster]] 04:12, 4 December 2008 (CST)&lt;br /&gt;
:::Thanks to both of you! Helen, how did you get that nice Contents menu on your Import and export FAQ page? I couldn&#039;t figure that out from the source. --[[User:Frank Ralf|Frank Ralf]] 05:30, 4 December 2008 (CST) Problem solved, just found the documentation ;-) --[[User:Frank Ralf|Frank Ralf]] 05:43, 4 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
== Suggestion that is probably total overkill ==&lt;br /&gt;
&amp;lt;onlyinclude&amp;gt;&lt;br /&gt;
# Create a new FAQ namespace.&lt;br /&gt;
# In this namespace, create one page for each frequent question, where the contents of the page is the answer.&lt;br /&gt;
# Use our new knowledge of transclusions to build the FAQ lists by just pulling in pages from the FAQ namespace.&lt;br /&gt;
&lt;br /&gt;
The benefits of doing this are&lt;br /&gt;
* The same FAQ can appear in more than one list without copying-and-pasting.&lt;br /&gt;
* Each question gets a unique URL that so in the forums, we can point people to a page that just answers their specific question.&lt;br /&gt;
&lt;br /&gt;
Disadvantages&lt;br /&gt;
* Editing FAQ lists becomes incomprehensible to anyone who is not a MediaWiki geek.&lt;br /&gt;
&lt;br /&gt;
If we went this way, I would like to use B to build a new FAQ page: &amp;quot;Troubleshooting FAQ&amp;quot;. Might be a good idea anyway.&lt;br /&gt;
&amp;lt;/onlyinclude&amp;gt;&lt;br /&gt;
I hasten to say that I am not recommending this approach. The disadvantages could easily outweigh the advantages. I am simply pointing out a technical possibility that may be worth considering either now, or in the future.&amp;lt;onlyinclude&amp;gt;--[[User:Tim Hunt|Tim Hunt]] 07:11, 4 December 2008 (CST)&amp;lt;/onlyinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:Just added [[MoodleDocs:Transclusion]].  Good thing I had my first cup of coffee, Tim&#039;s thoughtful post got me rubbing the sleep out of my eyes.  I wonder if I can get the partial transclusion of this section to work in Sandbox then in [[MoodleDocs_talk:Transclusion]]. Definitely a tool to be used with care. But Wowie Zowie ! --[[User:chris collman|chris collman]] 06:49, 5 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
:: Hello Tim, I think your suggested solution would indeed be overkill and would make maintaining FAQ too difficult. I see FAQ as an intermediary step between the unorganised kind of &amp;quot;documentation&amp;quot; which is provided in the forums towards &amp;quot;real&amp;quot; documentation. Therefore the ease of editing is crucial in my opinion. What about using Moodle&#039;s &#039;&#039;&#039;autolinking mechanism&#039;&#039;&#039; to automatically link to FAQ pages, e.g. if there is a mention of grades in the forums that would create an automatic link to Grades FAQ. I am quite new to Moodle, but couldn&#039;t that be done with setting up a kind of FAQ Glossary? --[[User:Frank Ralf|Frank Ralf]] 02:44, 16 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
::: Hi Tim, thanks for your suggestion, though I think it&#039;s overkill too!  The current FAQ pages have nice short titles which are easy to find and to include in forum posts. Having a page for each FAQ would result in really long URLs. Also, I think that when we point people to an FAQ page, and they have to look through it to find the answer to their question, they may well find answers to other questions they have. As other people have suggested, I think FAQ pages work well as start pages with links to lots of other pages i.e. they&#039;re kept fairly short, for example [[Contributed code FAQ]]. --[[User:Helen Foster|Helen Foster]] 04:49, 18 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
::: Frank, regarding autolinking to FAQ pages, have you come across the Moodle Docs filter on moodle.org? Please see the [[Moodle.org FAQ]] for more details. --[[User:Helen Foster|Helen Foster]] 04:49, 18 December 2008 (CST)&lt;br /&gt;
::::Helen, thanks for the hint. But isn&#039;t that the usual &#039;&#039;manual&#039;&#039; way of wiki linking? But on second thought that might really be the best way of linking to FAQ pages as it keeps getting the forums cluttered with too many (automatic) links. In fact, it just might be a matter of good practice to put advice of lasting value from the forums into a more structured form of documentation and nothing which could or should be done in an automatic and technical way... --[[User:Frank Ralf|Frank Ralf]] 05:11, 19 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
== Security Notification registration ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
It was suggested to me through the #moodle channel on freenode that I raise this concern with you.&lt;br /&gt;
&lt;br /&gt;
I&#039;m developing a moodle installation behind a firewall on a non-public URL and am interested in subscribing to security updates (prompted to check this after seeing a moodle vulnerability mentioned on Bugtraq). I had previously attempted to subscribe by registering our installation through the admin pages, however that registration was rejected as the site was located behind a firewall and not accessible.&lt;br /&gt;
&lt;br /&gt;
Due to that rejection, I wasn&#039;t subscribed to security updates.&lt;br /&gt;
&lt;br /&gt;
I now find myself in the unfortunate position where I cannot subscribe to security updates without having a public facing site (which I can&#039;t reasonably know is secure as I&#039;m not receiving security updates through your mailing list).&lt;br /&gt;
&lt;br /&gt;
The burden for those of us who have an internal site they&#039;re developing (or perhaps is in production) is that we must now create a public facing site to register for the sole purpose of receiving security updates. If the thought is that only parties interested in maintaining a moodle site should have access to those messages, perhaps a different measure could be put into place (a code that appears once moodle is installed, for example).&lt;br /&gt;
&lt;br /&gt;
I&#039;ve tried subscribing through sympa@lists.moodle.org, however that method does not work either.&lt;br /&gt;
&lt;br /&gt;
Could you please provide a process for folks like me to get on the security updates list without having to install moodle on a public web server first?&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
- P.&lt;br /&gt;
&lt;br /&gt;
:Hi Paul, how about subscribing to the [http://moodle.org/mod/forum/view.php?f=996 security announcements forum], where all important security issues are published. --[[User:Helen Foster|Helen Foster]] 04:34, 18 December 2008 (CST)&lt;br /&gt;
== Unseen (not hidden) activities==&lt;br /&gt;
Hi Helen (This is partly my attempt at practising here by the way!) I&#039;ve posted several times recently about the concept of &#039;unseen&#039; topics with resources that can be linked to on the course page where hidden ones wouldn&#039;t work. is there documentation about that somewhere here ? If so, where? Then I can point Moodlers to it next time.If not, shall I write it? Thanks - [[User: Mary Cooch|Mary Cooch]]&lt;br /&gt;
&lt;br /&gt;
:Hi Mary, I&#039;ve just had a quick look and can&#039;t find any documentation about unseen topics, so it would be helpful if you could write some, perhaps here: [[Course homepage]]. Thanks in advance :-) --[[User:Helen Foster|Helen Foster]] 17:20, 19 December 2008 (CST)&lt;br /&gt;
:Helen - please can you check what I have done as you know I&#039;m still a novice and don&#039;t want to put the wrong thing in the wrong place! Also, if you look on my usertalk Chris Colman said it might be useful on the html linking page? [[User: Mary Cooch|Mary Cooch]]&lt;br /&gt;
&lt;br /&gt;
== Downloading Moodle Core ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
I came across Moodle just this morning, and read a little about its design, and loved it, it is perfect for the project Im starting.&lt;br /&gt;
&lt;br /&gt;
Ive gone to the download page, to download the Moodle core zip package, but when I click on the link to download I get the following message;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;A server error that affects your login session was detected. Please login again or restart your browser.&#039;&lt;br /&gt;
&lt;br /&gt;
( Continue )&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I had a look around the FAQ pages, to see if there was anything on there, but it only mentions about people who already have moodle and are having this difficulty,&lt;br /&gt;
&lt;br /&gt;
Please could you send me an alternative link, &lt;br /&gt;
&lt;br /&gt;
Kind Regards&lt;br /&gt;
Andrew&lt;br /&gt;
:Hi Andrew, I left a comment on your [[User_talk:Andrew_Abel|user comment page]], just in case you were in a hurry to play with Moodle. --[[User:chris collman|chris collman]] 07:40, 1 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
::Hi Andrew, I hope you&#039;ve been successful in downloading Moodle by now. Chris, thanks for your helpful comments :-) --[[User:Helen Foster|Helen Foster]] 01:21, 2 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;experimental:&amp;quot; prefix ==&lt;br /&gt;
&lt;br /&gt;
[[User:Marc Grober|Marc Grober]] 12:00, 12 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
We started using experimental: as a prefix because there was some confusion about the use of Development: as a prefix.....&lt;br /&gt;
&lt;br /&gt;
In the Moodle docs, Development: appears to cover Moodle developer documentation, not docs under development,  so we wanted to use a prefix that connote that the docs were, as we suggest, &amp;quot;experimental&amp;quot; (i.e. not ready for prime time).   I had not come across [[Experimental|Experimental]] as the search is a bit temperamental and searching for the root, experiment, produced no result.....&lt;br /&gt;
&lt;br /&gt;
Perhaps we need a different topic name?&lt;br /&gt;
&lt;br /&gt;
I have encouraged AT to ask you to move these pages out of the experimental: topic but I think she feels they are not quite ready and I want to respect hre wishes on this.&lt;br /&gt;
&lt;br /&gt;
We also have some experimental pages under development with respect to gradebook &amp;quot;cases&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
I would encourage you to discuss the progress on all these pages with AT.&lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
:Marc, thanks for your comments. The use of experimental: as a prefix is fine by me. Alternatively you could use a [[MoodleDocs:Templates|Moodle Docs template]] to add a message saying that the page is experimental. --[[User:Helen Foster|Helen Foster]] 02:41, 13 January 2009 (CST)&lt;br /&gt;
::Marc and Helen, something new to me.  I found 7 pages when I searched on &amp;quot;experimental:&amp;quot; and found 7 Article title matches.  6 started with &amp;quot;experimental:&amp;quot; and of course &amp;quot;Experimental&amp;quot;. Wondering if an alternative draft to Main Page should be done that way with the Experimental template.  :)--[[User:chris collman|chris collman]] 06:00, 13 January 2009 (CST)&lt;br /&gt;
:::Helen, thanks for moving some of the experimental: pages.  The page here, however, has yet to be moved: [https://docs.moodle.org/en/experimental:Getting_Help_Installing_and_Managing_Moodle]. Vis-a-vis topics/categories, I think it makes sense to have a category that is not searched by default so that users do not find materials that is not ready for prime time.  By the same token,  I think, as I mentioned above,  that Development: is problematic because it confuses as far as whether it is a topic for Developers or addresses material under development, which are really two different areas.  Likewise, as long as there is an Experimental page the use of experimental: could cause confusion.    I would argue for three distinct categories.... [[User:Marc Grober|Marc Grober]] 12:16, 24 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
==Talk:Helen&#039;s page is over 32k==&lt;br /&gt;
FYI: I got that warning.  Maybe a subpage for the older stuff and a link, so we don&#039;t loose some stuff. Of course alternatively, if I deleted all my comments/questions, that would shorted it a lot :)  --[[User:chris collman|chris collman]] 06:04, 13 January 2009 (CST)&lt;br /&gt;
::Seriously, I would be happy to edit my posts here down to a nub or nothingness.  I think some of the language requests for help could be put in one heading and shortened, without losing anything.    --[[User:chris collman|chris collman]] 06:13, 13 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
:Chris, thanks for creating [[User talk:Helen Foster/1]]. I think it&#039;s a good solution :-) --[[User:Helen Foster|Helen Foster]] 02:51, 14 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[User talk:Helen Foster/1]] for older comments&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=User_talk:Marc_Grober&amp;diff=23888</id>
		<title>User talk:Marc Grober</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=User_talk:Marc_Grober&amp;diff=23888"/>
		<updated>2009-01-13T23:36:18Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: New page: ----&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;----&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=User_talk:Helen_Foster&amp;diff=23145</id>
		<title>User talk:Helen Foster</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=User_talk:Helen_Foster&amp;diff=23145"/>
		<updated>2009-01-12T18:00:01Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: New section: &amp;quot;experimental:&amp;quot; prefix&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Documentation for different versions ==&lt;br /&gt;
&lt;br /&gt;
Helen&lt;br /&gt;
&lt;br /&gt;
Is there a mechanism for specifying which version of Moodle a particular document refers to?  If, for instance, a feature is only available in version 1.6, how would a 1.5.3 user know they couldn&#039;t follow these instructions?&lt;br /&gt;
&lt;br /&gt;
Equally, if something is done differently in two versions, how would we stop an edit war breaking out between 1.5.3 and 1.6 users?&lt;br /&gt;
&lt;br /&gt;
I appreciate this probably isn&#039;t an issue just yet, but it&#039;s possible it may become one in later versions.&lt;br /&gt;
&lt;br /&gt;
Cheers,&lt;br /&gt;
&lt;br /&gt;
[[User:CHRISF|CHRISF]] 19:20, 1 February 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
:Hi ChrisF, thanks for highlighting the issue of differences in Moodle versions. Perhaps a Moodle 1.6 template, inserted using the code &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{Moodle 1.6}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;, may be used to show features specific to Moodle 1.6. What do you think? --[[User:Helen|Helen]] 04:22, 4 February 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
::Good idea.  I think that would clear it up nicely.  [[User:CHRISF|CHRISF]] 18:08, 7 February 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
== Template styles ==&lt;br /&gt;
Hi Helen! I noticed that you reverted my edits on [[Template:Book]] and [[Template:Assignments]]. You were right -- I didn&#039;t realise that the [[MoodleDocs:Styling|style]] doesn&#039;t match [[MoodleDocs:Style guide|moodle.org style]]. However, the current template doesn&#039;t look right either. It should float to the right instead of occupying a substantial part of the upper screen (for eg. on [[Calculated question developer docs]] page) -- this wil provide easier navigation. Also, the tempalate should be colorful and/or bordered -- this looks more attractive and the reader can understand that it is not a part of the article. May be we can have orange or similar colored templates (such as [[Template:Large Installations]] and [[Template:excerpted from Jason Cole]]) that match with moodle.org style? Is there any official style documentation? Is there a moodle.org style guide which describes styles for templates -- I couldn&#039;t find one? [[User:Utkarshraj Atmaram|Utkarshraj Atmaram]] 17:40, 30 March 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
:Hi Utkarshraj, thanks for your contributions to Moodle Docs. As you&#039;ve found, [[MoodleDocs:Style guide]] and [[MoodleDocs:Styling]] contain all the Moodle Docs styling documentation to-date. Please add your comments about template styling to [[MoodleDocs talk:Styling]]. --[[User:Helen Foster|Helen Foster]] 17:26, 31 March 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
::Thank you! I&#039;ve started the discussion at [[MoodleDocs talk:Styling]]. [[User:Utkarshraj Atmaram|Utkarshraj Atmaram]] 19:14, 31 March 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
:::LoL, I just realized that the problem is not with the templates, but with themes. Templates just look find with the MoodleDocs theme, but when I am logged in, I use MonoBook theme -- it doesn&#039;t display them as right-aligned (at Wikipedia, we explicity make the templates right-aligned). Sorry for wasting your time! [[User:Utkarshraj Atmaram|Utkarshraj Atmaram]] 14:44, 18 April 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
== Removing erroneous pages ==&lt;br /&gt;
&lt;br /&gt;
How can unsuitable pages be removed? I just found [[RHLANGUAGE]] which is not documentation-quality...&lt;br /&gt;
Maybe you could do it (please) Helen? Not sure.&lt;br /&gt;
&lt;br /&gt;
Best, Dan&lt;br /&gt;
--[[User:Dan Stowell|Dan Stowell]] 04:24, 4 May 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
:Thanks Dan, for future reference please add the deletion template, &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{Deletion}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;, to any unsuitable page you find. --[[User:Helen Foster|Helen Foster]] 04:45, 5 May 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
== Moodle Doc Is Great ==&lt;br /&gt;
&lt;br /&gt;
You have done a great job and inspired me to use Media Wiki!&lt;br /&gt;
&lt;br /&gt;
:Thanks Martin, though it&#039;s everyone&#039;s contributions that make Moodle Docs a great resource! --[[User:Helen Foster|Helen Foster]] 06:36, 24 May 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
== tr wiki ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
Can you arrange for a wiki https://docs.moodle.org/tr (Türkçe) to be set up.&lt;br /&gt;
&lt;br /&gt;
:Thanks Ethem, I&#039;ll do so as soon as possible. --[[User:Helen Foster|Helen Foster]] 17:12, 15 June 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
== Word Censorship Page ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen, &lt;br /&gt;
&lt;br /&gt;
Note sure why you deleted some of this page. The idea is (partly) to provide instructions on how to use the settings page of the filter. You also removed the &#039;see also&#039; back to the main filters administration page. I&#039;m not sure what&#039;s wrong with that either. Your advice appreciated :-)&lt;br /&gt;
&lt;br /&gt;
--[[User:Howard Miller|Howard Miller]] 22:54, 20 June 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
:Oh, sorry Howard for not explaining my changes to [[Word censorship]]. I deleted text duplicated on the Word censorship settings page in Moodle and removed the See also link since [[Filters]] is listed in [[:Category:Filter]]. However, please feel free to revert any/all of my changes. Your contributions to the documentation are always appreciated :-) --[[User:Helen Foster|Helen Foster]] 17:03, 21 June 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
::That&#039;s cool Helen. So is that the rule - don&#039;t put stuff in the docs that is already in the built-in help?? --[[User:Howard Miller|Howard Miller]] 18:15, 21 June 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
:::The [http://moodle.org/help.php?file=index.html Moodle help files] will remain in each language pack and so it is not necessary to include their text in this documentation, however sometimes it makes things clearer to do so, at least to start with. --[[User:Helen Foster|Helen Foster]] 15:46, 22 June 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
== Contrib code documentation ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
Where would you suggest I document contrib code. I have some documentation for the Moodle for Mobiles project which installs in {yourmoodleroot}/mobile The code is in cvs in contrib/mobile. It is general documentation about what MFM does.&lt;br /&gt;
&lt;br /&gt;
I guess the place to put it would be https://docs.moodle.org/en/mobile&lt;br /&gt;
&lt;br /&gt;
Jamie&lt;br /&gt;
&lt;br /&gt;
:Hi Jamie, actually the project already has a page, [[Moodle for Mobiles]] ;-) though [[mobile]] could redirect to it. You&#039;re also welcome to use any documentation pages linked to Moodle for Mobiles pages in Moodle 1.6. --[[User:Helen Foster|Helen Foster]] 15:56, 22 June 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
::Thanks Helen!! Adding the documentation now. Will redirect from mobile as well. [[User:Jamie Pratt|Jamie Pratt]] 16:08, 22 June 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
:::Cool Helen you did the redirect for me. Thanks for your very speedy response to my enquiry and all your help! -- [[User:Jamie Pratt|Jamie Pratt]] 16:22, 22 June 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
== Chinese Moodle Documentation==&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
I&#039;d like to launch the Chinese Moodle Documentation translation. As I know, MediaWiki has the function that convert charset between Simplified Chinese(GB2312, GB18030) and Traditional Chinese(BIG5). So maybe it&#039;s no need to create two. &lt;br /&gt;
&lt;br /&gt;
Now I&#039;m a translator of moodle and maintain a special moodle Chinese version.&lt;br /&gt;
&lt;br /&gt;
--[[User:Sun Sunner|Sun Sunner]] 21:31, 22 July 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
:Hi Sun, thanks for your offer. I&#039;ll be in touch soon. --[[User:Helen Foster|Helen Foster]] 19:42, 23 July 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
== Spam or what ever you call it in MoodleDocs ==&lt;br /&gt;
&lt;br /&gt;
Yikes, I just looked at Tips and Tricks and your reversal a while back.  I am too lazy/dumb to look, how often do you have to do that? That is not nice.  And since I can never give you enough praise,  THANKS ! --[[User:chris collman|chris collman]] 02:08, 31 July 2006 (WST) today and yesterday&lt;br /&gt;
&lt;br /&gt;
== Brazilian Portuguese Documentation ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen, we have met at MoodleMoot - i am coordinating the PT_BR translation and would like to launch the Wiki version in Português Brasileiro, starting with the documentation files. No problem with Wikis, i am already the admin of another wikimedia site. Our Moodle.org site has more than 400 people collaborating and i hope to get everybody involved in this new project!&lt;br /&gt;
--[[User:Paula de Waal|Paula de Waal]] 02:02, 1 August 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
== Went through teacher documentation links ==&lt;br /&gt;
Hi Helen, before I ran off on vacation (holiday to you :) for a week ) you will notice I did some editing and adjusting.   My focus was on what I consider the first impression a new teacher gets when they enter MoodleDocs.  Thus I went through most of the links in the text in the teacher documentation page.   I also put in some cross links via &amp;quot;see also&amp;quot; and added some images (yeah not real happy see below). &lt;br /&gt;
&lt;br /&gt;
I would really like us (notice that pronoun) to think about how to made the teacher documentation page look like the administrator documention or developer documentation pages.   I would copy the entire contents of the current teacher doc page to a new &amp;quot;course documentation&amp;quot; page. The major task is figuring out the sections for the new teacher doc page, so they function like the admin doc page. That kind of big thinking is just a bit beyond me before vacation perhaps you know of someone who would love that task?&lt;br /&gt;
&lt;br /&gt;
Changing the teacher doc page also means doublechecking other pages that were linked to it and  figuring out it they should point to the new course doc page. I could do that.&lt;br /&gt;
&lt;br /&gt;
Images, I am still feel akward.   I tried a floating table. I tried using thumb, resizing the images with a px and alignment.   I still can&#039;t figure out an easy way to force a section break so it will not appear to one side of the image, but rather below it.  I used a lot of  br .   The thumb resize method works but the quality of the image is not so hot.  Better to   have the file the correct size to begin with, but then we might have to have multiple files of the same image in different sizes.  &lt;br /&gt;
&lt;br /&gt;
Keep up the great work.  --[[User:chris collman|chris collman]] 22:43, 11 August 2006 (WST)&lt;br /&gt;
&lt;br /&gt;
== Thanks for sorting out the question type documentation ==&lt;br /&gt;
&lt;br /&gt;
That really needed doing. --[[User:Tim Hunt|Tim Hunt]] 11:28, 11 September 2006 (CDT)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Wowie Zowie  Helen &#039;&#039;&#039;- oh yeah, that is what we are talking about!   And ditto the thanks to Tim, it will take me a while to switch my head to having lesson questions and quiz questions able to come from the same place (bank).  I will be checking and changing links, away from Question types to specific pages on the Question Bank list.  --[[User:chris collman|chris collman]] 05:33, 12 September 2006 (CDT)  &lt;br /&gt;
&lt;br /&gt;
:Thanks Tim, and a big THANK YOU for your work on the [[Quiz module]]. --[[User:Helen Foster|Helen Foster]] 03:04, 12 September 2006 (CDT)&lt;br /&gt;
&lt;br /&gt;
Joseph and Chris, thanks for your additional comments, which I&#039;ve moved to [[Talk:Question types]] --[[User:Helen Foster|Helen Foster]] 02:23, 9 October 2006 (CDT)&lt;br /&gt;
&lt;br /&gt;
==mod/helps and redirects in MoodleDocs==&lt;br /&gt;
Hi Helen,  I need some big picture confirmation, the view wiki page comment raised a little red flag ontop of my Marblehead as dawn seemed to break here in the Great Granite State once again.  &lt;br /&gt;
&lt;br /&gt;
I try to not get into help pages because I understood those were  &amp;quot;Please don&#039;t edit&amp;quot; pages (and responsibility of developer), which makes a lot of sense, especially with new features. Also Help files have a different format (for example no images or examples of use) because of their in context purpose.  What are my guidelines when something is redirected from what I assume is an online help page link like &amp;quot;mod/wiki/helpsome topic&amp;quot; ?&lt;br /&gt;
&lt;br /&gt;
I am happy to edit and reorganize and add screen shots etc because I am pretty confident now in my edits and reformats (thank you very much and others who follow me around teaching me where to pay attention). When I see a redirect from help, I would like to assume somebody is going to write the help page after the MoodleDoc page has been created.  The redirect is the as a sort of &amp;quot;in the meantime&amp;quot;.   Same question: is this a good assumption to guide my editing?&lt;br /&gt;
&lt;br /&gt;
 I confess, reading some Moodle help pages causes me to wince, and (just like that pesky&lt;br /&gt;
 version of the lesson demo with the innapropriate cluster) they keep returning like an old&lt;br /&gt;
 tooth ache.  One of my todo&#039;s is to figure out the priorities of rewriting help pages on our&lt;br /&gt;
 production Moodles .  So in the meantime, I pretend all tooth aches are in another world :)  &lt;br /&gt;
&lt;br /&gt;
I am having entirely too much fun this morning, sorry for the lengthy post--[[User:chris collman|chris collman]] 06:28, 7 November 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
==Quizzes and Questions==&lt;br /&gt;
Hi Helen, this could me being confused, but if I am confused......&lt;br /&gt;
Example scenario, you go to the Quiz page and you wanted to know about quiz import/export (or worse still you didn&#039;t know it existed) that option doesn&#039;t exist on the menu. I know why - it&#039;s because that isn&#039;t part of the Quizzes &#039;group&#039; (is that the right word? those double squiggly bracket things at the top of the page). It&#039;s part of the Questions group. I&#039;m struggling big time to see how the two knit together - I&#039;m not sure that they do! --[[User:Howard Miller|Howard Miller]] 10:42, 1 December 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
:Hi Howard, the reason why quiz and question pages have different templates is because questions may be used in [[Lesson module|lessons]] as well as quizzes. I&#039;ve started adding a few question links to the page [[Editing a quiz]]. Please feel free to add more links wherever appropriate, thanks :-) --[[User:Helen Foster|Helen Foster]] 12:45, 3 December 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
== Those squiggly bracket thingies ==&lt;br /&gt;
Actually I can&#039;t find any documentation *anywhere* for those double-squiggly-bracket things at the top of many pages. Can we get something in the edit instructions please :-) --[[User:Howard Miller|Howard Miller]] 11:09, 1 December 2006 (CST)&lt;br /&gt;
Oh they&#039;re templates - I&#039;ll shut up now !!!!  --[[User:Howard Miller|Howard Miller]] 11:12, 1 December 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
:Hi Howard, glad you found the templates info in [[MoodleDocs:Style guide]]. Please feel free to add something on templates to [[Help:Editing]] too ;-) --[[User:Helen Foster|Helen Foster]] 12:35, 3 December 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
== Page rename please ==&lt;br /&gt;
&lt;br /&gt;
Helen, please can we rename [[Numerical_question_units_and_intervals]] to have a Development: prefix please. Thanks.&lt;br /&gt;
&lt;br /&gt;
:Done, thanks Tim. Any more pages to be renamed? --[[User:Helen Foster|Helen Foster]] 01:02, 2 December 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
Yes please, another one: can we rename [[Development:OM Protocol]] to [[Development:Open protocol for accessing question engines]], and change [[Development:Opaque]] to point to the new name too. Thanks 08:30, 4 December 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
Wow! That was fast![[User:Tim Hunt|Tim Hunt]] 09:22, 4 December 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
Another one please: [[Cleanups_required_in_the_quiz_and_question_bank]] -&amp;gt; [[Development:Required quiz cleanups]] or similar.&lt;br /&gt;
&lt;br /&gt;
== MoodleDocs in Arabic ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
I&#039;m Intrested in starting MoodleDocs in Arabic ... would you please provide a directory for Arabic (ar) language&lt;br /&gt;
&lt;br /&gt;
Many Thanks&lt;br /&gt;
&lt;br /&gt;
:Hi, thanks for your offer. Assuming you&#039;ve read [[MoodleDocs:Starting MoodleDocs|starting Moodle Docs in another language]], please email &#039;&#039;docs@moodle.org&#039;&#039;, stating how many people are interested in contributing and who is willing to be an administrator. --[[User:Helen Foster|Helen Foster]] 10:15, 12 December 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==template of templates ==&lt;br /&gt;
Hi wonderful Helen,&lt;br /&gt;
https://docs.moodle.org/en/User:chris_collman/sandbox1#Given_the_above&lt;br /&gt;
&lt;br /&gt;
*I tried creating the above template, which I thought might be useful in Teacher Documentation.  &lt;br /&gt;
*I am also playing around in my sandbox1 with formating a page of templates that will automatically adjust.  This might be beyond my skill at the moment but why not?   I am looking at the difference between the administrator page and the teacher page off the documentation link.   Think the &amp;quot;Given the above&amp;quot; might be useful for those one step beyond not &#039;noing &lt;br /&gt;
anything. I was thinking of sub title (which would have an index) for each module, that would show the template. &lt;br /&gt;
&lt;br /&gt;
* where or how can I find a list of templates in MoodleDocs.  &lt;br /&gt;
&lt;br /&gt;
Best Chris--[[User:chris collman|chris collman]] 20:42, 23 December 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
:Hi Chris, here&#039;s a list: [[Special%3AAllpages&amp;amp;from=&amp;amp;namespace=10|All pages (Template namespace)]]. Thanks, as always, for your contributions :-) --[[User:Helen Foster|Helen Foster]] 16:44, 25 December 2006 (CST)&lt;br /&gt;
::I am surprised that there are not more.  I will try to create one but only put it &amp;quot;off the beaten track&amp;quot; and will ask your opinion.  Thanks, and I appreciate all YOUR work. Happy Holidays. --[[User:chris collman|chris collman]] 16:55, 26 December 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
=== How about this ===&lt;br /&gt;
*[[:Template:Teacher documentation]]&lt;br /&gt;
I first thought this would be a list of other templates.  Now it it more than that.  Not sure, seems to long.&lt;br /&gt;
&lt;br /&gt;
I would put this on the [[Teacher documentation]] page for starters.   If you think this is too long then there are 3 options. 1) don&#039;t use it, 2)Keep it as is and see what reaction is, 3) Only have Resources, Activities and Teacher Admin template links (for lack of a better name, to contain course, reports, enrollment, maybe blocks), showing up here.   There is already a resources template.  I could create a Resources and Teacher Admin templates.  &lt;br /&gt;
&lt;br /&gt;
Hope you are having a nice holiday --[[User:chris collman|chris collman]] 13:57, 28 December 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
:Hi Chris, sorry I didn&#039;t see your Teacher documentation template before now. It looks great :-) Please go ahead and put it on the [[Teacher documentation]] page. --[[User:Helen Foster|Helen Foster]] 04:07, 16 January 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
== SUSE Linux Server 10 shell script ==&lt;br /&gt;
https://docs.moodle.org/en/SUSE_Linux_Server_10 by Alex Inman contains a link to whitfieldschool.org which downloads a shell script. The script looks like it requires root priviledges to run. From a security point, this is worrying - is there anything that can be done to quarantine the page until someone can verify (or preferably ask Alex if the install can do without the script altogether)? --[[User:Ken Wilson|Ken Wilson]] 17:24, 7 January 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
:Hi Ken, thanks for your comments which have been moved to [[Talk:SUSE Linux Server 10]]. Hopefully Alex will respond soon. --[[User:Helen Foster|Helen Foster]] 05:30, 9 January 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
== Norwegian version ==&lt;br /&gt;
&lt;br /&gt;
Hi!&lt;br /&gt;
Could you make a /no/Hovedside site where we could start editing Norwegian documentation.&lt;br /&gt;
I&#039;ve sent you a message in the Moodlesystem as well.&lt;br /&gt;
&lt;br /&gt;
KR&lt;br /&gt;
John Harald&lt;br /&gt;
&lt;br /&gt;
:Hi John Harald, thanks for your offer. I&#039;ll be in touch soon. --[[User:Helen Foster|Helen Foster]] 04:15, 16 January 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;Development:&amp;quot; Prefix ==&lt;br /&gt;
&lt;br /&gt;
I have noticed that names many of the articles in the Developer Category are prefixed with the word Development while others are not.  Ain&#039;t this inconsistent?&lt;br /&gt;
&lt;br /&gt;
[[User:vikram solia|vikram solia]] 20:53, 6 February 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
:Hi Vikram, thanks for your comments. There are no doubt more pages in [[:Category:Developer]] which require the Development prefix - the documentation wiki is a work in progress ;-) However, I don&#039;t think that all pages should be prefixed, as some pages are of interest to non-developers too, for example [[Themes]]. --[[User:Helen Foster|Helen Foster]] 03:54, 7 February 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
::In fact, wouldn&#039;t it be better if Development was a suffix and not a prefix as that would allow articles to be listed under their appropriate alphabet instead of getting aggregated under &#039;D&#039; due to the &#039;Development&#039; prefix. -- [[User:vikram solia|vikram solia]] 11:45, 7 February 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
:::The reason it&#039;s a prefix is that it makes it the [[Special%3AAllpages&amp;amp;from=&amp;amp;namespace=100|Development namespace]], which may be searched separately from the main namespace. Regarding the listing of pages in [[:Category:Developer]], this is reported as [http://tracker.moodle.org/browse/MDLSITE-96 bug MDLSITE-96] and awaits fixing ;-) --[[User:Helen Foster|Helen Foster]] 10:39, 8 February 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
==Lesson demo update==&lt;br /&gt;
Hi Helen, just realized when I sent you a message in your Moodle site, I did not reference that I was talking about what I had done there.   Figure you will look here before there.  I am slowly making progress.  - Best  Chris--[[User:chris collman|chris collman]] 17:26, 3 April 2007 (CDT)&lt;br /&gt;
::This project fell off my &amp;quot;daily chip away at it&amp;quot; list and I think I was within 4 hours of having an improved lesson topic section for demo.moodle.org  ready for the sharks to tear apart &amp;lt;grin&amp;gt;  I even made a special out of the way [[User:chris_collman/LessonDemo1|Lesson Demo]] page  in MoodleDocs! FYI: I am going to find what I was working on back in April, restore it to 1.9 localhost and pick up the ball again.  I will be asking you for a public sandbox 1.9 when I get it together.  I apologize.  Thanks to HOP this hit me over the head this morning. Mea cupa --[[User:chris collman|chris collman]] 06:05, 7 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
:: FYI; See tracker [http://tracker.moodle.org/browse/MDLSITE-304 MDLSITE-304]. --[[User:chris collman|chris collman]] 16:28, 7 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
== Please can you delete Cleanups_required_in_the_quiz_and_question_bank ==&lt;br /&gt;
&lt;br /&gt;
It is obsolete. Lots of it has been done, and the other items now exist as tracker bugs, which is the right place for them. Thanks.[[User:Tim Hunt|Tim Hunt]] 05:22, 23 June 2007 (CDT)&lt;br /&gt;
&lt;br /&gt;
:Done, thanks Tim. --[[User:Helen Foster|Helen Foster]] 06:43, 23 June 2007 (CDT)&lt;br /&gt;
&lt;br /&gt;
== Please fix my typo in a page title ==&lt;br /&gt;
&lt;br /&gt;
I screwed up. Emails notification and confirmation when quizzes are submitted should start Email, singular. There are only links there from the roadmap page, and the quiz template. Sorry for being so careless.&lt;br /&gt;
&lt;br /&gt;
:No problem, it&#039;s now [[Quiz submission email notification]]. --[[User:Helen Foster|Helen Foster]] 12:12, 26 June 2007 (CDT)&lt;br /&gt;
&lt;br /&gt;
==Page style question==&lt;br /&gt;
Hi Helen.  I seem to be back to MoodleDocs after a summer away.   &lt;br /&gt;
#I noticed in Lesson forum we had the usual confusion between questions in Lesson or questions in Quiz. I believe we should leave question pages to be primarily about the Quiz module. I did decide that &amp;quot;Tips and tricks&amp;quot; was a good standard place to point out there was a difference.  I made an exception in Multple choice because multianswer is so radically different and created a sub heading.&lt;br /&gt;
#When I got to True/False question, there were bullets in the intro.  I changed it to text to match what I thought was our usual style.  The next page was [[Random Short-Answer Matching question type]], something new to me.  It had the same thing and noticed you had created the page.   &lt;br /&gt;
&amp;lt;nowiki&amp;gt;:)&amp;lt;/nowiki&amp;gt; Is it ok if I a) reformat the opening before any sub heading to text (drop the bullets) and, b) change &amp;quot;respondent&amp;quot; to &amp;quot;student&amp;quot;.  I would like to do these two things when I see it on a page? Maybe I am being too &#039;old fashion&#039; or &#039;provincial&#039;, so I thought I would check.&lt;br /&gt;
Best as always  --[[User:chris collman|chris collman]] 12:30, 31 August 2007 (CDT)&lt;br /&gt;
&lt;br /&gt;
== Import Data to Grade Book ==&lt;br /&gt;
&lt;br /&gt;
I am new to Moodle and I do not know where to ask this.  Please excuse if I am at the wrong place .  I know that I can post  off-line assignment and grade it; Can I use this to import the marks that I have already awarded.  I have these marks in an excel file.  I know I can grade the off-line assignment one student at a time.  Ccan I copy + paste all the data in one step?     &lt;br /&gt;
What can the grade book plus do in this context?  [[User:Sanjay P. K.|Sanjay P. K.]] 06:05, 10 September 2007 (CDT)&lt;br /&gt;
&lt;br /&gt;
==Moodle database module - javascript==&lt;br /&gt;
&lt;br /&gt;
I have been trying in vain to find some documentation on using javascript templates in the database module. Could you possibly point me in the direction of how to use this feature? --[[User:Lindsay Magnus|Lindsay Magnus]] 04:27, 24 October 2007 (CDT)&lt;br /&gt;
&lt;br /&gt;
:Hi Lindsay, as far as I know there is not yet any documentation on using JavaScript templates in the database module. Perhaps you could take a look at the JavaScript template in the image gallery preset and/or ask about it in the Using Moodle [http://moodle.org/mod/forum/view.php?id=3505 Database module forum]. Please add anything you discover to [[Database templates]] to hopefully encourage others to contribute documentation too. --[[User:Helen Foster|Helen Foster]] 03:01, 25 October 2007 (CDT)&lt;br /&gt;
&lt;br /&gt;
::Thanx Helen, I have put what I have figured so far, I hope it is the type of thing that is useful on moodle Docs --[[User:Lindsay Magnus|Lindsay Magnus]] 06:00, 25 October 2007 (CDT)&lt;br /&gt;
&lt;br /&gt;
:::Great! It&#039;s very useful. Thanks Lindsay :-) --[[User:Helen Foster|Helen Foster]] 06:20, 25 October 2007 (CDT)&lt;br /&gt;
&lt;br /&gt;
== Organising New pages ==&lt;br /&gt;
Hi helen,&lt;br /&gt;
I&#039;ve started work on some Wimba pages.  The MoodleDocs links take me through to mod/voicetools/mod, mod/voicetools/index &amp;amp; mod/voicetool/view.  You will see that I have already statred working on /mod.&lt;br /&gt;
#How do I add rename pages so they are more friendly /Wimba/Adding_a_voice_tool for example?&lt;br /&gt;
#Can i create a /Wimba index page?&lt;br /&gt;
#Can i create a Wimba category?&lt;br /&gt;
&lt;br /&gt;
Many thanks&lt;br /&gt;
Matt&lt;br /&gt;
&lt;br /&gt;
:Hi Matt,&lt;br /&gt;
:It&#039;s probably easiest for me to rename pages for you if you let me know the more friendly names (see [http://moodle.org/mod/forum/discuss.php?d=82778&amp;amp;parent=371960 Moodle Docs page renaming] for an alternative method).&lt;br /&gt;
:Regarding creating additional pages, please respect the fact that Moodle Docs is for Moodle documentation. In general, the Moodle Docs link pages should be sufficient. --[[User:Helen Foster|Helen Foster]] 16:25, 14 November 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
::Thanks Helen.  I&#039;ve redirected a third page too, hope I got it right.  I&#039;ve created a wimba overview page in the non-standard modules category as well.&lt;br /&gt;
::Hoping to do some work on the assignment pages this week :-) --[[User:Matt Lingard|Matt Lingard]] 11:21, 19 November 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Assign admin ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
The other day, you redirected my &#039;assign admin&#039; page to a different. I was planning to submit this for the High School Open Source competition that google is holding. I havn&#039;t claimed it yet because i wanted to check anything and maybe submit and extra one with it.&lt;br /&gt;
&lt;br /&gt;
This page woul;d have counted as a Documentation Page fixed.&lt;br /&gt;
&lt;br /&gt;
Please reply soon&lt;br /&gt;
&lt;br /&gt;
Michael P&lt;br /&gt;
&lt;br /&gt;
:Hi Michael, thanks for your documentation on assigning admins and good to hear you&#039;re planning on taking part in the Google Highly Open Participation project :-) Please start by claiming a task from the list here: http://code.google.com/p/google-highly-open-participation-moodle/issues/list then if you claim a documentation task I can help you further --[[User:Helen Foster|Helen Foster]] 07:52, 17 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
== Change the name of site==&lt;br /&gt;
Hello, could you please change this:&lt;br /&gt;
Dodaj/edytuj kurs&lt;br /&gt;
into this:&lt;br /&gt;
Dodaj/edytuj kursy&lt;br /&gt;
(https://docs.moodle.org/pl/index.php?title=Dodaj/edytuj_kurs)&lt;br /&gt;
:No problem, it&#039;s changed. Thanks for your documentation contribution :-) --[[User:Helen Foster|Helen Foster]] 09:20, 26 December 2007 (CST)&lt;br /&gt;
&lt;br /&gt;
==FAQ mystery==&lt;br /&gt;
I&#039;m not sure when this happened but when you used to do a search for FAQ you got a list of the FAQs (sensible). Now you get an useless category page with nothing in it. I&#039;m unsure why --[[User:Howard Miller|Howard Miller]] 09:23, 8 January 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
:Hi Howard, the blank category page is a bug - it should display like this: [[:Category:FAQ]]. As a work-around I have listed the  FAQ pages here: [[FAQ]]. --[[User:Helen Foster|Helen Foster]] 10:33, 8 January 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
== Rename request ==&lt;br /&gt;
&lt;br /&gt;
Helen, please could you rename&lt;br /&gt;
&lt;br /&gt;
Development:Plans_for_enhancing_import/export_in_questiontype_plugins&lt;br /&gt;
&lt;br /&gt;
to&lt;br /&gt;
&lt;br /&gt;
Development:Import/export_for_questiontype_plugins&lt;br /&gt;
&lt;br /&gt;
Since Howard has now implemented it.&lt;br /&gt;
&lt;br /&gt;
::Done: [[Development:Import/export for questiontype plugins]]. Thanks Tim and Howard :-) --[[User:Helen Foster|Helen Foster]] 05:24, 11 January 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
I add topic in comunity brazil.&lt;br /&gt;
http://moodle.org/mod/forum/discuss.php?d=88252#p389946&lt;br /&gt;
and add dicussion for Paula de Wall&lt;br /&gt;
https://docs.moodle.org/pt_br/Usu%C3%A1rio_Discuss%C3%A3o:Paula_de_Waal&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
==Rewording to contributed code ?==&lt;br /&gt;
Hi Helen, Do I understand that you would like to see MoodleSpeak moving towards &amp;quot;contributed code&amp;quot;  and away from &amp;quot;non-standard&amp;quot; ?   Thus Certificate is a &amp;quot;Contributed code module&amp;quot; .  It sounds much more collaborative and MoodleLike AND less like a hack for some proprietary software package.  Good idea even if the ripples are going to be hard to predict !  --[[User:chris collman|chris collman]] 09:19, 3 February 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
:Chris, you&#039;re very observant! Yes, we&#039;re going to rename &amp;quot;non-standard code&amp;quot; as &amp;quot;contributed code&amp;quot; (or &amp;quot;contrib&amp;quot; for short) - see MDLSITE-329. --[[User:Helen Foster|Helen Foster]] 09:49, 15 February 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
==Messy pages and the like==&lt;br /&gt;
Helen, do you think it might be a thought to create a category for &amp;quot;Needing attention&amp;quot; pages. Some pages have become very &amp;quot;messy&amp;quot; and could do with some TLC. It would be handy to mark them when found and then we (or someone) can come back later and fix them. I know it puts a negative blight on a page though.... --[[User:Howard Miller|Howard Miller]] 06:23, 30 March 2008 (CDT)&lt;br /&gt;
:Nice idea, something like a stub.  Suggest whatever it is, be placed on the discussion page, not the main page (my pet peeve with wikipedia and their 1/3 page &amp;quot;improvement&amp;quot; templates). Ooops, Helen does such a great job in curtailing that sort of thing, it must be were I have learned my &amp;quot;attitude&amp;quot;. --[[User:chris collman|chris collman]] 11:49, 30 March 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
::Howard and Chris, thanks for your comments. Would the [[Template:Update|update template]] be suitable, or should we create a &amp;quot;Needing attention&amp;quot; template and category? --[[User:Helen Foster|Helen Foster]] 15:23, 30 March 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
:::Can not speak for Howard, but I have an excuse.  I didn&#039;t look hard enough because I am bald and forever a Newbie :)  That will do fine.  --[[User:chris collman|chris collman]] 06:19, 31 March 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
:::That&#039;s always been there hasn&#039;t it :-)  Yes, that&#039;ll do nicely. --[[User:Howard Miller|Howard Miller]] 03:24, 3 April 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
==Game module==&lt;br /&gt;
Hi, In https://docs.moodle.org/en/Category:Contributed_code the Game module is two times. One time as Hangman and one time as Game. Please delete the Hangman.&lt;br /&gt;
&lt;br /&gt;
:No problem, page deleted as requested. --[[User:Helen Foster|Helen Foster]] 14:56, 3 April 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
== Romanian help pages ==&lt;br /&gt;
&lt;br /&gt;
Dear Helen,&lt;br /&gt;
&lt;br /&gt;
My company implements Moodle in Cluj, Transylvania, (Romania) we have contracted two Moodle installations at universities in my city. We have to do (anyway) a full Moodle translation to Romanian: the existing one is 10% complete. &lt;br /&gt;
My coworkers will finish it this month, and it will be submitted to translations@moodle.org.&lt;br /&gt;
&lt;br /&gt;
In parallel, we have to ellaborate tutorials for Moodle (in Romanian), which will be assembled as a book. I would like to use this opportunity to translate the great amount of English articles to Romanian &#039;&#039;unsing the MoodleDocs&#039;&#039; framework. I think this can be beneficial to everybody, if you agree.&lt;br /&gt;
&lt;br /&gt;
Best regards,&lt;br /&gt;
&lt;br /&gt;
Marcel&lt;br /&gt;
&lt;br /&gt;
:Hi Marcel,&lt;br /&gt;
&lt;br /&gt;
:Regarding the translation of Moodle into Romanian, I suggest that you inform translation coordinator Koen Roggemans ([mailto:translation@moodle.org translation@moodle.org]) now, rather than after you finish your work.&lt;br /&gt;
&lt;br /&gt;
:Thanks for your offer to start a Romanian Moodle Docs :-) Assuming you&#039;ve read [[MoodleDocs:Starting MoodleDocs|starting Moodle Docs in another language]], please email [mailto:docs@moodle.org docs@moodle.org] stating how many people are interested in contributing and who is willing to be an administrator. --[[User:Helen Foster|Helen Foster]] 09:40, 5 April 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
== SCORM 2004 support - has this materialized? ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
I noticed that you&#039;ve been involved in efforts to make the SCORM/AICC module conformant with SCORM 2004.  Did this effort ever produce results?  We&#039;re thinking of using Moodle on a project that requires SCORM 2004 conformance.&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
&lt;br /&gt;
Dan Young&lt;br /&gt;
&lt;br /&gt;
== Can you remove... ==&lt;br /&gt;
&lt;br /&gt;
This page : [[Development:Import questions]] --[[User:Howard Miller|Howard Miller]] 03:47, 11 July 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
:Done. Thanks Howard --[[User:Helen Foster|Helen Foster]] 08:55, 11 July 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
== Wiki rights please! ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen! &lt;br /&gt;
&lt;br /&gt;
Would it be possible to get some more editing rights in the wiki?  Particularly being able to move pages would be helpful because I keep forgetting to namespace them in Development:&lt;br /&gt;
&lt;br /&gt;
Ta!&lt;br /&gt;
Penny&lt;br /&gt;
&lt;br /&gt;
:Done. Thanks Penny --[[User:Helen Foster|Helen Foster]] 10:14, 22 July 2008 (CDT)&lt;br /&gt;
==Chris Major page changes - Request reviews==&lt;br /&gt;
&lt;br /&gt;
===Administration block ultimate disambig===&lt;br /&gt;
I may have overstepped my bounds.   I was a little surprised to find so many links.  The list sort of demonstrates why I think Administration block should get a disambig tag.  &lt;br /&gt;
[https://docs.moodle.org/en/index.php?title=Special:Whatlinkshere/Administration_block&amp;amp;limit=500&amp;amp;from=2068 See this list of over 30 pages].&lt;br /&gt;
&lt;br /&gt;
Say yes and I will go through and modify all the disambig links on that page so course and site admin block gets sorted out at the source :)--[[User:chris collman|chris collman]] 08:00, 30 September 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
:Yes please Chris, that would be wonderful! Thanks for your offer :-) --[[User:Helen Foster|Helen Foster]] 17:02, 30 September 2008 (CDT)&lt;br /&gt;
::OK onto that I go, just for a change of pace--[[User:chris collman|chris collman]] 17:15, 30 September 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Authentication draft ===&lt;br /&gt;
Hi Helen.  Would you check out my draft [[Talk:Authentication#Start_Draft_here|Authentication page]]?  &lt;br /&gt;
&lt;br /&gt;
Best   --[[User:chris collman|chris collman]] 11:01, 24 July 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
:Hi Chris, please see [[Talk:Authentication]] for my comments on your draft. Again, a big THANK YOU for your ideas and suggestions :-) --[[User:Helen Foster|Helen Foster]] 08:04, 30 July 2008 (CDT)&lt;br /&gt;
::Changed the page, simple and I show links to all 5 submenus.  --[[User:chris collman|chris collman]] 11:15, 30 July 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
=== Upload Users draft ===&lt;br /&gt;
Hi Helen. Would you or somebody check out my draft [[Talk:Upload_users#Proposed_changes_July_2008|Upload users page]] ?  &lt;br /&gt;
Best --[[User:chris collman|chris collman]] 08:51, 25 July 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
:Hi Chris, as I&#039;m so slow at getting round to reviewing your suggested major page changes, I&#039;ve created a review template and a category - [[:Category:Pages requiring a review]] - to encourage others to help with reviewing! --[[User:Helen Foster|Helen Foster]] 12:07, 29 August 2008 (CDT)&lt;br /&gt;
::You know how I feel about banner like templates that demand  :-)  Here are the positive statements that I will try to follow.  I will use the category so it appears at the bottom of the article page.  &#039;&#039;&#039;If&#039;&#039;&#039; I use any banner like template (except stub), it will appear on the comment page with the proposed revision or comment below it. Thanks for suggestions, my biggest problem is remembering to do it! --[[User:chris collman|chris collman]] 07:22, 30 August 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
== Where did you find the information about MediaWiki:Loginprompt ==&lt;br /&gt;
&lt;br /&gt;
Oh, and hello! But a question: I really tried to search the MediaWiki manuals on how to change the login prompt, but didn&#039;t find out (or guess) that it is MediaWiki:Loginprompt. I tried MediaWiki:UserLogin. Where did you find that information? In case I need to dig up similar information some other time. (Plus I&#039;m going nuts not finding it :-) --[[User:Samuli Karevaara|Samuli Karevaara]] 22:42, 7 September 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
:Hi Samuli, Mediawiki&#039;s equivalent to Moodle&#039;s language packs is the [[Special:Allmessages|list of system messages]], available via the special pages link in the toolbox. To change any words or phrases in the interface, just search the system messages and edit the appropriate MediaWiki page. (Note: Only wiki admins can edit MediaWiki pages.) --[[User:Helen Foster|Helen Foster]] 02:48, 8 September 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
::Thanks a bunch! I &#039;&#039;was&#039;&#039; looking at that list also, but somehow didn&#039;t connect the dots. (Click the links, that is...) D&#039;oh. --[[User:Samuli Karevaara|Samuli Karevaara]] 04:59, 8 September 2008 (CDT)&lt;br /&gt;
&lt;br /&gt;
== New documentation in Galician ==&lt;br /&gt;
Hi Helen, I would like to start translating MoodleDocs into Galician (gl). I&#039;m familiar with wikis and am willing to become an administrator. [[User:Xosé Calvo|Xosé Calvo]] 02:16, 12 November 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
:Hi Xosé, thanks for your offer. Please email [mailto:docs@moodle.org docs@moodle.org] so I have your contact address. --[[User:Helen Foster|Helen Foster]] 08:47, 14 November 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
== Documentation in Persian (Farsi) ==&lt;br /&gt;
&lt;br /&gt;
Would you please setup a wiki for Persian (Farsi) language?&lt;br /&gt;
&lt;br /&gt;
:Hi, please start by reading [[MoodleDocs:Starting MoodleDocs|starting Moodle Docs in another language]]. --[[User:Helen Foster|Helen Foster]] 08:55, 14 November 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
:: Hi Helen, I already read that page and then wrote to you according to that page. Oh I checked it again right now and am seeing a different procedure. I guess you just updated it. Aren&#039;t you? ;-)&lt;br /&gt;
&lt;br /&gt;
:::You&#039;re very observant Shamim, yes, the page has just been updated. We think it&#039;s most helpful for new Moodlers to have help pop-ups in their own language. Do you agree? --[[User:Helen Foster|Helen Foster]] 05:39, 18 November 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
== Creating new FAQ pages ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
I have successfully created a stub for a XML FAQ page (https://docs.moodle.org/en/XML_FAQ) but how do I get it promoted on https://docs.moodle.org/en/Category:FAQ ?&lt;br /&gt;
&lt;br /&gt;
I also would like to create an Import/Export FAQ for collecting all the information regarding Moodle import and export which is scattered in different forums.&lt;br /&gt;
&lt;br /&gt;
Regards,&lt;br /&gt;
[[User:Frank Ralf|Frank Ralf]]&lt;br /&gt;
&lt;br /&gt;
:Hi Helen will have to answer the Import/Export question.  I jumped in and added &amp;lt;nowiki&amp;gt;[[Category:FAQ]]&amp;lt;/nowiki&amp;gt; to the bottom of the page, which anyone can do. And took your hint and added a &amp;lt;nowiki&amp;gt;{{stub}}&amp;lt;/nowiki&amp;gt; template at the top.  Thanks for the XML work. Best --[[User:chris collman|chris collman]] 14:16, 3 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
::Hi Frank, thanks for your offer - an [[Import and export FAQ]] page would be great, thanks! --[[User:Helen Foster|Helen Foster]] 04:12, 4 December 2008 (CST)&lt;br /&gt;
:::Thanks to both of you! Helen, how did you get that nice Contents menu on your Import and export FAQ page? I couldn&#039;t figure that out from the source. --[[User:Frank Ralf|Frank Ralf]] 05:30, 4 December 2008 (CST) Problem solved, just found the documentation ;-) --[[User:Frank Ralf|Frank Ralf]] 05:43, 4 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
== Suggestion that is probably total overkill ==&lt;br /&gt;
&amp;lt;onlyinclude&amp;gt;&lt;br /&gt;
# Create a new FAQ namespace.&lt;br /&gt;
# In this namespace, create one page for each frequent question, where the contents of the page is the answer.&lt;br /&gt;
# Use our new knowledge of transclusions to build the FAQ lists by just pulling in pages from the FAQ namespace.&lt;br /&gt;
&lt;br /&gt;
The benefits of doing this are&lt;br /&gt;
* The same FAQ can appear in more than one list without copying-and-pasting.&lt;br /&gt;
* Each question gets a unique URL that so in the forums, we can point people to a page that just answers their specific question.&lt;br /&gt;
&lt;br /&gt;
Disadvantages&lt;br /&gt;
* Editing FAQ lists becomes incomprehensible to anyone who is not a MediaWiki geek.&lt;br /&gt;
&lt;br /&gt;
If we went this way, I would like to use B to build a new FAQ page: &amp;quot;Troubleshooting FAQ&amp;quot;. Might be a good idea anyway.&lt;br /&gt;
&amp;lt;/onlyinclude&amp;gt;&lt;br /&gt;
I hasten to say that I am not recommending this approach. The disadvantages could easily outweigh the advantages. I am simply pointing out a technical possibility that may be worth considering either now, or in the future.&amp;lt;onlyinclude&amp;gt;--[[User:Tim Hunt|Tim Hunt]] 07:11, 4 December 2008 (CST)&amp;lt;/onlyinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:Just added [[MoodleDocs:Transclusion]].  Good thing I had my first cup of coffee, Tim&#039;s thoughtful post got me rubbing the sleep out of my eyes.  I wonder if I can get the partial transclusion of this section to work in Sandbox then in [[MoodleDocs_talk:Transclusion]]. Definitely a tool to be used with care. But Wowie Zowie ! --[[User:chris collman|chris collman]] 06:49, 5 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
:: Hello Tim, I think your suggested solution would indeed be overkill and would make maintaining FAQ too difficult. I see FAQ as an intermediary step between the unorganised kind of &amp;quot;documentation&amp;quot; which is provided in the forums towards &amp;quot;real&amp;quot; documentation. Therefore the ease of editing is crucial in my opinion. What about using Moodle&#039;s &#039;&#039;&#039;autolinking mechanism&#039;&#039;&#039; to automatically link to FAQ pages, e.g. if there is a mention of grades in the forums that would create an automatic link to Grades FAQ. I am quite new to Moodle, but couldn&#039;t that be done with setting up a kind of FAQ Glossary? --[[User:Frank Ralf|Frank Ralf]] 02:44, 16 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
::: Hi Tim, thanks for your suggestion, though I think it&#039;s overkill too!  The current FAQ pages have nice short titles which are easy to find and to include in forum posts. Having a page for each FAQ would result in really long URLs. Also, I think that when we point people to an FAQ page, and they have to look through it to find the answer to their question, they may well find answers to other questions they have. As other people have suggested, I think FAQ pages work well as start pages with links to lots of other pages i.e. they&#039;re kept fairly short, for example [[Contributed code FAQ]]. --[[User:Helen Foster|Helen Foster]] 04:49, 18 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
::: Frank, regarding autolinking to FAQ pages, have you come across the Moodle Docs filter on moodle.org? Please see the [[Moodle.org FAQ]] for more details. --[[User:Helen Foster|Helen Foster]] 04:49, 18 December 2008 (CST)&lt;br /&gt;
::::Helen, thanks for the hint. But isn&#039;t that the usual &#039;&#039;manual&#039;&#039; way of wiki linking? But on second thought that might really be the best way of linking to FAQ pages as it keeps getting the forums cluttered with too many (automatic) links. In fact, it just might be a matter of good practice to put advice of lasting value from the forums into a more structured form of documentation and nothing which could or should be done in an automatic and technical way... --[[User:Frank Ralf|Frank Ralf]] 05:11, 19 December 2008 (CST)&lt;br /&gt;
&lt;br /&gt;
== Security Notification registration ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
&lt;br /&gt;
It was suggested to me through the #moodle channel on freenode that I raise this concern with you.&lt;br /&gt;
&lt;br /&gt;
I&#039;m developing a moodle installation behind a firewall on a non-public URL and am interested in subscribing to security updates (prompted to check this after seeing a moodle vulnerability mentioned on Bugtraq). I had previously attempted to subscribe by registering our installation through the admin pages, however that registration was rejected as the site was located behind a firewall and not accessible.&lt;br /&gt;
&lt;br /&gt;
Due to that rejection, I wasn&#039;t subscribed to security updates.&lt;br /&gt;
&lt;br /&gt;
I now find myself in the unfortunate position where I cannot subscribe to security updates without having a public facing site (which I can&#039;t reasonably know is secure as I&#039;m not receiving security updates through your mailing list).&lt;br /&gt;
&lt;br /&gt;
The burden for those of us who have an internal site they&#039;re developing (or perhaps is in production) is that we must now create a public facing site to register for the sole purpose of receiving security updates. If the thought is that only parties interested in maintaining a moodle site should have access to those messages, perhaps a different measure could be put into place (a code that appears once moodle is installed, for example).&lt;br /&gt;
&lt;br /&gt;
I&#039;ve tried subscribing through sympa@lists.moodle.org, however that method does not work either.&lt;br /&gt;
&lt;br /&gt;
Could you please provide a process for folks like me to get on the security updates list without having to install moodle on a public web server first?&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
- P.&lt;br /&gt;
&lt;br /&gt;
:Hi Paul, how about subscribing to the [http://moodle.org/mod/forum/view.php?f=996 security announcements forum], where all important security issues are published. --[[User:Helen Foster|Helen Foster]] 04:34, 18 December 2008 (CST)&lt;br /&gt;
== Unseen (not hidden) activities==&lt;br /&gt;
Hi Helen (This is partly my attempt at practising here by the way!) I&#039;ve posted several times recently about the concept of &#039;unseen&#039; topics with resources that can be linked to on the course page where hidden ones wouldn&#039;t work. is there documentation about that somewhere here ? If so, where? Then I can point Moodlers to it next time.If not, shall I write it? Thanks - [[User: Mary Cooch|Mary Cooch]]&lt;br /&gt;
&lt;br /&gt;
:Hi Mary, I&#039;ve just had a quick look and can&#039;t find any documentation about unseen topics, so it would be helpful if you could write some, perhaps here: [[Course homepage]]. Thanks in advance :-) --[[User:Helen Foster|Helen Foster]] 17:20, 19 December 2008 (CST)&lt;br /&gt;
:Helen - please can you check what I have done as you know I&#039;m still a novice and don&#039;t want to put the wrong thing in the wrong place! Also, if you look on my usertalk Chris Colman said it might be useful on the html linking page? [[User: Mary Cooch|Mary Cooch]]&lt;br /&gt;
&lt;br /&gt;
== Downloading Moodle Core ==&lt;br /&gt;
&lt;br /&gt;
Hi Helen,&lt;br /&gt;
I came across Moodle just this morning, and read a little about its design, and loved it, it is perfect for the project Im starting.&lt;br /&gt;
&lt;br /&gt;
Ive gone to the download page, to download the Moodle core zip package, but when I click on the link to download I get the following message;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;A server error that affects your login session was detected. Please login again or restart your browser.&#039;&lt;br /&gt;
&lt;br /&gt;
( Continue )&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I had a look around the FAQ pages, to see if there was anything on there, but it only mentions about people who already have moodle and are having this difficulty,&lt;br /&gt;
&lt;br /&gt;
Please could you send me an alternative link, &lt;br /&gt;
&lt;br /&gt;
Kind Regards&lt;br /&gt;
Andrew&lt;br /&gt;
:Hi Andrew, I left a comment on your [[User_talk:Andrew_Abel|user comment page]], just in case you were in a hurry to play with Moodle. --[[User:chris collman|chris collman]] 07:40, 1 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
::Hi Andrew, I hope you&#039;ve been successful in downloading Moodle by now. Chris, thanks for your helpful comments :-) --[[User:Helen Foster|Helen Foster]] 01:21, 2 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;experimental:&amp;quot; prefix ==&lt;br /&gt;
&lt;br /&gt;
[[User:Marc Grober|Marc Grober]] 12:00, 12 January 2009 (CST)&lt;br /&gt;
&lt;br /&gt;
We started using experimental: as a prefix because there was some confusion about the use of Development: as a prefix.....&lt;br /&gt;
&lt;br /&gt;
In the Moodle docs, Development: appears to cover Moodle developer documentation, not docs under development,  so we wanted to use a prefix that connote that the docs were, as we suggest, &amp;quot;experimental&amp;quot; (i.e. not ready for prime time).   I had not come across [[Experimental|Experimental]] as the search is a bit temperamental and searching for the root, experiment, produced no result.....&lt;br /&gt;
&lt;br /&gt;
Perhaps we need a different topic name?&lt;br /&gt;
&lt;br /&gt;
I have encouraged AT to ask you to move these pages out of the experimental: topic but I think she feels they are not quite ready and I want to respect hre wishes on this.&lt;br /&gt;
&lt;br /&gt;
We also have some experimental pages under development with respect to gradebook &amp;quot;cases&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
I would encourage you to discuss the progress on all these pages with AT.&lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
&lt;br /&gt;
----&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=How_to_create_a_patch&amp;diff=6784</id>
		<title>How to create a patch</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=How_to_create_a_patch&amp;diff=6784"/>
		<updated>2008-10-10T17:24:43Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you have made some changes to the code that you would like to share with the community, particularly if you want to send them to one of the core developers for possible inclusion in Moodle Core, it is very helpful if you can provide them as a [[Patch|patch file]]. Sometimes also called a diff file.&lt;br /&gt;
&lt;br /&gt;
This page explains how you can make a patch file. Patch is a standard format, and there are many options for how to create one. Pick the one that is easiest for you.&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
One of the most critical aspects of patch usage is identifying for your audience the location for the patch file for application relative to the -p flag! When you create patches note your location and provide that when you share patches. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note, I have not been able to test most of these instructions. They are about right, but I am hoping that as people use them, they will fill in any gaps, correct any details, and so on.[[User:Tim Hunt|Tim Hunt]] 08:40, 25 June 2007 (CDT)&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==Creating a patch using diff==&lt;br /&gt;
&lt;br /&gt;
diff is the a linux command line program, and is where patch files originated. It requires that you have two copies of the code, one with your changes, and one without. Suppose these two copies are in folders called &#039;standard_moodle&#039; and &#039;my_moodle&#039; which are subdirectories of the current folder. Then to create the patch, type:&lt;br /&gt;
&lt;br /&gt;
 diff -Naur standard_moodle my_moodle &amp;gt; patch.txt&lt;br /&gt;
&lt;br /&gt;
==Creating a patch using CVS (command line)==&lt;br /&gt;
&lt;br /&gt;
It is easier if you are using CVS to manage your development, because you don&#039;t need to keep the copy of &#039;standard_moodle&#039;. CVS takes care of that for you. In you workspace (sandbox) type:&lt;br /&gt;
&lt;br /&gt;
 cvs diff -uN &amp;gt; patch.txt&lt;br /&gt;
&lt;br /&gt;
If you have unversioned files to include in your patch, you will notice that the above command simply adds the file&#039;s name to the top of your patch, prefixed with a question mark. This is because your new file is not tagged for adding to the repository. Just do&lt;br /&gt;
&lt;br /&gt;
 cvs add newfile&lt;br /&gt;
&lt;br /&gt;
Then &lt;br /&gt;
&lt;br /&gt;
 cvs diff -uNa &amp;gt; patch.txt&lt;br /&gt;
&lt;br /&gt;
This should add the correct code to the patch, so that someone applying the patch to their working copy will have a new file created at the right place (hopefully!).&lt;br /&gt;
&lt;br /&gt;
If your patch, for some reason, contains a lot of white space changes in many files, you might want to add -Bbw to the diff call. Make sure these changes are really not significant (like adding or removing a space at the end of a line - editors like Eclipse sometimes do this automatically). This can make a patch a lot smaller, and thus easier to review. The complete call would then be &lt;br /&gt;
&lt;br /&gt;
 cvs diff -uNawbB &amp;gt; patch.txt&lt;br /&gt;
&lt;br /&gt;
==Creating a patch using Tortoise CVS==&lt;br /&gt;
&lt;br /&gt;
[http://www.tortoisecvs.org/ Tortoise CVS] is a Windows GUI front end for CVS. To create a patch, right-click on a folder in CVS, and choose &#039;&#039;&#039;CVS -&amp;gt; Make patch ...&#039;&#039;&#039; from the context menu.&lt;br /&gt;
&lt;br /&gt;
==Creating a patch using Eclipse==&lt;br /&gt;
&lt;br /&gt;
See [[Setting_up_Eclipse#Creating_a_patch]]. Eclipse makes creating patches really easy, once you have got it set up correctly.&lt;br /&gt;
&lt;br /&gt;
==Creating a patch using WinMerge==&lt;br /&gt;
&lt;br /&gt;
[http://winmerge.org/ WinMerge] is a nice windows GUI for comparing folders. In this sense it is like the original command-line &#039;diff&#039; program. You need a copy of &#039;standard_moodle&#039; and &#039;my_moodle&#039;. Use &#039;&#039;&#039;File -&amp;gt; Open...&#039;&#039;&#039; to open the two versions for comparison. This will give you a nice view of what you have changed. Then do &#039;&#039;&#039;Tools -&amp;gt; Generate patch ...&#039;&#039;&#039;. In the dialogue box, make sure you select Style: Unified in the Format box.&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
&lt;br /&gt;
* [[How_to_apply_a_patch]]&lt;br /&gt;
* [[Patch]]&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=How_to_apply_a_patch&amp;diff=9993</id>
		<title>How to apply a patch</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=How_to_apply_a_patch&amp;diff=9993"/>
		<updated>2008-10-10T17:17:20Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
This page explains how you can apply a patch file. Patch is a standard format, and there are many options for how to apply one. Pick the one that is easiest for you.&lt;br /&gt;
&lt;br /&gt;
Perhaps most critical is the usage of the -p flag, which tells patch about the relationship between the directory where the patch file is located and the files that will be patched.  See the references below for details and DO NOT assume anything.  &lt;br /&gt;
&lt;br /&gt;
==Apply a Patch in Windows using [http://gnuwin32.sourceforge.net/packages/patch.htm gnuwin32]==&lt;br /&gt;
&lt;br /&gt;
* Download and extract patch for windows from [http://gnuwin32.sourceforge.net/packages/patch.htm sourceforge] I placed the patch.exe binary in C:\bin&lt;br /&gt;
&lt;br /&gt;
* Download and extract Moodle somewhere. eg: C:\moodle&lt;br /&gt;
&lt;br /&gt;
* Download the patch file and place it in the same directory you put Moodle (C:\moodle\password-policy-17.diff)&lt;br /&gt;
&lt;br /&gt;
* Open the patch file with Wordpad, and click &#039;File&#039; &amp;gt;&amp;gt; &#039;Save as...&#039;, choose a different name for the file eg (&#039;mynewpatch.diff&#039;) and &amp;quot;Save as type&amp;quot; &amp;gt;&amp;gt; &#039;Text Document - MS-DOS Format&#039;&lt;br /&gt;
&lt;br /&gt;
* Open up a command text window, and type:&lt;br /&gt;
&lt;br /&gt;
    cd \moodle&lt;br /&gt;
    c:\bin\patch.exe --dry-run -p1 &amp;lt; mynewpatch.diff&lt;br /&gt;
&lt;br /&gt;
:The number after &amp;lt;tt&amp;gt;&#039;-p&#039;&amp;lt;/tt&amp;gt; option can vary depending on the patch file, as it depends on the way the patch file was generated. Have a look at the [http://www.rt.com/man/patch.1.html &#039;patch&#039; utility manual page ] to see how the &amp;lt;tt&amp;gt;&#039;-p&#039;&amp;lt;/tt&amp;gt; option works. You could also have a look at this [http://www.linuxtutorialblog.com/post/introduction-using-diff-and-patch-tutorial diff and patch tutorial].&lt;br /&gt;
* You should get an output similar to this (the names and quantity of patched files vary from patch to patch):&lt;br /&gt;
&lt;br /&gt;
    patching file admin/settings/security.php&lt;br /&gt;
    patching file lang/en_utf8/admin.php&lt;br /&gt;
    patching file lib/moodlelib.php&lt;br /&gt;
    patching file login/change_password.php&lt;br /&gt;
    patching file login/signup.php&lt;br /&gt;
    patching file user/edit.php&lt;br /&gt;
    Hunk #1 succeeded at 430 (offset 2 lines).&lt;br /&gt;
&lt;br /&gt;
:At this stage the patch &amp;lt;b&amp;gt;has not been applied&amp;lt;/b&amp;gt;. We just simulated the application (with the &amp;lt;tt&amp;gt;&#039;--dry-run&#039;&amp;lt;/tt&amp;gt; option), to see if we are going to find any problems with it. Before explaining how to actually apply the patch, we are going to talk about what could be wrong, and how to deal with it.&lt;br /&gt;
&lt;br /&gt;
===Potential problems and how to deal with them===&lt;br /&gt;
====Potential problems====&lt;br /&gt;
If everything goes well, the patch will apply cleanly and life should be good! But sometimes the patch will not apply 100% cleanly due to a version mismatch between the original files used to produce the patch file and your local files. In this case, the &#039;patch&#039; command will try to apply as many changes as it can, and will emit some diagnostics describing the problems it encounters. &lt;br /&gt;
&lt;br /&gt;
* If you get any &amp;lt;tt&amp;gt;&#039;Hunk #n succeeded...&#039;&amp;lt;/tt&amp;gt; messages, the patch would have been applied correctly although at different line numbers than the original file. If we had actually applied the patch, the &#039;patch&#039; command would have created an additional file for each of the files where the hunk was applied at a different offset, that would be named like the original file with the additional extension &amp;lt;tt&amp;gt;.orig&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* If you get any &amp;lt;tt&amp;gt;&#039;Hunk #n failed...&#039;&amp;lt;/tt&amp;gt; messages, the patch would have not applied correctly. In this case the &#039;patch&#039; command would have created two additional files for each of the files where the hunk was not applied correctly, called:&lt;br /&gt;
** &amp;lt;tt&amp;gt;original-file-name.orig&amp;lt;/tt&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; This would be the original file before the patch was applied, just like above.&lt;br /&gt;
** &amp;lt;tt&amp;gt;original-file-name.rej&amp;amp;nbsp;&amp;lt;/tt&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; This file would contain the hunks that could not be applied correctly, so you could inspect them.&lt;br /&gt;
&lt;br /&gt;
====Dealing with potential problems====&lt;br /&gt;
Dealing with the first problem (the offsetted hunks) is trivial: we just need to delete the .orig files once we actually apply the patch.&lt;br /&gt;
&lt;br /&gt;
In the second case (failed hunks), unless you know how to fix the failed hunks by hand, you &amp;lt;b&amp;gt;should not apply&amp;lt;/b&amp;gt; the patch, as that would corrupt your Moodle install. If you want to apply the patch and try to fix the failed hunks by hand, you should use the &amp;lt;tt&amp;gt;&#039;-b&#039;&amp;lt;/tt&amp;gt; option. That option automatically makes a backup of every file the patch applies to, with the &amp;lt;tt&amp;gt;.orig&amp;lt;/tt&amp;gt; extension. That would allow you go back to the original files state by simply overwritting the modified files with their &amp;lt;tt&amp;gt;.orig&amp;lt;/tt&amp;gt; backups.&lt;br /&gt;
&lt;br /&gt;
===Actually applying the patch===&lt;br /&gt;
Now that we know what could go wrong and how to deal with it, let&#039;s see how to apply the patch. We only need to remove the &amp;lt;tt&amp;gt;&#039;--dry-run&#039;&amp;lt;/tt&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
    cd \moodle&lt;br /&gt;
    c:\bin\patch.exe -p1 &amp;lt; mynewpatch.diff&lt;br /&gt;
&lt;br /&gt;
and optionally use the &amp;lt;tt&amp;gt;&#039;-b&#039;&amp;lt;/tt&amp;gt; option if we are going to try to fix the failed hunks by hand:&lt;br /&gt;
&lt;br /&gt;
    cd \moodle&lt;br /&gt;
    c:\bin\patch.exe -b -p1 &amp;lt; mynewpatch.diff&lt;br /&gt;
&lt;br /&gt;
==Apply a Patch in Linux using &amp;quot;patch&amp;quot;==&lt;br /&gt;
use something like:&lt;br /&gt;
patch -p1 &amp;lt; patchfile.diff&lt;br /&gt;
see [http://linux.about.com/od/commands/l/blcmdl1_patch.htm here] for more details on using Patch in Linux&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
&lt;br /&gt;
* [[Patch]]&lt;br /&gt;
* [[How_to_create_a_patch]]&lt;br /&gt;
* [http://drupal.org/node/32875 Drupal - using Cygwin in Windows to apply a patch]&lt;br /&gt;
* [http://drupal.org/node/60818 Drupal - how to apply a patch in Mac OS X]&lt;br /&gt;
* [http://moodle.org/mod/forum/discuss.php?d=61379#p286372 moodle post - using gnuwin32 to apply a patch]&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=Setting_up_Eclipse&amp;diff=4961</id>
		<title>Setting up Eclipse</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=Setting_up_Eclipse&amp;diff=4961"/>
		<updated>2008-04-15T22:40:22Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* SSH2 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.eclipse.org/ Eclipse] is an IDE originally designed for Java, but now with plugins for many languages including PHP. It has lots of very powerful features, and it is the editor that some Moodle developers like to use. Other (more) popular choices are vim and emacs.&lt;br /&gt;
&lt;br /&gt;
However, Eclipse is not the easiest program in the world to get started with, so I&#039;m going to take you through it step by step. These instructions assume Eclipse 3.2, the current version at the time of writing. It should not change much between releases.&lt;br /&gt;
&lt;br /&gt;
This article started off as a brain-dump by [[User:Tim Hunt|Tim Hunt]]. Since then, several other people have worked through it and made corrections, so the information here should be pretty accurate.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites==&lt;br /&gt;
&lt;br /&gt;
Eclipse is written in Java, so I recommend getting the latest Java runtime environment from http://java.com/ for maximum speed and reliability.&lt;br /&gt;
&lt;br /&gt;
Eclipse is quite big, so I recommend lots of memory in your computer. I have used it on Windows, MacOS X and Linux, in each case with 1GB of memory, and that is plenty.&lt;br /&gt;
&lt;br /&gt;
==Installing Eclipse==&lt;br /&gt;
&lt;br /&gt;
Go to http://www.eclipse.org/downloads/. Click on the link corresponding to your operating system where it says &#039;&#039;&#039;Eclipse Classic&#039;&#039;&#039;. Choose a Mirror, and wait for the ~100MB download.&lt;br /&gt;
&lt;br /&gt;
You will notice that what you have got is a zip file (unless your system automatically decompresses it for you).&lt;br /&gt;
&lt;br /&gt;
On Windows, unzip it into &#039;&#039;&#039;C:\Program Files&#039;&#039;&#039; (all the files go into an &#039;&#039;&#039;Eclipse&#039;&#039;&#039; folder there). Then look in the Eclipse folder and drag Eclipse.exe to the Start menu/Desktop/Quicklaunch bar to make a shortcut for starting it.&lt;br /&gt;
&lt;br /&gt;
On MacOS, unzip and copy the Eclipse folder into Applications. Go into the Eclipse folder and drag the Eclipse app to the Dock for ease of launching.&lt;br /&gt;
&lt;br /&gt;
On Linux, unzip somewhere suitable, and make an easy way to launch it.&lt;br /&gt;
&lt;br /&gt;
==The first time you run Eclipse==&lt;br /&gt;
&lt;br /&gt;
The first time you launch Eclipse it does a bit of setup stuff, for instance, it create a &#039;&#039;&#039;workspace&#039;&#039;&#039;. This is where it stores the things you are working on. The default location is sensible on all platforms, so use that. &lt;br /&gt;
&lt;br /&gt;
For some reason, every time you start Eclipse, it asks you which workspace you want to use. I have never seen the need to have more than one, so I recommend turning on the checkbox that says &amp;quot;Use this as the default and do not ask again&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Another thing that happens the first time you run Eclipse is that you arrive at a welcome screen. This has links to various bits of help, which you can read if you like, but you probably don&#039;t need to if you are following these instructions. So find the button on the welcome page that closes it and gets you to the main Eclipse screen.&lt;br /&gt;
&lt;br /&gt;
==Installing the necessary plugins==&lt;br /&gt;
&lt;br /&gt;
By default, Eclipse comes with the Java tools. For everything else you will need to install some plugins.&lt;br /&gt;
&lt;br /&gt;
If you are sitting behind a web proxy, from the &#039;&#039;&#039;Window&#039;&#039;&#039; menu choose &#039;&#039;&#039;Preferences ...&#039;&#039;&#039;. Choose &#039;&#039;&#039;Install/Update&#039;&#039;&#039; from the tree view on the left, and enter the proxy information in the boxes on the right. If you aren&#039;t behind a proxy, ignore this step.&lt;br /&gt;
&lt;br /&gt;
From the &#039;&#039;&#039;Help&#039;&#039;&#039; menu choose &#039;&#039;&#039;Software Updates -&amp;gt; Find and Install&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
On the first screen of the wizard, make sure that &amp;quot;Search for new features to install&amp;quot; is selected, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The next screen is a list of upgrade sites to check. You need to add one to the list, so click the &#039;&#039;&#039;New Remote Site ...&#039;&#039;&#039; Button.&lt;br /&gt;
&lt;br /&gt;
In the pop-up dialog, give the remote site a name like &#039;&#039;&#039;PHPeclipse Update Site&#039;&#039;&#039;; set the URL to http://phpeclipse.sourceforge.net/update/releases/; then click &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note, there is now also another PHP editor for Eclipse. The update URL ishttp://download.eclipse.org/tools/pdt/updates/. I am just trying it--[[User:Tim Hunt|Tim Hunt]] 11:39, 7 November 2007 (CST)&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Back in the wizard, turn on just two things in the box &amp;quot;Sites to include in search&amp;quot;:&lt;br /&gt;
* Your newly created &#039;&#039;&#039;Phpeclipse Update Site&#039;&#039;&#039;; and&lt;br /&gt;
* the one called &#039;&#039;&#039;Europa Discovery Site&#039;&#039;&#039; (or possibly &#039;&#039;&#039;Callisto Discovery Site&#039;&#039;&#039;.&lt;br /&gt;
Then click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
It goes off sees what updates are available at those sites. As it does so, it may occasionally pop up a dialog asking you to choose a mirror. Each time, select a sensible one.&lt;br /&gt;
&lt;br /&gt;
Eventually, you get to a new wizard for selecting and installing the updates you want. The ones you want (you may have to search the tree structure) are, &#039;&#039;&#039;PHPeclipse&#039;&#039;&#039; (from your newly created PHPEclipse Update Site) and all the &#039;&#039;&#039;Web Standard Tools (WST)&#039;&#039;&#039; (usually under Callisto Discovery Site --&amp;gt; Web and J2EE Development).&lt;br /&gt;
&lt;br /&gt;
Next, and very importantly, you must click the &#039;&#039;&#039;Select Required&#039;&#039;&#039; button which should resolve dependencies and remove the warning message you are probably worrying about. Then you can click the &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
Read and agree to all the license agreements. Then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Finish&#039;&#039;&#039;, and wait for the plugins to download.&lt;br /&gt;
&lt;br /&gt;
Once the downloads have finished, a warning will pop-up telling you that all the plugins you downloaded are not digitally signed. The Eclipse Foundation build digital signing of plugins into their architecture as a security measure, and then did not sign any of their own plugins! Anyway, click the &#039;&#039;&#039;Install All&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
Finally, a window will pop up asking you to restart Eclipse. Do so.&lt;br /&gt;
&lt;br /&gt;
==Setting the preferences for Moodle development==&lt;br /&gt;
&lt;br /&gt;
Now go to the &#039;&#039;&#039;Window&#039;&#039;&#039; menu, and choose &#039;&#039;&#039;Preferences ...&#039;&#039;&#039; (&#039;&#039;&#039;Eclipse&#039;&#039;&#039; menu on Mac OS X).&lt;br /&gt;
&lt;br /&gt;
The Eclipse preferences are immense, with a tree view on the left, which selects which screen to display on the right. Don&#039;t panic, we&#039;ll guide you through it.&lt;br /&gt;
&lt;br /&gt;
===General settings===&lt;br /&gt;
&lt;br /&gt;
If you have strong feelings about fonts (I would hate to edit code an anything except Andale Mono), choose &#039;&#039;&#039;General -&amp;gt; Appearance -&amp;gt; Colors and Fonts&#039;&#039;&#039; from the tree on the left. Then on the right look under &#039;&#039;&#039;Basic&#039;&#039;&#039; and change &#039;&#039;&#039;Text Font&#039;&#039;&#039;. All the other editor font settings will inherit from this, so this is probably the only one you have to change.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;General -&amp;gt; Content Types&#039;&#039;&#039;, select PHP Source File, and add &#039;&#039;&#039;*.html&#039;&#039;&#039; to the box at the bottom.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;General -&amp;gt; Editors -&amp;gt; File Associations&#039;&#039;&#039;, if it is not already there, add &#039;&#039;&#039;*.php&#039;&#039;&#039; to the top box. With &#039;&#039;&#039;*.php&#039;&#039;&#039; selected in the top box, make sure &#039;&#039;&#039;PHP Editor&#039;&#039;&#039; is set to default in the bottom box. With &#039;&#039;&#039;*.html&#039;&#039;&#039; selected in the top box, select &#039;&#039;&#039;PHP Editor&#039;&#039;&#039; in the bottom box and click the &#039;&#039;&#039;Default&#039;&#039;&#039; button to change it, because in Moodle, most HTML files actually contain PHP code.&lt;br /&gt;
&lt;br /&gt;
If you use a web proxy, enter the details under &#039;&#039;&#039;Internet -&amp;gt; Proxy Settings&#039;&#039;&#039;. (Yes, I know you have entered them somewhere else before. Now you have to enter them again here. I don&#039;t know why. You just do.)&lt;br /&gt;
&lt;br /&gt;
===PHP Settings===&lt;br /&gt;
&lt;br /&gt;
These are all hidden under the &#039;&#039;&#039;PHPeclipse Web Development&#039;&#039;&#039; bit of the tree.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; Browser Preview Defaults&#039;&#039;&#039;, turn off both checkboxes.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP&#039;&#039;&#039;, on the &#039;&#039;&#039;Appearance&#039;&#039;&#039; tab, set &#039;&#039;&#039;Displayed tab width&#039;&#039;&#039; to 4.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP&#039;&#039;&#039;, on the &#039;&#039;&#039;Appearance&#039;&#039;&#039; tab, check &#039;&#039;&#039;Show line numbers&#039;&#039;&#039; to display line numbers in the left margin (optional). NOTE.- When you are editing a PHP file, you could left-click in the left margin and tick the &#039;&#039;&#039;Show Line Numbers&#039;&#039;&#039; line in the contextual menu. However, this toggle only applies to plain text files, &#039;&#039;not&#039;&#039; to HTML or PHP files. The only place where you can toggle line numbers on/off for such files is in the PHP/Appearance menu.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP&#039;&#039;&#039;, on the &#039;&#039;&#039;Typing&#039;&#039;&#039; tab, turn off all the options except &#039;&#039;&#039;Pasting for correct indentation&#039;&#039;&#039;, &#039;&#039;&#039;Insert spaces for tab&#039;&#039;&#039; and &#039;&#039;&#039;Close PHPdocs and comments&#039;&#039;&#039; and &#039;&#039;&#039;Remove trailing spaces on editor save&#039;&#039;&#039;. It would be nice to turn on more of these options, but most of the rest don&#039;t work very well.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP -&amp;gt; Formatter&#039;&#039;&#039;, on the &#039;&#039;&#039;New Lines&#039;&#039;&#039; tab, turn on &#039;&#039;&#039;Clear all blank lines&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP -&amp;gt; Formatter&#039;&#039;&#039;, on the &#039;&#039;&#039;Style&#039;&#039;&#039; tab, turn off &#039;&#039;&#039;Indentation is represented by a tab&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP -&amp;gt; Templates&#039;&#039;&#039;, I like to define a new template to help with debugging:&lt;br /&gt;
;Name&lt;br /&gt;
:dump &lt;br /&gt;
;Description&lt;br /&gt;
:Dump a PHP variable&lt;br /&gt;
;Pattern&lt;br /&gt;
&amp;lt;pre&amp;gt;print_object(${word_selection}${cursor}); // DONOTCOMMIT&amp;lt;/pre&amp;gt;&lt;br /&gt;
You can do other useful things with templates too. Here are two more I use:&lt;br /&gt;
&amp;lt;pre&amp;gt;debugging(&amp;quot;&#039;${word_selection}${cursor}&#039;&amp;quot;); // DONOTCOMMIT&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;$$string[&#039;${word_selection}${cursor}&#039;] = &#039;.&#039;;&amp;lt;/pre&amp;gt;&lt;br /&gt;
That is, a simple debug message with a stack trace, and a new language string.&lt;br /&gt;
&lt;br /&gt;
There is a really stupid bug. Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; Project Defaults&#039;&#039;&#039;, you would like to add &amp;quot;.&amp;quot; to the &#039;&#039;&#039;Include Paths&#039;&#039;&#039;, but you can&#039;t using the GUI. You will have to edit one of the Eclipse config files by hand. So&lt;br /&gt;
# Note down the path to your Eclipse profile. On Windows it will be something like &#039;&#039;&#039;C:/Documents and settings/XXXX/workspace&#039;&#039;&#039;, and on Unixy systems something like &#039;&#039;&#039;~/workspace&#039;&#039;&#039;.&lt;br /&gt;
# Close Eclipse. &lt;br /&gt;
# Open the file &#039;&#039;&#039;net.sourceforge.phpeclipse.ui.prefs&#039;&#039;&#039; that is in the directory &#039;&#039;&#039;(your workspace)/.metadata/.plugins/org.eclipse.core.runtime/.settings&#039;&#039;&#039; in a text editor.&lt;br /&gt;
# Look for a line in the file that starts &#039;&#039;&#039;_php_include_paths=&#039;&#039;&#039; If it is not there, add it at the end.&lt;br /&gt;
# Change this line to say &#039;&#039;&#039;_php_include_paths=.&#039;&#039;&#039;&lt;br /&gt;
# Run Eclipse again.&lt;br /&gt;
&lt;br /&gt;
===SSH2===&lt;br /&gt;
Information about generating SSH2 keys for the purpose of connecting to cvs.moodle.org can be found here at https://docs.moodle.org/en/Development:SSH_key , but please finish reading this section before reading that material.&lt;br /&gt;
&lt;br /&gt;
The Eclipse installation has its own SSH client plugin so you do not have to use a separate ssh client in connection with your use of Eclipse (this is one reason you will be using extssh below,  instead of just ext,  however,  if you wish you may alter the configuration to use an external client but please post news of your success and configuration). See, http://www.jcraft.com/eclipse-cvsssh2/ , for additional information on this plugin.  &lt;br /&gt;
&lt;br /&gt;
Please note that Eclipse is fully equipped to generate ssh2 rsa and dsa keys as well as import keys.  You may encounter issues with passphrases that are too long (a bug reportedly fixed but which may still in fact be present) and some issues with using keypairs generated by other applications have been seen, so it may be best to generate a key pair with Eclipse. Additional details on how to do this will be added.&lt;br /&gt;
&lt;br /&gt;
Sourceforge, at http://sourceforge.net/docs/F02/ , provides instructions on how to create a SSH key for it&#039;s CVS (remember,  Moodle does not use sourceforge for its CVS now and you will need to generate keys for cvs.moodle.org, not sourceforge). This is mentioned by way of general explanation, not for the purposes of providing instructions on how to generate your keys for Eclipse. To make use of the public key, login to Moodle.org and add it via the Update My Developer Information tab under CVS Developers (http://moodle.org/cvs). Remember,  public keys provided to Moodle must be in the Openssh format.&lt;br /&gt;
&lt;br /&gt;
===CVS Settings===&lt;br /&gt;
&lt;br /&gt;
These are all hidden under the &#039;&#039;&#039;Team&#039;&#039;&#039; bit of the tree.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team -&amp;gt; CVS -&amp;gt; SSH2 Connection Method&#039;&#039;&#039;, you can set up a public/private key pair. If you do this, you won&#039;t have to keep typing your password when doing CVS operations. &lt;br /&gt;
&lt;br /&gt;
The rest of the ones in this section are personal preferences, but I recommend them because the default settings are very irritating.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team&#039;&#039;&#039;, set &#039;&#039;&#039;Perspectives&#039;&#039;&#039; to &#039;&#039;&#039;None&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team -&amp;gt; CVS -&amp;gt; Annotate&#039;&#039;&#039; set &#039;&#039;&#039;Use Quick Diff annotate mode for local file annotations&#039;&#039;&#039; to &#039;&#039;&#039;Yes&#039;&#039;&#039;, and &#039;&#039;&#039;Open perspective after a &#039;Show Annotations&#039; operation&#039;&#039;&#039; to &#039;&#039;&#039;No&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team -&amp;gt; CVS -&amp;gt; Label Decorations&#039;&#039;&#039;, switch to the &#039;&#039;&#039;Icon Decorations&#039;&#039;&#039; tab and turn on all the settings, and then on the &#039;&#039;&#039;Text Decorations&#039;&#039;&#039; tab change both &#039;&#039;&#039;File Decoration&#039;&#039;&#039; and &#039;&#039;&#039;Folder Decoration&#039;&#039;&#039; to be just &#039;&#039;&#039;{name}&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
===Web and XML settings===&lt;br /&gt;
&lt;br /&gt;
Foreach XXX in CSS, HTML, Javascript, XML:&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Web and XML -&amp;gt; XXX Files -&amp;gt;XXX Source&#039;&#039;&#039;, choose &#039;&#039;&#039;Indent using spaces&#039;&#039;&#039; and &#039;&#039;&#039;indentation size&#039;&#039;&#039; 4.&lt;br /&gt;
&lt;br /&gt;
==Checking out the Moodle code==&lt;br /&gt;
&lt;br /&gt;
From the &#039;&#039;&#039;File&#039;&#039;&#039; menu, choose &#039;&#039;&#039;New -&amp;gt; Project ...&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
In the wizard that pops up, choose &#039;&#039;&#039;CVS -&amp;gt; Projects from CVS&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;&#039;Create a new repository location&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Fill in&lt;br /&gt;
&amp;lt;div style=&amp;quot;float: right; border: 1px solid orange; padding: 0 1em;&amp;quot;&amp;gt;&lt;br /&gt;
For anonymous CVS access use&lt;br /&gt;
;Host&lt;br /&gt;
:XX.cvs.moodle.org&lt;br /&gt;
where XX.cvs.moodle.org is one of [[CVS_for_Administrators#CVS_Servers|these mirrors]]&lt;br /&gt;
;Repository path&lt;br /&gt;
:/cvsroot/moodle&lt;br /&gt;
;User&lt;br /&gt;
:anonymous&lt;br /&gt;
;Password&lt;br /&gt;
:(leave blank)&lt;br /&gt;
;Connection type&lt;br /&gt;
:pserver&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
;Host&lt;br /&gt;
:cvs.moodle.org&lt;br /&gt;
;Repository path&lt;br /&gt;
:/cvsroot/moodle&lt;br /&gt;
;User&lt;br /&gt;
:(your Moodle CVS username)&lt;br /&gt;
;Password&lt;br /&gt;
:(if you set up the SSH2 key thing in preferences, leave this blank, otherwise, type in your Moodle CVS password.)&lt;br /&gt;
;Connection type&lt;br /&gt;
:extssh&lt;br /&gt;
(CVS experts, if you are confused by that last one, know it is an Eclipse-specific thing.) Then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
On the next screen of the Wizard, choose &#039;&#039;&#039;Use an existing module&#039;&#039;&#039;. Wait a moment, then select &#039;&#039;&#039;moodle&#039;&#039;&#039; from the list. Click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
On the next screen, make sure the option &#039;&#039;&#039;Check out as a project configured using the New Project Wizard&#039;&#039;&#039; is selected, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Refresh Tags&#039;&#039;&#039;, then choose the branch you want. For now leave it set to &#039;&#039;&#039;HEAD&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now you  will find yourself back at the start of the &#039;&#039;&#039;New Project&#039;&#039;&#039; Wizard. This is because of the option you chose three paragraphs ago. This time you should select &#039;&#039;&#039;PHP -&amp;gt; PHP Project&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Make up a project name. &#039;&#039;&#039;moodle&#039;&#039;&#039; would be sensible.&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Finish&#039;&#039;&#039;, and wait while all the moodle files are checked out of CVS.&lt;br /&gt;
&lt;br /&gt;
Once it has finished, it will probably ask you if you want to switch to the PHP perspective. Answer &#039;&#039;&#039;Yes&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you also need another branch (1.6, 1.7, 1.8, ...) repeat all the other steps with a few changes:&lt;br /&gt;
* This time you can choose &#039;&#039;&#039;Use an existing repository location&#039;&#039;&#039; instead of typing all the sourceforge CVS details again.&lt;br /&gt;
* Select the appropriate branch. If you don&#039;t see the branch you want, see [https://docs.moodle.org/en/Development:Setting_up_Eclipse#Resetting_the_branch_information this Troubleshooting tip].&lt;br /&gt;
* Use a different project name (e.g. moodle16, moodle17, etc.).&lt;br /&gt;
&lt;br /&gt;
==Let your development web server know where your files are==&lt;br /&gt;
&lt;br /&gt;
Either by editing you web server&#039;s config files, or using a symbolic link. Make sure your webserver can see your new working set of files at a sensible URL, so you can test the code you are working on.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Quick tour of some cool features, and remaining configuration changes==&lt;br /&gt;
&lt;br /&gt;
I find the default workbench setup is pretty good. Here is a quick guide to some of the bits.&lt;br /&gt;
&lt;br /&gt;
===Navigator===&lt;br /&gt;
&lt;br /&gt;
To the left is the &#039;&#039;&#039;Navigator&#039;&#039;&#039;. This is a tree view of all your files. If you double-click on a file, it opens in the editor in the middle. Try opening &#039;&#039;&#039;course/lib.php&#039;&#039;&#039; now. You will notice that it comes up nicely syntax-hightlighted.&lt;br /&gt;
&lt;br /&gt;
===Error highlighting===&lt;br /&gt;
&lt;br /&gt;
In the middle of the file, just type any old text, for example &amp;quot;I like Eclipse&amp;quot;. Obviously, this is not valid PHP syntax, and Eclipse will notice this, and put a red underline under it. Also, by the scrollbar is a ruler with a red mark in it to show the error.&lt;br /&gt;
&lt;br /&gt;
You will see some yellow marks lower down the ruler. There are warnings. Click on one, and you will be taken to where that warning is in the file. Hover your mouse over the warning, and you will get a tooltip explaining what the problem might be.&lt;br /&gt;
&lt;br /&gt;
Save the edited file. (Don&#039;t worry that it is broken, we&#039;ll clean up the mess later.) Notice that a red error marker is added to the file in the navigator, so you can see that there is a problem. Also, error markers are added to the course folder, and the whole project, so you could see there was an error even if the navigator tree was collapsed.&lt;br /&gt;
&lt;br /&gt;
You will probably find lots of warnings that the config.php file can&#039;t be found. In the navigator, find the file &#039;&#039;&#039;config-dist.php&#039;&#039;&#039;. Do &#039;&#039;&#039;Copy&#039;&#039;&#039; then &#039;&#039;&#039;Paste&#039;&#039;&#039; and choose to call the new file &#039;&#039;&#039;config.php&#039;&#039;&#039;. Edit this new config.php as normal. You should fine that most of the include file warnings have gone now.&lt;br /&gt;
&lt;br /&gt;
Notice also that there is another marker on each file icon. A little yellow cylinder on most files, but a white-on-brown star on the one you have edited. This is telling you the CVS status of each file. The brown stars are changes you have made but not checked in yet.&lt;br /&gt;
&lt;br /&gt;
===Outline===&lt;br /&gt;
&lt;br /&gt;
Over to the right is the Outline view. This shows a list of functions and classes defined in this file. By default, they are listed in the same order as in the file, but if you click on the &#039;&#039;&#039;az&#039;&#039;&#039; toolbar button, they are sorted into alphabetical order.&lt;br /&gt;
&lt;br /&gt;
Click on the function name &#039;&#039;&#039;add_course_module&#039;&#039;&#039; in the Outline. You will see that the editor scrolls to the definition of that function.&lt;br /&gt;
&lt;br /&gt;
===Code navigation===&lt;br /&gt;
&lt;br /&gt;
In that function, hover the mouse pointer over the function name &#039;&#039;&#039;insert_record&#039;&#039;&#039;. After a while, the documentation for that function will appear in a big tooltip.&lt;br /&gt;
&lt;br /&gt;
Hold down CTRL, move the mouse pointer over the function name &#039;&#039;&#039;insert_record&#039;&#039;&#039;, then click. Eclipse should load &#039;&#039;&#039;dmllib.php&#039;&#039;&#039;, and scroll you to where this function is defined.&lt;br /&gt;
&lt;br /&gt;
In the main Eclipse toolbar, there are forward and back arrows like in a web browser. Click back now to get back to &#039;&#039;&#039;course/lib.php&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
===Open resource===&lt;br /&gt;
&lt;br /&gt;
From the &#039;&#039;&#039;Navigate&#039;&#039;&#039; menu, choose &#039;&#039;&#039;Open Resource...&#039;&#039;&#039;. In the dialog that pops up, start typing a filename for instance type &#039;&#039;&#039;moodlel&#039;&#039;&#039;. In the box in the middle of the dialog, you will see it list all the files in the project whose names start that way. At the bottom is a box which lists the different folders that contain a file with that name. This can be a very quick way of opening files with fairly unique names like moodlelib.php, without having to click through the levels of the navigator tree. Of course, it is not so useful for an index.php file! Click OK now to open moodlelib.php. (It would actually work if you just did CTRL + Shift + R, moodlel, Enter.)&lt;br /&gt;
&lt;br /&gt;
===Multi-file search===&lt;br /&gt;
&lt;br /&gt;
Scroll down moodlelib a little bit, and double click on the name of the constant &#039;&#039;&#039;MOODLE_INTERNAL&#039;&#039;&#039; where it is defined, so that the text is selected. Then, from the &#039;&#039;&#039;Search&#039;&#039;&#039; menu, choose &#039;&#039;&#039;Search...&#039;&#039;&#039;. Notice that the &#039;&#039;&#039;Containing text&#039;&#039;&#039; box has already been filled in for you with the text you just selected. Of course you can just type text into this box without selecting it first. Notice that you can do regular expression searches, but leave that turned off for now. In the &#039;&#039;&#039;File name patterns&#039;&#039;&#039; box type &#039;&#039;&#039;*.css, *.html, *.inc, *.js, *.php, *.xml&#039;&#039;&#039;. (This is the most useful general setting for working on moodle. Eclipse will remember this setting, so you only have to enter it once.) Click &#039;&#039;&#039;Search&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The search results will appear in a new view underneath the editor. That view has a toolbar with yellow up and down arrows. Click the down arrow a few times and it will take you to the first few matches in the code, opening the relevant files as necessary.&lt;br /&gt;
&lt;br /&gt;
===Synchronize view===&lt;br /&gt;
&lt;br /&gt;
I think this is my favorite feature. From the &#039;&#039;&#039;Window&#039;&#039;&#039; menu, select &#039;&#039;&#039;Show View -&amp;gt; Other...&#039;&#039;&#039;. In the dialog that pops up, select &#039;&#039;&#039;Team -&amp;gt; Synchronize&#039;&#039;&#039;, then click &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
This opens the Synchronize view below the editor. The view has a toolbar. Click on the first toolbar button, which pops up the Synchronize wizard.&lt;br /&gt;
&lt;br /&gt;
On the first screen, there will probably only be one option: &#039;&#039;&#039;CVS&#039;&#039;&#039;. Make sure that is selected, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Scope&#039;&#039;&#039;, choose &#039;&#039;&#039;Workspace&#039;&#039;&#039;, then click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Wait while it talks to the CVS server. After a while, you will see that the Synchronize view lists course/lib.php, and something called &#039;&#039;&#039;.project.... That is, it is listing just the files you have edited, but not checked in yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;.project&#039;&#039;&#039; is something that belongs to Eclipse that we don&#039;t care about. So select it and bring up the context menu, and choose &#039;&#039;&#039;Add to .cvsignore...&#039;&#039;&#039;. In the dialog that pops up, choose the top option, then click &#039;&#039;&#039;OK&#039;&#039;&#039;. Then you will find the Synchronize view shows you a &#039;&#039;&#039;.cvsignore&#039;&#039;&#039; file that you aren&#039;t interested in, so add that to .cvsignore too!&lt;br /&gt;
&lt;br /&gt;
If you double-click on &#039;&#039;&#039;course/lib.php&#039;&#039;&#039; here, you will see that it opens the compare editor, which is a nice graphical display of the changes in this file.&lt;br /&gt;
&lt;br /&gt;
If you select a file or files here, then bring up the context menu, you will see the option to &#039;&#039;&#039;Commit...&#039;&#039;&#039; the changes. (But don&#039;t do that now!). This is the easiest way to commit things in Eclipse.&lt;br /&gt;
&lt;br /&gt;
However, our changes were rubbish, so we want to undo them. So open the context menu again, and choose &#039;&#039;&#039;Override and Update&#039;&#039;&#039;. This checks a clean copy of the file out of CVS, removing our changes.&lt;br /&gt;
&lt;br /&gt;
Note that the easiest way to do an ordinary CVS Update is to select the top-level project-folder in the Navigator view on the left, open the context menu, and choose &#039;&#039;&#039;Team -&amp;gt; Update&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
That&#039;s all the really important features. I sure you can learn everything else on your own. An you could always read the built in help!&lt;br /&gt;
&lt;br /&gt;
===Creating a patch===&lt;br /&gt;
&lt;br /&gt;
In the synchronise view, right click on an item (file or folder) and choose &#039;&#039;&#039;Create Patch...&#039;&#039;&#039;. Or in the navigator, right click on an item and choose &#039;&#039;&#039;Team -&amp;gt; Create Patch...&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
This brings up a two-page wizard. On the first page you can select where you want the patch made. For small patches it can be useful to create them on the clipboard, but normally you will want to save them in a file.&lt;br /&gt;
&lt;br /&gt;
On the second page, you can set some options, but normally you don&#039;t need to change the defaults which are &#039;&#039;&#039;Unified&#039;&#039;&#039; diff format, and Patch root set to &#039;&#039;&#039;Workspace&#039;&#039;&#039;. Well, sometimes it is helpful to change the second one to &#039;&#039;&#039;Project&#039;&#039;&#039; but it is not important.&lt;br /&gt;
&lt;br /&gt;
There is a corresponding apply patch wizard that you can use to apply a patch to a project.&lt;br /&gt;
&lt;br /&gt;
===Switching to another branch or version===&lt;br /&gt;
&lt;br /&gt;
Suppose you have been using a check-out of HEAD from CVS, and then as the 1.9 release approaches, the MOODLE_19_STABLE branch is created, and you want to start following that instead.&lt;br /&gt;
# Right click on the moodle project in the navigator view, and select &#039;&#039;&#039;Team -&amp;gt; Switch to Another Branch or Version ...&#039;&#039;&#039;.&lt;br /&gt;
# choose the second radio button: &#039;&#039;&#039;Select the tag from the following list&#039;&#039;&#039;.&lt;br /&gt;
# If the branch you want is not in the &#039;&#039;&#039;Matching tags&#039;&#039;&#039; box, see [[Setting_up_Eclipse#Resetting the branch information|Resetting the branch information]] below.&lt;br /&gt;
# Select the branch you want and click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
&lt;br /&gt;
Some tips on how to solve common problems that may crop up.&lt;br /&gt;
&lt;br /&gt;
===Resetting the branch information===&lt;br /&gt;
&lt;br /&gt;
Every now and then, Eclipse may lose information on the branch tags it knows about. Hitting refresh tags may fix it, but if not, try the following:&lt;br /&gt;
&lt;br /&gt;
#Bring up the tag dialogue (example using &amp;quot;Team / Switch to Another Branch or Version&amp;quot;).&lt;br /&gt;
#Click on Configure tags ... (not Refresh tags).&lt;br /&gt;
#Select config-dist.php in the top left box (if this is a Moodle checkout).&lt;br /&gt;
#Click Add Checked tags.&lt;br /&gt;
#Click OK.&lt;br /&gt;
#Then you will have all tags.&lt;br /&gt;
&lt;br /&gt;
(thanks to Tim Hunt)&lt;br /&gt;
&lt;br /&gt;
===Error loading php files after Ubuntu 7.04 Install===&lt;br /&gt;
&lt;br /&gt;
A java issue with Ubuntu 7.04 may cause an error when you attempt to load php pages. Refer to:&lt;br /&gt;
http://www.plog4u.org/index.php/Using_PHPEclipse_:_Installation_:_Installing_PHPEclipse for details about how to fix this in Ubuntu 7.04.&lt;br /&gt;
&lt;br /&gt;
After upgrading from Ubuntu 7.04 to 7.10, I had to go in and re-edit the /etc/eclipse/java_home file in order to get the CVS functions to work and be able to open PHP files. When I tried to do a CVS update I initially received an error about org.eclipse.team.internal.ccvs.ui.wizards.CheckoutWizard). Everything seemed to work again after reapplying the fix for the aforementioned 7.04 java issue.&lt;br /&gt;
&lt;br /&gt;
==Related Links==&lt;br /&gt;
&lt;br /&gt;
There is an excellent series of articles published by IBM on using Eclipse for Drupal developement here : [http://www-128.ibm.com/developerworks/ibm/osource/index.html Using open source software to design, develop, and deploy a collaborative Web site Tools and techniques for getting relatively complicated Web sites up and running quickly].&lt;br /&gt;
&lt;br /&gt;
[[Category:Setting up Eclipse]]&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8418</id>
		<title>SSH key</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8418"/>
		<updated>2008-04-15T22:35:19Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* Unix/Linux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==What is a SSH key?==&lt;br /&gt;
&lt;br /&gt;
SSH keys are used for secure connections across a network.  They come in pairs, so you have a public key and a private key.&lt;br /&gt;
&lt;br /&gt;
The standard ssh2 file format (see&lt;br /&gt;
http://www.openssh.org/txt/draft-ietf-secsh-publickeyfile-02.txt)&lt;br /&gt;
looks like this:&lt;br /&gt;
&lt;br /&gt;
 ---- BEGIN SSH2 PUBLIC KEY ----&lt;br /&gt;
 Comment: &amp;quot;jtbell@Jon-Bells-Computer&amp;quot;&lt;br /&gt;
 AAAAB3NzaC1kc3MAAACBAPNgmidbM2rhYjUXunpnlXjHWfV+vc8/5YKrn8Y5P0Y6KwmG2G&lt;br /&gt;
 GMgNBon3LX3iJlBhtuU3FCBj3G1Kdt5vUhQHhUmHVrOasi47vawTrv7ZJCfiaSGwRsiBHt&lt;br /&gt;
 Jta5CAp7t0EnzX2q6BvPbFBBHNLyy6uNVpL2jOR06Pkx/vaqyScvAAAAFQDHvwmjWYwK9g&lt;br /&gt;
 K6Sp+pSvI7bwEUtwAAAIANMJDotMpfj89N+7+FJylSS+uFEQSS61PxENl/Mcj1jUREjJg2&lt;br /&gt;
 eNsJdAB9Ev99hWYS+7lFRtTJ2eh4Y9gpGe7BX3e2YGHOqp8cWCVCIKaMzwk9To+xnfThWq&lt;br /&gt;
 IfHT8I6CJxp/5ez02m6F2k/5iukvOwbGms6EAZK1DTBhDOHjEQwQAAAIAlz2/qBWkaMP+s&lt;br /&gt;
 W8FLmGKM+cCw5+asOaJGTwrFVuwJkDMvdEWxmG92A2dxuUske0d/AkN6zJp7HD0wlfesRM&lt;br /&gt;
 3+c+Res5qun9lFcdM4i03VoV5mXd+T7laS8yku6vZgvZZFnPvr2LOUnc7XThGFwMaQpFEW&lt;br /&gt;
 U8cvQbttO6QrT2CD2w==&lt;br /&gt;
 ---- END SSH2 PUBLIC KEY ----&lt;br /&gt;
&lt;br /&gt;
However, Moodle uses OpenSSH on its server and this key will not work with the OpenSSH server in this format; OpenSSH requires the key to be in OpenSSH format. Here is an example of a DSA public key in OpenSSH format (usually they are all in one line):&lt;br /&gt;
&lt;br /&gt;
 ssh-dss AAAAB3NzaC1kc3MAAACBAJ3hB5SAF6mBXPlZlRoJEZi0KSIN+NU2iGiaXZXi9CDrgVxTp6/&lt;br /&gt;
 sc56UcYCp4qjfrZ2G3+6PWbxYso4P4YyUC+61RU5KPy4EcTJske3O+aNvec/20cW7PT3TvH1+sxwGry&lt;br /&gt;
 mD50kTiXDgo5nXdqFvibgM61WW2DGTKlEUsZys0njRAAAAFQDs7ukaTGJlZdeznwFUAttTH9LrwwAAA&lt;br /&gt;
 IAMm4sLCdvvBx9WPkvWDX0OIXSteCYckiQxesOfPvz26FfYxuTG/2dljDlalC+kYG05C1NEcmZWSNES&lt;br /&gt;
 GBGfccSYSfI3Y5ahSVUhOC2LMO3JNjVyYUnOM/iyhzrnRfQoWO9GFMaugq0jBMlhZA4UO26yJqJ+BtX&lt;br /&gt;
 IyItaEEJdc/ghIwAAAIBFeCZynstlbBjP648+mDKIvzNSS+JYr5klGxS3q8A56NPcYhDMxGn7h1DKbb&lt;br /&gt;
 2AV4pO6y+6hDrWo3UT4dLVuzK01trwp PYp6JXTSZZ12ZaXNPz7sX9/z6pzMqhX4UEfjVsLcuF+ZS6a&lt;br /&gt;
 QCPO0ZZEa1z+EEIZSD/ykLQsDwPxGjPBqw== someone@somewhere.com&lt;br /&gt;
&lt;br /&gt;
In addition to OpenSSH and Standard SSH formats there are a variety of proprietary formats as well as SSH1 and SSH2 differences to account for, which can make this confusing. &lt;br /&gt;
&lt;br /&gt;
In the example above you will note that the key starts with &amp;quot;ssh-dss&amp;quot;. This is because this key was generated using DSA as opposed to RSA. A number of vendors in the SSH arena have argued, as per the PuTTY documentation that can be found at http://the.earth.li/~sgtatham/putty/0.55/htmldoc/Chapter8.html#S8.2.10 that users should employ RSA encryption because&lt;br /&gt;
&lt;br /&gt;
 DSA has an intrinsic weakness which makes it very easy to create a signature&lt;br /&gt;
 which contains enough information to give away the private key! This would &lt;br /&gt;
 allow an attacker to pretend to be you for any number of future sessions. &lt;br /&gt;
&lt;br /&gt;
An SSH2 public key in OpenSSH format will start with &amp;quot;ssh-rsa&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The idea behind all of this is that once you have keys on the remote server and your local host,  access will be simpler since the server will only grant access to someone who has the matching private key.&lt;br /&gt;
&lt;br /&gt;
==Why do I need a SSH key?==&lt;br /&gt;
&lt;br /&gt;
Our CVS server uses OpenSSH, so if are a Moodle developer and you want to make your logins easier (by avoiding typing in your password all the time) then you will need to submit public key in Openssh format via the &amp;quot;Update my developer information&amp;quot; tab at http://moodle.org/cvs.&lt;br /&gt;
&lt;br /&gt;
==How do I create a SSH key pair?==&lt;br /&gt;
&lt;br /&gt;
===Platform Independent===&lt;br /&gt;
&lt;br /&gt;
Visit http://www.sshkeygen.com and simply follow the directions there.&lt;br /&gt;
&lt;br /&gt;
===Eclipse===&lt;br /&gt;
&lt;br /&gt;
If you plan to use Eclipse for development, please refer to the Eclipse document https://docs.moodle.org/en/Eclipse as Eclipse now has a plugin that allows you to manage all ssh key matters from within Eclipse.&lt;br /&gt;
&lt;br /&gt;
===Unix/Linux===&lt;br /&gt;
&lt;br /&gt;
You can use ssh-keygen at your system prompt.  Please consult the man page on your system for the options available to you.&lt;br /&gt;
&lt;br /&gt;
# Run:  &#039;&#039;&#039;ssh-keygen -t (rsa or dsa)&#039;&#039;&#039;. This will not include a passphrase. *&lt;br /&gt;
# Use of rsa or dsa above will result in rsa or dsa replacing each XXX below.&lt;br /&gt;
# Look in your ~/.ssh directory (or wherever you saved the output).  You&#039;ll find &#039;&#039;&#039;id_XXX&#039;&#039;&#039; (private) and &#039;&#039;&#039;id_XXX.pub&#039;&#039;&#039; (public).&lt;br /&gt;
# Cut and paste the contents of &#039;&#039;&#039;id_XXX.pub&#039;&#039;&#039; into your developer profile on http://moodle.org/cvs&lt;br /&gt;
# Put the private key wherever you will be calling CVS from (in your .ssh directory, for example).  Make sure it&#039;s secure!&lt;br /&gt;
&lt;br /&gt;
* This section initially recommended using &#039;&#039;ssh-keygen -d&#039;&#039; but it is unclear what the source of this -d option might be.&lt;br /&gt;
&lt;br /&gt;
===Windows===&lt;br /&gt;
&lt;br /&gt;
===Mac OS X===&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8417</id>
		<title>SSH key</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8417"/>
		<updated>2008-04-15T22:28:28Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* How do I create a SSH key pair? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==What is a SSH key?==&lt;br /&gt;
&lt;br /&gt;
SSH keys are used for secure connections across a network.  They come in pairs, so you have a public key and a private key.&lt;br /&gt;
&lt;br /&gt;
The standard ssh2 file format (see&lt;br /&gt;
http://www.openssh.org/txt/draft-ietf-secsh-publickeyfile-02.txt)&lt;br /&gt;
looks like this:&lt;br /&gt;
&lt;br /&gt;
 ---- BEGIN SSH2 PUBLIC KEY ----&lt;br /&gt;
 Comment: &amp;quot;jtbell@Jon-Bells-Computer&amp;quot;&lt;br /&gt;
 AAAAB3NzaC1kc3MAAACBAPNgmidbM2rhYjUXunpnlXjHWfV+vc8/5YKrn8Y5P0Y6KwmG2G&lt;br /&gt;
 GMgNBon3LX3iJlBhtuU3FCBj3G1Kdt5vUhQHhUmHVrOasi47vawTrv7ZJCfiaSGwRsiBHt&lt;br /&gt;
 Jta5CAp7t0EnzX2q6BvPbFBBHNLyy6uNVpL2jOR06Pkx/vaqyScvAAAAFQDHvwmjWYwK9g&lt;br /&gt;
 K6Sp+pSvI7bwEUtwAAAIANMJDotMpfj89N+7+FJylSS+uFEQSS61PxENl/Mcj1jUREjJg2&lt;br /&gt;
 eNsJdAB9Ev99hWYS+7lFRtTJ2eh4Y9gpGe7BX3e2YGHOqp8cWCVCIKaMzwk9To+xnfThWq&lt;br /&gt;
 IfHT8I6CJxp/5ez02m6F2k/5iukvOwbGms6EAZK1DTBhDOHjEQwQAAAIAlz2/qBWkaMP+s&lt;br /&gt;
 W8FLmGKM+cCw5+asOaJGTwrFVuwJkDMvdEWxmG92A2dxuUske0d/AkN6zJp7HD0wlfesRM&lt;br /&gt;
 3+c+Res5qun9lFcdM4i03VoV5mXd+T7laS8yku6vZgvZZFnPvr2LOUnc7XThGFwMaQpFEW&lt;br /&gt;
 U8cvQbttO6QrT2CD2w==&lt;br /&gt;
 ---- END SSH2 PUBLIC KEY ----&lt;br /&gt;
&lt;br /&gt;
However, Moodle uses OpenSSH on its server and this key will not work with the OpenSSH server in this format; OpenSSH requires the key to be in OpenSSH format. Here is an example of a DSA public key in OpenSSH format (usually they are all in one line):&lt;br /&gt;
&lt;br /&gt;
 ssh-dss AAAAB3NzaC1kc3MAAACBAJ3hB5SAF6mBXPlZlRoJEZi0KSIN+NU2iGiaXZXi9CDrgVxTp6/&lt;br /&gt;
 sc56UcYCp4qjfrZ2G3+6PWbxYso4P4YyUC+61RU5KPy4EcTJske3O+aNvec/20cW7PT3TvH1+sxwGry&lt;br /&gt;
 mD50kTiXDgo5nXdqFvibgM61WW2DGTKlEUsZys0njRAAAAFQDs7ukaTGJlZdeznwFUAttTH9LrwwAAA&lt;br /&gt;
 IAMm4sLCdvvBx9WPkvWDX0OIXSteCYckiQxesOfPvz26FfYxuTG/2dljDlalC+kYG05C1NEcmZWSNES&lt;br /&gt;
 GBGfccSYSfI3Y5ahSVUhOC2LMO3JNjVyYUnOM/iyhzrnRfQoWO9GFMaugq0jBMlhZA4UO26yJqJ+BtX&lt;br /&gt;
 IyItaEEJdc/ghIwAAAIBFeCZynstlbBjP648+mDKIvzNSS+JYr5klGxS3q8A56NPcYhDMxGn7h1DKbb&lt;br /&gt;
 2AV4pO6y+6hDrWo3UT4dLVuzK01trwp PYp6JXTSZZ12ZaXNPz7sX9/z6pzMqhX4UEfjVsLcuF+ZS6a&lt;br /&gt;
 QCPO0ZZEa1z+EEIZSD/ykLQsDwPxGjPBqw== someone@somewhere.com&lt;br /&gt;
&lt;br /&gt;
In addition to OpenSSH and Standard SSH formats there are a variety of proprietary formats as well as SSH1 and SSH2 differences to account for, which can make this confusing. &lt;br /&gt;
&lt;br /&gt;
In the example above you will note that the key starts with &amp;quot;ssh-dss&amp;quot;. This is because this key was generated using DSA as opposed to RSA. A number of vendors in the SSH arena have argued, as per the PuTTY documentation that can be found at http://the.earth.li/~sgtatham/putty/0.55/htmldoc/Chapter8.html#S8.2.10 that users should employ RSA encryption because&lt;br /&gt;
&lt;br /&gt;
 DSA has an intrinsic weakness which makes it very easy to create a signature&lt;br /&gt;
 which contains enough information to give away the private key! This would &lt;br /&gt;
 allow an attacker to pretend to be you for any number of future sessions. &lt;br /&gt;
&lt;br /&gt;
An SSH2 public key in OpenSSH format will start with &amp;quot;ssh-rsa&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The idea behind all of this is that once you have keys on the remote server and your local host,  access will be simpler since the server will only grant access to someone who has the matching private key.&lt;br /&gt;
&lt;br /&gt;
==Why do I need a SSH key?==&lt;br /&gt;
&lt;br /&gt;
Our CVS server uses OpenSSH, so if are a Moodle developer and you want to make your logins easier (by avoiding typing in your password all the time) then you will need to submit public key in Openssh format via the &amp;quot;Update my developer information&amp;quot; tab at http://moodle.org/cvs.&lt;br /&gt;
&lt;br /&gt;
==How do I create a SSH key pair?==&lt;br /&gt;
&lt;br /&gt;
===Platform Independent===&lt;br /&gt;
&lt;br /&gt;
Visit http://www.sshkeygen.com and simply follow the directions there.&lt;br /&gt;
&lt;br /&gt;
===Eclipse===&lt;br /&gt;
&lt;br /&gt;
If you plan to use Eclipse for development, please refer to the Eclipse document https://docs.moodle.org/en/Eclipse as Eclipse now has a plugin that allows you to manage all ssh key matters from within Eclipse.&lt;br /&gt;
&lt;br /&gt;
===Unix/Linux===&lt;br /&gt;
&lt;br /&gt;
# Run:  &#039;&#039;&#039;ssh-keygen -t (rsa or dsa)&#039;&#039;&#039;. This will not include a passphrase. *&lt;br /&gt;
# Look in your ~/.ssh directory (or wherever you saved the output).  You&#039;ll find &#039;&#039;&#039;id_dsa&#039;&#039;&#039; (private) and &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; (public).&lt;br /&gt;
# Cut and paste the contents of &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; into your developer profile on http://moodle.org/cvs&lt;br /&gt;
# Put the private key wherever you will be calling CVS from (in your .ssh directory, for example).  Make sure it&#039;s secure!&lt;br /&gt;
&lt;br /&gt;
* This section initially indicates ssh-keygen -d but it is unclear what the source of this -d option might be.&lt;br /&gt;
&lt;br /&gt;
===Windows===&lt;br /&gt;
&lt;br /&gt;
===Mac OS X===&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8416</id>
		<title>SSH key</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8416"/>
		<updated>2008-04-15T22:10:23Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* Unix/Linux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==What is a SSH key?==&lt;br /&gt;
&lt;br /&gt;
SSH keys are used for secure connections across a network.  They come in pairs, so you have a public key and a private key.&lt;br /&gt;
&lt;br /&gt;
The standard ssh2 file format (see&lt;br /&gt;
http://www.openssh.org/txt/draft-ietf-secsh-publickeyfile-02.txt)&lt;br /&gt;
looks like this:&lt;br /&gt;
&lt;br /&gt;
 ---- BEGIN SSH2 PUBLIC KEY ----&lt;br /&gt;
 Comment: &amp;quot;jtbell@Jon-Bells-Computer&amp;quot;&lt;br /&gt;
 AAAAB3NzaC1kc3MAAACBAPNgmidbM2rhYjUXunpnlXjHWfV+vc8/5YKrn8Y5P0Y6KwmG2G&lt;br /&gt;
 GMgNBon3LX3iJlBhtuU3FCBj3G1Kdt5vUhQHhUmHVrOasi47vawTrv7ZJCfiaSGwRsiBHt&lt;br /&gt;
 Jta5CAp7t0EnzX2q6BvPbFBBHNLyy6uNVpL2jOR06Pkx/vaqyScvAAAAFQDHvwmjWYwK9g&lt;br /&gt;
 K6Sp+pSvI7bwEUtwAAAIANMJDotMpfj89N+7+FJylSS+uFEQSS61PxENl/Mcj1jUREjJg2&lt;br /&gt;
 eNsJdAB9Ev99hWYS+7lFRtTJ2eh4Y9gpGe7BX3e2YGHOqp8cWCVCIKaMzwk9To+xnfThWq&lt;br /&gt;
 IfHT8I6CJxp/5ez02m6F2k/5iukvOwbGms6EAZK1DTBhDOHjEQwQAAAIAlz2/qBWkaMP+s&lt;br /&gt;
 W8FLmGKM+cCw5+asOaJGTwrFVuwJkDMvdEWxmG92A2dxuUske0d/AkN6zJp7HD0wlfesRM&lt;br /&gt;
 3+c+Res5qun9lFcdM4i03VoV5mXd+T7laS8yku6vZgvZZFnPvr2LOUnc7XThGFwMaQpFEW&lt;br /&gt;
 U8cvQbttO6QrT2CD2w==&lt;br /&gt;
 ---- END SSH2 PUBLIC KEY ----&lt;br /&gt;
&lt;br /&gt;
However, Moodle uses OpenSSH on its server and this key will not work with the OpenSSH server in this format; OpenSSH requires the key to be in OpenSSH format. Here is an example of a DSA public key in OpenSSH format (usually they are all in one line):&lt;br /&gt;
&lt;br /&gt;
 ssh-dss AAAAB3NzaC1kc3MAAACBAJ3hB5SAF6mBXPlZlRoJEZi0KSIN+NU2iGiaXZXi9CDrgVxTp6/&lt;br /&gt;
 sc56UcYCp4qjfrZ2G3+6PWbxYso4P4YyUC+61RU5KPy4EcTJske3O+aNvec/20cW7PT3TvH1+sxwGry&lt;br /&gt;
 mD50kTiXDgo5nXdqFvibgM61WW2DGTKlEUsZys0njRAAAAFQDs7ukaTGJlZdeznwFUAttTH9LrwwAAA&lt;br /&gt;
 IAMm4sLCdvvBx9WPkvWDX0OIXSteCYckiQxesOfPvz26FfYxuTG/2dljDlalC+kYG05C1NEcmZWSNES&lt;br /&gt;
 GBGfccSYSfI3Y5ahSVUhOC2LMO3JNjVyYUnOM/iyhzrnRfQoWO9GFMaugq0jBMlhZA4UO26yJqJ+BtX&lt;br /&gt;
 IyItaEEJdc/ghIwAAAIBFeCZynstlbBjP648+mDKIvzNSS+JYr5klGxS3q8A56NPcYhDMxGn7h1DKbb&lt;br /&gt;
 2AV4pO6y+6hDrWo3UT4dLVuzK01trwp PYp6JXTSZZ12ZaXNPz7sX9/z6pzMqhX4UEfjVsLcuF+ZS6a&lt;br /&gt;
 QCPO0ZZEa1z+EEIZSD/ykLQsDwPxGjPBqw== someone@somewhere.com&lt;br /&gt;
&lt;br /&gt;
In addition to OpenSSH and Standard SSH formats there are a variety of proprietary formats as well as SSH1 and SSH2 differences to account for, which can make this confusing. &lt;br /&gt;
&lt;br /&gt;
In the example above you will note that the key starts with &amp;quot;ssh-dss&amp;quot;. This is because this key was generated using DSA as opposed to RSA. A number of vendors in the SSH arena have argued, as per the PuTTY documentation that can be found at http://the.earth.li/~sgtatham/putty/0.55/htmldoc/Chapter8.html#S8.2.10 that users should employ RSA encryption because&lt;br /&gt;
&lt;br /&gt;
 DSA has an intrinsic weakness which makes it very easy to create a signature&lt;br /&gt;
 which contains enough information to give away the private key! This would &lt;br /&gt;
 allow an attacker to pretend to be you for any number of future sessions. &lt;br /&gt;
&lt;br /&gt;
An SSH2 public key in OpenSSH format will start with &amp;quot;ssh-rsa&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The idea behind all of this is that once you have keys on the remote server and your local host,  access will be simpler since the server will only grant access to someone who has the matching private key.&lt;br /&gt;
&lt;br /&gt;
==Why do I need a SSH key?==&lt;br /&gt;
&lt;br /&gt;
Our CVS server uses OpenSSH, so if are a Moodle developer and you want to make your logins easier (by avoiding typing in your password all the time) then you will need to submit public key in Openssh format via the &amp;quot;Update my developer information&amp;quot; tab at http://moodle.org/cvs.&lt;br /&gt;
&lt;br /&gt;
==How do I create a SSH key pair?==&lt;br /&gt;
&lt;br /&gt;
===Eclipse===&lt;br /&gt;
&lt;br /&gt;
If you plan to use Eclipse for development, please refer to the Eclipse document https://docs.moodle.org/en/Eclipse as Eclipse now has a plugin that allows you to manage all ssh key matters from within Eclipse.&lt;br /&gt;
&lt;br /&gt;
===Unix/Linux===&lt;br /&gt;
&lt;br /&gt;
# Run:  &#039;&#039;&#039;ssh-keygen -t (rsa or dsa)&#039;&#039;&#039;. This will not include a passphrase.&lt;br /&gt;
# Look in your ~/.ssh directory (or wherever you saved the output).  You&#039;ll find &#039;&#039;&#039;id_dsa&#039;&#039;&#039; (private) and &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; (public).&lt;br /&gt;
# Cut and paste the contents of &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; into your developer profile on http://moodle.org/cvs&lt;br /&gt;
# Put the private key wherever you will be calling CVS from (in your .ssh directory, for example).  Make sure it&#039;s secure!&lt;br /&gt;
&lt;br /&gt;
===Windows===&lt;br /&gt;
&lt;br /&gt;
===Mac OS X===&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8415</id>
		<title>SSH key</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8415"/>
		<updated>2008-04-15T21:59:36Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* What is a SSH key? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==What is a SSH key?==&lt;br /&gt;
&lt;br /&gt;
SSH keys are used for secure connections across a network.  They come in pairs, so you have a public key and a private key.&lt;br /&gt;
&lt;br /&gt;
The standard ssh2 file format (see&lt;br /&gt;
http://www.openssh.org/txt/draft-ietf-secsh-publickeyfile-02.txt)&lt;br /&gt;
looks like this:&lt;br /&gt;
&lt;br /&gt;
 ---- BEGIN SSH2 PUBLIC KEY ----&lt;br /&gt;
 Comment: &amp;quot;jtbell@Jon-Bells-Computer&amp;quot;&lt;br /&gt;
 AAAAB3NzaC1kc3MAAACBAPNgmidbM2rhYjUXunpnlXjHWfV+vc8/5YKrn8Y5P0Y6KwmG2G&lt;br /&gt;
 GMgNBon3LX3iJlBhtuU3FCBj3G1Kdt5vUhQHhUmHVrOasi47vawTrv7ZJCfiaSGwRsiBHt&lt;br /&gt;
 Jta5CAp7t0EnzX2q6BvPbFBBHNLyy6uNVpL2jOR06Pkx/vaqyScvAAAAFQDHvwmjWYwK9g&lt;br /&gt;
 K6Sp+pSvI7bwEUtwAAAIANMJDotMpfj89N+7+FJylSS+uFEQSS61PxENl/Mcj1jUREjJg2&lt;br /&gt;
 eNsJdAB9Ev99hWYS+7lFRtTJ2eh4Y9gpGe7BX3e2YGHOqp8cWCVCIKaMzwk9To+xnfThWq&lt;br /&gt;
 IfHT8I6CJxp/5ez02m6F2k/5iukvOwbGms6EAZK1DTBhDOHjEQwQAAAIAlz2/qBWkaMP+s&lt;br /&gt;
 W8FLmGKM+cCw5+asOaJGTwrFVuwJkDMvdEWxmG92A2dxuUske0d/AkN6zJp7HD0wlfesRM&lt;br /&gt;
 3+c+Res5qun9lFcdM4i03VoV5mXd+T7laS8yku6vZgvZZFnPvr2LOUnc7XThGFwMaQpFEW&lt;br /&gt;
 U8cvQbttO6QrT2CD2w==&lt;br /&gt;
 ---- END SSH2 PUBLIC KEY ----&lt;br /&gt;
&lt;br /&gt;
However, Moodle uses OpenSSH on its server and this key will not work with the OpenSSH server in this format; OpenSSH requires the key to be in OpenSSH format. Here is an example of a DSA public key in OpenSSH format (usually they are all in one line):&lt;br /&gt;
&lt;br /&gt;
 ssh-dss AAAAB3NzaC1kc3MAAACBAJ3hB5SAF6mBXPlZlRoJEZi0KSIN+NU2iGiaXZXi9CDrgVxTp6/&lt;br /&gt;
 sc56UcYCp4qjfrZ2G3+6PWbxYso4P4YyUC+61RU5KPy4EcTJske3O+aNvec/20cW7PT3TvH1+sxwGry&lt;br /&gt;
 mD50kTiXDgo5nXdqFvibgM61WW2DGTKlEUsZys0njRAAAAFQDs7ukaTGJlZdeznwFUAttTH9LrwwAAA&lt;br /&gt;
 IAMm4sLCdvvBx9WPkvWDX0OIXSteCYckiQxesOfPvz26FfYxuTG/2dljDlalC+kYG05C1NEcmZWSNES&lt;br /&gt;
 GBGfccSYSfI3Y5ahSVUhOC2LMO3JNjVyYUnOM/iyhzrnRfQoWO9GFMaugq0jBMlhZA4UO26yJqJ+BtX&lt;br /&gt;
 IyItaEEJdc/ghIwAAAIBFeCZynstlbBjP648+mDKIvzNSS+JYr5klGxS3q8A56NPcYhDMxGn7h1DKbb&lt;br /&gt;
 2AV4pO6y+6hDrWo3UT4dLVuzK01trwp PYp6JXTSZZ12ZaXNPz7sX9/z6pzMqhX4UEfjVsLcuF+ZS6a&lt;br /&gt;
 QCPO0ZZEa1z+EEIZSD/ykLQsDwPxGjPBqw== someone@somewhere.com&lt;br /&gt;
&lt;br /&gt;
In addition to OpenSSH and Standard SSH formats there are a variety of proprietary formats as well as SSH1 and SSH2 differences to account for, which can make this confusing. &lt;br /&gt;
&lt;br /&gt;
In the example above you will note that the key starts with &amp;quot;ssh-dss&amp;quot;. This is because this key was generated using DSA as opposed to RSA. A number of vendors in the SSH arena have argued, as per the PuTTY documentation that can be found at http://the.earth.li/~sgtatham/putty/0.55/htmldoc/Chapter8.html#S8.2.10 that users should employ RSA encryption because&lt;br /&gt;
&lt;br /&gt;
 DSA has an intrinsic weakness which makes it very easy to create a signature&lt;br /&gt;
 which contains enough information to give away the private key! This would &lt;br /&gt;
 allow an attacker to pretend to be you for any number of future sessions. &lt;br /&gt;
&lt;br /&gt;
An SSH2 public key in OpenSSH format will start with &amp;quot;ssh-rsa&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The idea behind all of this is that once you have keys on the remote server and your local host,  access will be simpler since the server will only grant access to someone who has the matching private key.&lt;br /&gt;
&lt;br /&gt;
==Why do I need a SSH key?==&lt;br /&gt;
&lt;br /&gt;
Our CVS server uses OpenSSH, so if are a Moodle developer and you want to make your logins easier (by avoiding typing in your password all the time) then you will need to submit public key in Openssh format via the &amp;quot;Update my developer information&amp;quot; tab at http://moodle.org/cvs.&lt;br /&gt;
&lt;br /&gt;
==How do I create a SSH key pair?==&lt;br /&gt;
&lt;br /&gt;
===Eclipse===&lt;br /&gt;
&lt;br /&gt;
If you plan to use Eclipse for development, please refer to the Eclipse document https://docs.moodle.org/en/Eclipse as Eclipse now has a plugin that allows you to manage all ssh key matters from within Eclipse.&lt;br /&gt;
&lt;br /&gt;
===Unix/Linux===&lt;br /&gt;
&lt;br /&gt;
# Run:  &#039;&#039;&#039;ssh-keygen -d&#039;&#039;&#039;&lt;br /&gt;
# Look in your ~/.ssh directory (or wherever you saved the output).  You&#039;ll find &#039;&#039;&#039;id_dsa&#039;&#039;&#039; (private) and &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; (public).&lt;br /&gt;
# Cut and paste the contents of &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; into your developer profile on http://moodle.org/cvs&lt;br /&gt;
# Put the private key wherever you will be calling CVS from (in your .ssh directory, for example).  Make sure it&#039;s secure!&lt;br /&gt;
&lt;br /&gt;
===Windows===&lt;br /&gt;
&lt;br /&gt;
===Mac OS X===&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8414</id>
		<title>SSH key</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8414"/>
		<updated>2008-04-15T21:55:47Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* What is a SSH key? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==What is a SSH key?==&lt;br /&gt;
&lt;br /&gt;
SSH keys are used for secure connections across a network.  They come in pairs, so you have a public key and a private key.&lt;br /&gt;
&lt;br /&gt;
The standard ssh2 file format (see&lt;br /&gt;
http://www.openssh.org/txt/draft-ietf-secsh-publickeyfile-02.txt)&lt;br /&gt;
looks like this:&lt;br /&gt;
&lt;br /&gt;
 ---- BEGIN SSH2 PUBLIC KEY ----&lt;br /&gt;
 Comment: &amp;quot;jtbell@Jon-Bells-Computer&amp;quot;&lt;br /&gt;
 AAAAB3NzaC1kc3MAAACBAPNgmidbM2rhYjUXunpnlXjHWfV+vc8/5YKrn8Y5P0Y6KwmG2G&lt;br /&gt;
 GMgNBon3LX3iJlBhtuU3FCBj3G1Kdt5vUhQHhUmHVrOasi47vawTrv7ZJCfiaSGwRsiBHt&lt;br /&gt;
 Jta5CAp7t0EnzX2q6BvPbFBBHNLyy6uNVpL2jOR06Pkx/vaqyScvAAAAFQDHvwmjWYwK9g&lt;br /&gt;
 K6Sp+pSvI7bwEUtwAAAIANMJDotMpfj89N+7+FJylSS+uFEQSS61PxENl/Mcj1jUREjJg2&lt;br /&gt;
 eNsJdAB9Ev99hWYS+7lFRtTJ2eh4Y9gpGe7BX3e2YGHOqp8cWCVCIKaMzwk9To+xnfThWq&lt;br /&gt;
 IfHT8I6CJxp/5ez02m6F2k/5iukvOwbGms6EAZK1DTBhDOHjEQwQAAAIAlz2/qBWkaMP+s&lt;br /&gt;
 W8FLmGKM+cCw5+asOaJGTwrFVuwJkDMvdEWxmG92A2dxuUske0d/AkN6zJp7HD0wlfesRM&lt;br /&gt;
 3+c+Res5qun9lFcdM4i03VoV5mXd+T7laS8yku6vZgvZZFnPvr2LOUnc7XThGFwMaQpFEW&lt;br /&gt;
 U8cvQbttO6QrT2CD2w==&lt;br /&gt;
 ---- END SSH2 PUBLIC KEY ----&lt;br /&gt;
&lt;br /&gt;
However, this key will not work with the OpenSSH server. OpenSSH requires the key in OpenSSH format. Here is an example of a DSA public key in OpenSSH format (usually they are all in one line):&lt;br /&gt;
&lt;br /&gt;
 ssh-dss AAAAB3NzaC1kc3MAAACBAJ3hB5SAF6mBXPlZlRoJEZi0KSIN+NU2iGiaXZXi9CDrgVxTp6/&lt;br /&gt;
 sc56UcYCp4qjfrZ2G3+6PWbxYso4P4YyUC+61RU5KPy4EcTJske3O+aNvec/20cW7PT3TvH1+sxwGry&lt;br /&gt;
 mD50kTiXDgo5nXdqFvibgM61WW2DGTKlEUsZys0njRAAAAFQDs7ukaTGJlZdeznwFUAttTH9LrwwAAA&lt;br /&gt;
 IAMm4sLCdvvBx9WPkvWDX0OIXSteCYckiQxesOfPvz26FfYxuTG/2dljDlalC+kYG05C1NEcmZWSNES&lt;br /&gt;
 GBGfccSYSfI3Y5ahSVUhOC2LMO3JNjVyYUnOM/iyhzrnRfQoWO9GFMaugq0jBMlhZA4UO26yJqJ+BtX&lt;br /&gt;
 IyItaEEJdc/ghIwAAAIBFeCZynstlbBjP648+mDKIvzNSS+JYr5klGxS3q8A56NPcYhDMxGn7h1DKbb&lt;br /&gt;
 2AV4pO6y+6hDrWo3UT4dLVuzK01trwp PYp6JXTSZZ12ZaXNPz7sX9/z6pzMqhX4UEfjVsLcuF+ZS6a&lt;br /&gt;
 QCPO0ZZEa1z+EEIZSD/ykLQsDwPxGjPBqw== someone@somewhere.com&lt;br /&gt;
&lt;br /&gt;
In addition to OpenSSH and Standard SSH formats there are a variety of proprietary formats as well as SSH1 and SSH2 differences to account for, which can make this confusing. &lt;br /&gt;
&lt;br /&gt;
In the example above you will note that the key starts with &amp;quot;ssh-dss&amp;quot;. This is because this key was generated using DSA as opposed to RSA. A number of vendors in the SSH arena have argued, as per the PuTTY documentation that can be found at http://the.earth.li/~sgtatham/putty/0.55/htmldoc/Chapter8.html#S8.2.10 that users should employ RSA encryption because&lt;br /&gt;
&lt;br /&gt;
 DSA has an intrinsic weakness which makes it very easy to create a signature&lt;br /&gt;
 which contains enough information to give away the private key! This would &lt;br /&gt;
 allow an attacker to pretend to be you for any number of future sessions. &lt;br /&gt;
&lt;br /&gt;
The idea is that you put your public key on servers that you want to establish a connection with.  The server will only grant access to someone who has the matching private key.&lt;br /&gt;
&lt;br /&gt;
==Why do I need a SSH key?==&lt;br /&gt;
&lt;br /&gt;
Our CVS server uses OpenSSH, so if are a Moodle developer and you want to make your logins easier (by avoiding typing in your password all the time) then you will need to submit public key in Openssh format via the &amp;quot;Update my developer information&amp;quot; tab at http://moodle.org/cvs.&lt;br /&gt;
&lt;br /&gt;
==How do I create a SSH key pair?==&lt;br /&gt;
&lt;br /&gt;
===Eclipse===&lt;br /&gt;
&lt;br /&gt;
If you plan to use Eclipse for development, please refer to the Eclipse document https://docs.moodle.org/en/Eclipse as Eclipse now has a plugin that allows you to manage all ssh key matters from within Eclipse.&lt;br /&gt;
&lt;br /&gt;
===Unix/Linux===&lt;br /&gt;
&lt;br /&gt;
# Run:  &#039;&#039;&#039;ssh-keygen -d&#039;&#039;&#039;&lt;br /&gt;
# Look in your ~/.ssh directory (or wherever you saved the output).  You&#039;ll find &#039;&#039;&#039;id_dsa&#039;&#039;&#039; (private) and &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; (public).&lt;br /&gt;
# Cut and paste the contents of &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; into your developer profile on http://moodle.org/cvs&lt;br /&gt;
# Put the private key wherever you will be calling CVS from (in your .ssh directory, for example).  Make sure it&#039;s secure!&lt;br /&gt;
&lt;br /&gt;
===Windows===&lt;br /&gt;
&lt;br /&gt;
===Mac OS X===&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8413</id>
		<title>SSH key</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8413"/>
		<updated>2008-04-15T21:40:46Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* How do I create a SSH key pair? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==What is a SSH key?==&lt;br /&gt;
&lt;br /&gt;
SSH keys are used for secure connections across a network.  They come in pairs, so you have a public key and a private key.&lt;br /&gt;
&lt;br /&gt;
Here is an example of a DSA public key in OpenSSH format (usually they are all in one line):&lt;br /&gt;
&lt;br /&gt;
 ssh-dss AAAAB3NzaC1kc3MAAACBAJ3hB5SAF6mBXPlZlRoJEZi0KSIN+NU2iGiaXZXi9CDrgVxTp6/&lt;br /&gt;
 sc56UcYCp4qjfrZ2G3+6PWbxYso4P4YyUC+61RU5KPy4EcTJske3O+aNvec/20cW7PT3TvH1+sxwGry&lt;br /&gt;
 mD50kTiXDgo5nXdqFvibgM61WW2DGTKlEUsZys0njRAAAAFQDs7ukaTGJlZdeznwFUAttTH9LrwwAAA&lt;br /&gt;
 IAMm4sLCdvvBx9WPkvWDX0OIXSteCYckiQxesOfPvz26FfYxuTG/2dljDlalC+kYG05C1NEcmZWSNES&lt;br /&gt;
 GBGfccSYSfI3Y5ahSVUhOC2LMO3JNjVyYUnOM/iyhzrnRfQoWO9GFMaugq0jBMlhZA4UO26yJqJ+BtX&lt;br /&gt;
 IyItaEEJdc/ghIwAAAIBFeCZynstlbBjP648+mDKIvzNSS+JYr5klGxS3q8A56NPcYhDMxGn7h1DKbb&lt;br /&gt;
 2AV4pO6y+6hDrWo3UT4dLVuzK01trwp PYp6JXTSZZ12ZaXNPz7sX9/z6pzMqhX4UEfjVsLcuF+ZS6a&lt;br /&gt;
 QCPO0ZZEa1z+EEIZSD/ykLQsDwPxGjPBqw== someone@somewhere.com&lt;br /&gt;
&lt;br /&gt;
The idea is that you put your public key on servers that you want to establish a connection with.  The server will only grant access to someone who has the matching private key.&lt;br /&gt;
&lt;br /&gt;
==Why do I need a SSH key?==&lt;br /&gt;
&lt;br /&gt;
Our CVS server uses OpenSSH, so if are a Moodle developer and you want to make your logins easier (by avoiding typing in your password all the time) then you will need to submit public key in Openssh format via the &amp;quot;Update my developer information&amp;quot; tab at http://moodle.org/cvs.&lt;br /&gt;
&lt;br /&gt;
==How do I create a SSH key pair?==&lt;br /&gt;
&lt;br /&gt;
===Eclipse===&lt;br /&gt;
&lt;br /&gt;
If you plan to use Eclipse for development, please refer to the Eclipse document https://docs.moodle.org/en/Eclipse as Eclipse now has a plugin that allows you to manage all ssh key matters from within Eclipse.&lt;br /&gt;
&lt;br /&gt;
===Unix/Linux===&lt;br /&gt;
&lt;br /&gt;
# Run:  &#039;&#039;&#039;ssh-keygen -d&#039;&#039;&#039;&lt;br /&gt;
# Look in your ~/.ssh directory (or wherever you saved the output).  You&#039;ll find &#039;&#039;&#039;id_dsa&#039;&#039;&#039; (private) and &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; (public).&lt;br /&gt;
# Cut and paste the contents of &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; into your developer profile on http://moodle.org/cvs&lt;br /&gt;
# Put the private key wherever you will be calling CVS from (in your .ssh directory, for example).  Make sure it&#039;s secure!&lt;br /&gt;
&lt;br /&gt;
===Windows===&lt;br /&gt;
&lt;br /&gt;
===Mac OS X===&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8412</id>
		<title>SSH key</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8412"/>
		<updated>2008-04-15T21:37:18Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* Why do I need a SSH key? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==What is a SSH key?==&lt;br /&gt;
&lt;br /&gt;
SSH keys are used for secure connections across a network.  They come in pairs, so you have a public key and a private key.&lt;br /&gt;
&lt;br /&gt;
Here is an example of a DSA public key in OpenSSH format (usually they are all in one line):&lt;br /&gt;
&lt;br /&gt;
 ssh-dss AAAAB3NzaC1kc3MAAACBAJ3hB5SAF6mBXPlZlRoJEZi0KSIN+NU2iGiaXZXi9CDrgVxTp6/&lt;br /&gt;
 sc56UcYCp4qjfrZ2G3+6PWbxYso4P4YyUC+61RU5KPy4EcTJske3O+aNvec/20cW7PT3TvH1+sxwGry&lt;br /&gt;
 mD50kTiXDgo5nXdqFvibgM61WW2DGTKlEUsZys0njRAAAAFQDs7ukaTGJlZdeznwFUAttTH9LrwwAAA&lt;br /&gt;
 IAMm4sLCdvvBx9WPkvWDX0OIXSteCYckiQxesOfPvz26FfYxuTG/2dljDlalC+kYG05C1NEcmZWSNES&lt;br /&gt;
 GBGfccSYSfI3Y5ahSVUhOC2LMO3JNjVyYUnOM/iyhzrnRfQoWO9GFMaugq0jBMlhZA4UO26yJqJ+BtX&lt;br /&gt;
 IyItaEEJdc/ghIwAAAIBFeCZynstlbBjP648+mDKIvzNSS+JYr5klGxS3q8A56NPcYhDMxGn7h1DKbb&lt;br /&gt;
 2AV4pO6y+6hDrWo3UT4dLVuzK01trwp PYp6JXTSZZ12ZaXNPz7sX9/z6pzMqhX4UEfjVsLcuF+ZS6a&lt;br /&gt;
 QCPO0ZZEa1z+EEIZSD/ykLQsDwPxGjPBqw== someone@somewhere.com&lt;br /&gt;
&lt;br /&gt;
The idea is that you put your public key on servers that you want to establish a connection with.  The server will only grant access to someone who has the matching private key.&lt;br /&gt;
&lt;br /&gt;
==Why do I need a SSH key?==&lt;br /&gt;
&lt;br /&gt;
Our CVS server uses OpenSSH, so if are a Moodle developer and you want to make your logins easier (by avoiding typing in your password all the time) then you will need to submit public key in Openssh format via the &amp;quot;Update my developer information&amp;quot; tab at http://moodle.org/cvs.&lt;br /&gt;
&lt;br /&gt;
==How do I create a SSH key pair?==&lt;br /&gt;
&lt;br /&gt;
===Unix/Linux===&lt;br /&gt;
&lt;br /&gt;
# Run:  &#039;&#039;&#039;ssh-keygen -d&#039;&#039;&#039;&lt;br /&gt;
# Look in your ~/.ssh directory (or wherever you saved the output).  You&#039;ll find &#039;&#039;&#039;id_dsa&#039;&#039;&#039; (private) and &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; (public).&lt;br /&gt;
# Cut and paste the contents of &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; into your developer profile on http://moodle.org/cvs&lt;br /&gt;
# Put the private key wherever you will be calling CVS from (in your .ssh directory, for example).  Make sure it&#039;s secure!&lt;br /&gt;
&lt;br /&gt;
===Windows===&lt;br /&gt;
&lt;br /&gt;
===Mac OS X===&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8411</id>
		<title>SSH key</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=SSH_key&amp;diff=8411"/>
		<updated>2008-04-15T19:51:35Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* What is a SSH key? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==What is a SSH key?==&lt;br /&gt;
&lt;br /&gt;
SSH keys are used for secure connections across a network.  They come in pairs, so you have a public key and a private key.&lt;br /&gt;
&lt;br /&gt;
Here is an example of a DSA public key in OpenSSH format (usually they are all in one line):&lt;br /&gt;
&lt;br /&gt;
 ssh-dss AAAAB3NzaC1kc3MAAACBAJ3hB5SAF6mBXPlZlRoJEZi0KSIN+NU2iGiaXZXi9CDrgVxTp6/&lt;br /&gt;
 sc56UcYCp4qjfrZ2G3+6PWbxYso4P4YyUC+61RU5KPy4EcTJske3O+aNvec/20cW7PT3TvH1+sxwGry&lt;br /&gt;
 mD50kTiXDgo5nXdqFvibgM61WW2DGTKlEUsZys0njRAAAAFQDs7ukaTGJlZdeznwFUAttTH9LrwwAAA&lt;br /&gt;
 IAMm4sLCdvvBx9WPkvWDX0OIXSteCYckiQxesOfPvz26FfYxuTG/2dljDlalC+kYG05C1NEcmZWSNES&lt;br /&gt;
 GBGfccSYSfI3Y5ahSVUhOC2LMO3JNjVyYUnOM/iyhzrnRfQoWO9GFMaugq0jBMlhZA4UO26yJqJ+BtX&lt;br /&gt;
 IyItaEEJdc/ghIwAAAIBFeCZynstlbBjP648+mDKIvzNSS+JYr5klGxS3q8A56NPcYhDMxGn7h1DKbb&lt;br /&gt;
 2AV4pO6y+6hDrWo3UT4dLVuzK01trwp PYp6JXTSZZ12ZaXNPz7sX9/z6pzMqhX4UEfjVsLcuF+ZS6a&lt;br /&gt;
 QCPO0ZZEa1z+EEIZSD/ykLQsDwPxGjPBqw== someone@somewhere.com&lt;br /&gt;
&lt;br /&gt;
The idea is that you put your public key on servers that you want to establish a connection with.  The server will only grant access to someone who has the matching private key.&lt;br /&gt;
&lt;br /&gt;
==Why do I need a SSH key?==&lt;br /&gt;
&lt;br /&gt;
Our CVS server uses this system, so if are a Moodle developer and you want to make your logins easier (by avoiding typing in your password all the time) then send us your public key on this form:  http://moodle.org/cvs&lt;br /&gt;
&lt;br /&gt;
==How do I create a SSH key pair?==&lt;br /&gt;
&lt;br /&gt;
===Unix/Linux===&lt;br /&gt;
&lt;br /&gt;
# Run:  &#039;&#039;&#039;ssh-keygen -d&#039;&#039;&#039;&lt;br /&gt;
# Look in your ~/.ssh directory (or wherever you saved the output).  You&#039;ll find &#039;&#039;&#039;id_dsa&#039;&#039;&#039; (private) and &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; (public).&lt;br /&gt;
# Cut and paste the contents of &#039;&#039;&#039;id_dsa.pub&#039;&#039;&#039; into your developer profile on http://moodle.org/cvs&lt;br /&gt;
# Put the private key wherever you will be calling CVS from (in your .ssh directory, for example).  Make sure it&#039;s secure!&lt;br /&gt;
&lt;br /&gt;
===Windows===&lt;br /&gt;
&lt;br /&gt;
===Mac OS X===&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=Setting_up_Eclipse&amp;diff=4960</id>
		<title>Setting up Eclipse</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=Setting_up_Eclipse&amp;diff=4960"/>
		<updated>2008-04-15T19:49:23Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: Break SSH info out of CVS settings&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.eclipse.org/ Eclipse] is an IDE originally designed for Java, but now with plugins for many languages including PHP. It has lots of very powerful features, and it is the editor that some Moodle developers like to use. Other (more) popular choices are vim and emacs.&lt;br /&gt;
&lt;br /&gt;
However, Eclipse is not the easiest program in the world to get started with, so I&#039;m going to take you through it step by step. These instructions assume Eclipse 3.2, the current version at the time of writing. It should not change much between releases.&lt;br /&gt;
&lt;br /&gt;
This article started off as a brain-dump by [[User:Tim Hunt|Tim Hunt]]. Since then, several other people have worked through it and made corrections, so the information here should be pretty accurate.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites==&lt;br /&gt;
&lt;br /&gt;
Eclipse is written in Java, so I recommend getting the latest Java runtime environment from http://java.com/ for maximum speed and reliability.&lt;br /&gt;
&lt;br /&gt;
Eclipse is quite big, so I recommend lots of memory in your computer. I have used it on Windows, MacOS X and Linux, in each case with 1GB of memory, and that is plenty.&lt;br /&gt;
&lt;br /&gt;
==Installing Eclipse==&lt;br /&gt;
&lt;br /&gt;
Go to http://www.eclipse.org/downloads/. Click on the link corresponding to your operating system where it says &#039;&#039;&#039;Eclipse Classic&#039;&#039;&#039;. Choose a Mirror, and wait for the ~100MB download.&lt;br /&gt;
&lt;br /&gt;
You will notice that what you have got is a zip file (unless your system automatically decompresses it for you).&lt;br /&gt;
&lt;br /&gt;
On Windows, unzip it into &#039;&#039;&#039;C:\Program Files&#039;&#039;&#039; (all the files go into an &#039;&#039;&#039;Eclipse&#039;&#039;&#039; folder there). Then look in the Eclipse folder and drag Eclipse.exe to the Start menu/Desktop/Quicklaunch bar to make a shortcut for starting it.&lt;br /&gt;
&lt;br /&gt;
On MacOS, unzip and copy the Eclipse folder into Applications. Go into the Eclipse folder and drag the Eclipse app to the Dock for ease of launching.&lt;br /&gt;
&lt;br /&gt;
On Linux, unzip somewhere suitable, and make an easy way to launch it.&lt;br /&gt;
&lt;br /&gt;
==The first time you run Eclipse==&lt;br /&gt;
&lt;br /&gt;
The first time you launch Eclipse it does a bit of setup stuff, for instance, it create a &#039;&#039;&#039;workspace&#039;&#039;&#039;. This is where it stores the things you are working on. The default location is sensible on all platforms, so use that. &lt;br /&gt;
&lt;br /&gt;
For some reason, every time you start Eclipse, it asks you which workspace you want to use. I have never seen the need to have more than one, so I recommend turning on the checkbox that says &amp;quot;Use this as the default and do not ask again&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Another thing that happens the first time you run Eclipse is that you arrive at a welcome screen. This has links to various bits of help, which you can read if you like, but you probably don&#039;t need to if you are following these instructions. So find the button on the welcome page that closes it and gets you to the main Eclipse screen.&lt;br /&gt;
&lt;br /&gt;
==Installing the necessary plugins==&lt;br /&gt;
&lt;br /&gt;
By default, Eclipse comes with the Java tools. For everything else you will need to install some plugins.&lt;br /&gt;
&lt;br /&gt;
If you are sitting behind a web proxy, from the &#039;&#039;&#039;Window&#039;&#039;&#039; menu choose &#039;&#039;&#039;Preferences ...&#039;&#039;&#039;. Choose &#039;&#039;&#039;Install/Update&#039;&#039;&#039; from the tree view on the left, and enter the proxy information in the boxes on the right. If you aren&#039;t behind a proxy, ignore this step.&lt;br /&gt;
&lt;br /&gt;
From the &#039;&#039;&#039;Help&#039;&#039;&#039; menu choose &#039;&#039;&#039;Software Updates -&amp;gt; Find and Install&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
On the first screen of the wizard, make sure that &amp;quot;Search for new features to install&amp;quot; is selected, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The next screen is a list of upgrade sites to check. You need to add one to the list, so click the &#039;&#039;&#039;New Remote Site ...&#039;&#039;&#039; Button.&lt;br /&gt;
&lt;br /&gt;
In the pop-up dialog, give the remote site a name like &#039;&#039;&#039;PHPeclipse Update Site&#039;&#039;&#039;; set the URL to http://phpeclipse.sourceforge.net/update/releases/; then click &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note, there is now also another PHP editor for Eclipse. The update URL ishttp://download.eclipse.org/tools/pdt/updates/. I am just trying it--[[User:Tim Hunt|Tim Hunt]] 11:39, 7 November 2007 (CST)&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Back in the wizard, turn on just two things in the box &amp;quot;Sites to include in search&amp;quot;:&lt;br /&gt;
* Your newly created &#039;&#039;&#039;Phpeclipse Update Site&#039;&#039;&#039;; and&lt;br /&gt;
* the one called &#039;&#039;&#039;Europa Discovery Site&#039;&#039;&#039; (or possibly &#039;&#039;&#039;Callisto Discovery Site&#039;&#039;&#039;.&lt;br /&gt;
Then click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
It goes off sees what updates are available at those sites. As it does so, it may occasionally pop up a dialog asking you to choose a mirror. Each time, select a sensible one.&lt;br /&gt;
&lt;br /&gt;
Eventually, you get to a new wizard for selecting and installing the updates you want. The ones you want (you may have to search the tree structure) are, &#039;&#039;&#039;PHPeclipse&#039;&#039;&#039; (from your newly created PHPEclipse Update Site) and all the &#039;&#039;&#039;Web Standard Tools (WST)&#039;&#039;&#039; (usually under Callisto Discovery Site --&amp;gt; Web and J2EE Development).&lt;br /&gt;
&lt;br /&gt;
Next, and very importantly, you must click the &#039;&#039;&#039;Select Required&#039;&#039;&#039; button which should resolve dependencies and remove the warning message you are probably worrying about. Then you can click the &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
Read and agree to all the license agreements. Then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Finish&#039;&#039;&#039;, and wait for the plugins to download.&lt;br /&gt;
&lt;br /&gt;
Once the downloads have finished, a warning will pop-up telling you that all the plugins you downloaded are not digitally signed. The Eclipse Foundation build digital signing of plugins into their architecture as a security measure, and then did not sign any of their own plugins! Anyway, click the &#039;&#039;&#039;Install All&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
Finally, a window will pop up asking you to restart Eclipse. Do so.&lt;br /&gt;
&lt;br /&gt;
==Setting the preferences for Moodle development==&lt;br /&gt;
&lt;br /&gt;
Now go to the &#039;&#039;&#039;Window&#039;&#039;&#039; menu, and choose &#039;&#039;&#039;Preferences ...&#039;&#039;&#039; (&#039;&#039;&#039;Eclipse&#039;&#039;&#039; menu on Mac OS X).&lt;br /&gt;
&lt;br /&gt;
The Eclipse preferences are immense, with a tree view on the left, which selects which screen to display on the right. Don&#039;t panic, we&#039;ll guide you through it.&lt;br /&gt;
&lt;br /&gt;
===General settings===&lt;br /&gt;
&lt;br /&gt;
If you have strong feelings about fonts (I would hate to edit code an anything except Andale Mono), choose &#039;&#039;&#039;General -&amp;gt; Appearance -&amp;gt; Colors and Fonts&#039;&#039;&#039; from the tree on the left. Then on the right look under &#039;&#039;&#039;Basic&#039;&#039;&#039; and change &#039;&#039;&#039;Text Font&#039;&#039;&#039;. All the other editor font settings will inherit from this, so this is probably the only one you have to change.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;General -&amp;gt; Content Types&#039;&#039;&#039;, select PHP Source File, and add &#039;&#039;&#039;*.html&#039;&#039;&#039; to the box at the bottom.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;General -&amp;gt; Editors -&amp;gt; File Associations&#039;&#039;&#039;, if it is not already there, add &#039;&#039;&#039;*.php&#039;&#039;&#039; to the top box. With &#039;&#039;&#039;*.php&#039;&#039;&#039; selected in the top box, make sure &#039;&#039;&#039;PHP Editor&#039;&#039;&#039; is set to default in the bottom box. With &#039;&#039;&#039;*.html&#039;&#039;&#039; selected in the top box, select &#039;&#039;&#039;PHP Editor&#039;&#039;&#039; in the bottom box and click the &#039;&#039;&#039;Default&#039;&#039;&#039; button to change it, because in Moodle, most HTML files actually contain PHP code.&lt;br /&gt;
&lt;br /&gt;
If you use a web proxy, enter the details under &#039;&#039;&#039;Internet -&amp;gt; Proxy Settings&#039;&#039;&#039;. (Yes, I know you have entered them somewhere else before. Now you have to enter them again here. I don&#039;t know why. You just do.)&lt;br /&gt;
&lt;br /&gt;
===PHP Settings===&lt;br /&gt;
&lt;br /&gt;
These are all hidden under the &#039;&#039;&#039;PHPeclipse Web Development&#039;&#039;&#039; bit of the tree.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; Browser Preview Defaults&#039;&#039;&#039;, turn off both checkboxes.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP&#039;&#039;&#039;, on the &#039;&#039;&#039;Appearance&#039;&#039;&#039; tab, set &#039;&#039;&#039;Displayed tab width&#039;&#039;&#039; to 4.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP&#039;&#039;&#039;, on the &#039;&#039;&#039;Appearance&#039;&#039;&#039; tab, check &#039;&#039;&#039;Show line numbers&#039;&#039;&#039; to display line numbers in the left margin (optional). NOTE.- When you are editing a PHP file, you could left-click in the left margin and tick the &#039;&#039;&#039;Show Line Numbers&#039;&#039;&#039; line in the contextual menu. However, this toggle only applies to plain text files, &#039;&#039;not&#039;&#039; to HTML or PHP files. The only place where you can toggle line numbers on/off for such files is in the PHP/Appearance menu.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP&#039;&#039;&#039;, on the &#039;&#039;&#039;Typing&#039;&#039;&#039; tab, turn off all the options except &#039;&#039;&#039;Pasting for correct indentation&#039;&#039;&#039;, &#039;&#039;&#039;Insert spaces for tab&#039;&#039;&#039; and &#039;&#039;&#039;Close PHPdocs and comments&#039;&#039;&#039; and &#039;&#039;&#039;Remove trailing spaces on editor save&#039;&#039;&#039;. It would be nice to turn on more of these options, but most of the rest don&#039;t work very well.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP -&amp;gt; Formatter&#039;&#039;&#039;, on the &#039;&#039;&#039;New Lines&#039;&#039;&#039; tab, turn on &#039;&#039;&#039;Clear all blank lines&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP -&amp;gt; Formatter&#039;&#039;&#039;, on the &#039;&#039;&#039;Style&#039;&#039;&#039; tab, turn off &#039;&#039;&#039;Indentation is represented by a tab&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP -&amp;gt; Templates&#039;&#039;&#039;, I like to define a new template to help with debugging:&lt;br /&gt;
;Name&lt;br /&gt;
:dump &lt;br /&gt;
;Description&lt;br /&gt;
:Dump a PHP variable&lt;br /&gt;
;Pattern&lt;br /&gt;
&amp;lt;pre&amp;gt;print_object(${word_selection}${cursor}); // DONOTCOMMIT&amp;lt;/pre&amp;gt;&lt;br /&gt;
You can do other useful things with templates too. Here are two more I use:&lt;br /&gt;
&amp;lt;pre&amp;gt;debugging(&amp;quot;&#039;${word_selection}${cursor}&#039;&amp;quot;); // DONOTCOMMIT&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;$$string[&#039;${word_selection}${cursor}&#039;] = &#039;.&#039;;&amp;lt;/pre&amp;gt;&lt;br /&gt;
That is, a simple debug message with a stack trace, and a new language string.&lt;br /&gt;
&lt;br /&gt;
There is a really stupid bug. Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; Project Defaults&#039;&#039;&#039;, you would like to add &amp;quot;.&amp;quot; to the &#039;&#039;&#039;Include Paths&#039;&#039;&#039;, but you can&#039;t using the GUI. You will have to edit one of the Eclipse config files by hand. So&lt;br /&gt;
# Note down the path to your Eclipse profile. On Windows it will be something like &#039;&#039;&#039;C:/Documents and settings/XXXX/workspace&#039;&#039;&#039;, and on Unixy systems something like &#039;&#039;&#039;~/workspace&#039;&#039;&#039;.&lt;br /&gt;
# Close Eclipse. &lt;br /&gt;
# Open the file &#039;&#039;&#039;net.sourceforge.phpeclipse.ui.prefs&#039;&#039;&#039; that is in the directory &#039;&#039;&#039;(your workspace)/.metadata/.plugins/org.eclipse.core.runtime/.settings&#039;&#039;&#039; in a text editor.&lt;br /&gt;
# Look for a line in the file that starts &#039;&#039;&#039;_php_include_paths=&#039;&#039;&#039; If it is not there, add it at the end.&lt;br /&gt;
# Change this line to say &#039;&#039;&#039;_php_include_paths=.&#039;&#039;&#039;&lt;br /&gt;
# Run Eclipse again.&lt;br /&gt;
&lt;br /&gt;
===SSH2===&lt;br /&gt;
Information about generating SSH2 keys for the purpose of connecting to cvs.moodle.org can be found here at https://docs.moodle.org/en/Development:SSH_key , but please finish reading this section before reading that material.&lt;br /&gt;
&lt;br /&gt;
The Eclipse installation has its own SSH client plugin so you do not have to use a separate ssh client in connection with your use of Eclipse (this is one reason you will be using extssh below,  instead of just ext,  however,  if you wish you may alter the configuration to use an external client but please post news of your success and configuration). See, http://www.jcraft.com/eclipse-cvsssh2/ , for additional information on this plugin.  &lt;br /&gt;
&lt;br /&gt;
Please note that Eclipse is fully equipped to generate ssh2 rsa and dsa keys as well as import keys.  You may encounter issues with passphrases that are too long (a bug reportedly fixed but which may still in fact be present) and some issues with using keypairs generated by other applications have been seen, so it may be best to generate a key pair with Eclipse. Additional details on how to do this will be added.&lt;br /&gt;
&lt;br /&gt;
See http://sourceforge.net/docs/F02/ has instructions on how to create a SSH key for it&#039;s CVS. This is mentioned by way of general explanation,  not for the purposes of instrucvtions on how to generate your keys for Eclipse.  Note that the public key generated will be for cvs.moodle.org (not sourceforge). To make use of the public key, login to Moodle.org and add it via the Update My Developer Information tab under CVS Developers (http://moodle.org/cvs). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===CVS Settings===&lt;br /&gt;
&lt;br /&gt;
These are all hidden under the &#039;&#039;&#039;Team&#039;&#039;&#039; bit of the tree.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team -&amp;gt; CVS -&amp;gt; SSH2 Connection Method&#039;&#039;&#039;, you can set up a public/private key pair. If you do this, you won&#039;t have to keep typing your password when doing CVS operations. &lt;br /&gt;
&lt;br /&gt;
The rest of the ones in this section are personal preferences, but I recommend them because the default settings are very irritating.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team&#039;&#039;&#039;, set &#039;&#039;&#039;Perspectives&#039;&#039;&#039; to &#039;&#039;&#039;None&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team -&amp;gt; CVS -&amp;gt; Annotate&#039;&#039;&#039; set &#039;&#039;&#039;Use Quick Diff annotate mode for local file annotations&#039;&#039;&#039; to &#039;&#039;&#039;Yes&#039;&#039;&#039;, and &#039;&#039;&#039;Open perspective after a &#039;Show Annotations&#039; operation&#039;&#039;&#039; to &#039;&#039;&#039;No&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team -&amp;gt; CVS -&amp;gt; Label Decorations&#039;&#039;&#039;, switch to the &#039;&#039;&#039;Icon Decorations&#039;&#039;&#039; tab and turn on all the settings, and then on the &#039;&#039;&#039;Text Decorations&#039;&#039;&#039; tab change both &#039;&#039;&#039;File Decoration&#039;&#039;&#039; and &#039;&#039;&#039;Folder Decoration&#039;&#039;&#039; to be just &#039;&#039;&#039;{name}&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
===Web and XML settings===&lt;br /&gt;
&lt;br /&gt;
Foreach XXX in CSS, HTML, Javascript, XML:&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Web and XML -&amp;gt; XXX Files -&amp;gt;XXX Source&#039;&#039;&#039;, choose &#039;&#039;&#039;Indent using spaces&#039;&#039;&#039; and &#039;&#039;&#039;indentation size&#039;&#039;&#039; 4.&lt;br /&gt;
&lt;br /&gt;
==Checking out the Moodle code==&lt;br /&gt;
&lt;br /&gt;
From the &#039;&#039;&#039;File&#039;&#039;&#039; menu, choose &#039;&#039;&#039;New -&amp;gt; Project ...&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
In the wizard that pops up, choose &#039;&#039;&#039;CVS -&amp;gt; Projects from CVS&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;&#039;Create a new repository location&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Fill in&lt;br /&gt;
&amp;lt;div style=&amp;quot;float: right; border: 1px solid orange; padding: 0 1em;&amp;quot;&amp;gt;&lt;br /&gt;
For anonymous CVS access use&lt;br /&gt;
;Host&lt;br /&gt;
:XX.cvs.moodle.org&lt;br /&gt;
where XX.cvs.moodle.org is one of [[CVS_for_Administrators#CVS_Servers|these mirrors]]&lt;br /&gt;
;Repository path&lt;br /&gt;
:/cvsroot/moodle&lt;br /&gt;
;User&lt;br /&gt;
:anonymous&lt;br /&gt;
;Password&lt;br /&gt;
:(leave blank)&lt;br /&gt;
;Connection type&lt;br /&gt;
:pserver&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
;Host&lt;br /&gt;
:cvs.moodle.org&lt;br /&gt;
;Repository path&lt;br /&gt;
:/cvsroot/moodle&lt;br /&gt;
;User&lt;br /&gt;
:(your Moodle CVS username)&lt;br /&gt;
;Password&lt;br /&gt;
:(if you set up the SSH2 key thing in preferences, leave this blank, otherwise, type in your Moodle CVS password.)&lt;br /&gt;
;Connection type&lt;br /&gt;
:extssh&lt;br /&gt;
(CVS experts, if you are confused by that last one, know it is an Eclipse-specific thing.) Then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
On the next screen of the Wizard, choose &#039;&#039;&#039;Use an existing module&#039;&#039;&#039;. Wait a moment, then select &#039;&#039;&#039;moodle&#039;&#039;&#039; from the list. Click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
On the next screen, make sure the option &#039;&#039;&#039;Check out as a project configured using the New Project Wizard&#039;&#039;&#039; is selected, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Refresh Tags&#039;&#039;&#039;, then choose the branch you want. For now leave it set to &#039;&#039;&#039;HEAD&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now you  will find yourself back at the start of the &#039;&#039;&#039;New Project&#039;&#039;&#039; Wizard. This is because of the option you chose three paragraphs ago. This time you should select &#039;&#039;&#039;PHP -&amp;gt; PHP Project&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Make up a project name. &#039;&#039;&#039;moodle&#039;&#039;&#039; would be sensible.&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Finish&#039;&#039;&#039;, and wait while all the moodle files are checked out of CVS.&lt;br /&gt;
&lt;br /&gt;
Once it has finished, it will probably ask you if you want to switch to the PHP perspective. Answer &#039;&#039;&#039;Yes&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you also need another branch (1.6, 1.7, 1.8, ...) repeat all the other steps with a few changes:&lt;br /&gt;
* This time you can choose &#039;&#039;&#039;Use an existing repository location&#039;&#039;&#039; instead of typing all the sourceforge CVS details again.&lt;br /&gt;
* Select the appropriate branch. If you don&#039;t see the branch you want, see [https://docs.moodle.org/en/Development:Setting_up_Eclipse#Resetting_the_branch_information this Troubleshooting tip].&lt;br /&gt;
* Use a different project name (e.g. moodle16, moodle17, etc.).&lt;br /&gt;
&lt;br /&gt;
==Let your development web server know where your files are==&lt;br /&gt;
&lt;br /&gt;
Either by editing you web server&#039;s config files, or using a symbolic link. Make sure your webserver can see your new working set of files at a sensible URL, so you can test the code you are working on.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Quick tour of some cool features, and remaining configuration changes==&lt;br /&gt;
&lt;br /&gt;
I find the default workbench setup is pretty good. Here is a quick guide to some of the bits.&lt;br /&gt;
&lt;br /&gt;
===Navigator===&lt;br /&gt;
&lt;br /&gt;
To the left is the &#039;&#039;&#039;Navigator&#039;&#039;&#039;. This is a tree view of all your files. If you double-click on a file, it opens in the editor in the middle. Try opening &#039;&#039;&#039;course/lib.php&#039;&#039;&#039; now. You will notice that it comes up nicely syntax-hightlighted.&lt;br /&gt;
&lt;br /&gt;
===Error highlighting===&lt;br /&gt;
&lt;br /&gt;
In the middle of the file, just type any old text, for example &amp;quot;I like Eclipse&amp;quot;. Obviously, this is not valid PHP syntax, and Eclipse will notice this, and put a red underline under it. Also, by the scrollbar is a ruler with a red mark in it to show the error.&lt;br /&gt;
&lt;br /&gt;
You will see some yellow marks lower down the ruler. There are warnings. Click on one, and you will be taken to where that warning is in the file. Hover your mouse over the warning, and you will get a tooltip explaining what the problem might be.&lt;br /&gt;
&lt;br /&gt;
Save the edited file. (Don&#039;t worry that it is broken, we&#039;ll clean up the mess later.) Notice that a red error marker is added to the file in the navigator, so you can see that there is a problem. Also, error markers are added to the course folder, and the whole project, so you could see there was an error even if the navigator tree was collapsed.&lt;br /&gt;
&lt;br /&gt;
You will probably find lots of warnings that the config.php file can&#039;t be found. In the navigator, find the file &#039;&#039;&#039;config-dist.php&#039;&#039;&#039;. Do &#039;&#039;&#039;Copy&#039;&#039;&#039; then &#039;&#039;&#039;Paste&#039;&#039;&#039; and choose to call the new file &#039;&#039;&#039;config.php&#039;&#039;&#039;. Edit this new config.php as normal. You should fine that most of the include file warnings have gone now.&lt;br /&gt;
&lt;br /&gt;
Notice also that there is another marker on each file icon. A little yellow cylinder on most files, but a white-on-brown star on the one you have edited. This is telling you the CVS status of each file. The brown stars are changes you have made but not checked in yet.&lt;br /&gt;
&lt;br /&gt;
===Outline===&lt;br /&gt;
&lt;br /&gt;
Over to the right is the Outline view. This shows a list of functions and classes defined in this file. By default, they are listed in the same order as in the file, but if you click on the &#039;&#039;&#039;az&#039;&#039;&#039; toolbar button, they are sorted into alphabetical order.&lt;br /&gt;
&lt;br /&gt;
Click on the function name &#039;&#039;&#039;add_course_module&#039;&#039;&#039; in the Outline. You will see that the editor scrolls to the definition of that function.&lt;br /&gt;
&lt;br /&gt;
===Code navigation===&lt;br /&gt;
&lt;br /&gt;
In that function, hover the mouse pointer over the function name &#039;&#039;&#039;insert_record&#039;&#039;&#039;. After a while, the documentation for that function will appear in a big tooltip.&lt;br /&gt;
&lt;br /&gt;
Hold down CTRL, move the mouse pointer over the function name &#039;&#039;&#039;insert_record&#039;&#039;&#039;, then click. Eclipse should load &#039;&#039;&#039;dmllib.php&#039;&#039;&#039;, and scroll you to where this function is defined.&lt;br /&gt;
&lt;br /&gt;
In the main Eclipse toolbar, there are forward and back arrows like in a web browser. Click back now to get back to &#039;&#039;&#039;course/lib.php&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
===Open resource===&lt;br /&gt;
&lt;br /&gt;
From the &#039;&#039;&#039;Navigate&#039;&#039;&#039; menu, choose &#039;&#039;&#039;Open Resource...&#039;&#039;&#039;. In the dialog that pops up, start typing a filename for instance type &#039;&#039;&#039;moodlel&#039;&#039;&#039;. In the box in the middle of the dialog, you will see it list all the files in the project whose names start that way. At the bottom is a box which lists the different folders that contain a file with that name. This can be a very quick way of opening files with fairly unique names like moodlelib.php, without having to click through the levels of the navigator tree. Of course, it is not so useful for an index.php file! Click OK now to open moodlelib.php. (It would actually work if you just did CTRL + Shift + R, moodlel, Enter.)&lt;br /&gt;
&lt;br /&gt;
===Multi-file search===&lt;br /&gt;
&lt;br /&gt;
Scroll down moodlelib a little bit, and double click on the name of the constant &#039;&#039;&#039;MOODLE_INTERNAL&#039;&#039;&#039; where it is defined, so that the text is selected. Then, from the &#039;&#039;&#039;Search&#039;&#039;&#039; menu, choose &#039;&#039;&#039;Search...&#039;&#039;&#039;. Notice that the &#039;&#039;&#039;Containing text&#039;&#039;&#039; box has already been filled in for you with the text you just selected. Of course you can just type text into this box without selecting it first. Notice that you can do regular expression searches, but leave that turned off for now. In the &#039;&#039;&#039;File name patterns&#039;&#039;&#039; box type &#039;&#039;&#039;*.css, *.html, *.inc, *.js, *.php, *.xml&#039;&#039;&#039;. (This is the most useful general setting for working on moodle. Eclipse will remember this setting, so you only have to enter it once.) Click &#039;&#039;&#039;Search&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The search results will appear in a new view underneath the editor. That view has a toolbar with yellow up and down arrows. Click the down arrow a few times and it will take you to the first few matches in the code, opening the relevant files as necessary.&lt;br /&gt;
&lt;br /&gt;
===Synchronize view===&lt;br /&gt;
&lt;br /&gt;
I think this is my favorite feature. From the &#039;&#039;&#039;Window&#039;&#039;&#039; menu, select &#039;&#039;&#039;Show View -&amp;gt; Other...&#039;&#039;&#039;. In the dialog that pops up, select &#039;&#039;&#039;Team -&amp;gt; Synchronize&#039;&#039;&#039;, then click &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
This opens the Synchronize view below the editor. The view has a toolbar. Click on the first toolbar button, which pops up the Synchronize wizard.&lt;br /&gt;
&lt;br /&gt;
On the first screen, there will probably only be one option: &#039;&#039;&#039;CVS&#039;&#039;&#039;. Make sure that is selected, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Scope&#039;&#039;&#039;, choose &#039;&#039;&#039;Workspace&#039;&#039;&#039;, then click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Wait while it talks to the CVS server. After a while, you will see that the Synchronize view lists course/lib.php, and something called &#039;&#039;&#039;.project.... That is, it is listing just the files you have edited, but not checked in yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;.project&#039;&#039;&#039; is something that belongs to Eclipse that we don&#039;t care about. So select it and bring up the context menu, and choose &#039;&#039;&#039;Add to .cvsignore...&#039;&#039;&#039;. In the dialog that pops up, choose the top option, then click &#039;&#039;&#039;OK&#039;&#039;&#039;. Then you will find the Synchronize view shows you a &#039;&#039;&#039;.cvsignore&#039;&#039;&#039; file that you aren&#039;t interested in, so add that to .cvsignore too!&lt;br /&gt;
&lt;br /&gt;
If you double-click on &#039;&#039;&#039;course/lib.php&#039;&#039;&#039; here, you will see that it opens the compare editor, which is a nice graphical display of the changes in this file.&lt;br /&gt;
&lt;br /&gt;
If you select a file or files here, then bring up the context menu, you will see the option to &#039;&#039;&#039;Commit...&#039;&#039;&#039; the changes. (But don&#039;t do that now!). This is the easiest way to commit things in Eclipse.&lt;br /&gt;
&lt;br /&gt;
However, our changes were rubbish, so we want to undo them. So open the context menu again, and choose &#039;&#039;&#039;Override and Update&#039;&#039;&#039;. This checks a clean copy of the file out of CVS, removing our changes.&lt;br /&gt;
&lt;br /&gt;
Note that the easiest way to do an ordinary CVS Update is to select the top-level project-folder in the Navigator view on the left, open the context menu, and choose &#039;&#039;&#039;Team -&amp;gt; Update&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
That&#039;s all the really important features. I sure you can learn everything else on your own. An you could always read the built in help!&lt;br /&gt;
&lt;br /&gt;
===Creating a patch===&lt;br /&gt;
&lt;br /&gt;
In the synchronise view, right click on an item (file or folder) and choose &#039;&#039;&#039;Create Patch...&#039;&#039;&#039;. Or in the navigator, right click on an item and choose &#039;&#039;&#039;Team -&amp;gt; Create Patch...&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
This brings up a two-page wizard. On the first page you can select where you want the patch made. For small patches it can be useful to create them on the clipboard, but normally you will want to save them in a file.&lt;br /&gt;
&lt;br /&gt;
On the second page, you can set some options, but normally you don&#039;t need to change the defaults which are &#039;&#039;&#039;Unified&#039;&#039;&#039; diff format, and Patch root set to &#039;&#039;&#039;Workspace&#039;&#039;&#039;. Well, sometimes it is helpful to change the second one to &#039;&#039;&#039;Project&#039;&#039;&#039; but it is not important.&lt;br /&gt;
&lt;br /&gt;
There is a corresponding apply patch wizard that you can use to apply a patch to a project.&lt;br /&gt;
&lt;br /&gt;
===Switching to another branch or version===&lt;br /&gt;
&lt;br /&gt;
Suppose you have been using a check-out of HEAD from CVS, and then as the 1.9 release approaches, the MOODLE_19_STABLE branch is created, and you want to start following that instead.&lt;br /&gt;
# Right click on the moodle project in the navigator view, and select &#039;&#039;&#039;Team -&amp;gt; Switch to Another Branch or Version ...&#039;&#039;&#039;.&lt;br /&gt;
# choose the second radio button: &#039;&#039;&#039;Select the tag from the following list&#039;&#039;&#039;.&lt;br /&gt;
# If the branch you want is not in the &#039;&#039;&#039;Matching tags&#039;&#039;&#039; box, see [[Setting_up_Eclipse#Resetting the branch information|Resetting the branch information]] below.&lt;br /&gt;
# Select the branch you want and click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
&lt;br /&gt;
Some tips on how to solve common problems that may crop up.&lt;br /&gt;
&lt;br /&gt;
===Resetting the branch information===&lt;br /&gt;
&lt;br /&gt;
Every now and then, Eclipse may lose information on the branch tags it knows about. Hitting refresh tags may fix it, but if not, try the following:&lt;br /&gt;
&lt;br /&gt;
#Bring up the tag dialogue (example using &amp;quot;Team / Switch to Another Branch or Version&amp;quot;).&lt;br /&gt;
#Click on Configure tags ... (not Refresh tags).&lt;br /&gt;
#Select config-dist.php in the top left box (if this is a Moodle checkout).&lt;br /&gt;
#Click Add Checked tags.&lt;br /&gt;
#Click OK.&lt;br /&gt;
#Then you will have all tags.&lt;br /&gt;
&lt;br /&gt;
(thanks to Tim Hunt)&lt;br /&gt;
&lt;br /&gt;
===Error loading php files after Ubuntu 7.04 Install===&lt;br /&gt;
&lt;br /&gt;
A java issue with Ubuntu 7.04 may cause an error when you attempt to load php pages. Refer to:&lt;br /&gt;
http://www.plog4u.org/index.php/Using_PHPEclipse_:_Installation_:_Installing_PHPEclipse for details about how to fix this in Ubuntu 7.04.&lt;br /&gt;
&lt;br /&gt;
After upgrading from Ubuntu 7.04 to 7.10, I had to go in and re-edit the /etc/eclipse/java_home file in order to get the CVS functions to work and be able to open PHP files. When I tried to do a CVS update I initially received an error about org.eclipse.team.internal.ccvs.ui.wizards.CheckoutWizard). Everything seemed to work again after reapplying the fix for the aforementioned 7.04 java issue.&lt;br /&gt;
&lt;br /&gt;
==Related Links==&lt;br /&gt;
&lt;br /&gt;
There is an excellent series of articles published by IBM on using Eclipse for Drupal developement here : [http://www-128.ibm.com/developerworks/ibm/osource/index.html Using open source software to design, develop, and deploy a collaborative Web site Tools and techniques for getting relatively complicated Web sites up and running quickly].&lt;br /&gt;
&lt;br /&gt;
[[Category:Setting up Eclipse]]&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/dev/index.php?title=Setting_up_Eclipse&amp;diff=4956</id>
		<title>Setting up Eclipse</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/dev/index.php?title=Setting_up_Eclipse&amp;diff=4956"/>
		<updated>2008-04-14T01:17:16Z</updated>

		<summary type="html">&lt;p&gt;Net-buoy: /* CVS Settings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.eclipse.org/ Eclipse] is an IDE originally designed for Java, but now with plugins for many languages including PHP. It has lots of very powerful features, and it is the editor that some Moodle developers like to use. Other (more) popular choices are vim and emacs.&lt;br /&gt;
&lt;br /&gt;
However, Eclipse is not the easiest program in the world to get started with, so I&#039;m going to take you through it step by step. These instructions assume Eclipse 3.2, the current version at the time of writing. It should not change much between releases.&lt;br /&gt;
&lt;br /&gt;
This article started off as a brain-dump by [[User:Tim Hunt|Tim Hunt]]. Since then, several other people have worked through it and made corrections, so the information here should be pretty accurate.&lt;br /&gt;
&lt;br /&gt;
==Prerequisites==&lt;br /&gt;
&lt;br /&gt;
Eclipse is written in Java, so I recommend getting the latest Java runtime environment from http://java.com/ for maximum speed and reliability.&lt;br /&gt;
&lt;br /&gt;
Eclipse is quite big, so I recommend lots of memory in your computer. I have used it on Windows, MacOS X and Linux, in each case with 1GB of memory, and that is plenty.&lt;br /&gt;
&lt;br /&gt;
==Installing Eclipse==&lt;br /&gt;
&lt;br /&gt;
Go to http://www.eclipse.org/downloads/. Click on the link corresponding to your operating system where it says &#039;&#039;&#039;Eclipse Classic&#039;&#039;&#039;. Choose a Mirror, and wait for the ~100MB download.&lt;br /&gt;
&lt;br /&gt;
You will notice that what you have got is a zip file (unless your system automatically decompresses it for you).&lt;br /&gt;
&lt;br /&gt;
On Windows, unzip it into &#039;&#039;&#039;C:\Program Files&#039;&#039;&#039; (all the files go into an &#039;&#039;&#039;Eclipse&#039;&#039;&#039; folder there). Then look in the Eclipse folder and drag Eclipse.exe to the Start menu/Desktop/Quicklaunch bar to make a shortcut for starting it.&lt;br /&gt;
&lt;br /&gt;
On MacOS, unzip and copy the Eclipse folder into Applications. Go into the Eclipse folder and drag the Eclipse app to the Dock for ease of launching.&lt;br /&gt;
&lt;br /&gt;
On Linux, unzip somewhere suitable, and make an easy way to launch it.&lt;br /&gt;
&lt;br /&gt;
==The first time you run Eclipse==&lt;br /&gt;
&lt;br /&gt;
The first time you launch Eclipse it does a bit of setup stuff, for instance, it create a &#039;&#039;&#039;workspace&#039;&#039;&#039;. This is where it stores the things you are working on. The default location is sensible on all platforms, so use that. &lt;br /&gt;
&lt;br /&gt;
For some reason, every time you start Eclipse, it asks you which workspace you want to use. I have never seen the need to have more than one, so I recommend turning on the checkbox that says &amp;quot;Use this as the default and do not ask again&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Another thing that happens the first time you run Eclipse is that you arrive at a welcome screen. This has links to various bits of help, which you can read if you like, but you probably don&#039;t need to if you are following these instructions. So find the button on the welcome page that closes it and gets you to the main Eclipse screen.&lt;br /&gt;
&lt;br /&gt;
==Installing the necessary plugins==&lt;br /&gt;
&lt;br /&gt;
By default, Eclipse comes with the Java tools. For everything else you will need to install some plugins.&lt;br /&gt;
&lt;br /&gt;
If you are sitting behind a web proxy, from the &#039;&#039;&#039;Window&#039;&#039;&#039; menu choose &#039;&#039;&#039;Preferences ...&#039;&#039;&#039;. Choose &#039;&#039;&#039;Install/Update&#039;&#039;&#039; from the tree view on the left, and enter the proxy information in the boxes on the right. If you aren&#039;t behind a proxy, ignore this step.&lt;br /&gt;
&lt;br /&gt;
From the &#039;&#039;&#039;Help&#039;&#039;&#039; menu choose &#039;&#039;&#039;Software Updates -&amp;gt; Find and Install&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
On the first screen of the wizard, make sure that &amp;quot;Search for new features to install&amp;quot; is selected, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The next screen is a list of upgrade sites to check. You need to add one to the list, so click the &#039;&#039;&#039;New Remote Site ...&#039;&#039;&#039; Button.&lt;br /&gt;
&lt;br /&gt;
In the pop-up dialog, give the remote site a name like &#039;&#039;&#039;PHPeclipse Update Site&#039;&#039;&#039;; set the URL to http://phpeclipse.sourceforge.net/update/releases/; then click &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note, there is now also another PHP editor for Eclipse. The update URL ishttp://download.eclipse.org/tools/pdt/updates/. I am just trying it--[[User:Tim Hunt|Tim Hunt]] 11:39, 7 November 2007 (CST)&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Back in the wizard, turn on just two things in the box &amp;quot;Sites to include in search&amp;quot;:&lt;br /&gt;
* Your newly created &#039;&#039;&#039;Phpeclipse Update Site&#039;&#039;&#039;; and&lt;br /&gt;
* the one called &#039;&#039;&#039;Europa Discovery Site&#039;&#039;&#039; (or possibly &#039;&#039;&#039;Callisto Discovery Site&#039;&#039;&#039;.&lt;br /&gt;
Then click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
It goes off sees what updates are available at those sites. As it does so, it may occasionally pop up a dialog asking you to choose a mirror. Each time, select a sensible one.&lt;br /&gt;
&lt;br /&gt;
Eventually, you get to a new wizard for selecting and installing the updates you want. The ones you want (you may have to search the tree structure) are, &#039;&#039;&#039;PHPeclipse&#039;&#039;&#039; (from your newly created PHPEclipse Update Site) and all the &#039;&#039;&#039;Web Standard Tools (WST)&#039;&#039;&#039; (usually under Callisto Discovery Site --&amp;gt; Web and J2EE Development).&lt;br /&gt;
&lt;br /&gt;
Next, and very importantly, you must click the &#039;&#039;&#039;Select Required&#039;&#039;&#039; button which should resolve dependencies and remove the warning message you are probably worrying about. Then you can click the &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
Read and agree to all the license agreements. Then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Finish&#039;&#039;&#039;, and wait for the plugins to download.&lt;br /&gt;
&lt;br /&gt;
Once the downloads have finished, a warning will pop-up telling you that all the plugins you downloaded are not digitally signed. The Eclipse Foundation build digital signing of plugins into their architecture as a security measure, and then did not sign any of their own plugins! Anyway, click the &#039;&#039;&#039;Install All&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
Finally, a window will pop up asking you to restart Eclipse. Do so.&lt;br /&gt;
&lt;br /&gt;
==Setting the preferences for Moodle development==&lt;br /&gt;
&lt;br /&gt;
Now go to the &#039;&#039;&#039;Window&#039;&#039;&#039; menu, and choose &#039;&#039;&#039;Preferences ...&#039;&#039;&#039; (&#039;&#039;&#039;Eclipse&#039;&#039;&#039; menu on Mac OS X).&lt;br /&gt;
&lt;br /&gt;
The Eclipse preferences are immense, with a tree view on the left, which selects which screen to display on the right. Don&#039;t panic, we&#039;ll guide you through it.&lt;br /&gt;
&lt;br /&gt;
===General settings===&lt;br /&gt;
&lt;br /&gt;
If you have strong feelings about fonts (I would hate to edit code an anything except Andale Mono), choose &#039;&#039;&#039;General -&amp;gt; Appearance -&amp;gt; Colors and Fonts&#039;&#039;&#039; from the tree on the left. Then on the right look under &#039;&#039;&#039;Basic&#039;&#039;&#039; and change &#039;&#039;&#039;Text Font&#039;&#039;&#039;. All the other editor font settings will inherit from this, so this is probably the only one you have to change.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;General -&amp;gt; Content Types&#039;&#039;&#039;, select PHP Source File, and add &#039;&#039;&#039;*.html&#039;&#039;&#039; to the box at the bottom.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;General -&amp;gt; Editors -&amp;gt; File Associations&#039;&#039;&#039;, if it is not already there, add &#039;&#039;&#039;*.php&#039;&#039;&#039; to the top box. With &#039;&#039;&#039;*.php&#039;&#039;&#039; selected in the top box, make sure &#039;&#039;&#039;PHP Editor&#039;&#039;&#039; is set to default in the bottom box. With &#039;&#039;&#039;*.html&#039;&#039;&#039; selected in the top box, select &#039;&#039;&#039;PHP Editor&#039;&#039;&#039; in the bottom box and click the &#039;&#039;&#039;Default&#039;&#039;&#039; button to change it, because in Moodle, most HTML files actually contain PHP code.&lt;br /&gt;
&lt;br /&gt;
If you use a web proxy, enter the details under &#039;&#039;&#039;Internet -&amp;gt; Proxy Settings&#039;&#039;&#039;. (Yes, I know you have entered them somewhere else before. Now you have to enter them again here. I don&#039;t know why. You just do.)&lt;br /&gt;
&lt;br /&gt;
===PHP Settings===&lt;br /&gt;
&lt;br /&gt;
These are all hidden under the &#039;&#039;&#039;PHPeclipse Web Development&#039;&#039;&#039; bit of the tree.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; Browser Preview Defaults&#039;&#039;&#039;, turn off both checkboxes.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP&#039;&#039;&#039;, on the &#039;&#039;&#039;Appearance&#039;&#039;&#039; tab, set &#039;&#039;&#039;Displayed tab width&#039;&#039;&#039; to 4.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP&#039;&#039;&#039;, on the &#039;&#039;&#039;Appearance&#039;&#039;&#039; tab, check &#039;&#039;&#039;Show line numbers&#039;&#039;&#039; to display line numbers in the left margin (optional). NOTE.- When you are editing a PHP file, you could left-click in the left margin and tick the &#039;&#039;&#039;Show Line Numbers&#039;&#039;&#039; line in the contextual menu. However, this toggle only applies to plain text files, &#039;&#039;not&#039;&#039; to HTML or PHP files. The only place where you can toggle line numbers on/off for such files is in the PHP/Appearance menu.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP&#039;&#039;&#039;, on the &#039;&#039;&#039;Typing&#039;&#039;&#039; tab, turn off all the options except &#039;&#039;&#039;Pasting for correct indentation&#039;&#039;&#039;, &#039;&#039;&#039;Insert spaces for tab&#039;&#039;&#039; and &#039;&#039;&#039;Close PHPdocs and comments&#039;&#039;&#039; and &#039;&#039;&#039;Remove trailing spaces on editor save&#039;&#039;&#039;. It would be nice to turn on more of these options, but most of the rest don&#039;t work very well.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP -&amp;gt; Formatter&#039;&#039;&#039;, on the &#039;&#039;&#039;New Lines&#039;&#039;&#039; tab, turn on &#039;&#039;&#039;Clear all blank lines&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP -&amp;gt; Formatter&#039;&#039;&#039;, on the &#039;&#039;&#039;Style&#039;&#039;&#039; tab, turn off &#039;&#039;&#039;Indentation is represented by a tab&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; PHP -&amp;gt; Templates&#039;&#039;&#039;, I like to define a new template to help with debugging:&lt;br /&gt;
;Name&lt;br /&gt;
:dump &lt;br /&gt;
;Description&lt;br /&gt;
:Dump a PHP variable&lt;br /&gt;
;Pattern&lt;br /&gt;
&amp;lt;pre&amp;gt;print_object(${word_selection}${cursor}); // DONOTCOMMIT&amp;lt;/pre&amp;gt;&lt;br /&gt;
You can do other useful things with templates too. Here are two more I use:&lt;br /&gt;
&amp;lt;pre&amp;gt;debugging(&amp;quot;&#039;${word_selection}${cursor}&#039;&amp;quot;); // DONOTCOMMIT&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;$$string[&#039;${word_selection}${cursor}&#039;] = &#039;.&#039;;&amp;lt;/pre&amp;gt;&lt;br /&gt;
That is, a simple debug message with a stack trace, and a new language string.&lt;br /&gt;
&lt;br /&gt;
There is a really stupid bug. Under &#039;&#039;&#039;PHPeclipse Web Development -&amp;gt; Project Defaults&#039;&#039;&#039;, you would like to add &amp;quot;.&amp;quot; to the &#039;&#039;&#039;Include Paths&#039;&#039;&#039;, but you can&#039;t using the GUI. You will have to edit one of the Eclipse config files by hand. So&lt;br /&gt;
# Note down the path to your Eclipse profile. On Windows it will be something like &#039;&#039;&#039;C:/Documents and settings/XXXX/workspace&#039;&#039;&#039;, and on Unixy systems something like &#039;&#039;&#039;~/workspace&#039;&#039;&#039;.&lt;br /&gt;
# Close Eclipse. &lt;br /&gt;
# Open the file &#039;&#039;&#039;net.sourceforge.phpeclipse.ui.prefs&#039;&#039;&#039; that is in the directory &#039;&#039;&#039;(your workspace)/.metadata/.plugins/org.eclipse.core.runtime/.settings&#039;&#039;&#039; in a text editor.&lt;br /&gt;
# Look for a line in the file that starts &#039;&#039;&#039;_php_include_paths=&#039;&#039;&#039; If it is not there, add it at the end.&lt;br /&gt;
# Change this line to say &#039;&#039;&#039;_php_include_paths=.&#039;&#039;&#039;&lt;br /&gt;
# Run Eclipse again.&lt;br /&gt;
&lt;br /&gt;
===CVS Settings===&lt;br /&gt;
&lt;br /&gt;
These are all hidden under the &#039;&#039;&#039;Team&#039;&#039;&#039; bit of the tree.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team -&amp;gt; CVS -&amp;gt; SSH2 Connection Method&#039;&#039;&#039;, you can set up a public/private key pair. If you do this, you won&#039;t have to keep typing your Sourceforge password when doing CVS operations. See http://sourceforge.net/docs/F02/ for the instructions on what people used to do when the CVS was at Sourceforge. However, If you follow the Sourceforge instructions now you will spend a good deal of time trying to add a public key to your sourceforge profile to no purpose; the key generated is for cvs.moodle.org, NOT, sourceforge,  and you add it via the Update My Developer Information tab on the moodle developers page at http://moodle.org/mod/cvsadmin/view.php?id=7134. Once you have uploaded your public key you can then try to fgure out how to make Eclipse use this keyset. &lt;br /&gt;
&lt;br /&gt;
The rest of the ones in this section are personal preferences, but I recommend them because the default settings are very irritating.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team&#039;&#039;&#039;, set &#039;&#039;&#039;Perspectives&#039;&#039;&#039; to &#039;&#039;&#039;None&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team -&amp;gt; CVS -&amp;gt; Annotate&#039;&#039;&#039; set &#039;&#039;&#039;Use Quick Diff annotate mode for local file annotations&#039;&#039;&#039; to &#039;&#039;&#039;Yes&#039;&#039;&#039;, and &#039;&#039;&#039;Open perspective after a &#039;Show Annotations&#039; operation&#039;&#039;&#039; to &#039;&#039;&#039;No&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Team -&amp;gt; CVS -&amp;gt; Label Decorations&#039;&#039;&#039;, switch to the &#039;&#039;&#039;Icon Decorations&#039;&#039;&#039; tab and turn on all the settings, and then on the &#039;&#039;&#039;Text Decorations&#039;&#039;&#039; tab change both &#039;&#039;&#039;File Decoration&#039;&#039;&#039; and &#039;&#039;&#039;Folder Decoration&#039;&#039;&#039; to be just &#039;&#039;&#039;{name}&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
===Web and XML settings===&lt;br /&gt;
&lt;br /&gt;
Foreach XXX in CSS, HTML, Javascript, XML:&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Web and XML -&amp;gt; XXX Files -&amp;gt;XXX Source&#039;&#039;&#039;, choose &#039;&#039;&#039;Indent using spaces&#039;&#039;&#039; and &#039;&#039;&#039;indentation size&#039;&#039;&#039; 4.&lt;br /&gt;
&lt;br /&gt;
==Checking out the Moodle code==&lt;br /&gt;
&lt;br /&gt;
From the &#039;&#039;&#039;File&#039;&#039;&#039; menu, choose &#039;&#039;&#039;New -&amp;gt; Project ...&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
In the wizard that pops up, choose &#039;&#039;&#039;CVS -&amp;gt; Projects from CVS&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Select &#039;&#039;&#039;Create a new repository location&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Fill in&lt;br /&gt;
&amp;lt;div style=&amp;quot;float: right; border: 1px solid orange; padding: 0 1em;&amp;quot;&amp;gt;&lt;br /&gt;
For anonymous CVS access use&lt;br /&gt;
;Host&lt;br /&gt;
:XX.cvs.moodle.org&lt;br /&gt;
where XX.cvs.moodle.org is one of [[CVS_for_Administrators#CVS_Servers|these mirrors]]&lt;br /&gt;
;Repository path&lt;br /&gt;
:/cvsroot/moodle&lt;br /&gt;
;User&lt;br /&gt;
:anonymous&lt;br /&gt;
;Password&lt;br /&gt;
:(leave blank)&lt;br /&gt;
;Connection type&lt;br /&gt;
:pserver&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
;Host&lt;br /&gt;
:cvs.moodle.org&lt;br /&gt;
;Repository path&lt;br /&gt;
:/cvsroot/moodle&lt;br /&gt;
;User&lt;br /&gt;
:(your sourceforge username)&lt;br /&gt;
;Password&lt;br /&gt;
:(if you set up the SSH2 key thing in preferences, leave this blank, otherwise, type in your Moodle CVS password.)&lt;br /&gt;
;Connection type&lt;br /&gt;
:extssh&lt;br /&gt;
(CVS experts, if you are confused by that last one, know it is an Eclipse-specific thing.) Then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
On the next screen of the Wizard, choose &#039;&#039;&#039;Use an existing module&#039;&#039;&#039;. Wait a moment, then select &#039;&#039;&#039;moodle&#039;&#039;&#039; from the list. Click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
On the next screen, make sure the option &#039;&#039;&#039;Check out as a project configured using the New Project Wizard&#039;&#039;&#039; is selected, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Refresh Tags&#039;&#039;&#039;, then choose the branch you want. For now leave it set to &#039;&#039;&#039;HEAD&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now you  will find yourself back at the start of the &#039;&#039;&#039;New Project&#039;&#039;&#039; Wizard. This is because of the option you chose three paragraphs ago. This time you should select &#039;&#039;&#039;PHP -&amp;gt; PHP Project&#039;&#039;&#039;, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Make up a project name. &#039;&#039;&#039;moodle&#039;&#039;&#039; would be sensible.&lt;br /&gt;
&lt;br /&gt;
Click &#039;&#039;&#039;Finish&#039;&#039;&#039;, and wait while all the moodle files are checked out of CVS.&lt;br /&gt;
&lt;br /&gt;
Once it has finished, it will probably ask you if you want to switch to the PHP perspective. Answer &#039;&#039;&#039;Yes&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you also need another branch (1.6, 1.7, 1.8, ...) repeat all the other steps with a few changes:&lt;br /&gt;
* This time you can choose &#039;&#039;&#039;Use an existing repository location&#039;&#039;&#039; instead of typing all the sourceforge CVS details again.&lt;br /&gt;
* Select the appropriate branch. If you don&#039;t see the branch you want, see [https://docs.moodle.org/en/Development:Setting_up_Eclipse#Resetting_the_branch_information this Troubleshooting tip].&lt;br /&gt;
* Use a different project name (e.g. moodle16, moodle17, etc.).&lt;br /&gt;
&lt;br /&gt;
==Let your development web server know where your files are==&lt;br /&gt;
&lt;br /&gt;
Either by editing you web server&#039;s config files, or using a symbolic link. Make sure your webserver can see your new working set of files at a sensible URL, so you can test the code you are working on.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Quick tour of some cool features, and remaining configuration changes==&lt;br /&gt;
&lt;br /&gt;
I find the default workbench setup is pretty good. Here is a quick guide to some of the bits.&lt;br /&gt;
&lt;br /&gt;
===Navigator===&lt;br /&gt;
&lt;br /&gt;
To the left is the &#039;&#039;&#039;Navigator&#039;&#039;&#039;. This is a tree view of all your files. If you double-click on a file, it opens in the editor in the middle. Try opening &#039;&#039;&#039;course/lib.php&#039;&#039;&#039; now. You will notice that it comes up nicely syntax-hightlighted.&lt;br /&gt;
&lt;br /&gt;
===Error highlighting===&lt;br /&gt;
&lt;br /&gt;
In the middle of the file, just type any old text, for example &amp;quot;I like Eclipse&amp;quot;. Obviously, this is not valid PHP syntax, and Eclipse will notice this, and put a red underline under it. Also, by the scrollbar is a ruler with a red mark in it to show the error.&lt;br /&gt;
&lt;br /&gt;
You will see some yellow marks lower down the ruler. There are warnings. Click on one, and you will be taken to where that warning is in the file. Hover your mouse over the warning, and you will get a tooltip explaining what the problem might be.&lt;br /&gt;
&lt;br /&gt;
Save the edited file. (Don&#039;t worry that it is broken, we&#039;ll clean up the mess later.) Notice that a red error marker is added to the file in the navigator, so you can see that there is a problem. Also, error markers are added to the course folder, and the whole project, so you could see there was an error even if the navigator tree was collapsed.&lt;br /&gt;
&lt;br /&gt;
You will probably find lots of warnings that the config.php file can&#039;t be found. In the navigator, find the file &#039;&#039;&#039;config-dist.php&#039;&#039;&#039;. Do &#039;&#039;&#039;Copy&#039;&#039;&#039; then &#039;&#039;&#039;Paste&#039;&#039;&#039; and choose to call the new file &#039;&#039;&#039;config.php&#039;&#039;&#039;. Edit this new config.php as normal. You should fine that most of the include file warnings have gone now.&lt;br /&gt;
&lt;br /&gt;
Notice also that there is another marker on each file icon. A little yellow cylinder on most files, but a white-on-brown star on the one you have edited. This is telling you the CVS status of each file. The brown stars are changes you have made but not checked in yet.&lt;br /&gt;
&lt;br /&gt;
===Outline===&lt;br /&gt;
&lt;br /&gt;
Over to the right is the Outline view. This shows a list of functions and classes defined in this file. By default, they are listed in the same order as in the file, but if you click on the &#039;&#039;&#039;az&#039;&#039;&#039; toolbar button, they are sorted into alphabetical order.&lt;br /&gt;
&lt;br /&gt;
Click on the function name &#039;&#039;&#039;add_course_module&#039;&#039;&#039; in the Outline. You will see that the editor scrolls to the definition of that function.&lt;br /&gt;
&lt;br /&gt;
===Code navigation===&lt;br /&gt;
&lt;br /&gt;
In that function, hover the mouse pointer over the function name &#039;&#039;&#039;insert_record&#039;&#039;&#039;. After a while, the documentation for that function will appear in a big tooltip.&lt;br /&gt;
&lt;br /&gt;
Hold down CTRL, move the mouse pointer over the function name &#039;&#039;&#039;insert_record&#039;&#039;&#039;, then click. Eclipse should load &#039;&#039;&#039;dmllib.php&#039;&#039;&#039;, and scroll you to where this function is defined.&lt;br /&gt;
&lt;br /&gt;
In the main Eclipse toolbar, there are forward and back arrows like in a web browser. Click back now to get back to &#039;&#039;&#039;course/lib.php&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
===Open resource===&lt;br /&gt;
&lt;br /&gt;
From the &#039;&#039;&#039;Navigate&#039;&#039;&#039; menu, choose &#039;&#039;&#039;Open Resource...&#039;&#039;&#039;. In the dialog that pops up, start typing a filename for instance type &#039;&#039;&#039;moodlel&#039;&#039;&#039;. In the box in the middle of the dialog, you will see it list all the files in the project whose names start that way. At the bottom is a box which lists the different folders that contain a file with that name. This can be a very quick way of opening files with fairly unique names like moodlelib.php, without having to click through the levels of the navigator tree. Of course, it is not so useful for an index.php file! Click OK now to open moodlelib.php. (It would actually work if you just did CTRL + Shift + R, moodlel, Enter.)&lt;br /&gt;
&lt;br /&gt;
===Multi-file search===&lt;br /&gt;
&lt;br /&gt;
Scroll down moodlelib a little bit, and double click on the name of the constant &#039;&#039;&#039;MOODLE_INTERNAL&#039;&#039;&#039; where it is defined, so that the text is selected. Then, from the &#039;&#039;&#039;Search&#039;&#039;&#039; menu, choose &#039;&#039;&#039;Search...&#039;&#039;&#039;. Notice that the &#039;&#039;&#039;Containing text&#039;&#039;&#039; box has already been filled in for you with the text you just selected. Of course you can just type text into this box without selecting it first. Notice that you can do regular expression searches, but leave that turned off for now. In the &#039;&#039;&#039;File name patterns&#039;&#039;&#039; box type &#039;&#039;&#039;*.css, *.html, *.inc, *.js, *.php, *.xml&#039;&#039;&#039;. (This is the most useful general setting for working on moodle. Eclipse will remember this setting, so you only have to enter it once.) Click &#039;&#039;&#039;Search&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The search results will appear in a new view underneath the editor. That view has a toolbar with yellow up and down arrows. Click the down arrow a few times and it will take you to the first few matches in the code, opening the relevant files as necessary.&lt;br /&gt;
&lt;br /&gt;
===Synchronize view===&lt;br /&gt;
&lt;br /&gt;
I think this is my favorite feature. From the &#039;&#039;&#039;Window&#039;&#039;&#039; menu, select &#039;&#039;&#039;Show View -&amp;gt; Other...&#039;&#039;&#039;. In the dialog that pops up, select &#039;&#039;&#039;Team -&amp;gt; Synchronize&#039;&#039;&#039;, then click &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
This opens the Synchronize view below the editor. The view has a toolbar. Click on the first toolbar button, which pops up the Synchronize wizard.&lt;br /&gt;
&lt;br /&gt;
On the first screen, there will probably only be one option: &#039;&#039;&#039;CVS&#039;&#039;&#039;. Make sure that is selected, then click &#039;&#039;&#039;Next &amp;gt;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Under &#039;&#039;&#039;Scope&#039;&#039;&#039;, choose &#039;&#039;&#039;Workspace&#039;&#039;&#039;, then click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Wait while it talks to the CVS server. After a while, you will see that the Synchronize view lists course/lib.php, and something called &#039;&#039;&#039;.project.... That is, it is listing just the files you have edited, but not checked in yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;.project&#039;&#039;&#039; is something that belongs to Eclipse that we don&#039;t care about. So select it and bring up the context menu, and choose &#039;&#039;&#039;Add to .cvsignore...&#039;&#039;&#039;. In the dialog that pops up, choose the top option, then click &#039;&#039;&#039;OK&#039;&#039;&#039;. Then you will find the Synchronize view shows you a &#039;&#039;&#039;.cvsignore&#039;&#039;&#039; file that you aren&#039;t interested in, so add that to .cvsignore too!&lt;br /&gt;
&lt;br /&gt;
If you double-click on &#039;&#039;&#039;course/lib.php&#039;&#039;&#039; here, you will see that it opens the compare editor, which is a nice graphical display of the changes in this file.&lt;br /&gt;
&lt;br /&gt;
If you select a file or files here, then bring up the context menu, you will see the option to &#039;&#039;&#039;Commit...&#039;&#039;&#039; the changes. (But don&#039;t do that now!). This is the easiest way to commit things in Eclipse.&lt;br /&gt;
&lt;br /&gt;
However, our changes were rubbish, so we want to undo them. So open the context menu again, and choose &#039;&#039;&#039;Override and Update&#039;&#039;&#039;. This checks a clean copy of the file out of CVS, removing our changes.&lt;br /&gt;
&lt;br /&gt;
Note that the easiest way to do an ordinary CVS Update is to select the top-level project-folder in the Navigator view on the left, open the context menu, and choose &#039;&#039;&#039;Team -&amp;gt; Update&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
That&#039;s all the really important features. I sure you can learn everything else on your own. An you could always read the built in help!&lt;br /&gt;
&lt;br /&gt;
===Creating a patch===&lt;br /&gt;
&lt;br /&gt;
In the synchronise view, right click on an item (file or folder) and choose &#039;&#039;&#039;Create Patch...&#039;&#039;&#039;. Or in the navigator, right click on an item and choose &#039;&#039;&#039;Team -&amp;gt; Create Patch...&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
This brings up a two-page wizard. On the first page you can select where you want the patch made. For small patches it can be useful to create them on the clipboard, but normally you will want to save them in a file.&lt;br /&gt;
&lt;br /&gt;
On the second page, you can set some options, but normally you don&#039;t need to change the defaults which are &#039;&#039;&#039;Unified&#039;&#039;&#039; diff format, and Patch root set to &#039;&#039;&#039;Workspace&#039;&#039;&#039;. Well, sometimes it is helpful to change the second one to &#039;&#039;&#039;Project&#039;&#039;&#039; but it is not important.&lt;br /&gt;
&lt;br /&gt;
There is a corresponding apply patch wizard that you can use to apply a patch to a project.&lt;br /&gt;
&lt;br /&gt;
===Switching to another branch or version===&lt;br /&gt;
&lt;br /&gt;
Suppose you have been using a check-out of HEAD from CVS, and then as the 1.9 release approaches, the MOODLE_19_STABLE branch is created, and you want to start following that instead.&lt;br /&gt;
# Right click on the moodle project in the navigator view, and select &#039;&#039;&#039;Team -&amp;gt; Switch to Another Branch or Version ...&#039;&#039;&#039;.&lt;br /&gt;
# choose the second radio button: &#039;&#039;&#039;Select the tag from the following list&#039;&#039;&#039;.&lt;br /&gt;
# If the branch you want is not in the &#039;&#039;&#039;Matching tags&#039;&#039;&#039; box, see [[Setting_up_Eclipse#Resetting the branch information|Resetting the branch information]] below.&lt;br /&gt;
# Select the branch you want and click &#039;&#039;&#039;Finish&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
&lt;br /&gt;
Some tips on how to solve common problems that may crop up.&lt;br /&gt;
&lt;br /&gt;
===Resetting the branch information===&lt;br /&gt;
&lt;br /&gt;
Every now and then, Eclipse may lose information on the branch tags it knows about. Hitting refresh tags may fix it, but if not, try the following:&lt;br /&gt;
&lt;br /&gt;
#Bring up the tag dialogue (example using &amp;quot;Team / Switch to Another Branch or Version&amp;quot;).&lt;br /&gt;
#Click on Configure tags ... (not Refresh tags).&lt;br /&gt;
#Select config-dist.php in the top left box (if this is a Moodle checkout).&lt;br /&gt;
#Click Add Checked tags.&lt;br /&gt;
#Click OK.&lt;br /&gt;
#Then you will have all tags.&lt;br /&gt;
&lt;br /&gt;
(thanks to Tim Hunt)&lt;br /&gt;
&lt;br /&gt;
===Error loading php files after Ubuntu 7.04 Install===&lt;br /&gt;
&lt;br /&gt;
A java issue with Ubuntu 7.04 may cause an error when you attempt to load php pages. Refer to:&lt;br /&gt;
http://www.plog4u.org/index.php/Using_PHPEclipse_:_Installation_:_Installing_PHPEclipse for details about how to fix this in Ubuntu 7.04.&lt;br /&gt;
&lt;br /&gt;
After upgrading from Ubuntu 7.04 to 7.10, I had to go in and re-edit the /etc/eclipse/java_home file in order to get the CVS functions to work and be able to open PHP files. When I tried to do a CVS update I initially received an error about org.eclipse.team.internal.ccvs.ui.wizards.CheckoutWizard). Everything seemed to work again after reapplying the fix for the aforementioned 7.04 java issue.&lt;br /&gt;
&lt;br /&gt;
==Related Links==&lt;br /&gt;
&lt;br /&gt;
There is an excellent series of articles published by IBM on using Eclipse for Drupal developement here : [http://www-128.ibm.com/developerworks/ibm/osource/index.html Using open source software to design, develop, and deploy a collaborative Web site Tools and techniques for getting relatively complicated Web sites up and running quickly].&lt;br /&gt;
&lt;br /&gt;
[[Category:Setting up Eclipse]]&lt;/div&gt;</summary>
		<author><name>Net-buoy</name></author>
	</entry>
</feed>