Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PDF exports as 1 long page. #1867

Closed
1 task done
insidiousdog opened this issue Apr 19, 2024 · 5 comments
Closed
1 task done

PDF exports as 1 long page. #1867

insidiousdog opened this issue Apr 19, 2024 · 5 comments
Assignees
Labels
bug Something isn't working needs triage Issues that need to be triaged v4 Issues related to the latest version

Comments

@insidiousdog
Copy link

insidiousdog commented Apr 19, 2024

Is there an existing issue for this?

  • Yes, I have searched the existing issues and none of them match my problem.

Product Variant

Self-Hosted

Current Behavior

Exporting to a pdf, the pdf renders successfully and downloads, but the page breaks don't carry across. This results in a Page 1 of 1 pdf, with none of the separations in the editor being reflected in the rendered document.

Expected Behavior

The pdf output is multi page.

Steps To Reproduce

  1. Go to Export.
  2. Click PDF icon.
  3. Open downloaded PDF.

What browsers are you seeing the problem on?

Firefox, Chrome, Safari

What template are you using?

None

Anything else?

My compose file:

version: "3.8"
services:
  Database (Postgres)
  postgres:
    image: postgres:15-alpine
    restart: unless-stopped
    volumes:
      - postgres_data:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: postgres
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres -d postgres"]
      interval: 10s
      timeout: 5s
      retries: 5

  Storage (for image uploads)
  minio:
    image: minio/minio
    restart: unless-stopped
    command: server /data
    ports:
      - 9000:9000
    volumes:
      - minio_data:/data
    environment:
      MINIO_ROOT_USER: minioadmin
      MINIO_ROOT_PASSWORD: minioadmin

  Chrome Browser (for printing and previews)
  chrome:
    image: ghcr.io/browserless/chromium:latest
    restart: unless-stopped
    extra_hosts:
      - host.docker.internal:host-gateway
    environment:
      TIMEOUT: 10000
      CONCURRENT: 10
      TOKEN: chrome_token
      EXIT_ON_HEALTH_FAILURE: true
      PRE_REQUEST_HEALTH_CHECK: true

  Redis (for cache & server session management)
  redis:
    image: redis:alpine
    restart: unless-stopped
    command: redis-server --requirepass password

  app:
    image: amruthpillai/reactive-resume:latest
    restart: unless-stopped
    ports:
      - 3000:3000
    depends_on:
      - postgres
      - minio
      - redis
      - chrome
    environment:
      -- Environment Variables --
      PORT: 3000
      NODE_ENV: production

      -- URLs --
      PUBLIC_URL: http://<my server local ip address>:3000
      STORAGE_URL: http://<my server local ip address>:9000/default

      -- Printer (Chrome) --
      CHROME_TOKEN: chrome_token
      CHROME_URL: ws://chrome:3000

      -- Database (Postgres) --
      DATABASE_URL: postgresql://postgres:postgres@postgres:5432/postgres

      -- Auth --
      ACCESS_TOKEN_SECRET: access_token_secret
      REFRESH_TOKEN_SECRET: refresh_token_secret

      -- Emails --
      MAIL_FROM: noreply@localhost
      SMTP_URL: smtp://user:pass@smtp:587 # Optional

      -- Storage (Minio) --
      STORAGE_ENDPOINT: minio
      STORAGE_PORT: 9000
      STORAGE_REGION: us-east-1 # Optional
      STORAGE_BUCKET: default
      STORAGE_ACCESS_KEY: minioadmin
      STORAGE_SECRET_KEY: minioadmin
      STORAGE_USE_SSL: false

      -- Cache (Redis) --
      REDIS_URL: redis://default:password@redis:6379

      -- Sentry --
      VITE_SENTRY_DSN: https://id.sentry.io # Optional

      -- Crowdin (Optional) --
      CROWDIN_PROJECT_ID:
      CROWDIN_PERSONAL_TOKEN:

      -- Email (Optional) --
      DISABLE_EMAIL_AUTH: true
      VITE_DISABLE_SIGNUPS: true

volumes:
  minio_data:
  postgres_data:
@insidiousdog insidiousdog added bug Something isn't working needs triage Issues that need to be triaged v4 Issues related to the latest version labels Apr 19, 2024
@alex1712
Copy link

I also thought this must be a bug, but it is actually documented here (https://docs.rxresu.me/product-guides/making-your-resume-publicly-available#you-are-not-restricted-to-a-page).

But to be honest this should be an option, I think it is not realistic to say that nowadays nobody prints the CV's anymore.

It looks weird and document x times longer than A4. Is there any workaround we can use? Something like adding a break page symbol in some of the text fields or something like that?

@lulu-cao
Copy link

Have you checked out this doc? https://docs.rxresu.me/product-guides/creating-a-multi-page-resume

@alex1712
Copy link

Yes, i got it to work by splitting the work experience section into 2 sections and putting the second one in the second page without name

@radiatewishbone
Copy link

Have you checked out this doc? https://docs.rxresu.me/product-guides/creating-a-multi-page-resume

This is an imperfect solution for two reasons:

  1. Attempting to "split" the PDF by guessing where a good place would be to add a second work experience section means that you will never have a perfect A4 split, because it's impossible to guess the exact place to split the page to create an A4 page.
  2. The documentation says that there is "no need" for A4 pages on a PDF anymore, because nobody prints them out. This is untrue. In my industry, people do still print resumes. Also, for many job applications I make online, application forms require you to upload PDFs, not provide a link to a PDF. Hiring teams will then want to print the PDFs out themselves to read.

It would be very good if you could add the option to split the PDF into a specified page size.

@AmruthPillai
Copy link
Owner

Closing in favor of #1834.

@AmruthPillai AmruthPillai closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage Issues that need to be triaged v4 Issues related to the latest version
Projects
None yet
Development

No branches or pull requests

5 participants