|
How to Remove Genrated by Joomla |
 |
 |
 |
|
Friday, 15 August 2008 23:15 |
So you want to remove the geneerated tag
<meta name="generator" content="Joomla! 1.5 - Open Source Content Management">
Personaly, I think you should leave the joomla code, I mean after all give credit to the CMS
Many may find the inclusion of this meta tag to be inappropriate for their website. However, determining how to remove it is surprisingly difficult. Here is the recommended solution:
in your template, add the following above the <head> tag:
<?php $this->setGenerator('Anything you want or leave empty'); ?>
thats it!
you can also edit the core joomla file, however this change will be lost if you upgrade the site!
The file you want to edit is called head.php and is found here:
/libraries/joomla/document/html/renderer/head.php
you will want to find the following code (~line 167):
$strHtml .= $tab.'<meta name="generator" content="'.$document->getGenerator().'" />'.$lnEnd;
you can turn it off by simply commenting the line with // at the beginning:
//$strHtml .= $tab.'<meta name="generator" content="'.$document->getGenerator().'" />'.$lnEnd; |
|
Last Updated on Friday, 15 August 2008 23:38 |
|
Help! I just got hacked and cant login to admin! |
|
|
|
|
Wednesday, 13 August 2008 15:54 |
|
If you know the email address that was used, the simplest thing is to do is to use the "lost password" Front-end function if you have made it available.
You can also watch the video we have on how to do this.
If not, you will need access to the MySQL database.
You have two choices, either add a new super administrator or change the password stored in the data base. To do this you need to go to phpMyAdmin (or use a similar tool) and manually edit the database. Before doing this back up our complete database.
Run this to create a new user known as admin2.
INSERT INTO `jos_users` VALUES
(62, 'Administrator2', 'admin2', 'your...@email.com', '21232f297a57a5a743894a0e4a801fc3',
'Super Administrator', 0, 1, 25, '2005-09-28 00:00:00', '2005-09-28 00:00:00', '', '');
INSERT INTO `jos_core_acl_aro` VALUES (10,'users','62',0,'Administrator2',0);
INSERT INTO `jos_core_acl_groups_aro_map` VALUES (25,'',10);
The password will be admin. Immediately log in and change this password.
Or
You can change the password in the table for your admin user (assuming you never changed the user name; if you have just change the instructions below to .
The password is stored in the MySQL database jos_users table password field. (change this for your table prefix if different)
Open the table, find your admin username, and then select that row for editing.
The password must be hashed, you cannot simply enter text into this field.
Set the password to a known value
- password = "this is the MD5 hashed password"
------------------------------------------------------
- admin = 21232f297a57a5a743894a0e4a801fc3
- secret = 5ebe2294ecd0e0f08eab7690d2a6ee69
- OU812 = 7441de5382cf4fecbaa9a8c538e76783
Paste the hashed password into the field, save the change, and log-in using the new password. Immediately change your password to something more secure!
You interested in having your Joomla 1.5.x site automaticly updated for you? If so check out this |
|
Last Updated on Wednesday, 20 August 2008 00:23 |
|
|
Migrating from 1.0.x to 1.5 Stable |
|
|
|
|
Wednesday, 13 August 2008 12:36 |
Migrating from 1.0.x to 1.5 Stable
from joomla.org
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.
Prerequisites
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 1.1. 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 separate 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. You need to install '1.5 into a completely new directory, you should keep this separate to your 1.0 directory. If you just unzip over the top of your existing 1.0 site, you will have issues with it finding an invalid copy of the configuration.php" file, so either move your original install or create a new directory. 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.
Please note you also need to tick the "This script is a Joomla! 1.0 migration script" box as well before you migrate otherwise you will have issues with importing data. |
|
Upgrading 1.5 from an existing 1.5x version |
|
|
|
|
Wednesday, 13 August 2008 12:30 |
Upgrading 1.5 from an existing 1.5x version
It is risky to upgrade a live site without testing the upgrade process first. So before upgrading the live site you need to set up a test site which is as close as possible to the configuration of your live site, then test the upgrade on that. When you are happy with the process you can apply it to the live site (having taken a fresh backup of the live site first, of course).
You interested in having your Joomla 1.5.x site automaticly updated for you? If so check out this
Step 1: Download the patch package
To download the most recent patch package and to obtain the MD5 hash:
- From the joomla.org home page, click the Joomla! 1.5.x download link
- On the Joomla! 1.5.x release page, click the Joomla!1.5.xupdates link in the left column.
- Click the word Files in the blue bar to expand the list of patch packages available.
- Locate the row that matches your current installation version.
- On that row, select the patch package (zip, tar.gz and tar.bz2) that is most convenient for you.
- Verify the download using the MD5 hash listed in the right column on the same line as the package you selected.
If you have questions about these instructions, read the Additional Information below this table.
Additional information:
Step 2: Make a copy of your live site
Ideally this should be on the same platform (operating system, PHP and database version) as the live site, but don't worry if this is not possible. Making a working copy of a Joomla! website involves copying the files and the database (these are separate activities). You will then need to amend the configuration.php to reflect the new location. Check that your test site is fully functional.
Step 3: Install the patch package on the copy site
There are different ways of installing a package file depending on your particular circumstances. If you have difficulty with one of these methods, then simply try another.
- Alternative 1: Unpack the package file on your local computer then use an FTP client to upload them to your site.
- Alternative 2: Use an FTP client to upload the package to your site, then use a terminal session (eg. SSH) to connect to your site and unpack the files there.
- Alternative 3: If your hosting provider gives you access to your site via some sort of web control panel like CPanel or Plesk, you can use the control panel file manager to upload the package, then use a terminal session (which might also be available via the control panel) to unpack the package file and overwrite all changed files on the server.
Step 4: Test thoroughly
Check out as much of the functionality on your test site as possible. If there are any problems that will affect the way that you will need to handle the live upgrade then make a written note of them for later.
If you find errors you might check out the following possibilities:
- Ensure that all of the files were properly transferred. There have been verified reports of some FTP clients not properly transferring files across to a server without notifying the user of such a problem. One possible cause of this problem is that under certain circumstances the web server locks the files it is using and the FTP-server can't update those files. If this is the case you might try taking the site offline shortly during the FTP transfer.
Step 5: Backup your live site
Take a full backup copy of your live site immediately prior to upgrading. You may want to take your site offline prior to doing this so that updates are not lost.
Step 6: Install the patch package on your live site
There are different ways of installing a package file depending on your particular circumstances. If you have difficulty with one of these methods, then simply try another.
- Alternative 1: Unpack the package file on your local computer then use an FTP client to upload them to your site.
- Alternative 2: Use an FTP client to upload the package to your site, then use a terminal session (eg. SSH) to connect to your site and unpack the files there.
- Alternative 3: If your hosting provider gives you access to your site via some sort of web control panel like CPanel or Plesk, you can use the control panel file manager to upload the package, then use a terminal session (which might also be available via the control panel) to unpack the package file and overwrite all changed files on the server.
The alternative selected may be different from that used in step 3 if the hosting platform for the site is different.
Step 7: Make any other changes required
Referring to your notes from step 4, make any other changes that are required to bring the site into operation following the patch installation.
Step 8: Check your live site to make sure it is working correctly
Don't assume that the upgrade will work flawlessly just because the test upgrade worked. Check to make sure that nothing untoward has happened. It could be that differences between the live site and test site platforms will bring out a problem that you did not notice during testing. If you find a problem and it cannot be resolved quickly you might have to rollback the upgrade using the backup copy you created in step 5.
Hopefully all will be well and you can relax |
|
Last Updated on Wednesday, 03 September 2008 19:13 |
|
