So, what exactly does this do?
The first query retrieves the post count of any entries (in this case, the URL TITLE of the entry is in the third segment of the URL) that are assigned to a specific category (we are looking for 1 here; in fact, the LIMIT 1 line keeps the query from searching for anything greater, as our relevant choices are either 1 or 0). The count is then applied to a PHP variable called assignedCatVar.

If the assignedCatVar is = 1, then the next query grabs the contents of the right-hand menu entry and displays it appropriately on the page.

Simple and effective.

For example, setting the Search Results URL value to
{homepage}staff-members will create a SEARCH RESULT of http://mysite.com/staff-members/.

Easy enough, right?

Now, what do you do when you have a Weblog that contains category-based information. The specified Search Results URL does not take this information into account. So, if you have a weblog with a hard-coded path of http://mysite.com/staff-members/category1/johndoe , how do you get the category to show up in the search results?

I have a workaround on the RESULTS template in my SEARCH template group:

{exp:search:search_results}

<?php $autoPath = ‘{auto_path}’;

$lastSegment = basename($autoPath);

//Staff-member URL update, based on the category assigned to the entry

if(strpos($autoPath, ‘staff-members’)){

//variable to assign the category to the appropriate URL segment for the Rule

$catVar = 1;

$basename = ‘catPath’;

?>

{categories}

<?php

$tempname = $basename.$catVar;

$$tempname = “{category_url_title}”;

$catVar++;

?>

{/categories}

<?php $autoPath = “{homepage}”.”staff-members/$catPath1/$lastSegment”;

} ?>

<br /><span><?php echo $autoPath; ?></span>

</div>

{/exp:search:search_results}

So, if the staff-members URL segment exists in the specified URL’s path, the Category/Categories assigned to the Entry are obtained and then added to the URL, defined by the $autoPath variable.

It might not be the most elegant solution, but it works great for us.

Luckily, there is an easy fix:

• Open up any MS Office 2007 product. In my instance, I used Office 2007.
• Go to Help>Office Diagnostics.
• Run diagnostics. This took about 5 minutes to complete.
• Return to your SharePoint site. the multiple document upload tool should now be working. Apparently, this fix re-registered any .DLLs that were causing the error. I love easy fixes!

LDAP (short for Lightweight Directory Access Protocol), a directory service that runs over TCP/IP, stores information. The storage is similar to how a database stores information, but the structure is ideal for attribute-based, hierarchical structured data that does not undergo frequent changes (for example, the employees’s name, Active Directory group membership, address, and so forth). The LDAP directory can be thought of as a tree of nodes, where each node represents an entry in the LDAP database. These entries are comprised of a collection of attribute-value pairs, and they are identified uniquely by a ‘distinguished name’ or DN. The DN is important, because this is what we will be using to determine a user’s group membership.
Our login script will

1. First bind to our LDAP server with a resource account (we are not using anonymous binding, so we will need to provide a resource account’s credentials)
2. Check that the user’s ID and password are legit and exist in our Active Directory environment
3. Check if the user is a member of a particular security group

If all of these conditions are met, the users will have successfully logged on and will be granted access to our application.

We will store our authentication function in a php file entitled resourceBind.php. The entire contents of resourceBind.php:
[php]<?php

?>
[/php]

