I should explain the _() method. I set this up so I could do a Singleton. It also allows me to use it in a sorta static method by doing “userInfo::_()->id;”. Nice quick and easy.

I could of wrote this like my smcFunc class, but choose otherwise on the fact I wanted to use it as a object rather than a static method. A setup like that should be possible, but I didn’t test that.

I never tested but I don’t think accessing multiple dimensional parts of the $user_info will work. Things like $user_info['group'][1] most likely won’t work here. I should add support to drill down into the array, but will save that for a later day.

/*
* userInfo as a class.  We kinda do a poor method, but its the best way for now.
*/
class userInfo
{
	public static $instanceID = 0;

	public static function _()
	{
		if (self::$instanceID == 0)
			self::$instanceID = new userInfo;

		return self::$instanceID;
	}

	public function __set($key, $value)
	{
		global $user_info;
		$user_info[$key] = $value;
	}

	public function __get($key)
	{
		global $user_info;
		return isset($user_info[$key]) ? $user_info[$key] : null;
	}

	public function __isset($key)
	{
		global $user_info;
		return isset($user_info[$key]);
	}

	public function __unset($key)
	{
		global $user_info;
		unset($user_info[$key], $user_info[$key]);
	}
}

I wrote it so it should be plugable with different databases, user information and templating engines. The design was mostly to implant it into my mixed environment of SMF and WordPress, but also to make it robust so it could be used in other ways.

The source of the code is up on GitHub at https://github.com/jdarwood007/pastebin

Well it turns out it is sorta a SMF old PHP support issue, but the problem lies in WordPress. This is the function in WordPress wp-includes/load.php

/**
 * Add magic quotes to $_GET, $_POST, $_COOKIE, and $_SERVER.
 *
 * Also forces $_REQUEST to be $_GET + $_POST. If $_SERVER, $_COOKIE,
 * or $_ENV are needed, use those superglobals directly.
 *
 * @access private
 * @since 3.0.0
 */
function wp_magic_quotes() {
        // If already slashed, strip.
        if ( get_magic_quotes_gpc() ) {
                $_GET    = stripslashes_deep( $_GET    );
                $_POST   = stripslashes_deep( $_POST   );
                $_COOKIE = stripslashes_deep( $_COOKIE );
        }

        // Escape with wpdb.
        $_GET    = add_magic_quotes( $_GET    );
        $_POST   = add_magic_quotes( $_POST   );
        $_COOKIE = add_magic_quotes( $_COOKIE );
        $_SERVER = add_magic_quotes( $_SERVER );

        // Force REQUEST to be GET + POST.
        $_REQUEST = array_merge( $_GET, $_POST );
}

The problem here, is that they add magic quotes to the cookie. Not quite sure why they are even doing this. But it broke adding SMF. The part in SMF which failed because of this is in SMFs Sources/Load.php in the loadUserSettings function

		// Fix a security hole in PHP 4.3.9 and below...
		if (preg_match('~^a:[34]:\{i:0;(i:\d{1,6}|s:[1-8]:"\d{1,8}");i:1;s:(0|40):"([a-fA-F0-9]{40})?";i:2;[id]:\d{1,14};(i:3;i:\d;)?\}$~i', $_COOKIE[$cookiename]) == 1)
		{
			list ($id_member, $password) = @unserialize($_COOKIE[$cookiename]);
			$id_member = !empty($id_member) && strlen($password) > 0 ? (int) $id_member : 0;
		}
		else
			$id_member = 0;

Because of old PHP support in SMF, its trying to combat a cookie security issue that existed below PHP 4.3.9. Now I don’t use that version, but I rather not strip out the code. The preg match was failing because it was not finding that valid string in the cookie. Since all the double quotes where escaped with a slash \.

For my code, I called in Settings.php from SMF and then did a stripslashes on the cookie. Then I included SSI.php, with the results I expected of it finding my active SMF session.

		require_once(pBS::get('smf_dir') . '/Settings.php');
		if (isset($_COOKIE[$cookiename]))
			$_COOKIE[$cookiename] = stripslashes($_COOKIE[$cookiename]);

		require_once(pBS::get('smf_dir') . '/SSI.php');

I should note because SMF uses a lot of global variables, that I had to globalize all of those before hand. I just borrowed the globals from SSI.php and put them into that scripts function.

However, todays times are different. So with JQuery out there, I decided to take breaks from my projects for a couple hours for a few days and put forth a effort to rewrite this. Needless to say, I had the initial code wrote in only a few hours. My original script took me a few days alone. That didn’t count the package-info creator I made later which also took a while.

The new script attempts to rely all on JavaScripting via JQuery. It was a fun experience to build it this way. Although, because of JavaScript’s security measures, I couldn’t leave downloading the file outside of the server. So alas, I still have to process the actual download via the server. There is a work around with using Data URIs, however it didn’t provide the filename and sounds a bit flaky when the length of the url gets to be a bit long. I included both as a option though.

Oh and Its on github, because I see no reason to not share the code. Including the code I used to integrate it into my WordPress blog.

Well after debugging and messing around for a while, I was able to figure out how to resolve this issue. In jquery.weekcalendar.js open up the file and locate:

          if ($target.hasClass('wc-cal-event')) {
            options.eventMouseover($target.data('calEvent'), $target, event);
          }

After that code we want to add:

          if ($target.hasClass('wc-time') || $target.hasClass('wc-title')) {
            options.eventMouseover($target.parents('.wc-cal-event').data('calEvent'), $target, event);
          }

A little further down the file is:

          if ($target.hasClass('wc-cal-event')) {
            if ($target.data('sizing')) { return;}
            options.eventMouseout($target.data('calEvent'), $target, event);
          }

We want to add after that:

          if ($target.hasClass('wc-time') || $target.hasClass('wc-title')) {
            if ($target.data('sizing')) { return;}
            options.eventMouseout($target.parents('.wc-cal-event').data('calEvent'), $target, event);
          }

This makes it work as I excepted it to. My thoughts here are that the inner divs are removing the mouseover events. So by attaching an event to them as well, it makes it work as well.

As a good GitHub person does, I submitted a pull request with these fixes in hopes that it gets merged into the plugin.

These are some examples:
FireFox on Windows 7: Wed Dec 07 2011 16:26:38 GMT-0800 (Pacific Standard Time)
IE 8 on Windows 7: Wed Dec 7 16:29:21 PST 2011
Chrome on Windows 7: Wed Dec 07 2011 16:45:45 GMT -0800 (Pacific Standard Time)
FireFox on OS X Lion: Wed Dec 07 2011 16:37:12 GMT-0800 (PST)
Opera on OS X Lion: Wed Dec 07 2011 16:37:21 GMT-0800
Safari on OS X Lion: Wed Dec 07 2011 16:44:54 GMT-0800 (PST)

It appears that the format of this is left up to the browser to decide. It would be nice if they all followed a specific format. Well it was because of the (Pacific Standard Time) not being recognized by php’s strtotime, that my code failed to work. Some helpful members on IRC brought it to my knowledge that it is up to the browser really.

I find it interesting that out of all the tests, it appears IE just takes a completely method. While the other browsers are at least semi-similar other than the time zone string at the end. OS X at least appears to be consistent and it appears Opera may just be stripping the string from the end.

At least there is a simple solution. Just use some regular expressions to strip off (Pacific Standard Time) and any other variation.

	$date = preg_replace('~\(([^(]+)\)~', '', $_POST['date']);

Well after scrambling the web, I came to the conclusion that it wasn’t possible in the code by default. So away into the code I went. To say the least, my solution is nowhere near perfect nor does it allow for reoccurring events yet from different weeks or months. It was decided to take another course of action rather than trying to hack reoccurring events into the code. I just wanted to post what I had so far:

In jquery.weekcalendar.js we have this code:

              //put back the initial start date

Now before this and the block of code before it, I added in:

			if ($.isArray(recurring))
			{
				var cur_date = new Date();
				var cur_dayofweek = cur_date.getDay();
				var org_start_date = calEvent.start.getDate();
				var org_end_date = calEvent.end.getDate();

				for(var i= 0; i<recurring.length; i++)
				{
					calEvent.readOnly = true;
					var value = recurring[i];
					var offset = value - cur_dayofweek;

					calEvent.start.setDate(cur_date.getDate() + offset);
					calEvent.end.setDate(cur_date.getDate() + offset);

					if (($weekDay = self._findWeekDayForEvent(calEvent, $weekDayColumns))) {
						self._renderEvent(calEvent, $weekDay);
					}
				}

				calEvent.start.setDate(org_start_date);
				calEvent.end.setDate(org_end_date);
				calEvent.readOnly = false;
			}

This lets me do reoccurring events for the current week. I am sure it could be greatly improved and somebody may be able to make it support multiple weeks.

In case anybody else wondered, this simply just needs a json array in the data of the weekday numbers (0-6). The key is recurring.

				{
					"id":15,
					"start": "Sun, 4 Dec 2011 21:00:00 -0500",
					"end": "Sun, 4 Dec 2011 22:30:00 -0500",
					"title":"Reoccurring",
					"recurring": [1,2,5,6]
				}

After some thankless google searches, I came up with code that accomplishes this task easily.

