Fetch My Campaigns: Uncaught (in promise) TypeError: campaigns is undefined

[miri64]

When trying to fetch my campaigns I get the following output in the developer console:

Uncaught (in promise) TypeError: campaigns is undefined [Settings.js:387]
[Detected 1 package: ddb-importer]
    activateListeners Settings.js:387
    jQuery 9
        dispatch
        handle
        add
        Ee
        each
        each
        Ee
        on
        n
    activateListeners Settings.js:382
    _render foundry.js:3090
    _render foundry.js:3764
    render foundry.js:3021
    _onClickSubmenu foundry.js:55705
    jQuery 2
        dispatch
        handle

I am using Firefox 100.0.2 as a browser and my Foundry VTT instance (Version 9, Build 269) is running on a CentOS 7 machine. D&D Beyond importer is on version 2.9.48 and my cobalt cookie was freshly reset.

[MrPrimate]

This can happen at time when the CDN at DDB suspects you might be a bot and marks your origin as potentially a bot. It should disappear after a while

[miri64]

Mh, is there a workaround maybe? I also get DDB Importer | ERR > Error: The world.ddb-<campaign-name>-spells Datastore is not yet connected! when I try to import my players' characters from that campaign (this time as an error actually shown on screen).

[MrPrimate]

That sounds unconnected and like it's been unable to load your compendium for storing spells in.

[miri64]

That sounds unconnected and like it's been unable to load your compendium for storing spells in.

Should I open a separate issue for that?

[MrPrimate]

No - you need to check that the compendiums set in the Compendiums section are correct, exist, and can be opened.

[miri64]

No - you need to check that the compendiums set in the Compendiums section are correct, exist, and can be opened.

Not sure how to check the correctness, but "DDB Spells" exists, but when I try open (or delete) it I get the same error. Same if I try to open DDB Muncher.

[MrPrimate]

I think this is a core foundry problem at this point - you may need to remove the file from the disk, and also from the json manifest for your world.

[MrPrimate]

Regarding the campaigns issues - are you running your own ddb-proxy or is it mine?

[miri64]

Regarding the campaigns issues - are you running your own ddb-proxy or is it mine?

My own.

[MrPrimate]

Regarding the campaigns issues - are you running your own ddb-proxy or is it mine?

My own.

Something that sometimes helps, is logging into DDB, going to the encounter builder tool and creating an encounter based on a campaign in the list, using the same session that you used to generate the cobalt cookie.

[miri64]

I think this is a core foundry problem at this point - you may need to remove the file from the disk, and also from the json manifest for your world.

That worked btw!

[miri64]

Something that sometimes helps, is logging into DDB, going to the encounter builder tool and creating an encounter based on a campaign in the list, using the same session that you used to generate the cobalt cookie.

Sadly the voodoo here did not work :-(.

[MrPrimate]

If you know what the campaign ID (it's a number, you can find it in the URL of your campaign on DDB) you can manually set it using:

game.settings.set("ddb-importer", "campaign-id", "ID_HERE")

As a work around you could also try setting these details using my proxy and then switching back to your local one once complete

[miri64]

If you know what the campaign ID (it's a number, you can find it in the URL of your campaign on DDB) you can manually set it using:

game.settings.set("ddb-importer", "campaign-id", "ID_HERE")`

That worked! Thanks.

As a work around you could also try setting these details using my proxy and then switching back to your local one once complete

Already tried that earlier, same result. But I'm happy with the console-based workaround.