General discussion on the "services/logs/submit" method.

[opencaching]

General discussion on the "services/logs/submit" method.

[GoogleCodeExporter]

It maybe add parameter optional "recom" for recommendation cache and next param 
"rate" to rate cache like during use log.php and some caches need password to 
put log entry and we are need param "password"

Original comment by sp2ong on 30 Aug 2011 at 5:45

[GoogleCodeExporter]

I have test cache 
http://opencaching.pl/viewcache.php?wp=OP28F9

we can use this cache to test submit logs. Password for log entry "Found" is 
"haslo123"

Original comment by sp2ong on 30 Aug 2011 at 5:50

[GoogleCodeExporter]

It mabye better change name of param "when" to "date" ?

Original comment by sp2ong on 30 Aug 2011 at 5:52

[GoogleCodeExporter]

See issue 66, issue 67, issue 68.

Original comment by rygielski on 30 Aug 2011 at 6:02

[GoogleCodeExporter]

In r93 I can see line 118: 

"throw new CannotPublishException("Your comment must have at least 5 
characters."." 

Why? On opencaching.pl site, You can "write" an *empty* log (found it/didn't 
found it) or comment with 1 character.

Original comment by kkarczmarczyk on 30 Aug 2011 at 8:00

[GoogleCodeExporter]

You're right. I was quite sure you couldn't. Will fix this later.

Original comment by rygielski on 30 Aug 2011 at 8:17

[GoogleCodeExporter]

Easy - It's low priority, but, You now... Many people say only "TFTC" in 
comment, or something like this ;)

Original comment by kkarczmarczyk on 30 Aug 2011 at 8:28

[GoogleCodeExporter]

Related issue 114: Add langpref parameter for logs/submit.

Original comment by rygielski on 15 May 2012 at 9:27

[GoogleCodeExporter]

It would be great to get a structured information about what went wrong, and 
not only a localized message. For example, if the password is wrong, an 
application could let the user type a new password in a dedicated interface.

Original comment by [email protected] on 13 Aug 2014 at 10:47

[GoogleCodeExporter]

Good idea! Please submit it as a new feature request. Perhaps someone will 
implement it soon.

Original comment by rygielski on 13 Aug 2014 at 11:48

[GoogleCodeExporter]

A possibility to add a photo with title and description would be nice.

Original comment by [email protected] on 22 Jun 2015 at 4:52

[following5]

Some more explanation on the handling of the needs_maintenance logs/submit option:

OKAPI follows the straightforward paradigm that one log entry can completely describe one cache search, e.g. including the information "I did find the cache" and "the cache needs maintenance". However, some OC installations (the OCPL-based ones) have copied the GC paradigm of assigning a separate log type to the information "needs maintenance" - so the user in this example case must post two logs e.g. on Opencaching.pl.

As OKAPI consequently does not include the option to submit dedicated "needs-maintenance"-type logs, it needs to translate the cases mentioned above from one to two logs. E.g. the application submits a "Found it" + "needs maintenance" log entry, and OKAPI will split it up into a "found it" and a "needs maintenance" logs on OCPL sites. The supplied comment text will end up in one of these two logs, while the other will have an empty text. Note that this is not the case for logs of type 'Comment', which are stored as just one NM log.

On the other hand, the (upcoming) OCDE implementation follows the same paradigm as OKAPI. So any log submitted via OKAPI will be published as one log; there is no translation.

[bacza]

Hello, are there any constraints on log text length (comment field) imposed by this method?
I mean min/max length of the text (maybe depending on log type?)
Thanks!

[following5]

Logs of type "Comment" must not be empty, so the minimum size is 1 character. Any other log type's comment - e.g. "Found" - may be empty.

The maximum length is dependent on the OC site's database configuration. All OC sites currently accept at least 16 MB; longer comments may be truncated.