In GitLab by @adrien.schiehle on Nov 17, 2021, 10:29

Merges third_step_secrets_management -> secrets

Next step : Secret management.

Only Storyteller seeds are managed for now. I've chosen to split those seeds by checking if there is some <h3 ...> inside of it. Each h3 indicating the start of a new secret. It will allow GMs to reveal secrets step by step for a given article.

<h3> inside what we retrieve are what we write as [h2] inside BBCode.

It works like that :

• When importing article, we store one property inside world-avil.secrets flag each secret.
• GMs can toggle each secret insde the Journal Entry. Or toggle all in one go inside the WorldAnvilBrowser.
• The WorldAnvilBrowser indicates which article contains secrets.
• Players can't see secrets which has not been revealed.
• Players see revealed secret inside Journal Entries the same way they see other sections.

In GitLab by @adrien.schiehle on Sep 24, 2021, 12:17

Merges categories -> categories

A little bigger one. It has some recursive code to go through the whole category tree.

But that shouldn't pose any problem as long as there is no infinite loop in what we retrieve for World Anvil.

By saying that... I may need to add a security and the categoryBranchLevel :angel:

This is what it does :

In GitLab by @adrien.schiehle on Sep 21, 2021, 04:53

Merges first_step_cosmetics -> master

Some screenshots that will help you see what changed

Default configuration :

Article display with the default configuration :

Custom configuration :

Article display with the custom configuration (GM side) :

Article display with the custom configuration (Player side) :

I didn't update the Readme for this kind of modifications. Is it necessary ?

Numerous users on reddit and the FVTT discord are reporting issues similar to this one. Suspect there may have been an API change at WA, may need a reach out to Dimitris.

In GitLab by @adrien.schiehle on Nov 3, 2021, 11:09

Merges fix_categories -> categories

First commit

For fixing importAll and some hierarchy problems.

We had in fact two Root folder when importing. ( The parent tree node was also a folder named Root )

I decided to let one here. I tested : If they want to remove the upper folder after moving the other one outside of it, it still works. Link remains

Second commit

For visibility buttons. I think that when you tried to simplify things, you found that I didn't use entry.visible and chose to use it.

But its purpose slightly differs from what you thought : WA Panel control is only for GMs, and those buttons gives him info on what is visible by other players? It's great to keep track of what you have shared to your players until now.

It can also be used when you have a NPC who have evolved and its description changed.

• Hide its description on prior category
• Set it visible on the new one.

(For campaign data, I use a WA category for each act)

In GitLab by @myk1e on Jun 13, 2020, 01:56

Using the World Anvil Integration module with:

• FVTT 0.6.2
• The Forge (hosting)
• FF 77 (browser)

I'm having the following issue:
After importing an article, all "meta-links" (to categories, types, etc.) are shown as button and work fine.
On the other hand, the links which are included in the text of the article (shown as texte links in bold underlined orange) don't.
These text links open a new browser tab and give a "Cannot GET /w/ayo-leakimka/a/waelt-article" error message.
They're pointing to an incorrect URI, in this case:

• https://ayo.eu.forge-vtt.com/w/ayo-leakimka/a/waelt-article \instead of:
• https://www.worldanvil.com/w/ayo-leakimka/a/waelt-article

It seems they are using a relative path (use of a global server variable maybe?)
Thanks for your help!

In GitLab by @johnnolan on Sep 18, 2021, 01:24

Clicking the sync button in FoundryVTT for articles causes CORS errors to return from the Article API Endpoint

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at xxxxx (Reason: CORS header 'Access-Control-Allow-Origin' missing)

Using Postman with the same api call I get the same error

curl --location --request GET 'https://www.worldanvil.com/api/aragorn/article/(GUID)?x-application-key=xxx&x-auth-token=xxx

Changing the request from a params to a header gives a success.

curl --location --request GET 'https://www.worldanvil.com/api/aragorn/article/(GUID)' \ --header 'x-application-key: xxx' \ --header 'x-auth-token: xxx'

Would this be solved by changing the folowing lines to use the header instead of params? https://gitlab.com/foundrynet/world-anvil/-/blob/master/module/api.js#L66-67

In GitLab by @mod100 on Feb 2, 2022, 04:02

Merges master -> master

I hit an error when trying to import my WorldAnvil content because of this line (252) in framework.js.

const isLongContent = section.content.length > 100;

In some cases section.content is null and so this line fails, hence the change.