jQuery(function(){
	$('#banners').change(function(){
		$('#images_preview_loader').empty();
		$('#images_preview_box').empty();
		$('#images_preview_tower').empty();

		$('#banners :selected').each(function(i, selected){
			id = $(selected).attr('value');
			filename = $(selected).attr('name');
			$('#images_preview_loader').append("<img id='bp_" + id + "' src='/images/banners/" + filename + "'/>");

			height = document.getElementById('bp_' + id).height;
			width = document.getElementById('bp_' + id).width;

			if (width < height)
			{
				$('#images_preview_tower').append("<img id='bp_" + id + "' src='/images/banners/" + filename + "'/>");
			}
			else
			{
				$('#images_preview_box').append("<img id='bp_" + id + "' src='/images/banners/" + filename + "'/>");
			}
		});
		$('#images_preview_loader').empty();
	});
});

As for the HTML, I have my select box with multiple=”multiple” in it. Each option has a value attribute that I use for the database and a name attribute containing the filename. They also contain the friendly name. I then have 3 divs setup like so:

<div id="images_preview_loader" style="display: none;"></div><br /><div id="images_preview_box"></div><br /><div id="images_preview_tower"></div>

The loader lets me simply get the image loading, once it has the height and width of the image it moves it to the correct box. I keep the loader div hidden so there is no moving around showing as it does its work. Does the job for what I need it to do. Which is a simple previewer of the images being selected. I need the bigger ones to be separate as these are usually tower based images and would make a ugly looking layout otherwise.

This does also require a template edit to your wordpress templates. Sadly I couldn’t avoid this, I looked around and tried to see if I could modify the_content(), however it doesn’t look very pleasant to do so. I might in the future look into doing this. If somebody has a better solution that requires no wordpress template edits, please let me know. Back on topic, I modified page.php in my template and changed:

					<?php the_content(); ?>

To this line:

					<?php if (isset($specialPageContent)) echo $specialPageContent; else the_content(); ?>

Next I will just dump a file I named wp-ssi.php and explain how it works at the end.

<?php
// Change the default template to use.
define('WP_SSI_DEFAULT_TEMPLATE', 'page');

// Register a shutdown function (DOES THE ACTUAL WORK!)
register_shutdown_function('do_wp_ssi_wrap');

// Don't output anything yet.
ob_start();

// Get WordPress going.
require_once('./wp-blog-header.php');

// The shutdown function that does the actual work.
function do_wp_ssi_wrap()
{
	global $specialPageContent;

	// Simply get all contents.
	$specialPageContent = ob_get_clean();

	// Allow some over rides.
	$theme = defined('WP_SSI_THEME') ? WP_SSI_THEME : get_template_directory();
	$template = defined('WP_SSI_TEMPLATE') ? WP_SSI_TEMPLATE : WP_SSI_DEFAULT_TEMPLATE;

	// Pass it on as if it was a page.
	require($theme . '/' . $template . '.php');
}

Now for all my files I add at the very top. Of course, you need to substitute the path to match yours.

require('/path/to/wordpress/wp-ssi.php');

As for wp-ssi.php, I will can explain more about how that works.

define('WP_SSI_DEFAULT_TEMPLATE', 'page');

Our first bit of code, simply is a option, nothing more nothing less. It just lets me define the default template, in this example code I used page, however for my theme I customized the page template to display full width and not have the sidebar.

register_shutdown_function('do_wp_ssi_wrap');

This is the most important piece of code, without it this wouldn’t work. This registers with php a function to run at the end of page execution. I may of been able to use ob_start with a buffer function, but I avoided it.

ob_start();

This is simple, we are turning on a output buffer. I don’t need any buffer replacements, so I just call the function.

require_once('./wp-blog-header.php');

This gets wordpress going. This same piece of code is used to start wordpress in the index.php

function do_wp_ssi_wrap()
{
	global $specialPageContent;

Consolidating some lines here, we are creating a new function called ‘do_wp_ssi_wrap’. We also used ‘do_wp_ssi_wrap’ in the argument lines with our register_shutdown_function a few lines up. This is the shutdown function that is going to do some stuff before php exits and sends all contents to the browser.

	$specialPageContent = ob_get_clean();

We are capturing all output sent to the buffer at this time. Any output our script has sent is now in a easy to use variable.

	$theme = defined('WP_SSI_THEME') ? WP_SSI_THEME : get_template_directory();
	$template = defined('WP_SSI_TEMPLATE') ? WP_SSI_TEMPLATE : WP_SSI_DEFAULT_TEMPLATE;

Some more overrides here. I simply setup a way to override the theme, otherwise it uses wordpress functions to get the path to the current theme in use. The next one allows me to override the template. Both of these may come in handy if I have a page I want a different theme on or if I want to use a different template on it.

	require($theme . '/' . $template . '.php');
}

This is simply just including the template from the theme we selected. Oh and the closing function curly bracket. That is all the code needed here.