1. Forum
  2. Fidonet
  3. SYNC SYSOPS

  • gopher: null or undefined error

    From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Sat Aug 16 15:15:05 2025
    close https://gitlab.synchro.net/main/sbbs/-/issues/964
    --- SBBSecho 3.29-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Sat Aug 16 15:15:06 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/964#note_7537

    Pretty sure this is addressed, so closing. Please reopen if you see it again. --- SBBSecho 3.29-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Mon Aug 18 12:34:49 2025
    reopen https://gitlab.synchro.net/main/sbbs/-/issues/964

    Just spotting this in my error log:

    ```
    srvc 0042 Gopher <Guest> !JavaScript /sbbs/exec/gopherservice.js line 173: Error: Argument #1 is an unexpected 'null' or 'undefined' value
    ```

    This is the corresponding log entry:

    Aug 2 06:46:09 bbs synchronet: srvc 0042 Gopher client request: 'nodelist'
    --- SBBSecho 3.29-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Mon Aug 18 12:34:49 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/964#note_7552

    Using a custom node activity while in MRC I tried to access gopher and it worked fine. No error so confirming the fix works.
    --- SBBSecho 3.29-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)