Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Paperless-ngx
  3. New paperless-ngx doc upload status

New paperless-ngx doc upload status

Scheduled Pinned Locked Moved Paperless-ngx
8 Posts 3 Posters 1.4k Views 3 Watching
  • 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.
    • timconsidineT Offline
      timconsidineT Offline
      timconsidine
      App Dev
      wrote on last edited by
      #1

      Thanks so much to @staff for making PaperlessNG available on Cloudron and then upgrading to NGX.

      I may be wrong but there may be a small backward step ref display of uploaded document status. It shows as partial even when completed and doesn't fully update ... even though upload process is complete.

      Screenshot 2022-05-03 at 14.01.13.png

      I experienced this in the custom package, and lived with it.
      It went away in the official Cloudron package.
      But seems to have come back in the NGX deployment.

      Not a major problem. I can live with it. Just bit confusing and requires some checking after uploading when display shows incomplete upload status.

      Anyone else seeing this ?

      girishG 1 Reply Last reply
      1
      • timconsidineT timconsidine

        Thanks so much to @staff for making PaperlessNG available on Cloudron and then upgrading to NGX.

        I may be wrong but there may be a small backward step ref display of uploaded document status. It shows as partial even when completed and doesn't fully update ... even though upload process is complete.

        Screenshot 2022-05-03 at 14.01.13.png

        I experienced this in the custom package, and lived with it.
        It went away in the official Cloudron package.
        But seems to have come back in the NGX deployment.

        Not a major problem. I can live with it. Just bit confusing and requires some checking after uploading when display shows incomplete upload status.

        Anyone else seeing this ?

        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #2

        @timconsidine Looks like https://forum.cloudron.io/topic/6325/not-uploading again ?

        1 Reply Last reply
        0
        • girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #3

          The upload actually works just fine for me for 2 PDF docs. Do you see any errors in the browser console?

          timconsidineT 2 Replies Last reply
          0
          • girishG girish

            The upload actually works just fine for me for 2 PDF docs. Do you see any errors in the browser console?

            timconsidineT Offline
            timconsidineT Offline
            timconsidine
            App Dev
            wrote on last edited by
            #4

            @girish : not currently seeing errors in web console.
            I will monitor it and test with some documents.

            1 Reply Last reply
            0
            • robiR Offline
              robiR Offline
              robi
              wrote on last edited by
              #5

              This is likely an issue upstream with their progress code.. if an update is missed or gets out of sync it may reject further updates instead of continuing to update the progress display.

              Have a look there and report if necessary. 🙂

              Conscious tech

              timconsidineT 1 Reply Last reply
              1
              • girishG girish

                The upload actually works just fine for me for 2 PDF docs. Do you see any errors in the browser console?

                timconsidineT Offline
                timconsidineT Offline
                timconsidine
                App Dev
                wrote on last edited by
                #6

                @girish so I did some more testing with live documents.
                Some sailed through.
                Others didn't.
                No errors in console.

                I "cleaned" one problematic PDF with QPDF (https://github.com/jamesacampbell/pdf-cleaner)
                I used brew install qpdf to install rather than a .sh script.
                The document created with qpdf filename.pdf newname.pdf sails through Perpeless-ngx import.

                So I suspect it is a document issue (metadata or pdf creator).
                And therefore an upstream issue.

                girishG 1 Reply Last reply
                1
                • robiR robi

                  This is likely an issue upstream with their progress code.. if an update is missed or gets out of sync it may reject further updates instead of continuing to update the progress display.

                  Have a look there and report if necessary. 🙂

                  timconsidineT Offline
                  timconsidineT Offline
                  timconsidine
                  App Dev
                  wrote on last edited by
                  #7

                  @robi 👍

                  1 Reply Last reply
                  0
                  • timconsidineT timconsidine

                    @girish so I did some more testing with live documents.
                    Some sailed through.
                    Others didn't.
                    No errors in console.

                    I "cleaned" one problematic PDF with QPDF (https://github.com/jamesacampbell/pdf-cleaner)
                    I used brew install qpdf to install rather than a .sh script.
                    The document created with qpdf filename.pdf newname.pdf sails through Perpeless-ngx import.

                    So I suspect it is a document issue (metadata or pdf creator).
                    And therefore an upstream issue.

                    girishG Offline
                    girishG Offline
                    girish
                    Staff
                    wrote on last edited by
                    #8

                    @timconsidine ah, good job narrowing it down! maybe you can report it upstream with the problematic pdf.

                    1 Reply Last reply
                    1
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Bookmarks
                      • Search