Strict Standards: Redefining already defined constructor for class wpdb in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/wp-db.php on line 52

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/cache.php on line 389

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/classes.php on line 556

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/classes.php on line 678

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/theme.php on line 507

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/wp-db.php:52) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-content/plugins/contactforms/cforms.php on line 61

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/wp-db.php:52) in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-content/plugins/contactforms/cforms.php on line 61

Deprecated: Function split() is deprecated in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-content/themes/jr_articles/header.php on line 3
J.R. Photoblog - Articles & Tutorials » Blog Archive » Is your Pixelpost template available anywhere?
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/kses.php on line 446

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/kses.php on line 510

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/kses.php on line 511

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28

Is your Pixelpost template available anywhere?


Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/formatting.php on line 74

template.jpgUnfortunately no, and that for two reasons:

1. Because coding it took me nearly 100 hours of work and, as the pictures, it is part of my identity.
2. Because I had to patch up my Pixelpost a bit and it won’t be compatible with the standard version.

One of the most frequent questions is “How did you achieve the comments sliding panel?“.

It is very difficult to answer this question because it is web coding and you need to have some quite strong knowledge about HTML, CSS and JAVASCRIPT.

Luckily, not all has to be done because I’m using the MOOTOOLS javascript framework; this tremendous library can do a lot of thing but I only use animation effects and more technically the Fx.Style class. This class take care of interpolating values between the start and the end value of a CSS property. What is this gibberish? This is simple and very powerful, lets say we have a DIV tag with a width of 300 and at the end of the animation I want a width of 600. I simply ask to the mootools function “animate this DIV from 300 width to 600 width”, you can even chose between “transition styles” (like linear, elastic, etc.). This class can drive any CSS property, so I let you imagine the possibilities…

Here is a very simple example of how I did to have a “smooth” background color change: demosource

Unfortunately I don’t have enough time to speak more about that and it would be useless because the creators already took care of that.
On the MOOTOOLS website, you will find an expanded documentation and excellent examples.

6 Comments »


  1. Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/formatting.php on line 74

    hey, thank for the info

    i was wondering if you have any info/links on the mouseover effect you have, i see that you are using jquery, ive been struggling to make jquery and mootools run together. You’ve done it beautifully, keep up the great work.

    thanks for sharing

    Julien : I use Mootools, especially the Fx.Styles part of Mootools ;)

    Comment by tomms —
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    April 8, 2008 @
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    1:44 pm


  2. Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/formatting.php on line 74

    So you used open source software to make this website but you don’t release the code?
    Isn’t this a little selfish of you?
    And you don’t share your code because you spent 100 hours on it?
    How many hours do you think were needed to build the mootools that you liked using so much?
    This entire post makes absolutely no sense, dude…

    Julien :
    Not because I spent 100 hours on it but because this is a template, so this is a graphical identity and this is my identiy… Would you like everyone to wear the same t-shirt as you ? I know what is sharing because I share some others of my programs but sharing a graphical identity makes absolutely no sense, dude…

    Comment by Francesco
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    December 31, 2008 @
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    7:22 am


  3. Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/formatting.php on line 74

    LOL - the other person is upset because you won’t give him a free copy of your template! Open Source of not, it’s your creative material. I, on the other hand would be happy to PAY GOOD MONEY for your template!!!! :) However, I understand the idea of developing a unique identity, so in that regard, it is important for you to maintain that.

    Let me just say that your photoblog is the most elegant and stunning format I have ever seen. Great job, and if you ever got the itch to develop a modified version of your template, please, please, please let me know!

    Julien :
    I’m glad to hear that Bry993, thanks ! :)

    Comment by Bry993 —
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    January 29, 2009 @
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    11:29 am


  4. Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/formatting.php on line 74

    I had the same question so I’m glad you posted the answer, to save me searching around for that template! It is very nice.

    Comment by Beth —
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    March 29, 2009 @
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    6:59 am


  5. Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/formatting.php on line 74

    After being directed here and seeing your site, I just want to say well done on one of the best photoblog sites I have ever seen, an amazing deisgn, as we all would love to hav eyour design i understand why you want to keep it to yourself. After 100 hours coding is a lot of time well spent on the end product.

    Well done

    Comment by Dan
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    October 10, 2009 @
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    3:46 am


  6. Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/formatting.php on line 74

    Hi,
    Impressive, but is there a way that we can add a blog into pixelposts, one that shows the photos in a post, but also is posted in the gallery, or album?
    Probably not, but was just hoping someone knows how to do this…?
    Thanks,
    Jim

    Julien :
    I have no idea Jim, perhaps a pixelpost plugin. You should ask this into the pixelpost forum

    Comment by Jim —
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    October 21, 2009 @
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 14

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 23

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 25

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 27

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/15/d175376943/htdocs/BLOG_JR_WORDPRESS/wp-includes/functions.php on line 28
    3:47 pm

Leave a comment

Please don't leave a comment to say 'thank you' but only if you have something interesting to add or to ask, ;) .


» Close
E-mail It