Copy button for trigger link fails and link is truncated in UI

  • Resolved josch87

    (@josch87)


    4 weeks, 1 day ago

    Summary

    In the latest version of BackWPup, the copy button for the trigger link does not work. Clicking the button throws a JavaScript error and the link is not copied to the clipboard.

    Steps to Reproduce

    1. Open an existing BackWPup job.
    2. Click the “Frequency” link.
    3. In the BackWPup sidebar, select “Triggered by link” as the frequency.
    4. A partial trigger link and a Copy button are displayed.
    5. Click the Copy button.

    Expected Behavior

    Clicking the Copy button should copy the full trigger link to the clipboard and provide visual feedback (e.g., a success message or tooltip). Current Behavior

    Clicking the Copy button does nothing and no error message is shown in the UI. From a user’s perspective it may appear as if the link was copied successfully but simply without visual feedback.

    However, the link is not copied to the clipboard. The following error is logged in the browser console:

    Uncaught TypeError: Cannot read properties of undefined (reading 'writeText')
    at HTMLDocument.<anonymous> (backwpup-admin.js?ver=5.6.6:2535:33)

    Additionally, the full trigger link is not visible in the UI. It is truncated with ..., which makes it impossible to manually copy the full link from the interface.

    Currently, the only workaround is to inspect the DOM in the browser developer tools and copy the full link directly from there.

    Environment

    • BackWPup: 5.6.6
    • WordPress: 6.9.1
    • Chrome: 145.0.7632.160
    • Firefox: 148.0
    • This topic was modified 4 weeks, 1 day ago by josch87.
    • This topic was modified 4 weeks, 1 day ago by josch87.
    • This topic was modified 4 weeks, 1 day ago by josch87.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support WPM Support

    (@saranshwpm)

    4 weeks ago

    Hi @josch87,

    Thank you for the detailed report.

    I tried to replicate this on my end but was not able to reproduce the issue. The Copy button works correctly here and copies the full trigger link without any JavaScript error. For reference, here is a quick screenshot from my test:

    https://shottr.cc/s/15f0/SCR-20260310-mz5.png

    Regarding the truncated link in the UI, that behavior is expected in the interface. However, I’ve passed this feedback to the team as well.

    Also, thank you for taking the time to share multiple reports and feedback recently. Since many of these are UI/UX improvements or feature-related observations, it would actually help a lot if you could open them directly on our GitHub repository so they reach the development team more quickly:

    https://github.com/wp-media/backwpup/issues

    That way they can review, track, and discuss the suggestions more efficiently.

    Thanks again for helping improve the plugin.

    Thread Starter josch87

    (@josch87)

    4 weeks ago

    Hi @saranshwpm,

    thank you for taking the time to test this.

    I did some additional investigation and it seems the issue is related to the execution context of the Clipboard API.

    The installation where the error occurs is running over HTTP, not HTTPS.
    In that environment the following error appears in the console when clicking the Copy button:

    Uncaught TypeError: Cannot read properties of undefined (reading 'writeText')

    This suggests that navigator.clipboard is not available in that context. As far as I understand, the Clipboard API is only available in secure contexts (HTTPS or localhost).

    I verified that navigator.clipboard works correctly in my browser in general, but in the affected WordPress installation it appears to be unavailable due to the HTTP context.

    This would explain why you are unable to reproduce the issue if your test environment is running over HTTPS.

    It might be sufficient to add a simple guard before calling the Clipboard API:

    if (navigator.clipboard && navigator.clipboard.writeText) {
      // Modern Clipboard API (works in secure contexts like HTTPS)
      navigator.clipboard.writeText(text);
    } else {
      // Clipboard API not available (e.g. HTTP context or older browsers)
      // → optionally implement a fallback such as document.execCommand('copy')
      // → or at least avoid the JavaScript error, hide the button, show the full link ...
    }

    This would prevent the JavaScript error in environments where the Clipboard API is unavailable.

    Hope this helps narrow it down.

    Plugin Support WPM Support

    (@saranshwpm)

    3 weeks, 6 days ago

    Hi @josch87,

    Thank you for digging into this and for the detailed explanation — that makes a lot of sense.

    You are correct that the Clipboard API is only available in secure contexts (HTTPS or localhost), so that would explain why the error appears on HTTP installations while it works normally in HTTPS environments.

    If you’d like, I would invite you to open a report on our GitHub repository so the development team can review your findings and suggestion directly:

    https://github.com/wp-media/backwpup/issues

    Otherwise, feel free to let me know and I can open the issue on your behalf and include your investigation there.

    Thanks again for taking the time to analyze this so thoroughly.

    Thread Starter josch87

    (@josch87)

    2 weeks, 5 days ago

    Reference: https://github.com/wp-media/backwpup/issues/236

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.