Step 1 – Enable the module(s)
. Go to ‘admin/build/modules/list’ and at the very bottom is the ‘XML
Sitemap’ module.
. Tick the first ‘XML Sitemap’ and the ‘XML sitemap node’ module.
. You might want to look at the ‘XML sitemap engines’ module, as it
submits to search engines, etc. I won’t turn it on here as it’s not what we
want to do on the test site.
. Press ‘Save Configuration’ at the bottom of the page.

Step 2 – Enable the ‘content types’ we want the ‘XML sitemap node’ module to
pick-up. (this is the bit that was causing the problem).
. Go to ‘admin/content/types/list’
. You’ll need to decide ‘which’ to activate, but for example, use
‘Tabbed Page’. Press the ‘edit’ link.
. At the bottom of the next page you’ll see ‘XML sitemap’ which opens
up to show 2 dropdown menus.
o Inclusion – allows you to turn on/off
o Default priority – allows you to choose a level. You probably know
more about the ‘correct’ level than I do.
. Press ‘Save content type’ to save.
. Do the same for all of the ‘content types’ you want to be shown.

Step 3 – Sitemap Settings
. Go to ‘admin/settings/xmlsitemap’
. Under the settings set the ‘minimum sitemap lifetime’ to 1 day as
they recommend.
. Drop down ‘Content’ and you’ll see a list of ‘content types’ along
with numbers to represent how many are ‘available’, ‘indexed’, and visible’.

. If ‘indexed’ and ‘visible’ are at zero, you’ll need to run cron
(which normally happens every hour), or use the ‘Rebuild links’ tab to
‘Rebuild sitemap’.
. Check ‘Content’ on the ‘Settings’ tab again

http://www.scorchsoft.com/news/youtube-z-index-embed-if=
rame-fix

http://www.sitepoint.com/the-missing-guide-301-redirects-for-mac-and-pc/

This is a Drupal 6 (6.22) set-up on Heart Internet hosting (Reseller account).

