You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When importing any single document or importing any category the below error message triggers in the console. Additionally, when selecting Sync, nothing happens despite claiming it was successful.
Clean world install using multiple systems/worlds with no other modules running.
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'replace')
at createImagePage (framework.js:471:39)
at addJournalImagePages (framework.js:491:5)
at getArticleContent (framework.js:368:3)
at importArticle (framework.js:116:17)
at async WorldAnvilBrowser._importCategory (journal.js:373:7)
The text was updated successfully, but these errors were encountered:
aaclayton
changed the title
TypeError when attempting to import any document
TypeError when attempting to import a JournalEntry document.
Sep 5, 2022
Hello,
The problem comes from the article cover.
It seems the API with WA has changed when retrieving cover url.
I've sent a message to WA developpers to understand how we need to retrieve them now.
I will publish a fix tomorrow so that you won't be stuck because of this. But the retrieval of article cover will need to wait the end of the discussion with WA developpers.
Sorry about that.
Foundry v10 Build 284
Integration v1.4.0
When importing any single document or importing any category the below error message triggers in the console. Additionally, when selecting Sync, nothing happens despite claiming it was successful.
Clean world install using multiple systems/worlds with no other modules running.
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'replace')
at createImagePage (framework.js:471:39)
at addJournalImagePages (framework.js:491:5)
at getArticleContent (framework.js:368:3)
at importArticle (framework.js:116:17)
at async WorldAnvilBrowser._importCategory (journal.js:373:7)
The text was updated successfully, but these errors were encountered: