Skip to content

Change script to use JSON as opposed to Markdown files #24

@GitMurf

Description

@GitMurf

weird that they have the 10 limit! I guess they assume that the Markdown exports and imports aren't meant for total DB backup? and for that they expect you use the JSON export/import? otherwise I dont understand the 10 limite.

9:11 AM
so now the question is, is it worth spending the time looking into my script creating a JSON file instead of individual markdown files? that would probably solve alot of our problems... if not all of them: Attribute:: bug, invalid windows page names, 10 markdown import limit...

9:12 AM
shoot looks like a new pet project for me for this weekend 😉 haha... JSON may be the right way but I need to play around with it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions