Posted by jupiterchild on September 13, 2008 at 9:43am
5 followers
| Project: | Trackfield |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Since I updated KML module to version 5.x-1.x-dev (2008-Sep-11) I have noticed this error appearing in my logs:
join() [function.join]: Invalid arguments passed in /****/****/****/cms/sites/all/modules/trackfield/trackfield_kml_out.module on line 28.
Comments
#1
I can only imagine this could happen if the
$node_arraypassed into functiontrackfield_kml_out_kml_feed_extrasis empty.Can you check the URL that is being accessed and if the KML that is supposed to be generated should contain any nodes?
#2
The error message above only happens for anonymous user ie user not logged in.
On the same node I get this error when logged in with admin rights:
array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /****/****/****/cms/sites/all/modules/trackfield/trackfield_kml_out.module on line 18.
Played around with some of the changes I have recently made and found both these error messages only occur if CCK_Location module is enabled. I need to test this a little more to confirm this is this issue.
Also noticed that for anonymous user KML does not zoom to the co-ordinates but stops at the global display. Will create an issue over at the KML project.
#3
Ignore number 2 (can you believe a Mac keyboard does not have an hash key, and I cannot remember the code for the hash!)
Anyway as anonymous user I still get the original error message even when CCK_location is disabled. I cannot yet find any common problem here. I have checked the nodes which are shown in the logs with an error but cannot always repeat the error, sometimes I get the error and other times not. Will work on this somemore tomorrow.
#4
hello,
I try to use this module with Garmin MapSource GPX files. Ideally, I'd upload a GPX File as attachment and have the module show the map with the track.
But I also get this error
Now, the GPX file itself is fine. If I take the content of the GPX and put it in the "Track data" text field, I do get the map showing my track!
So I tried another route: CSV files. Here I get the same error when I try to usse an attached uploaded file. (Putting data in the text box kind of works, it just complains about invalid format of the CSF format that I get from Garmin MapSource)
So, something with parsing the attached file seems wrong?
And btw, thanks for this module - exactly what I need :)
#5
changed the subject because it seems to be independent of file type
#6
Re: #4 - this is with the D6 version, right?
#7
sorry, forgot to mention: Trackfield 6.x-1.0
#8
ahem, I feel so stupid :(
I just forgot to
" Place the filename with your data in inside the value part of the trackfield. Thus multiple files can be attached to a node but only one used for this purpose."
Attached GPX is working fine now
sorry!
#9
Ah, yeah. I guess this could do with some better error checking. Not urgent but not able to close this one yet then either.
#10
I'm getting the same join related error as above in a totally different circumstance. I have an optional data only trackfield setup (no use of file attachments) for gpx data, which is fine on a normal node save edit. When I use a view that saves nodes, such as a draggable_views view or a views_bulk_operations view, I get one of these errors for every single node in the view:
warning: join(): Invalid arguments passed in ../sites/all/modules/trackfield/trackfield.module on line 292.As you can imagine, in a view with 50 nodes a cascade of these submission errors becomes very annoying. To make matters worse, this error prevents editablefields from validating at all, so trackfield is essentially incompatible with the editablefields module even if the trackfield itself is not set as an editablefield.
Is there any chance you could issue a fix or workaround to prevent this error from occurring?
#11
Obviously (duh) setting errors to be displayed only in the logs solves the usability issue, but It'd still be great to have this solved so as to avoid having the error logs weigh down the database.
#12
I found the error, is imposible to config the upload file field because drupal need field looks like "field_something", my pach solved it but you MUST call the field "field_files". You will find an example in the attached files.