In GitLab by @zdaar on Jun 15, 2020, 12:27

Dimitri thinks the issue is foundry side and told me it is unrelated to the journeyman api access issue. You can see in the screenshot the authentication gets done as it finds my username (blurred) but no world are shown in the dropdown.

Tested on : Linux headless foundry 0.6.2 //

Fresh install of foundry 0.6.2 on windows 10 with zero modules except WA, in a different physical location/network to rule out firewall issues.

In GitLab by @Fulla3 on Sep 30, 2021, 12:27

After updating to the new version (yeah, the module is not dead! :-)), I started to re-sync my articles, and I've been experiencing some formatting issues. The problem occurs as soon as I edit an entry within Foundry (I wanted to get rid of spoilers, as the spoiler tags from World Anvil don't transfer and spoilers just show up as regular text).

Character entry pre-editing:

Character entry after I edited something in the main character description text (not anywhere close to the now messed up formatting):

Note how from "date of birth" forward, everything appears as one single block of text.

Formatting issues continue in the other sections as well as soon as I edit anywhere - like when I edit something in the family section here to remove the spoiler:

It messes up this section here (religion etc.) as well as the formatting of the date of birth, height etc. section further up in the entry (the the screenshot above).

The first three commits seems to come from somethink we already merged : Refresh button + category sort I don't know why it is back in this PR :(

The rest is V10 compliance + entry pages for new Journal management

13-08-2022: I recently added some additionnal changes du to another change in WA API. And while doing it, I added a new buttion for shrinking categories in the journal. (When you have a big WA world, it become difficult to navigate without it)

Cover images on an article aren't importing. Getting this error:

GET https://[[URL REDACTED]]/media/cache/mapthumb/uploads/maps/e92cbf4605c7733b9c04f656aae06a2e.png 404

Seems like it's trying to create a folder that doesn't exist?

If I have a person who has a sidebar image, they don't import. get this error:

Uncaught (in promise) TypeError: Cannot read properties of null (reading 'replace')
[Detected 1 package: world-anvil]
    at createImagePage (framework.js:471:39)
    at addJournalImagePages (framework.js:483:5)
    at getArticleContent (framework.js:368:3)
    at importArticle (framework.js:116:17)
createImagePage @ framework.js:471
addJournalImagePages @ framework.js:483
getArticleContent @ framework.js:368
importArticle @ framework.js:116

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)

In GitLab by @juliantabel.jt on Mar 21, 2022, 16:58

I have tried many things, but I can't get it to work, that links in world anvil are transfered to foundry. I am using the forge and have tried with many other modules as well as only the world-anvil module active. This is the world anvil entry (example):

When importing to foundry, it looks like this:

I can click on the Bold text, nothing happens, same for the entries below that. When running foundry 0.8.x I can at least click on the entries below the text and the other entry opens (also imported), however even then it doesn't work in the content section.

In GitLab by @spaceflows on Sep 13, 2021, 19:55

Foundry has such amazing integration with World Anvil. Are there any plans to allow WA Timelines to be linkable like the articles are??

In GitLab by @adrien.schiehle on Mar 14, 2021, 11:50

Hi, I'm new here, so first :

Thank you for this integration module !

It will allow me to create my article in advance and share what I want directly inside fvtt.

When I tried it, some of my articles couldn't be imported. Here was the stack :

framework.js:71 Uncaught (in promise) TypeError: Cannot read property 'id' of undefined
    at framework.js:71
    at Array.map (<anonymous>)
    at _getArticleContent (framework.js:71)
    at importArticle (framework.js:12)
    at async WorldAnvilBrowser._onClickControlButton (journal.js:146)

If I understand correctly, timeline relations inside an article are not correctly interpreted. section.items is undefined.

  // Article relations
  if ( article.relations ) {
    for ( let [id, section] of Object.entries(article.relations) ) {
      const title = section.title || id.titleCase();
      const items = section.items instanceof Array ? section.items: [section.items];  // Items can be one or many
      const relations = items.map(i => `<span data-article-id="${i.id}" data-template="${i.type}">${i.title}</span>`);
      aside += `<dt>${title}:</dt><dd>${relations.join(", ")}</dd>`
    }
  }

Something like this could do the job. What do you think ?

      let items = section.items;
      if( ! items ) {
         items = []; // There can be no items in an article relation. (Ex: timeline)
      } else if (! items instanceof Array ) {
         items = [section.items];  // Items can be one or many
      }