• Resolved geplmarketing

    (@geplmarketing)


    In Chrome, print-o-matic in Code of Conduct accordion is printing entire page content. <div> class is set to only Code of Content section.
    [print-me target=”.my_print_target”/]

    On SECOND try, the content is limited to only two pages (content should only require one page, but at least it’s limiting the content on the second try.)

    Why does this happen in Chrome?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor twinpictures

    (@twinpictures)

    try adding more pause before print time to allow the content to fully load before the print is triggered. If this is still an issue, please get back to us and we’ll link you to an upcoming release candidate that should better address the two-click print issue. However, if it’s only happening in chrome be sure to clear the cache, maybe try viewing it in incognito mode.

    Thread Starter geplmarketing

    (@geplmarketing)

    How would I “try adding more pause before print time”?

    It’s not the cache, and I’m not going to tell all of my users to use incognito mode.

    Thanks

    Plugin Contributor twinpictures

    (@twinpictures)

    Wow, take about 20% off there Bud.
    How would I “try adding more pause before print time”?
    Dashboard > Settings > Print-O-Matic > Pause before Print

    It’s not the cache, and I’m not going to tell all of my users to use incognito mode.
    using incognito mode was to test that it’s not a caching issue.

    Given that the other questions we asked have not been answered, we are going to go ahead and mark this issue as resolved. If you require more assistance, please consider looking for another plugin.

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

The topic ‘Chrome not initially using class to set target’ is closed to new replies.