Strict warning: Declaration of date_handler_field_multiple::pre_render()

After applying the patch in comment #61 here https://www.drupal.org/node/893128, the patch here should no longer be necessary.

@akosipax: I do have the patch #61 from #893128: Fix E_STRICT notices - method declaration compatibility with init(), pre_render(), _validate() and _submit() with PHP 5.4.x applied to Views 6.x-2.18, which in fact fixes many "Declaration of ... should be compatible with ..." errors.

However, I was still getting the error

Declaration of date_handler_field_multiple::pre_render() should be compatible with views_handler_field::pre_render(&$values) in /etc/drupal6/all/modules/date/date/date_handler_field_multiple.inc on line 185.

with Date 6.x-2.10. Applying mikeytown2 's patch #1 from this report does fix the error! So, both patches are required.

UPDATE:

The error came back after applying patch #4 from #2327005: E_STRICT compliance to CCK 6.x-3.0-alpha3+13-dev.

Thus, no patch should be applied to Date 6.x-2.10! The fix is to patch CCK.

For anyone else that is confused by #4, it turns out there is a layer of class hierarchy between Date and Views provided by CCK and this bit of the patch takes care of making CCK match both Date and Views:

- function pre_render($values) {
+ function pre_render(&$values) {

Sorry, still confused.

Server was upgraded to PHP and MySQL 5.5, been updating all my drupal sites since then. One in particular is giving this error: Declaration of date_handler_field_multiple...

So, what do I need to patch?

;)

Steel Rat: You need to patch CCK since that is where the actual error is. The patch is in https://www.drupal.org/node/2327005 .

Thanks Michelle.

Another question, I rarely patch, and usually do so manually because I don't have shell access to the server.

Is there a way I can patch locally on my PC? Then upload the patched files back to the server? Some of these patches are just too extensive to do manually.

Many thanks!

We use a git workflow so that the patching is done locally and then the changes are pushed to dev/test/prod. If you aren't using version control, you can just use an FTP program to overwrite the files on prod with the patched version. Make sure you keep a note of which patches you've applied so you don't overwrite them with updates.

Which application would I use on a windows machine to run a patch?

I don't use Windows for web development. Try something from here: https://www.drupal.org/node/60179

This wasn't actually "fixed" because it wasn't actually a problem. No patch was committed here.