| | 56 | |
| | 57 | == Entries == |
| | 58 | |
| | 59 | To post a new entry you can either: |
| | 60 | * send it to bot like always, |
| | 61 | * send it to {{{jogger:}}} UID in jogger session (which is gateway to bot), |
| | 62 | * use file-based interface described below. |
| | 63 | |
| | 64 | If {{{ignore_outgoing_entries}}} session variable is set, jogger plugin will not display sent entries as messages. Else they'll appear as messages sent to {{{jogger:}}}. |
| | 65 | |
| | 66 | === File-based interface === |
| | 67 | |
| | 68 | First you need to write new entry and save it as a standard file. Here we'll assume that you named it {{{~/entry.html}}} (using .html extension triggers syntax highliting in many editors). |
| | 69 | |
| | 70 | Then (in jogger session) you call: |
| | 71 | {{{ |
| | 72 | /prepare ~/entry.html |
| | 73 | }}} |
| | 74 | |
| | 75 | Now if file can be read successfully, jogger plugin can output some warnings and then: |
| | 76 | {{{ |
| | 77 | 14:03:39 ::: File ~/entry.html is ready for submission. |
| | 78 | }}} |
| | 79 | |
| | 80 | If you want to modify the file and recheck it, just run {{{/prepare}}} again. It does memorize last used file, so you don't have to enter it again. |
| | 81 | |
| | 82 | When your entry is ready for submission, use: |
| | 83 | {{{ |
| | 84 | /publish |
| | 85 | }}} |
| | 86 | |
| | 87 | If file was modified after last {{{/prepare}}}, {{{/publish}}} will notify you about checksum change and refuse to publish it. You can then call {{{/prepare}}} to check the entry, or use {{{/publish}}} again to force submission. |
