Add a connect callback handler.

See merge request !320

DDMsgReader: Fix for "Message header has 'expanded fields'" error when updating message header attributes in certain conditions

See merge request !317

DDMsgReader: Fix for "Message header has 'expanded fields'" error when updating message header attributes in certain conditions

Defeats local auto-screen-pausing

Fixes issue #603 reported by Nelgin

This appears to just be a miss from the initial commit (70b835d0) of the
directory default configuration (per lib) feature, so a file
lib's directory default "data dir" wouldn't be read from file.ini.

This fixes issue #602 reported by Nelgin.

SlyEdit: More small tweaks for quote line wrapping to determine ideal places to append a CRLF

See merge request !316

DDMsgReader: Allows kwyeord searching of personal email with command-line arguments

See merge request main/sbbs!315

Refactor the node spy page

See merge request !314

SlyEdit: For quote lines, a small tweak for long line (>120 character) adding a CRLF for paragraph formatting

See merge request !313

Eric Oulashin authored 1 year ago and Rob Swindell committed 1 year ago

SlyEdit: For quote lines, a small tweak for long line (>120 character) adding a CRLF for paragraph formatting

SlyEdit: Improvement to paragraph/line breaks in quote line wrapping. The version is now 1.87

See merge request !312

Add a node spy to the web interface

See merge request !308

DDFileLister: Traditional UI - Fixes for qutiting certain actions. Prints selected actions. Up & down arrow keys.

See merge request !311

Eric Oulashin authored 1 year ago and Rob Swindell committed 1 year ago

DDFileLister: Traditional UI - Fixes for qutiting certain actions. Prints selected actions. Up & down arrow keys.

ddfilelister now has its own implementation of a traditional (non-lightbar) UI. Its version is now 2.12

See merge request !309

Eric Oulashin authored 1 year ago and Rob Swindell committed 1 year ago

ddfilelister now has its own implementation of a traditional (non-lightbar) UI. Its version is now 2.12

- sbbs/BBSID/exec (publish the timed event's internal code)
- sbbs/BBSID/call (publish the QWKnet hub's ID)

The message contents are not case-sensitive.

e.g. publishing "0" to node/#/set/intr will clear the node-interrupt flag.
Any non-zero message value will "set" the flag. Same is true for the
lock, down, and rerun topics/flags.

These node attributes (misc) flags could be cleared previously
by setting the 'misc' topic (e.g. to 0), but since that's not an atomic
read/modify/write operation, other set misc flags could be lost clearing flags
in that manner.

<nelgin> can I push an intr instruction to a node with mqtt?

node/#/set/status - set the node status value (to an integer)
node/#/set/errors - set the node error counter (to an integer, e.g. "0")
node/#/set/misc - set the node's miscellaneous attributes/flags value
 (hexadecimal values can be set by including "0x" prefix)

The message (payload) doesn't matter for the following topics:
node/#/set/lock - lock a node (no one but sysop can login)
node/#/set/intr - interrupt a node (disconnect a user)
node/#/set/down - down a node (not available for connections)
node/#/set/rerun - rerun a node (reload config upon next connection)

These should probably be moved (along with other node functions in this file)
to nodedat.* some day.

Just fall-through to display help output for unrecognized options.

Remove unnecessary call to JSON.stringify() in non-JSON mode

This allows command-lines to be more cross-platform/host

As requested by Nelgin

Use a timed event and/or execute via jsexec

Nelgin's request/idea

DD Upload Processor: Scan failure output is now logged to the system log instead of outputted to the logged-in user

See merge request !307

Eric Oulashin authored 1 year ago and Rob Swindell committed 1 year ago

DD Upload Processor: Scan failure output is now logged to the system log instead of outputted to the logged-in user

A "prepped" means directory means a relative path from the configuration files
(or default settings) has been converted to a full/absolute path with proper
slashes for the platform (i.e. backslashes instead of forward-slashes on
Windows).

JSexec doesn't require that the new v3.20 ctrl/*.ini files exist to run; this
was necessary to be able to run 'jsexec update -> upgrade_to_v320.js' which
does the ctrl/*.cnf to .ini file conversion (egg not required to build
chicken). When JSexec failed to load ctrl/msgs.ini
(e.g. "!ERROR loading configuration files: 2 (No such file or directory)
opening /sbbs/ctrl\msgs.ini"), it would continue to run, but not "prep" any
of the "path" settings (e.g. exec_dir).

The first run of 'jsexec update.js' would fail to run upgrade_to_v320.exe
(which does the v3.20 user base conversion) and a bunch of other (but not as
important) update steps because Windows couldn't execute "../exec/*".

Multiple errors would be displayed in this case, but the most important (as
reported by Ree in #synchronet of irc.synchro.net) was:
  '..' is not recognized as an internal or external command

right after the status output:
  No v3.20 user base found, running ../exec/upgrade_to_v320

Notice the "../exec/" prefix, which is not support by Windows when specifying
a file path to execute.

A second run of 'jsexec update' would work fine because the new v3.20 .ini
files would be successfully created after the first run (though the user base
was not).

This is likely the same issue that MRO reported recently when upgrading a
Windows SBBS v3.19 install to v3.20 and not having the user base upgraded
the first time.

Fixed a typo in the DD Upload Processor readme.txt

See merge request !306

DD arc viewer & upload processor: Refactor of how the configuration files are read. Arc viewer: Control characters are no longer needed for color settings.

See merge request !305