• Hello,

    We have been running a wordpress website successfully on php5.2 with ISAPI but we need to upgrade the server to 5.3 which no longer supports isapi so using fastcgi.

    When the upgrade was done we are getting a lot of errors similar to these:-

    Warning: Parameter 1 to ec3_filter_posts_where() expected to be a reference, value given in C:\Wordpress_orginal\wp-includes\plugin.php on line 166
    
    Warning: Parameter 1 to ec3_filter_posts_join() expected to be a reference, value given in C:\Wordpress_orginal\wp-includes\plugin.php on line 166
    
    Warning: Parameter 1 to ec3_filter_posts_groupby() expected to be a reference, value given in C:\Wordpress_orginal\wp-includes\plugin.php on line 166
    
    Warning: Parameter 1 to ec3_filter_posts_orderby() expected to be a reference, value given in C:\Wordpress_orginal\wp-includes\plugin.php on line 166
    
    Warning: Parameter 1 to ec3_filter_posts_fields() expected to be a reference, value given in C:\Wordpress_orginal\wp-includes\plugin.php on line 166

    These are referring to a plugin I am using called event calendar (http://wpcal.firetree.net/) which is essential for the running of the site.

    If I disable this plugin i get the following errors:-

    Warning: strtotime() [function.strtotime]: 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 'Europe/London' for '1.0/DST' instead in C:\Wordpress_orginal\wp-includes\functions.php on line 35
    
    Warning: date() [function.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 'Europe/London' for '1.0/DST' instead in C:\Wordpress_orginal\wp-includes\functions.php on line 43
    
    Warning: strtotime() [function.strtotime]: 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 'Europe/London' for '1.0/DST' instead in C:\Wordpress_orginal\wp-includes\functions.php on line 35
    
    Warning: date() [function.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 'Europe/London' for '1.0/DST' instead in C:\Wordpress_orginal\wp-includes\functions.php on line 43

    Can anyone help me fix both the timezone issue and the event calendar plugin.

    Thanks

    Dave.

Viewing 5 replies - 1 through 5 (of 5 total)
  • I had a similar problem with Event Calendar when we moved up to PHP5.3 although I didn’t see the timezone errors.

    Oddly, another site where WP and EC were freshly installed on 5.3 worked without complaint.

    Anyway, I found this, applied the hack to eventcalendar3.php and it seems to be working fine.

    Hope this helps,
    Mick

    I found that : http://wpcal-archive.firetree.net/2009-November.txt

    In eventcalendar3.php change all of the “filter” function definitions to not declare “pass by reference”. Make them look like the lines with “+” in front of them.

    -function ec3_filter_getarchives_where(&$where)
    +function ec3_filter_getarchives_where($where)

    -function ec3_filter_getarchives_join(&$join)
    +function ec3_filter_getarchives_join($join)

    -function ec3_filter_get_archives_link(&$link_html)
    +function ec3_filter_get_archives_link($link_html)

    -function ec3_filter_posts_where(&$where)
    +function ec3_filter_posts_where($where)

    -function ec3_filter_posts_join(&$join)
    +function ec3_filter_posts_join($join)

    -function ec3_filter_posts_orderby(&$orderby)
    +function ec3_filter_posts_orderby($orderby)

    -function ec3_filter_posts_groupby(&$groupby)
    +function ec3_filter_posts_groupby($groupby)

    -function ec3_filter_posts_fields(&$fields)
    +function ec3_filter_posts_fields($fields)

    -function ec3_filter_post_limits(&$limits)
    +function ec3_filter_post_limits($limits)

    -function ec3_filter_the_content(&$post_content)
    +function ec3_filter_the_content($post_content)

    -function ec3_filter_the_content_bigcal(&$post_content)
    +function ec3_filter_the_content_bigcal($post_content)

    Worked for me,
    wordpress 2.9.1
    ec3 calendar Version 3.2.beta2

    I had the same problem and
    changed some thing binding on @rwanito

    result is it worked 🙂

    I’m using Event Calendar Version 3.1.4 :
    http://wpcal.firetree.net/
    I don’t follow. What is the fix? Just get rid of the ampersands?
    That was too easy?? 🙂 It works.

    I see some other functions with the (&$variable) form in admin.php and date.php. Has anyone seen any problems arising from them?

    In other words, was it just a problem with the specific functions mentioned above, or is this syntax no longer valid in PHP5.3.3 at all? I’ve never seen (&$variable) used before, so I don’t know what it’s even supposed to do or if there’s a preferred alternative.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘php5.3 and fastcgi on IIS with wordpress’ is closed to new replies.