February 17, 2010
January 27, 2008
You do not need to download Moodle to your local PC. On your SiteGround Hosting account Moodle CMS can be easily installed through our Fantastico Autoinstaller in just several clicks! In order to do that, please, locate the Fantastico icon in the cPanel's home page. Find the Moodle link.
Now choose the location of your Moodle CMS - if you would like to have it as your site front, leave the directory box blank, otherwise fill in the appropriate folder name. Next, fill in the administrator details and click the Install button.
Click the confirmation button on the next page, and then you will see the success notice on the third page.
Add the addresses from the success notice page to your bookmarks, since you will be using them often.
January 26, 2008
Welcome to the Joomla! 1.5 Template Tutorials Project. Here you will find information about how we are going about writing these fabulous new tutorials. If you would like to volunteer to lend us a hand then please send an email to Chris Davenport.
Consult the User's Guide for information on using the wiki software.
New or potential contributors to this project should read the Introduction to the Template Tutorials Project. The process of writing the new template tutorials is also an experiment in single source modular documentation. The idea is that we write the material in "fragments" or "chunks" which can be re-used in a variety of contexts. In order for this to work, we need to write the chunks in a context-free manner so that they can be assembled into different output documents in any sequence. In other words we need to ensure that each chunk still makes sense even when taken out of context.
The following is the current Table of Contents for the Template Tutorials:- Tutorial:Table of Contents
How to do stuff
Stuff you need to refer to
- Outline of the Template Tutorials
- This has been produced as a starting point. The tutorials listed on the main page show how one document can been produced by automatically assembling, on the fly, fragments which are stored and managed as individual wiki pages. Click on the Edit tab and see how the source for each of these tutorials is simply a list of references to modules. There is no actual content in any of them.
- Template Tutorial Guidelines
- These guidelines will help us to keep some consistency over all the tutorials where multiple authors are working on different sections of the material. They will be continuously revised and refined in the light of experience.
- Who is working on what
- If you want to work on one or more pages of the documentation then please update this page so we don't get duplication of effort. If you want to collaborate with someone on one or more pages, that's fine too of course; you can use this page to find out who to contact.
The following sections on this page list category pages for all the principal categories required for the Template Tutorials Project. You can use these pages to help you find a suitable module to include (or rather transclude) into a compound document. You can't create new chunk pages using these pages.
Contents by Chunk Type
- Primary chunks (listed alphabetically)
- Definition lists
- These are most commonly used to list components, so for example, we might create a definition list which lists the names of the principal files contained within a template and introduce the purpose of each.
- These are a specific form of definition list that defines technical terms.
- These are step-by-step instructions that explain how to perform tasks.
- These are similar to procedures and topics. Processes differ from procedures in that they are narrative rather than imperative. They explain what someone or something does (declarative), not what users should do (imperative).
- These are texts that answer specific questions.
- Troubleshooting scenarios
- These are a hybrid of topics and procedures. Each scenario explains one problem and its solution.
- Definition lists
Secondary chunks are always included into primary chunks. They are never used directly. Secondary chunks can be constructed separately, although they don't have to be. For example, figures will probably be constructed using a separate graphics package and may well be produced by a graphic artist working independently within the documentation team. Secondary chunks can be re-used within different primary chunks. Documents are assembled from primary chunks only; secondary chunks must be integrated into primary chunks before they are used.
Contents by User Experience Level
Contents by Joomla! Resource Type
January 25, 2008
The migration from Joomla! 1.0 to 1.5 is handled for the most part automatically in two stages. The first stage is the export migration component for Joomla! 1.0 and the second stage is the import or migration phase of the Joomla! 1.5 installer. The system is automated due to a large number of changes that make data slightly incompatible between Joomla! 1.0 and 1.5, such as parameters for menus and content items. Whilst it is still possible to use a database dump to migrate, this is not advised as there will be data loss. This page aims to detail how to migrate from Joomla! 1.0 to Joomla! 1.5 with as much ease as possible.
Note: Read all of this document first and test before you attempt this in your production site to minimise down time.
You will need a working Joomla! install, though using the latest available release of Joomla! 1.0 is always the best option. It is suggested that if you are using 1.0.13 you install Rob Schley's patch for admin sessions. As with everything you should take a full backup of everything before you start just in case something does go wrong. We advise that you do not destroy your 1.0.x install until you have completely finished migrating to 1.5 and are happy that things are working properly. Ideally you should complete migration using a testing system first before attempting it on your production system (e.g. either by using sites restored from backups or other replicas) and when deploying, separate your 1.0.x install from 1.5 (e.g. different database or at the least a different prefix).
Step 1: Downloading the Migrator component and installing it into your 1.0 instance
The latest version of the migrator component exists at the Pasamio Project's FRS site. At the time of writing the latest release is Migrator RC5. Download the Migrator component to your system and then install it into the 1.0 install. This is done like any normal component install. There will be a Migrator entry in the Component menu option where you can access the Migrator.
Step 2: Installing Third Party Migrator plugins
The Migration system only handles the core system in its migration which means that if you want to include third party extension data from other tables you will have to install migrator plugins to handle the migration of this data. There are two types of plugins that are used: an "SQL" plugin which is a plain text SQL file and an "ETL" Plugin which is a bit of PHP that tells the migrator how to handle the data stored in tables (or in configuration files). This is done by selecting "Add Third Party Migrators", and then locating the plugin you wish to install and uploading the file. SQL files will be prepended to the output automatically and ETL plugins will be executed automatically. You can view a list of ETL plugins by clicking "List Plugins" in the main screen.
Step 3: Creating the Migration SQL File
Once you have installed any third party migrator plugins, you can select the "Create Migration SQL file" to begin the creation process. The system is designed to build an SQL file without causing a timeout on the server, so you may notice that the page automatically refreshes and displays status information. Eventually it will display a notification that the process has been completed and the SQL file will be available for download. Part of the SQL file generation involves the alteration of various fields to make them compatible with changes made in Joomla! 1.5, including the rewriting of mosimage tags.
Step 4: Installing Joomla! 1.5
Note: Create your new Joomla! 1.5 install in a seperate directory and database to your existing install (or different prefix if you cannot create a new database). You cannot extract over the top of your 1.0 install, you have to create a new Joomla! 1.5 site. Alternatively, move your 1.0 install to a safe location and install into the empty directory 1.0 will have created.
Note: It is not a very good idea to install a new Joomla! 1.5 site over the top of your existing 1.0 site, it is better to test things in a seperate directory and progress from there.
If you haven't done so already, take a full back up of your 1.0 site, including all of the filesystem and the database.
The last phase of the migration is the installation of a new Joomla! 1.5 site. Complete the initial steps of the installation as per a normal installation. In the final step where you are prompted for the site name you are given the opportunity to initiate the migration process. Migration requires the generated SQL file to complete its operation, which might need to be uploaded to your new 1.5 site, there are two options for doing this:
- HTTP Upload
- FTP/SCP Upload
The first method, HTTP upload, is best for smaller SQL files that will fit within the upload limits of PHP. The alternative is to upload a file using either FTP, SCP or some other method of file transfer that your hosting provider offers. This is useful for larger SQL files that would normally not be permitted by PHP. To use the HTTP method, simply select the file like a normal component installation. To use the alternative upload method, upload the files into the installation/sql/migration folder and rename the file to be called "migrate.sql". If for some reason the migration fails you will need to reupload the SQL file for both methods, HTTP and FTP/SCP, as the file is altered through the migration process. The prefix for all migration dumps is "jos_", this should be placed into the provided text box. Once migration has been completed, enter in a site name (the site name cannot be migrated for technical reasons) and finish the installation.
Using either method the "/installation/sql/migration" folder and your temporary files folder (e.g. "/tmp") need to be writeable by the web user (e.g. "wwwrun", "www-data" or "apache"). The migrator will write data back to these locations as it updates the dump files.
Return to Upgrade Instructions