And, our login page, which we will call login.php, and which will be located in the same directory as resourceBind.php:
[php]<?php
//Disable error messages
error_reporting(0);
?>
<?php require_once(‘resourceBind.php’); ?>
<?php
if ($_POST) {

//Handy function to remove specific special characters from user provided input. ALWAYS validate user input. In this case, we are removing characters that are not allowed in usernames and passwords.
function cleanTxt($text)
{
$code_entities_match =

array(‘–’,'>’,'&quot;’,'!’,'#’,'$’,'%’,'^’,'&’,'*’,'(‘,’)',’{‘,’}',’|',’:',’"’,'<’,’[',']‘,’\\’,';’,"’",’,',’/',’*',’~',’`');
$code_entities_replace = array(‘-’,'-’,”,”,”,”,”,”,”,”,”,”,”,”,”,”,”,”,”);
$text = str_replace($code_entities_match, $code_entities_replace, $text);
return $text;
}
//Set form variables
$Username=stripslashes(cleanTxt($_POST['ssoname']));
$SSO_Password=stripslashes($_POST['ssopass']);

//Get Ip Address and User Agent information. This is useful info to store in sessions, or a database table, especially if you need to track timestamps and access
$userIP = $_SERVER['REMOTE_ADDR'];
//Get Timestamp
$myDate = date("Y-m-d H:i:s");//Date in easy-to-read format

$displayForm=false;

if(UMldap($Username,$SSO_Password)){
//set complex string in case there is no ‘whencreated’ field for the username

//User has valid credentials. We are creating a new session variable with the user name. This is also a good place to effectively double up your authentication security by checking to see if the user name exists in another medium, such as a MySQL or Oracle table.
$_SESSION['USERCMS'] = $Username;

//The login is a smashing success, so redirect the user to the protected page.
$MM_redirectWithSuccess = "Successful_login.php";
header("Location: ". $MM_redirectWithSuccess );

} else {
/We can’t log the user in, so display the login form again
$displayForm=true;
}

//unbind
ldap_unbind($ldapconn);

//*************************************
}//end POST check

?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" >

<head>
<title>LDAP Login Form</title>
</head>
<body>
<h1>Login</h1>
<?php

//—————————————————————————-
//Form variables to display previously filled out fields
$displayForm=true;
$ssoname=”;
$ssopass=”;
//—————————————————————————-

//Display the login form
if ($displayForm){//Display the request form
?>

<form action="<?php echo $_SERVER['PHP_SELF']; ?>" method="POST" id="login" name="login">

UserID:
<input type=text size=30 name="ssoname" maxlength=30 />

Password:
<input type=password size=30 name="ssopass" maxlength=30 />
<br />

<button type="submit" value="submit" name="submit" >Logon</button>

</form>

<?php
}
?>

<!– Javascript to move the cursor to the Username form field. This is a small convenience to the user. –>
<script type="text/javascript" language="JavaScript">
document.forms['login'].elements['ssoname'].focus();
</script>

</body>
</html>
[/php]

To figure out how everything works, please read the comments within the code. If you are interested in learning more, please check out Hugh’s excellent book:

First off, it pays to research your particular topic. If you are looking for an excellent primer, you can find some good information in the following book:

At my job, we have web pages that are automatically generated and emailed to us.  We are tired of manually moving these files to the appropriate web directory (in this case, samba shares that are mapped with drive letters assigned to them).  So, the logical solution is to use Outlook Rules to push the attachments to the mapped drive.  However, Outlook rules have one limitation: you can move messages to specific folders, but moving attachments is another matter that is almost impossible to perform with the default Outlook Rules wizard.  So, we are going to use Outlook’s built in Visual Basic Editor to create some custom code to drive the attachment migration.  Here is how we did it:

1. Open up Outlook.  I am using Outlook 2007, but this should also work in Outlook 2003.  Go to Tools>Macro>Visual Basic Editor.
   
2. With your project folder highlighted (in the top left, in the PROJECT pane; I just used the default project, Project1), right click and choose Insert>Module, double-click Project1, and then double-click Microsoft Outlook Objects. Double-click ThisOutlookSession to open a code window. 
   
   Copy and paste the following code into the code window of the editor:
   Sub SaveAttachmentsToDisk(Item As Outlook.MailItem)
Dim olkFolder As Outlook.MAPIFolder, _
olkAttachment As Outlook.Attachment, _
objFSO As Object, _
strRootFolderPath As String, _
strFilename As String, _
intCount As Integer
'Change the following path to match your environment
strRootFolderPath = "z:\www\departments\webreports\"
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set olkFolder = Application.ActiveExplorer.CurrentFolder
If Item.Attachments.Count > 0 Then
For Each olkAttachment In Item.Attachments
If objFSO.GetExtensionName(LCase(olkAttachment.FileName)) = "htm" Then
strFilename = olkAttachment.FileName
intCount = 0
Do While True
If objFSO.FileExists(strRootFolderPath & strFilename) Then
intCount = intCount + 1
objFSO.deletefile (strRootFolderPath & strFilename)
Else
Exit Do
End If
Loop
olkAttachment.SaveAsFile strRootFolderPath & strFilename
End If
Next
End If
Set objFSO = Nothing
Set olkAttachment = Nothing
Set olkFolder = Nothing
End Sub
3. You will need to ensure that you have the proper security level set in order to properly process the script. In Outlook, go to Tools>Macro> Security.  I chose No security check for macros.  This might be too loose of a restriction for your environment; if so, try the next highest setting.
4. Create a new Outlook rule (Tools>Rules and Alerts) to reflect your changes.  My rule looks for new messages from a specific email address and has an attachment (the web file that I want to move), moves the message to a specific folder (so I can have a backup of the message/attachment), then runs the module/script above to move the web file to the appropriate samba share.  Here is what my Rule Description looks like:

   
   
   Apply this rule after the message arrives
   from joeuser@email.com
   and which has an attachment
   and on this machine only
   move it to the WEBBACKUP folder
   and run Project1.SaveAttachmentsToDisk

5. Hit Apply and OK to save your rule. A couple of caveats: this is a client-side rule, so you must keep Outlook running in order for the rule to process. Also, the code will overwrite any file (in my case, in the target samba share) that has the same name as the attachment. If you only wish to make a copy, you can append a number to the attachment name. To do so, replace this line of code:

   objFSO.deletefile (strRootFolderPath & strFilename)

   with

   strFilename = "Copy (" & intCount & ") of " & olkAttachment.FileName 

   That’s it!

View additional details at this Microsoft Support article.