Table of Contents

Joomla Content Management System

Security

You should secure the admin area with .htaccess.

Edit the 'allow' line for your needs:

cd administrator

cat << EOF >> .htaccess
# Limit access by IP address or range
<Limit GET POST PUT>
  order deny,allow
  deny from all
  allow from 123.123.123.123 234.234.234.234
</Limit>
EOF

SME Server 8

http://forums.contribs.org/index.php?topic=48816.0

PHP Temporary Locations

mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
cd /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
cp /etc/e-smith/templates/etc/httpd/conf/httpd.conf/95AddType00PHP2ibays .

Edit the custom-template and add the three lines preceded by “+” below:

vim 95AddType00PHP2ibays

Add the three lines:

                my $basedir = $ibay->prop('PHPBaseDir')
                    || ("/home/e-smith/files/ibays/" . $ibay->key . "/");
                $OUT .= "    php_admin_value open_basedir $basedir\n";
+                my $tmpdir = $ibay->prop('PHPTmpDir')
+                    || ("/home/e-smith/files/ibays/" . $ibay->key . "/tmp");
+                $OUT .= "    php_admin_value upload_tmp_dir $tmpdir\n";
                $OUT .= "</Directory>\n";

Lastly, create the 'tmp' folder and reset all the permissions:

mkdir -p /home/e-smith/files/ibays/website/tmp
signal-event remoteaccess-update
signal-event ibay-modify <website-ibay-name>

Developement

Moving From Subdirectory to Main

http://www.drostdesigns.com/move-joomla-to-root-of-same-server-how-to-transfer-a-joomla-site-to-a-different-directory/

Migration

http://cyend.com/extensions/extensions/components/documentation/24-user-guide-how-to-migrate-to-joomla-16

http://www.ostraining.com/blog/joomla/sp-upgrade/

Migration Process

  1. Install Joomla 2.5 in a subdirectory
  2. Make the migration from 1.5 to the new 2.5 site
  3. Deal with third party extensions
  4. Deal with template issues
  5. Go live with the new site
  6. Move the 2.5 site from the subdirectory to the main directory

JOOMLA 2.5 MIGRATION STEPS

INITIAL INSTALL Create new MySQL Database and User for 2.5 Create dev.xxxxxx development subdomain Download newest RocketLauncher for the selected template Install the 2.5 site in the dev subdomain Update the Joomla software to latest version (0.5hrs to this point) Install Akeeba, JCE, RSFirewall and RSSEO Install Mission Control from standard installer rather than Akeeba enhanced one Install update license codes for Akeeba, RSFirewall, etc. Update the addons to latest version Run configuration of Akeeba, RSFirewall, etc. Enable Mission Control Do Backup of full fresh install

REMOVE UNNEEDED CONTENT - 2.5 DEV SITE Leave Home menu item alone since it can't be deleted Trash and then Empty Trash most Articles, Menu Items and Modules Purge Caches Do Backup of cleared-out site (1.25hrs to this point)

PREPARE 1.5 SITE Back-up site Perform any needed updates Trash and then Empty Trash any UNUSED Articles, Menu Items and Modules. This step is usually performed on new sites, but there may be some sites that stuff have unused content on them.

MIGRATION Install SPUpgrade addon in dev 2.5 site Go to Options and input the database info for the 1.5 site Database Type: Check configuration.php to see whether to use MySQL or MySQLi (?) Host: localhost or host url with no http: Database Name: Source DB Name with prefix User Name: Source DB User with prefix Password: Source DB User password Database Tables Prefix: On older installs, usually jos_ but check configuration.php to confirm Source Path: Usually /home/public_html can't be used unless both sites are on the same server. YOU MAY have to transfer the images folder separately if the database is not located on localhost Back up site once the connection to the database is confirmed DON'T transfer the registered user Note any transfer errors CLEAN UP Reassign modules to the correct pages Install updated addons and plugins Compare the sites side-by-side to ensure everything is present and working * TROUBLESHOOTING * You may see H1 page titles showing up above the article title. This is a result of the SPUpdate migration. Save and Close each menu item to clear the problem.