I've been creating a few new events (with repeats) and the following warning has been popping up after each one:

"Warning: implode():Invalid arguments passed in form_error() (line 1645 of /usr/share/OpenChurch7/includes/form.inc).

It does save the event and add to my calendar, but is not repeating the event so I'm guess the error has something to do with this??

What does this warning message mean? and how do I fix the problem?
Thanks!

Comments

PedroDDM’s picture

PedroDDM CreditAttribution: PedroDDM commented

Hello, for errors (and warnings) for PHP5 which should be displayed only in development mode but not when our site is in production (is this your problem?), I tried to fix it by making modifications as suggested in the comments of the php.ini file itself for the deployment of these ads are not shown when my site is in production, but apparently the drupal core (my site is in D6) assume (I do not know the reason) the directive value "error_reporting" by default, so that my modifications in php.ini no effect.
Although there have been patches that fix this, in my case, I solved this drawback by changing the index.php file in the root of my site drupal installation.
This is the file: htdocs/name_of_my_site/index.php, add the line:

error_reporting (! E_WARNING);

immediately below of the lines:

require_once '. / includes / bootstrap.inc';
drupal_bootstrap (DRUPAL_BOOTSTRAP_FULL);

Note that in my case it was enough to E_WARNING, but we have to try different values ​​allowed for this directive in php.ini.

Hope this helps somewhat.

thefranklincrew’s picture

thefranklincrew CreditAttribution: thefranklincrew commented

Thanks for the tip. Does anyone know though why it is not repeating the events on my calendar? Is there an association with the warning message? Thanks!

j_ali’s picture

j_ali CreditAttribution: j_ali commented

It's clearly related to what is described in this issue: http://drupal.org/node/1248274

It may be that deleting all current events and the field_oc_dates field and then re-creating it all again would fix it although drupalninja99 seemed to suggest he'd worked out a way of implementing it so that this wouldn't be necessary.

Once a few more people start using 1.11-alpha2 we'll know a bit more.

Meantime, I'll see if I can put together a test instance and see if such drastic actions would solve the problem.

j_ali’s picture

j_ali CreditAttribution: j_ali commented
Status: Active » Closed (works as designed)

Found it! The problem was that we hadn't reverted the OpenChurch Event feature at /admin/structure/features/openchurch_events as instructed in the upgrade instructions. Oops.