I love the theory of this module but I have not been able to successfully run it.

I am using the Alpha 3 Version with the latest DataSync FeedAPI module.

I get this error message only on the job schedule. I am curious if it is conflicting with another module??

Comments

andrewlevine’s picture

andrewlevine commented

Do you have the latest (rc1) of ctools installed?

LiveWire’s picture

LiveWire commented

Yes.

I am thinking that I did not apply the fork patch correctly??

andrewlevine’s picture

andrewlevine commented

Could you temporarily put a 

print_r(debug_backtrace());

on line 978 of form.inc and paste me the debug output it creates?

LiveWire’s picture

LiveWire commented

This is what it kicks out now

Parse error: syntax error, unexpected '<' in /home3/flirtwit/public_html/Gator/includes/form.inc on line 977

andrewlevine’s picture

andrewlevine commented
Category: bug » support

Don't actually put the php tags, just the line inside.

LiveWire’s picture

LiveWire commented

:( I apologize for not paying attention.

Once I ran it I received over 1000 lines of Arrays. They did not appear to have a rhyme or reason. It then crashed the browser repeatedly. Would the first line be helpful?

Thank you in advance.

andrewlevine’s picture

andrewlevine commented

try adding this (without php tags again)

if (strpos($form_id, 'datasync') !== FALSE) print_r(debug_backtrace());

That should be less verbose

LiveWire’s picture

LiveWire commented

Andrew,

Thanks for your help. I apologize for being a noob with php.

On the schedule screen I get the same screen long array messages . . .

Array ( [0] => Array ( [file] => /home3/flirtwit/public_html/Gator/includes/form.inc [line] => 876 [function] => _form_builder_handle_input_element [args] => Array ( [0] => datasync_schedule_job_form [1] => Array ( [#name] => datasync_scheduler_job_type [#title] => Job type [#type] => select [#options] => Array ( [datasync_feedapi] => FeedAPI ) [#description] => Type of job you want to add [#default_value] => datasync_feedapi [#attributes] => Array ( [class] => ctools-use-ajax-onchange ) [#id] => ctools-ajax-url-4a8173be05cc1 [#post] => Array ( ) [#programmed] => [#tree] =>

andrewlevine’s picture

andrewlevine commented

It looks like all the output wasn't included in your post. try wrapping what you paste with

andrewlevine’s picture

andrewlevine commented

that didn't show up right, i meant wrap it with code tags

brianbrown’s picture

brianbrown commented

I'm having the same issue with the dev. branch.
I would suggest altering the readme.txt as follows:
Change from:

3. Copy the db_allow_fork.patch file from the DataSync folder
to your Drupal root directory and run the command
patch -p0 < db_allow_fork.patch to patch Drupal core.
(note this is a one line change and should not affect
any other modules) [sic]

to read:

3. Copy the db_allow_fork.patch file from the DataSync folder
to your Drupal includes directory and run the command
patch -p0 < db_allow_fork.patch to patch Drupal core
(note this is a one line change and should not effect
any other modules).

This is the only way the patch will be applied as written; it must be copied to the 'includes' directory.
Regards,

Brian Brown, Ph.D.
"Geeking for 47 years!"
Drupal Grammar Nazi

P.S. Sorry about the hijack, but I, too, have the same issue as captioned above!

andrewlevine’s picture

andrewlevine commented

brian - can you paste in the same debug output that I asked musry to? And make sure it's in the proper code tag so it all shows up? Also, are you sure you're using the most recent dev version? I fixed the patch to use the includes directory on july 24th

andrewlevine’s picture

andrewlevine commented
Status: Active » Fixed

actually fixed this in commit 1.1.2.5 when I ran into another bug it caused. Let me know if the bug still persists in beta2 (it shouldn't)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.