View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001325The World of SecfeniaOtherpublic2019-01-09 13:092019-01-12 13:21
Reporteruser113Assigned Todaviceroy  
PrioritynormalSeveritymajorReproducibilityN/A
Status resolvedResolutionfixed 
Product Version3.1.004 
Fixed in Version3.1.005 
Summary0001325: News Ticker Saying No News: Backend Issue or wording?
Descriptionjquery.simpleTicker.js is correctly building the html element, but the plugin seems to be failing to pass along data from your backend.
Additional InformationConsole log caught nothing other than unrelated errors:

fallingsnow_v6.js:106 Uncaught TypeError: Cannot read property 'parentNode' of null
    at generateSnowflakes (fallingsnow_v6.js:106)
generateSnowflakes @ fallingsnow_v6.js:106


client.js?eacbbc4:16 [WARNING] Crisp found shims of native JavaScript methods. This can alter the chatbox behavior and break things. Make sure not to override listed functions to ensure your chatbox works as expected. You may be looking for other JavaScript libraries in use on this page.

You can disable this warning by adding: $crisp.push(["safe", true]) to your page JavaScript.

Methods to check: (2) ["document.addEventListener", "document.removeEventListener"]
Crisp.Polyfill.e.__warn_incompatible @ client.js?eacbbc4:16
(anonymous) @ client.js?eacbbc4:15
setTimeout (async)
Crisp.Polyfill.e.schedule_warn_incompatible @ client.js?eacbbc4:15
Crisp.Base.e.init @ client.js?eacbbc4:18
s @ client.js?eacbbc4:15
(anonymous) @ l.js:7
setTimeout (async)
r @ l.js:7
t.init @ l.js:7
(anonymous) @ l.js:7
client.js?eacbbc4:11


WebSocket connection to 'wss://client.relay.crisp.chat/?EIO=3&transport=websocket' failed: Error during WebSocket handshake: Unexpected response code: 504
r.doOpen @ client.js?eacbbc4:11
r.open @ client.js?eacbbc4:11
r.open @ client.js?eacbbc4:10
r @ client.js?eacbbc4:10
r @ client.js?eacbbc4:10
r.open.r.connect @ client.js?eacbbc4:10
(anonymous) @ client.js?eacbbc4:10
TagsNo tags attached.

Activities

daviceroy

2019-01-09 17:02

administrator   ~0000914

While looking into this issue, I see that the code is working as expected. Since there has been no news in 14 days, there is no new news available. Perhaps the days that news can show on the ticker should change?

user113

2019-01-09 17:13

  ~0000915

I see, I wasn't aware of the two week limit. Perhaps two weeks is enough, but maybe fallback to something more specific? "There are no current events to report at this time."

daviceroy

2019-01-09 20:43

administrator   ~0000916

Is that any clearer than "There is no news at this time"? Perhaps something that specially mentions the 14 days like...

"There are no news events for the past 14 days"

user113

2019-01-11 23:32

  ~0000920

I think that's a perfect compromise. Also, sorry for the late reply. My spam filter decided there were unwanted reports for some unknown reason.

daviceroy

2019-01-12 13:21

administrator   ~0000921

New wording will be live for 3.1.005

Issue History

Date Modified Username Field Change
2019-01-09 13:09 user113 New Issue
2019-01-09 13:09 user113 Status new => assigned
2019-01-09 13:09 user113 Assigned To => daviceroy
2019-01-09 17:02 daviceroy Note Added: 0000914
2019-01-09 17:13 user113 Note Added: 0000915
2019-01-09 20:43 daviceroy Note Added: 0000916
2019-01-11 23:32 user113 Note Added: 0000920
2019-01-12 13:20 daviceroy Summary News Ticker not receiving data from backend => News Ticker Saying No News: Backend Issue or wording?
2019-01-12 13:21 daviceroy Status assigned => resolved
2019-01-12 13:21 daviceroy Resolution open => fixed
2019-01-12 13:21 daviceroy Fixed in Version => 3.1.005
2019-01-12 13:21 daviceroy Note Added: 0000921