sytone / foundry-vtt-journal-sync

Import and Export Journal entries in Foundry VTT

Hi 👋, I'm Jon

Principal Group Engineering Manager @microsoft in the US. Worked across Azure and Services and love to tinker with pretty much everything.

🔭 I’m currently working on a new azure product and other things
🌱 I’m currently learning everything
👯 I’m looking to collaborate on anything
🤝 I’m looking for help with anything
👨‍💻 All of my projects are available at https://github.com/sytone
📝 I regularly write articles on http://blog.sytone.com
💬 Ask me about Microsoft, C# or any of my repos

🌐 Socials:

💻 Tech Stack:

📊 GitHub Stats:

---

foundry-vtt-journal-sync's Issues

Add a setting for a list of folders to exclude

This module causes problems with https://github.com/Forien/foundryvtt-forien-quest-log

the quest log assumes that the journal content stays valid JSON but on reimport, the content is wrapped with <p></p>

I temporarily got around this by running this function form the developer console ingame

function fix_quest_log() {
    let folder = game.journal.directory.folders.find(f => f.name === "_fql_quests");

    folder.content.forEach( entry => {
        let data = entry.data;
        let content = data.content.replace(/((^\<p\>)|(\<\/p\>$))/mg, "");
        console.log(content)
        entry.update({ content: content}).then(e => {
            console.log("updated", e);
        })
    })
}

Issues on Forge for export due to the data folder

https://discord.com/channels/170995199584108546/722566083499786352/732257090940436490

@sytone I was using your Journals Sync and really like it, there are some issues with using it on Forge because it uses "data" in the code. Is it possible to change the settings to use the filepicker and save out the source object to pick locations other than data to save in?

Broken on 0.8.8

Is this module still active?

Error exporting entry not in a folder

Trying to export a journal entry that is NOT stored in a folder failed. In the console, the module reported:

Uploading journal-sync/test5e//First Entry (hKX2V3Lo3GUne88M).md

It looks like it had trouble with the double slash. When I moved the journal entry down into a folder, the export worked.

Is there a problem with line 375 of journal-sync.js? If I comment out this line of code, the problem seems to go away.

Sync journal links?

Would it be possible to sync journal links into the native markdown format ![name](path/to/md file)? Is that beyond the scope of this module?

Can only export once on hosted FVTT

I am running FVTT 0.6.5 on a remote Ubuntu server on Digital Ocean. I can run the module once successfully to export all journal entries. But it fails if I edit the entries in FVTT and try to export them again. I get this error in the console:

journal-sync.js:399 Uncaught (in promise) EEXIST: file already exists, mkdir '/home/taylor/foundrydata/Data/journal-sync/test5e/'

Why is it trying to create the folders again?

Is there a problem with line 375 of journal-sync.js? It seems to be trying to recreate the parent folder. If I comment out this line of code, the problem seems to go away.

Using Journal Notes button to export only exported 2 out of 25 notes

When I tried running the /js export command, I had an error that it wasn't a command. Then I tried to use the Journal Notes Export button, and it said that it only exported two notes and it completed. So I looked at the ${HOME}/.local/share/FoundryVTT/Data/journal-sync folder saw it only exported 2 items out of 25 and an empty folder. Is there something I did wrong?

FoundryVTT Version: 0.6.5
foundry-vtt-journal-sync version: 0.5.0 (installed through module manager)

Exporting adds '<!-- -->' at the end of ordered and unordered lists.

I'm having this problem where exporting my journal entries adds <!-- --> at the end of lists.

Example:

- NPC 1
   - trait 1
   - trait2
   - trait3
- NPC 2

<!-- --> 

If exporting only did this once, it wouldn't be much of an issue. Unfortunately, every time I export journal notes, the <!-- --> text is added at the end of each list. So if I exported the above example 5 times, there would be five lines with <!-- -->.

Has anyone else encountered this?

.7x beta?

Any thoughts on supporting the .7x beta?