Jan 1

Did I mention this in a previous post?  managing┬ĚParadox was setup as a blog on a forum backbone to test/exercise a new concept (new to me anyway...I should patent this if it's not already) in online community launching, whereby the much harder to manage forum, requiring diligent marketing and considerable energy to foster a following and participation is reserved in lieu of a comparatively simple blog.

So, the switch has been flipped and managing┬ĚParadox has softly rolled out in blog-form with the first article to come shortly, and regular posts thereafter. If, at some point, traffic and readership demand (or even quietly request it), the forum will be opened and the project elevated to the next level.

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Dec 31

Pleased to announce that I will make, come Hell or high-water, the managing┬ĚParadox go-live that I'd envisioned for Jan 1.  All the bits are in place, it's only a matter now of bringing the site out of maintenance mode.  I'm only marginally happy with the copy that I'm going live with - as minimal as it is, I was shooting for short, sweet, on-topic, and impactful.  I got to short, I got to sweet, it's mostly on-topic, but lacks a suitable degree of impact.  There-in lies a lesson though - sometmes any decision or action is better than none at all, or one which is terminally delayed. 

Therefore, my mantra for '10: "it is what it is".

There will be plenty of time to tighten up the site and the content, and I'm sure well before any significant traffic is generated.  If this site proves anything, it's not the quality of the content that seems to bring traffic in bulk, rather it's the total quantity and frequency of information change that does so.

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Dec 19

Here's a little something that I hurried together to fulfill an interest in consolidating multiple user blogs into a single panel - the setup:

  • Simple Machines Forum (SMF) 2.0 RC2,
  • SimplePortal 2.3.1,
  • PortaMx Blox Extension (PmxBlog) 0.952.

The requirement:

  • A auto-extensible panel in SimplePortal to support N number owners of blogs (via PmxBlog).
  • Zero customization of existing forum, portal or blog code.
  • Adherence to blog and portal permissioning.
  • Fast and simple.

The execution:

The best way to achieve the desired - naturally, a tabbed UI.  The fastest, cleanest, bestest way to get tabs?  YUI of course!  Using the built-in PmxBlog SSI functions provided in PmxBlogSSI.php, I was able to achieve the desired without writing a single query or doing anything outside of the pre-rolled routines provided.  Building the functionality into a single PHP (named PmxBlogSimPortalTabs.php in /Sources page and including it into a SimplePortal PHP panel was all that was required.  In fact, the only customization done was to pull in the YUI tab CSS locally and brush it up to give a more consistent style against the default SMF 2.0 Curve theme.

What it does:

  • First, I use PmxBlogSSI_Recent (one of the pre-wrapped API functions provided with PmxBlog) to fetch the last N number of blog entries - this effectively controls the maximum number of users for which tabs will be created.  However, should one person be a very active blogger, they may fulfill the "last N" quantity before other bloggers' entries are found.  Conversely, should you have many blogs, and an even distribution of entries over time, and a high "last N" value, you could end up with way too many tabs.  So, find a suitable balance based on the number of blogs versus typical behavior.
  • I parse the array of last N blog entries returned for the bit that includes the blog owner (provided as a URL) and strip the html around it to get just the name.
  • Next, I grab the BlogRoll, again using PmxBlogSSI_Recent, and stuff it into a buffer for use later - I ended up having to buffer this stuff because of the way in YUI tabs were working...somehow the PmxBlog functions would not return output if run inline to the tab content markup.  Maybe it's something to do with how/when the tabs are rendered versus the API returning results...who knows??
  • Then I build the YUI tabs markup.  For tab labels, I grab the results array from step 1 above, which could now have multiple of the same user represented, and let array_unique parse out the duplicates.  These become the tab labels, and also get passed into PmxBlogSSI_ShowArticles where I fetch and buffer the last blog entry for the given user.
  • Finally, the tab content is generated - first the BlogRoll data  from step 3 above, then looping through the buffered array from step 4.

See the screen shots below, and code in the extended content:

The BlogRollA Sample Blog

Continue reading "PmxBlog in Tabs on Simple Portal"

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Dec 11

Getting back to requirements for a blog system within the Managing Paradox forum - this was not looking like a very hopeful endeavor in SMF 2.0.  I was just about resolved to either a sloppy integration with a stand-alone blogging system (probably S9Y since it's my favorite and I know the most about it), or foregoing the feature altogether. 

I was surprised, after a great deal of hunting, to find PMXBlog.  PMXBlog, as it turns out, is the new "Fel Blog" - of relative SMF acclaim.  Being new to SMF, I only knew Fel Blog by reputation, and reading between the lines at the Simple Machines site, it seems as though the relationship is a bit strained - perhaps for disputes over licensing?  Someday, perhaps I'll take time out to learn more.  In the meantime, I was very pleased to find PMXBlog as a fully-integrated blogging solution designed with SMF in-mind.

Installation into SMF 2.0 RC2 was painless, though a portion needed to be done manually for modifications made to the button/menu array by the Simple Portal installation.  This includes only one modification in Sources/Subs.php and involves insertion of the following, at the following location:

        $buttons = array(
            'home' => array(
                'title' => $txt['home'],
                'href' => $modSettings['sp_portal_mode'] == 3 && empty($context['disable_sp']) ? $modSettings['sp_standalone_url'] : $scripturl,
                'show' => true,
                'sub_buttons' => array(
                ),
                'is_last' => $context['right_to_left'],
                // 'target' => '_blank',
            ),

// --- start PmxBlog
            'pmxblog' => array(
                'title' => $txt['PmxBlog_blogbutton'],
                'href' => $scripturl .'?action=pmxblog',
                'show' => !empty($modSettings['pmxblog_enabled']) && AllowedToBlog('view', $context['user']['id']),
                'sub_buttons' => array(
                    'showall' => array(
                        'title' => $txt['PmxBlog_show_all_nav'],
                        'href' => $scripturl . '?action=pmxblog;sa=list',
                        'show' => !empty($modSettings['pmxblog_enabled']) && AllowedToBlog('view', $context['user']['id']),
                    ),
                    'showunread' => array(
                        'title' => $txt['PmxBlog_show_unread_nav'],
                        'href' => $scripturl . '?action=pmxblog;sa=unread',
                        'show' => !empty($modSettings['pmxblog_enabled']) && AllowedToBlog('view', $context['user']['id']) && !$user_info['is_guest'],
                    ),
                    'showtracked' => array(
                        'title' => $txt['PmxBlog_show_tracked_nav'],
                        'href' => $scripturl . '?action=pmxblog;sa=tracked',
                        'show' => !empty($modSettings['pmxblog_enabled']) && AllowedToBlog('view', $context['user']['id']) && !$user_info['is_guest'],
                    ),
                    'yourblogview' => array(
                        'title' => $txt['PmxBlog_your_blog_nav'],
                        'href' => $scripturl . '?action=pmxblog;sa=view',
                        'show' => !empty($modSettings['pmxblog_enabled']) && AllowedToBlog('manager', $context['user']['id']) && !empty($context['PmxBlog']['blogexist']),
                    ),
                    'yourblogsettings' => array(
                        'title' => $txt['PmxBlog_set_newblog_nav'],
                        'href' => $scripturl . '?action=pmxblog;sa=manager;set',
                        'show' => !empty($modSettings['pmxblog_enabled']) && AllowedToBlog('manager', $context['user']['id']) && empty($context['PmxBlog']['blogexist']),
                    ),
                    'blogadmin' => array(
                        'title' => $txt['PmxBlog_admin_nav'],
                        'href' => $scripturl . '?action=pmxblog;sa=admin',
                        'show' => !empty($modSettings['pmxblog_enabled']) && AllowedTo('admin_forum'),
                    ),
                 ),
             ),
 // --- end PmxBlog

            'forum' => array(
                'title' => empty($txt['sp-forum']) ? 'Forum' : $txt['sp-forum'],
                'href' => $scripturl . ($modSettings['sp_portal_mode'] == 1 && empty($context['disable_sp']) ? '?action=forum' : ''),
                'show' => in_array($modSettings['sp_portal_mode'], array(1, 3)) && empty($context['disable_sp']),
                'sub_buttons' => array(
                ),
            ),

Now, Simple Portal does pre-package a block for blogs, however PMXBlog is not recognized by Simple Portal as an installed blog mod/package.  Not to fear, with great foresight, PMXBlog includes their PmxBlogSSI.php by which one can create a PHP block in Simple Portal with one of several parameterized calls out to PmxBlogSSI.  This facilitates showing the community's blogroll in one of the sidebars or the entire blog in the main portal content area.

For reference, find examples of the PMXBlog functions available, along with descriptions of their use, recognized parameters, and so on, by hitting PmxBlogSSI_example.php.

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Nov 28

Having invested so much energy into phpBB as the forum software that drove past forum projects, and remembering the considerable investment that went into implementing and managing each of them, I decided it prudent to once again weigh my options.

In particular, I wanted for the new project, a proper forum portal as the entry point.  Look at most forum-based sites today, and notice that very few put the forum front-and-center as the entry point into the site, nay, nearly all wrap the forum within a portal giving a more polished appearance and experience.

Several months ago, I'd investigated several options for phpBB and was happiest with the portal project (phpBB Primetime) under development over at www.mylatterdays.com.  The project has been underway for some time, and is generating a following.  However Primetime seems locked in eternal release candidacy and I determined a couple of weeks ago that I can not afford the luxury of waiting any longer.  Further, phpBB is perplexing in it's degree of administrative overhead and I couldn't quite get past the thought of trying to once again wrap myself around such a tiring administrative experience.

Due diligence sent me shopping once again for a better core solution (the forum) which might also present a fully developed portal package.  Years ago, I'd looked at Vanilla, and many others as well.  Looking afresh, I made a critical evaluation of Simple Machines Forum (SMF).   I don't recall looking closely at SMF prior to landing on phpBB for the original round of forum projects - I do recall considering the general popularity and adoption of phpBB, which made it seem so appealing originally. 

I fear now that I made a gross oversight, and was about to do so once again, for truly, SMF is the simpler solution (as its name implies) yet is every bit as powerful. The key difference in my opinion is in SMF's fundamentally more logical administrative UI - this is both a measure in concept as well as function.  Finally, with several fully fledged portal options (including my choice of Simple Portal), the cut-over to SMF becomes a natural one.  Where the learning curve on phpBB made past projects tedious and cast a certain fear that the system was delicate and not for the inexperienced, I find SMF to be fantastically straight-forward and exceedingly friendly to those who don't plan to make forum administration their career.

Check it out, it's well worth putting on the eval list. Smile

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Aug 30

One annoyance that I've discovered with phpBB when incorporating the Primetime CMS mod that I've been compelled to build a fix for is the decidedly unappealing way in which the forum grid wraps the last column (Last Post in my case) when Primetime is configured to display right-side panels. 

Of course everything looks fine in "standard" resolution in full-screen mode, but shrink the window so that the (main) content column is less than about 765px and the last/fourth column in the forum grid finds its way below (and slightly overlapping) the first column in the grid.

The goal in fixing this was: 1. simplest possible solution, 2. sustainable through upgrades/updates, 3. effective.

The simple solution was ultimately plain 'ole javascript executing on window load and resize.  Meeting objective #2 meant off-boarding as much as possible into a .js include and not modifying existing .css files.  To achieve #3, I offer the following:

In /styles/prosilver/template/cms/mods, create hidelastpostcol.js and place the script below:

<script type="text/javascript">
function hidelastpostcol() {
    if (document.getElementById("cms-main-content").offsetWidth < 770) {
        i = 0;
        c = document.getElementsByTagName("dd");
        while (element = c[i++]) {
            if (element.className == "lastpost") {
                element.style.display = "none";
            }
        }
    } else {
        i = 0;
        c = document.getElementsByTagName("dd");
        while (element = c[i++]) {
            if (element.className == "lastpost") {
                element.style.display = "inline";
            }
        }
    }
}
window.onload = hidelastpostcol;
window.onresize = hidelastpostcol;
</script>

In /styles/prosilver/template/overall_header.html, above </head>, add

<!-- INCLUDE cms/mods/hidelastpostcol.js -->

In phpBB admin > Styles tab > Templates, select Refresh to clear cache.  You're done Cool

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Aug 16

Been looking forward to the next release candidate of Primetime (the premier CMS to phpBB).  This is a critical component to the new project and am hoping that it will address a couple of frustrating items that I've struggled with doing, by way of configuration, that have simply alluded me.  Mind, I'm quite sure that I can get phpBB (and Primetime) to do/act/display just about anything, anyway that I want, but this project is supposed to be all about end, without getting so caught up in the means, that the end gets forgotten.  To this, it hasn't been easy to detach with a "it's good 'nuff", but I'm trying my hardest in this respect.

So, without any further adieu, let's update to Primetime 1.0.1RC4!

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Jul 26

ManagingParadox will include the phpBB mod by EXreaction "User Blog Mod".  User Blog Mod adds a blogging system into phpBB - configurable, and controllable via the phpBB permissioning system.  This system allows registered users (if permitted) to create a blog within the forum - useful for power users and others who have higher-level 

One small mod that I have added into the User Blog Mod is a panel to list all blogs on the system.  Surprisingly, this one seemingly obvious feature is missing.  Following is my modification to include a "Blogs" panel in the left-hand menu.

In blog/includes/functions_view.php, find:

blog_plugins::plugin_do_ref('function_generate_menu', $temp);
extract($temp):

Add new lines after:

// BEGIN BLOG USER LIST
    $sql = 'SELECT pbu.user_id AS user_id, pbu.title AS title, pu.username AS username, MAX(pb.blog_id) AS blog_id, COUNT(pb.blog_id) AS cblog_id, FROM_UNIXTIME(MAX(pb.blog_time),"%b %d, %Y %l:%i %p") AS blog_time
            FROM phpbb_blogs_users AS pbu
            LEFT JOIN phpbb_users AS pu ON pu.user_id = pbu.user_id
            LEFT JOIN phpbb_blogs AS pb ON pb.user_id = pbu.user_id
            GROUP BY pbu.user_id
            ORDER BY MAX(pb.blog_id) DESC';
    $result = $db->sql_query($sql);
    while ($row = $db->sql_fetchrow($result)) {
        $template->assign_block_vars('blog_list',array('USER_ID' => $row['user_id'],'TITLE' => $row['title'],'USERNAME' => $row['username'],'COUNT' => $row['cblog_id'],'LAST' => $row['blog_time']));
    }
//    print_r($template); //debug
    $db->sql_freeresult($result);
// END BLOG USER LIST

In styles/prosilver/template/blog/left_menu.html, find:

<!-- IF S_BLOG_STATS -->

Add new lines before:

<!-- IF blog_list -->
    <div class="post bg1">
        <div class="inner">
            <span class="corners-top"><span></span></span>
            <div class="left_menu_title">{L_BLOGS}</div>
            <ul style="list-style: none;">
                <!-- BEGIN blog_list -->
                    <li class="{left_blog_links.CLASS}" style="font-weight: normal; padding-bottom: <!-- IF left_blog_links.S_LAST_ROW -->6<!-- ELSE -->4<!-- ENDIF -->px;">
                        &nbsp;<a href=blog.php?u={blog_list.USER_ID} title="{blog_list.TITLE}">{blog_list.USERNAME}</a><span title="{blog_list.COUNT} blog entries<!-- IF blog_list.COUNT --> as of {blog_list.LAST}<!-- ENDIF -->">&nbsp;(<i><b>i</b></i>)&nbsp;</span>
                    </li>
                <!-- END blog_list -->
            </ul>
            <span class="corners-bottom"><span></span></span>
        </div>
    </div>
<!-- ENDIF -->

Recache left_menu.html, and you should find a panel as shown below (Blogs) featuring all active blogs in the system, by username, in sequence of last blog entry.

 

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Jul 26

I've retired two dead forums, and put all other development projects on hold - largely because I'm too busy at my day job to continue, and partly because I want to concentrate on a forum project that I think has relevance.  More on the purpose later, in an appropriately categorized entry.

ManagingParadox.com, for the sake of rapid roll-out, will use phpBB with its most widely-adopted theme (prosilver), and few personal customization - I will include mainstream mods, but only those with real purpose and justification.  A lesson learned, my last two forums suffered low membership due to a failure to properly market and promote.  This, in turn, was due to a lack of focus and energy - I spent a great deal of time getting the look and feel of both forums "just right"...as this effort was underway, my attention was drawn elsewhere.  Bottom line: too many irons in the fire, and so much energy put into development that I simply ran out of steam to deal with the business aspect of running the site.  What I have come to learn about forum management is that the process to build legitimate membership is slow and tedious - it requires focus and attention, and (of course) a rock-solid purpose/target.

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Jul 12

Though a great deal of progress was made on RedBug over the past several months, the project will go on hold in favor of concentrating on the launch of the new forum.  The project will be re-opened in the future - the concept still has merit and deserves a fair shake at completion.

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Jul 11

Launched as an afterthought to BeenSoldOut.com, iSoothsay was originally intended to by a "fun" site - in concept, a place where people could present and open for discussion their vision (prediction) of future events, trends, etc.

iSoothsay was an easy launch in that the technology was a direct take-off from BeenSoldOut minus a logo change.  But alas, with a nebulous focus and weak purpose, the forum bombed.  I will now be redirecting all iSoothsay traffic to PigsLipstick.com.

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Jul 11

I've decided to retire BeenSoldOut.com - the site, not the domain name - while I still believe that the domain name itself has value, the work that I did to stand-up a forum based on the premise that folks had something to say about Being Sold Out has simply not materialized.  It's largely my own fault - I invested far too much time on the technology side getting the phpBB forum setup "just so" that I ran out of energy/desire to properly market the site.  That is a powerful lesson learned...

For now, I'll point BeenSoldOut.com to PigsLipstick.com.  All of the Eastern European forum spammers won't know what do with themselves once they realize what is going on, as I'm probably one of their best customer Undecided

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Sep 29

I've (re)launched iSoothsay.com today. Published at iSoothsay, the statement of purpose:

iSoothsay - simple and elegant, a name which says it all.  It must, as I am unable to conjur a suitably catchy and clever tag line.

Let us say that iSoothsay is a social sounding board - a repository of ideas, notions, predictions, and forward-looking thoughts.  Apropos for current events and attitudes, all contributions and discussion is welcome here.

Despite the fact that I feel iSoothsay is apropos given current events, and that it could develop into a positive and fruitful endeavor, I'm having somewhat of a difficult time getting into the project.

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL

Sep 28

One of my other projects, BeenSoldOut.com, a forum whose purpose is a social experiment in exploring a fundamental flaw in our human society of selling others out, is officially open now.  Having sat in Beta since the end of July, it occurred to me that something had to be done - and since there was really nothing left from a technical perspective, why not flip the switch.  Also, since I am anxious to reinvent and re-launch iSoothsay.com, I simply couldn't bear to sit on a stagnating project that (my opinion) has fair potential.

The following is the mission of BeenSoldOut.com as noted on the site itself:

Quite simply, BeenSoldOut.com is my response to feelings of immense frustration, with a society of our own creation, in which selling out is systemic and prolific in its saturation of our core value system.

As I navigate the increasingly murky and turbulent waters of the work-a-day world in which I live, I try hard to govern my actions on higher principle - act always with integrity.

I observe, all around me, quite the opposite.  I observe within myself, all too often, quite the opposite.  To sell out, or sell others out, has become part and parcel of our modus operandi - a core function, a primary means to an end, a solution of convenience, efficiency, and efficacy.

Let us consider this project a study in sociology, a learning exercise, a collection of datapoints on the topic of selling out, and the effects of being sold out. 

We should endeavor to realize true value from the data - to synthesize it, digest it, learn lessons from it.  But, let us also not be naive, as there truly is no singular objective - only to collect and glean, to learn a bit about ourselves in the process, and perhaps to affect even a glimmer of positive change in our own guiding philosophy, and that of those around us.

Best of luck to us all,
Adam Krause

So, feeling frustrated, angry, guilty, maybe even giddy or proud of having been "sold out" or "selling someone out"?  I respectfully invite you to record the incident for examination and comment.

Posted by Adam KrauseGo w.i.d.eTweet MeShort URL


Strict Standards: Declaration of serendipity_event_s9ymarkup::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_s9ymarkup/serendipity_event_s9ymarkup.php on line 146

Strict Standards: Declaration of serendipity_event_s9ymarkup::uninstall() should be compatible with serendipity_plugin::uninstall(&$propbag) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_s9ymarkup/serendipity_event_s9ymarkup.php on line 146

Strict Standards: Declaration of serendipity_event_emoticate::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_emoticate/serendipity_event_emoticate.php on line 204

Strict Standards: Declaration of serendipity_event_emoticate::uninstall() should be compatible with serendipity_plugin::uninstall(&$propbag) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_emoticate/serendipity_event_emoticate.php on line 204

Strict Standards: Declaration of serendipity_event_nl2br::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_nl2br/serendipity_event_nl2br.php on line 395

Strict Standards: Declaration of serendipity_event_nl2br::uninstall() should be compatible with serendipity_plugin::uninstall(&$propbag) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_nl2br/serendipity_event_nl2br.php on line 395

Strict Standards: Declaration of serendipity_event_browsercompatibility::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_browsercompatibility/serendipity_event_browsercompatibility.php on line 80

Strict Standards: Declaration of serendipity_event_spartacus::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_spartacus/serendipity_event_spartacus.php on line 1183

Strict Standards: Declaration of serendipity_event_imageselectorplus::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_imageselectorplus/serendipity_event_imageselectorplus.php on line 1105

Strict Standards: Declaration of serendipity_event_imageselectorplus::uninstall() should be compatible with serendipity_plugin::uninstall(&$propbag) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_imageselectorplus/serendipity_event_imageselectorplus.php on line 1105

Strict Standards: Declaration of serendipity_event_sidebarlogin::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_plugin_sidebarlogin/serendipity_event_sidebarlogin.php on line 148

Strict Standards: Declaration of serendipity_event_popfetcher::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_popfetcher/serendipity_event_popfetcher.php on line 1426

Strict Standards: Declaration of serendipity_event_lightbox::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_lightbox/serendipity_event_lightbox.php on line 281

Strict Standards: Declaration of serendipity_event_lightbox::uninstall() should be compatible with serendipity_plugin::uninstall(&$propbag) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_lightbox/serendipity_event_lightbox.php on line 281

Strict Standards: Declaration of serendipity_event_tinymce::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_tinymce/serendipity_event_tinymce.php on line 291

Strict Standards: Declaration of serendipity_event_tinybrowser::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_tinybrowser/serendipity_event_tinybrowser.php on line 150

Strict Standards: Declaration of serendipity_event_prettify::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_prettify/serendipity_event_prettify.php on line 245

Strict Standards: Declaration of serendipity_event_xmlrpc::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_xmlrpc/serendipity_event_xmlrpc.php on line 160

Strict Standards: Declaration of serendipity_event_podcast::event_hook() should be compatible with serendipity_event::event_hook($event, &$bag, &$eventData, $addData = NULL) in /home1/pigslips/public_html/s9y/plugins/serendipity_event_podcast/serendipity_event_podcast.php on line 939

Strict Standards: Non-static method TwitterPluginFileAccess::get_permaplugin_path() should not be called statically, assuming $this from incompatible context in /home1/pigslips/public_html/s9y/plugins/serendipity_plugin_twitter/serendipity_event_twitter.php on line 1554

Strict Standards: Non-static method TwitterPluginDbAccess::load_short_urls() should not be called statically, assuming $this from incompatible context in /home1/pigslips/public_html/s9y/plugins/serendipity_plugin_twitter/serendipity_event_twitter.php on line 1518