• Once the hosting account has been set-up and the ‘install hour’ has passed, go to the ‘Manage Hosting Accounts’ page (https://customer.heartinternet.co.uk/manage/manage-packages.cgi) and select ‘Super User’ for the account you want to set-up.
• From the ‘Control Panel Home’ page, select ‘Drupal CMS’ from the ‘CGI Scripts’ section near the bottom of the page.
• Choose the location. Normally we’re installing at ‘root’ so leave the box blank. Press ‘Install Now’.
• Once it has installed the scripts and database for you, you’ll notice 2 links near the bottom of the page. Both link to the domain name root (i.e. http://domainname.co.uk) however one will have the server name at the front (i.e. http://79.170.44.155/domainname.co.uk). If the first one works, use it, however if the domain name isn’t quite ready (DNS records) use the 2^nd….
• You are now at the beginning of ‘Drupals Installation Process’. Simply follow the instructions page by page adding in the Site Name, Your email address, Username and Password. Once done you’ll be at a familiar ‘welcome’ page…
• Using Dreamweaver, download the ‘sites’ folder, which includes the ‘all’ and ‘default’ folders.
• In the ‘default’ folder is the ‘settings.php’ file used to configure the database, etc. Open this file and locate the PHP settings, normally on lines  156 to 167.
• Add a new line on the end to increase the memory allocation and to stop ‘white pages’ on heavy resource pages like ‘modules’ and ‘blocks’. So line 168 can become:
  ‘ini_set(‘memory_limit’,’516M’);’.
  Save and upload.
• In the ‘all’ folder we need to add folders for the ‘modules’, ‘themes’, libraries’ plus our own ‘clereJquery’ folder. This is easiest done by copying the ‘all’ folder from another site already set up. It’s worth noting here that you don’t need to copy a theme already in the ‘theme’ folder unless you intend to use it… Like wise, you can copy a theme from another Drupal site into this folder if you want to use it. The ‘theme’ folder can contain as many themes as you want available, but it’s best to just copy the one you intend to use…
• Upload your ‘new’ ‘all’ folder with your modules and themes.
• Now you can go back to your browser and log into the site using the username and password you added a few steps ago…
• Once in, we need to set a few basic thing up, so first we’ll start with ‘Modules’….
• Go to ‘Administer > Site Building > Modules’ (or use this admin/build/modules for speed).
• Preferably with another similar site open, tick the modules you are going to need, a suggestion is:
  • Administration
    • Administration Menu
  • CCK
    • Content
    • Content Copy
    • Fieldgroup
    • Number
    • Text
  • Core Optional
    • Aggregator
    • Contact
    • Database Logging
    • Help
    • Menu
    • Path
    • Taxonomy
    • Update Status
    • Upload
  • Event
    • Event
  • Image
    • Image
    • Image Attach
    • Image Gallery
  • Mate Tags
    • Admin interface for Nodewords
    • Basic meta tags
    • Extra meta tags
    • Nodewords
    • Site verification meta tags
  • Other
    • Clone modules
    • Global redirect
    • Googtube
    • IMCE
    • Lightbox 2
    • Path redirect
    • Pathauto
    • Sitemap
    • Token
    • Transliteration
    • Weather
  • SEO Compliance Checker
    • Basic SEO Rules
    • Keyword Rules
    • SEO Compliance Checker
  • User Interface
    • IMCE Wysiwyg API bridge
    • Wysiwyg
  • Views
    • Views
    • Views Exporter
    • Views UI
• Next we need to set the default time zone (admin/settings/date-time), to ‘Europe/London’, plus the date formats and the ‘First day of the week’.
• Nodeword Meta tags can be set-up here: admin/content/nodewords
• The ‘Event’ content type needs to be created by going here: admin/content/node-type/event
• Set ‘Full HTML’ as the default Input Format here: admin/settings/filters/list
• Set WYSIWYG editior here: admin/settings/wysiwyg for ‘Full HTML’, then press ‘Edit’ to select the icons to use. Suggestions under ‘Buttons and plugins’:
  • Bold
  • Italic
  • Underline
  • Bullet list
  • Numbered list
  • Outdent
  • Indent
  • Undo
  • Redo
  • Link
  • Unlink
  • Image
  • Remove Format
  • HTML block format
  • Paste from Word
  • IMCE
• Set ‘Automated alias settings’, here: admin/build/path/pathauto. Drop ‘Node paths’ down and change:
  • the default from ‘content/[title-raw]’ to just ‘[title-raw]’
  • ‘Event’ to ‘event/[eventyyyy]/[eventmon]/[eventdd]/[title-raw]’
  • ‘image’ to ‘image/[title-raw]’
• Check for available updates here: admin/reports/updates. Download and install any updated modules, unzip, upload, etc.
  • Run ‘Updates’ to make sure the new modules are in sync with the database. (www.domain.co.uk/update.php?op=info)
• Check ‘Status Report’ (admin/reports/status) for any issues, run cron and check again.
• Create a ‘Home’ page, then go to ‘Site Information (admin/settings/site-information) and change the setting ‘Default front page’ at the bottom from ‘node’ to ‘home’. Note: this is assuming you home page URL is ‘/home’…
• Set up ‘Scheduled Tasks’ from the Heart Internet Control panel. It’s under ‘Web Tools’.
  • Under ‘Run this command’ paste: /usr/bin/php5 /home/sites/##########.co.uk/public_html/cron.php
  • Change ‘##########’ for the domain name (no www.) and leave the other settings as they are.
  • Press ‘Update’ to save.
  • To test if it’s working, press ‘Test Command’, and you should get a message back ending with ‘Content-Type: text/html; charset=utf-8’.
  • Go back to Status Report, (admin/reports/status), and under ‘Cron maintenance tasks’ it should say ‘Last run’ and then how many minutes/seconds ago you pressed ‘Test Command’.
• Install a theme here: admin/build/themes, make sure that the only theme enabled is the one you uploaded to the ‘theme’ folder. Press ‘Save Configuration’. If everything has gone to plan, you should be looking at an empty site with your selected theme. If images are missing, it’ll just be the path in either the stylesheet, page.tpl.php or template.php files….
• Reset Blocks (admin/build/block)  – Remove ‘Powered by Drupal’, ‘Navigation’ and ‘User Login’ from their regions by selecting ‘<none>’ from their dropdown lists and press ‘Save Blocks’.

In each ‘theme’ you will have a .info file, a page.tpl.php file and the style sheet. The .info file will start with the name of you theme, so themename.info for example.

INFO
To add a new region called ‘Banner’, you open the .info file and you should see a section like:

regions[sidebar_first] = sidebar first
regions[sidebar_last] = sidebar last
regions[header] = header
regions[nav] = nav
regions[content_top] = content top
regions[content] = content
regions[content_bottom] = content bottom
regions[footer] = footer

To add our new region we just add it to the above like: regions[banner] = Banner
Note: the first ‘banner’ is all lowercase, no spaces, and the second ‘Banner’ is for display, so can have spaces, etc, just be careful with punctuation.

Your new region will now show on the ‘blocks’ page, and you can start assigning blocks to your new region. (Flush cache if it doesn’t show). However it won’t appear on the website pages yet.

PAGE TPL
In the page.tpl.php page, find the area you want the new region to show and paste the following:

<?php if($banner){ ?>
    <div id="banner">
        <?php print $banner; ?>
    </div>
<?php } ?>

Note: The variable you used in region[] (banner) is also used here, but it has a $ sign in front. i.e. $banner. The first line in the code above uses if to check that something has been put in the banner region, (i.e. a block), and if it has, line 3 prints/writes it to the page as it’s being built. Lines 2 and 4 add the CSS div start/end with an id of banner so you can control it in the stylesheet by using #banner.

STYLESHEET
Add the following and amend it as you see fit:

#banner  { 
    width: 960px; 
    height: 300px; 
    clear: both; 
    margin: 0; 
    padding: 0; 
    background: #f0f; 
    position: relative;
}

See? Painless really… If something isn’t showing, remember to flush the cache so the system loads the .info and template files again.

The first is something I found online somewhere, and has been modified a little…

$email = 'you@youremailaddress.com';

if(preg_match("/^[_a-z0-9-]+(\.[_a-z0-9-]+)*@[a-z0-9-]+(\.[a-z0-9-]+)*(\.[a-z]{2,3})+$/i", $email)) {
    // All OK, do something
}
else {
    // Not OK, throw error
}

The second is from the legendary Mark Jackson, it requires PHP5 and in his words:

PHP actually has a built in function called filter_var which has an email validation flag in it but it will allow for any hostname (like mark@localhost) which I do not like so I have added another simple check to make sure it has a dot after the @ sign the function I use is:

function checkEmail($e,$bypassVal=false) {
    // ensure the email has a valid extension
    if(($bypassVal!==false)&&(is_array($bypassVal))&&(in_array($e,$bypassVal))) { return true; }
    if(strpos($e,'@')>=strrpos($e,'.')) { return false; }
    return (filter_var($e, FILTER_VALIDATE_EMAIL) && preg_match('/@.+\./', $e)) ? true : false;
}

The $bypassVal variable allows you to specify any email addresses (in an array format) which can can go through without validation – just in case you want to specify a particular string or email which can get through.

Examples
checkEmail(‘mark@domainname.co.uk’); // returns true
checkEmail(‘mark@localhost’); // returns false
checkEmail(‘mark@localhost’,array(‘mark@localhost’)); // returns true
checkEmail(‘__I_GET_THROUGH__’,array(‘mark@localhost’,'__I_GET_THROUGH__’)); // returns true

Open the page.tpl.php file and add this code at the very top, so that the end ?> is followed immediately by the HTML declaration, i.e. <!DOCTYPE html PUBLIC etc.

<?php
if(isset($_GET['dev']) && $_GET['dev']==1){ $_SESSION['dev'] = true; }
if(isset($_GET['dev']) && $_GET['dev']==0){ $_SESSION['dev'] = false; }

if(!isset($_SESSION['dev']) || $_SESSION['dev']!=true){
   echo '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
      <title>Page Under Construction</title>
   </head>
   <body>
      <p>This site is under construction</p>
   </body>
   </html>';
   exit();
}
?>

If you visit the site without setting anything, (or if you reset ‘dev mode’ by using ‘?dev=0‘), you’ll just get the ‘Under construction’ text. This of course can be replaced with include files, etc…

<?php
print_r(get_defined_vars());
?>

if(isset($_GET['logout'])){ // trigger if ?logout is in the url
	$_SESSION = array();
	if(isset($_COOKIE[session_name()])){
   		setcookie(session_name(), '', time()-42000, '/');
	}
	session_destroy();
	header ('location: /'); // redirect to root
	exit();
}

To trigger it, simply add ‘?logout‘ after a url path, i.e. www.mydomain.com/?logout.