Ticket #428 (closed defect: duplicate)

Opened 4 years ago

Last modified 4 years ago

Error message when adding project

Reported by: ed Owned by: jim
Priority: critical Milestone: PSE
Component: Drupal modules & settings Keywords:
Cc: Estimated Number of Hours: 0.0
Add Hours to Ticket: 0 Billable?: yes
Total Hours: 0

Description

Add project from widget added to edmitchell.co.uk while logged in as test user1 in other tab), went straight to step 2, got error message but it still said it stored the project:
" • Warning: mysql_real_escape_string() expects parameter 1 to be string, array given in db_escape_string() (line 410 of /web/transitionnetwork.org/www/includes/database.mysql.inc).

• Unknown error: Function split() is deprecated in mimemail_extract_files() (line 102 of /web/transitionnetwork.org/www/sites/all/modules/mimemail/mimemail.inc)."

Change History

comment:1 Changed 4 years ago by jim

The second error is a PHP5.3 issue in Mime Mail module, now patched.

The first error is actually indicative of a set of bigger issues I have just realised exist... It boils down to me asking Drupal for a project form, then removing the items we don't want... This means lots of stuff is hanging around which is causing a bunch of errors and warnings behind the scenes.

I need to rewrite a portion of the widget code to build my own slimline form and save to a new Project node, rather than manhandle the project node form... Annoying but not too big a change. Wish I'd spotted this before :-(

I'll therefore fix the first message when the new code is written shortly.

comment:2 Changed 4 years ago by ed

now we're cooking with gas!

comment:3 Changed 4 years ago by jim

OK so the rewrite is done, and things are much cleaner... That fking message is still there though, and it's caused by a related save to the initiative that the 'corresponding node references' module fires -- when we add a related ini to a project, the reverse relationship updates, causes an ini save and tries to send a notification.... What precisely is wrong with this I can't tell as yet.

I'll come back to this...

Version 0, edited 4 years ago by jim (next)

comment:4 Changed 4 years ago by jim

  • Status changed from new to closed
  • Resolution set to duplicate

Now covered by/a duplicate of #445, and the new approach is outlined there.

Note: See TracTickets for help on using tickets.