Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi,

    Have you tried the troubleshooting guide? https://time.ly/document/user-guide/troubleshooting/first-troubleshooting-step/

    There is no such option, but you are welcome to suggest this on Timely Product ideas page: https://ideas.time.ly/, upvote an existing request or make a new request there.

    Thanks,
    Ben

    Thread Starter nic137

    (@nic137)

    I followed the link you posted, and determined it seems to be an issue with our theme. The dropdown in the Twenty Fifteen theme works fine. Besides those posted, do you have any suggestions as to why this might be happening?

    It’s hard to know without checking, try to remove javascripts one by one until you find a script that is causing this issue.

    Thread Starter nic137

    (@nic137)

    I’m not having any luck with troubleshooting this issue. I’m not very savvy in javascript, so I’m not sure exactly what I’m looking for. I did receive the message below in the script debugger, is this related to the issue?

    I also came across an older support post where an additional CSS line was added to the child theme. Could my issue be resolved by something like that? (I did try the code in the post but it didn’t make a difference on our site). Any help is greatly appreciated, as we are ready to launch the site.

    Handler function NM__httpResponseExaminer threw an exception: TypeError: aChannel.loadInfo is null
    Stack: NetworkMonitor.prototype._createNetworkEvent@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/webconsole/network-monitor.js:841:1
    NM__httpResponseExaminer@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/webconsole/network-monitor.js:635:26
    makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/DevToolsUtils.js:87:14
    Firebug.TabCache.prototype<.loadFromCache@chrome://firebug/content/net/tabCache.js:497:22
    Firebug.SourceCache.prototype<.load@chrome://firebug/content/net/sourceCache.js:158:16
    Firebug.SourceCache.prototype<.loadText@chrome://firebug/content/net/sourceCache.js:54:21
    SourceFile.prototype.loadFromSourceCache@chrome://firebug/content/debugger/script/sourceFile.js:173:1
    SourceFile.prototype.loadScriptLines@chrome://firebug/content/debugger/script/sourceFile.js:147:13
    CompilationUnit.prototype.getSourceLines@chrome://firebug/content/bti/inProcess/compilationunit.js:148:5
    ScriptPanel.prototype<.showSource@chrome://firebug/content/debugger/script/scriptPanel.js:744:9
    ScriptPanel.prototype<.updateLocation@chrome://firebug/content/debugger/script/scriptPanel.js:557:13
    ScriptPanel.prototype<.newSource@chrome://firebug/content/debugger/script/scriptPanel.js:1777:13
    Events.dispatch@chrome://firebug/content/lib/events.js:83:34
    EventSource.prototype.dispatch@chrome://firebug/content/chrome/eventSource.js:64:1
    SourceTool.prototype<.addScript@chrome://firebug/content/debugger/script/sourceTool.js:195:9
    SourceTool.prototype<.newSource@chrome://firebug/content/debugger/script/sourceTool.js:217:9
    Events.dispatch@chrome://firebug/content/lib/events.js:83:34
    EventSource.prototype.dispatch@chrome://firebug/content/chrome/eventSource.js:64:1
    DebuggerClient<.dispatch@chrome://firebug/content/remoting/debuggerClient.js:437:9
    DebuggerClient<.newSource@chrome://firebug/content/remoting/debuggerClient.js:300:9
    bind@chrome://firebug/content/lib/object.js:29:36
    eventSource/aProto.emit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/client/main.js:131:9
    DebuggerClient.prototype.onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/client/main.js:948:9
    LocalDebuggerTransport.prototype.send/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/transport/transport.js:569:11
    makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/DevToolsUtils.js:87:14
    makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/DevToolsUtils.js:87:14
    EventLoop.prototype.enter@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/actors/script.js:347:5
    ThreadActor.prototype._pushThreadPause@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/actors/script.js:543:5
    ThreadActor.prototype.onAttach@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/actors/script.js:657:7
    DSC_onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/main.js:1643:15
    LocalDebuggerTransport.prototype.send/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/transport/transport.js:569:11
    makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/DevToolsUtils.js:87:14
    makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/DevToolsUtils.js:87:14
    Line: 841, column: 1

    Thread Starter nic137

    (@nic137)

    Any support that can be offered on this? The site is live now, and it’s disappointing that this feature doesn’t work. We might have to look for another option ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Category dropdown not working’ is closed to new replies.