Per comment #84 in issue "Fix E_STRICT notices...", I am opening up a new issue.

It's my understanding that the current release, Views 6.x-2.18 2015-Feb-11, should be PHP 5.4x compatible? Forgive me if I've overlooked the obvious.

Current warnings using Views 6.x-2.18 on PHP 5.4.38:

strict warning: Declaration of views_handler_filter_node_status::operator_form() should be compatible with views_handler_filter::operator_form(&$form, &$form_state) in sites/all/modules/views/modules/node/views_handler_filter_node_status.inc on line 13.

strict warning: Declaration of date_handler_field_multiple::pre_render() should be compatible with content_handler_field_multiple::pre_render($values) in sites/all/modules/date/date/date_handler_field_multiple.inc on line 185.

strict warning: Declaration of uc_views_handler_field_money_amount::options() should be compatible with views_object::options() in sites/all/modules/uc_views/views/uc_views_handler_field_money_amount.inc on line 36.

strict warning: Declaration of uc_views_handler_field_cart_user::init() should be compatible with views_handler_field::init(&$view, $options) in sites/all/modules/uc_views/views/uc_views_handler_field_cart_user.inc on line 78.

strict warning: Declaration of views_handler_field_user_name::init() should be compatible with views_handler_field_user::init(&$view, $data) in sites/all/modules/views/modules/user/views_handler_field_user_name.inc on line 61.

strict warning: Declaration of semanticviews_plugin_style_default::options() should be compatible with views_object::options() in sites/all/modules/semanticviews/semanticviews_plugin_style_default.inc on line 232.

strict warning: Declaration of views_attach_plugin_display_node_content::options_submit() should be compatible with views_plugin_display::options_submit(&$form, &$form_state) in sites/all/modules/views_attach/views_attach_plugin_display_node_content.inc on line 248.

Comments

IFL Todd’s picture

IFL Todd commented
Priority: Major » Critical

I am changing this to be marked as critical. Here's why:

PHP 5.3x, since reaching EOL, fails PCI compliance. Whether we like it or we don't many, many website owners are being forced now to move to a currently supported version of PHP. D6.x Views releases, being a critical component to still more than 118K sites, should operate on at least the minimum currently supported version of PHP - in this case that is PHP 5.4x.

Actually, it really should operate on at least PHP 5.5.x because PHP 5.4 is slated to reach EOL on 14 Sep 2015 - just 5 months from now. At that time, Drupal 6 will still be supported, and again Views is just critical to almost any Drupal website, beyond a simple static site. If we extrapolate the current Views 6.x decline in usage through September, their will still be more than 100,000 6.x users, a great number of whom need PCI compliant software, and also whom rely on their websites for their means.

Most people, I would guess, are scrambling to get Drupal 7 replacement sites built before Drupal 6 reaches EOL itself - I know we are. In the mean time, Drupal 6 is what we have, and Views is the single most critical modular component to our Drupal 6 websites, well that and CCK. :-)

I realize everyone here donates their time, and I am unbelievably grateful as I know thousands of others are for Drupal, and especially the awesomeness Views brings to the table to extend Drupal. If I could fix this I would. I just don't have the skills to do it. If I can help with this issue, tell me how.

Please, please help.
Thank you,
Todd

IFL Todd’s picture

IFL Todd commented
Status: Active » Closed (duplicate)

I just saw this thread, which appears to fix this issue with views 6.x-2.x. So I am marking this as a duplicate and closing it.

Strict warnings with PHP 5.4.x (fixed - comment #61)