Joomla 3.6, SEBLOD 3.8.4, PHP 7.0.7.
For a few years I was using BreezingForms for my frontend forms (BF looks great, is super easy and works out of the box) and SEBLOD for backend forms/content types. Now I decided to make things right and to recreate all my frontend forms in SEBLOD to get rid of BF. Everything went smooth - I created one form, made it send the results to two email accounts. But then looked into errors_log and saw these two lines multiplied every time I filled the form for testing purposes:
Undefined Index: to_admin in /.../plugins/cck_field/email/email.php on line 177
Undefined index: _ in /.../libraries/cck/base/form/store_inc.php on line 227
As for the first line - I pointed one administrator in 'To (Administrators)' and the first error disappeared, BUT the form also stopped sending results to emails completly. So I un-pointed that administrator, the form started sending the results again, but the error also appeared in my errors_log. Is pointing at least one administrator in 'To (Administrators)' compulsory?
As for the second line - I have in my form two text fields, one textarea, one email field, one recaptcha and one button-submit field - all of them hava disabled storage option or set the storage to NONE, as I want the filled forms only to be sent to email addresses defined by me.
Don't get me wrong - the form seems to work flawlessly, there is no sign of any malfunction, it's just that fast growing errors_log gets me worried.
What is going on? Or what am I doing wrong?
Hi there,
Glad to hear you're creating all your forms the correct way with everything using SEBLOD :)
Can you send a screenshot of your email field setup please? It is not compulsory to define an admin as a recipient, so I am confused by this. Also, did you set up all of your fields with storage <none> the first time? Or did you go back and edit your fields to do this?
I would suggest that you should re-create your email field again, to see if this solves the issue. I would also suggest turning off error reporting, if you can confirm that all the behaviour in your form is OK.
Cheers,
James
Thank you for your kind reply,
Yep, I created forms (4 of them actually) from the scratch, setting the storage for all fields to NONE right from the beginning. And all 4 of them cause these stupid warnings in my log. Below you can find my configuration of email field (in fact I changed only e-mail addresses for the screenshots purposes).
I'm a type of guy that has logging warnings turned on and LOVE to keep it clean, but I'm tired of struggling. The forms work like they should, so I turned logging warnings off, but... it's just the workaround, you know. It would be great to know the cause of these warnings - is it a bug or is it my lack of skills ;-)
Hi,
it is a harmless notice, in code we should add check if mentioned array index is present before checking for it's value, I'll make a pull for next version. YOu can as well just lower erorr reporting level to minimum, so that it will still report when something bad happens (actual error or fatal error).
Thank you Klas, I've already done that. Lowering level of error reporting is these days good for my mental health.
I made 2 pull requests to fix this notices
