The biggest issue with this setting was the process of creating galleries. By default in NextGen you create the gallery on one page, upload the images in another, and then create new post yet elsewhere. But there had to be a way to at least merge the gallery creation with photo upload, especially considering a new gallery form consisted of a single “gallery name” field.Surprisingly enough after checking the code, both actions are actually processed in the same place. Thus by adding a new field on the photo upload form this time consuming problem could be solved:

Edit the file: wp-content/plugins/nggallery/admin/wp25/addgallery.php (line: 15)

// link for the flash file
$swf_upload_link = NGGALLERY_URLPATH . 'admin/wp25/upload.php';
$swf_upload_link = wp_nonce_url($swf_upload_link, 'ngg_swfupload');
//flash doesn't seem to like encoded ampersands, so convert them back here
$swf_upload_link = str_replace('&', '&', $swf_upload_link);

$defaultpath = $ngg_options['gallerypath'];

if ($_POST['addgallery'] || !empty($_POST['newgalleryname'])){
  if(!empty($_POST['newgalleryname']))
    $_POST['galleryname'] = $_POST['newgalleryname'];
  check_admin_referer('ngg_addgallery');
  $newgallery = attribute_escape($_POST['galleryname']);
  if (!empty($newgallery))
    $_POST['galleryselect'] = nggAdmin::create_gallery($newgallery, $defaultpath);
}
if ($_POST['zipupload']){

Edit the file: wp-content/plugins/nggallery/admin/wp25/addgallery.php (line: 263)

	<tr valign="top">
		<th scope="row"><?php _e('in to', 'nggallery') ;?></th>
		<td><select name="galleryselect" id="galleryselect">
		<option value="0" ><?php _e('Choose gallery', 'nggallery') ?></option>
		<?php
			$gallerylist = $wpdb->get_results("SELECT * FROM $wpdb->nggallery ORDER BY gid ASC");
			if(is_array($gallerylist)) {
				foreach($gallerylist as $gallery) {
					echo '<option value="'.$gallery->gid.'" >'.$gallery->name.' | '.$gallery->title.'</option>'."n";
				}
			}
		?>
		</select> <label>or <input type="text" name="newgalleryname"  /></label>
		<br /><?php echo _e('Note : The upload limit on your server is ','nggallery') . "<strong>" . ini_get('upload_max_filesize') . "Byte</strong>n"; ?>
		<br /><?php if ((IS_WPMU) && wpmu_enable_function('wpmuQuotaCheck')) display_space_usage(); ?></td>
	</tr>

Edit the file: wp-content/plugins/nggallery/admin/wp25/functions.php (line: 77)

if ($result) {
	nggallery::show_error(__('Gallery', 'nggallery').' <strong>'.$galleryname.'</strong> '.__('already exists', 'nggallery'));
	return false;
} else {
	$result = $wpdb->query("INSERT INTO $wpdb->nggallery (name, path, title) VALUES ('$galleryname', '$nggpath', '$gallerytitle') ");
	if ($result) nggallery::show_message(__('Gallery', 'nggallery').' <strong>'.$wpdb->insert_id." : ".$galleryname.'</strong> '.__('successfully created!','nggallery')."
".__('You can show this gallery with the tag','nggallery').'<strong> </strong>');
	return $wpdb->insert_id;
}  

Minimal is a very good word to describe jTree, which most of the time is good, however sometimes you might just want a little bit more. One of the biggest issues for me was lack of clickable links inside the LIs. Fortunately after some tweaking I came up with a hacky but working solution:

if ($("#jTreeHelper").is(":not(:animated)") && e.button !=2) {
 	//	Allow for clickable links
	if(new String(e.target).match(/(f|ht)tp(s{0,1}):///ig)){
 		return false;
	}
	$("body").css("cursor","move");

Just add the highlighted lines in the jquery.jtree.js file. Basically it just checks if the target of the click is a link and if it is it ignores the dragging.

AuthName "Restricted Area"
AuthType Basic
AuthUserFile /YOUR_PATH/www/.htpasswd
AuthGroupFile /dev/null
require valid-user

After commenting things out it seemed that it was the last line that was causing the problems. However do not be fooled. Careful inspection and a bit of Google searching led me back to the AuthUserFile declaration.

But what could be wrong with it? The file exists on the server. The passwords are properly encrypted. The problem was the “www” folder. Or should I rather say symlink. Changing “www” to the original folder: “public_html” solved the issue.

Moral for today: .htaccess does not like symlink folders when it comes to .htpasswd…