omz:forum

    • Register
    • Login
    • Search
    • Recent
    • Popular

    Welcome!

    This is the community forum for my apps Pythonista and Editorial.

    For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.


    Can not Update my workflow

    Editorial
    3
    7
    4439
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • zrzka
      zrzka last edited by

      How does Editorial know that I previously shared workflow and offers me an update rather than a new link? I did ...

      • upload RV: Workflow Installer, update it several times
      • deleted it locally to test it as a fresh install
      • installed again on the same device (no other changes made at all)
      • and when I want to share updates it doesn't offer me Update, just Share

      ... don't want to create new link, new entry at editorial-workflows.com, just want to update my old one. How this is done internally? I mean, is there a way to fix this, to tell Editorial that it's my workflow? wkflw contains just actions, Commands.edcmd does not contain anything useful in this case as well, ... Any idea?

      Discussion started with RV: Forums New Discussion workflow

      1 Reply Last reply Reply Quote 0
      • omz
        omz last edited by

        Basically, a randomly generated "editing password" is stored on the device for each shared workflow, and it's associated with the workflow's unique identifier (UUID). When you install any workflow though (regardless of who created it), it gets a new, random UUID, so the association breaks...

        Anyway, I just made this little workflow/script: → Restore Shared Workflow... — If you run this on the same device where you shared the workflow, it can re-install it in a way that also restores/preserves the editing permission.

        1 Reply Last reply Reply Quote 0
        • zrzka
          zrzka last edited by

          You rock, as always! :-) Thanks, this did the trick and workflow is updated.

          BTW shouldn't SharedWorkflows.sqlite be included in Editorial Backup as well?

          1 Reply Last reply Reply Quote 0
          • zrzka
            zrzka last edited by

            @omz there's an issue with your Restore Shared Workflow. Actually it's an API issue, not workflow issue. The problem is ...

            Recent Workflows Endpoint

            When I get workflow_data from recent workflows endpoint and store it directly to .wkflv file, workflow does work perfectly.

            Workflow Info

            When I get workflow_data from $url?format=json, workflow_data are crippled in response and it leads to ...

            ... and workflow installed in this way doesn't work at all. Just compare workflow_data from /recent and workflow_data from $url?format=json and you'll see. They differ. Wrong one is Workflow Info endpoint.

            This is the reason why I removed direct save of '.wkflv' files with workflow_data in my RV: Workflow Installer. I switched to editorial://add-workflow scheme to be safe.

            1 Reply Last reply Reply Quote 0
            • omz
              omz last edited by

              I see, thanks! I've just deployed a server-side change that should fix this issue.

              1 Reply Last reply Reply Quote 0
              • zrzka
                zrzka last edited by

                Yep, confirmed, does work now. Thanks for the quick fix.

                1 Reply Last reply Reply Quote 0
                • TutorialDoctor
                  TutorialDoctor last edited by

                  Awesome workflow! Thanks!

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Powered by NodeBB Forums | Contributors