Regression in Scheduler Export Service — Blank Pages and Watermark Issues

Scheduler
#1

Hello DHTMLX Team,

We’re encountering issues with the Scheduler export service that appear to have started recently, without any changes on our end. It seems like a recent regression that affects older versions of Scheduler.

We have been using v5.0.0 for a long time without problems, but in the last few days, the export function began generating hundreds of blank pages.

After forcing the version to v5.3.8, the export works again, but we’re now facing another issue:
the watermark added at the end of the page drops to a new blank page, resulting in an extra empty page at the end of every export.

This issue can be easily reproduced on your official demo: Export to PDF/PNG

Steps to reproduce:

  1. Open the link above.
  2. Set export configuration to:
  • Format: A5
  • Orientation: Landscape
  • Zoom: 1
  1. Export the scheduler.

Observed results:

  • The generated file includes an extra blank page caused by the watermark position.
  • Using Scheduler v5.0.0 results in hundreds of blank pages.

Additional findings:
When we change the export domain to the beta environment: the https://export.dhtmlx.com/beta/scheduler, everything works correctly again:

  • v5.0.0 exports normally (no blank pages).
  • The watermark no longer causes an extra blank page.

So my questions are:

  1. Are you aware of these regressions in the current production export service?
  2. Is there any plan to roll out the beta version’s fixes to production?

Thanks!

#2

Hello,

Thank you for bringing this to our attention. It appears to be a bug on our side. I have already forwarded the issue to our development team, and they are working on a fix.
Currently, you can use this workaround by accessing the scheduler through the following URL https://export.dhtmlx.com/beta/scheduler to avoid the problem.

#3

Hi,

Thank you for the update. Could you please share an estimate for when the fix might be available? Also, kindly let me know once the issue has been resolved so I can verify it on my end.

Thanks!