Problem with GC code being cut on printouts

[+deepo]

I'd like to report an error that occurs when printing out a cache page.

The GC number is at the top right corner of the printed page, both for Letter and A4, but it's cut, so you can't see the GC number on the printed page.

[+HHL]

Click one of the Print links beforehand. THEN use Ctrl-P.

Result:

Edited August 2, 2023 by HHL

[+NanCycle]

or print from a screenshot

[+HHL]

4 minutes ago, NanCycle said:

or print from a screenshot

That's not as clear as the print version, and a waste of toner as well. Not recommended.

[+deepo]

Thanks for the hint. That works fine.

[+The Snowdog]

This has been an issue with the "old" page view for years. Since I don't use the "new" view (for oh so many reasons) I don't know if the fix mentioned here works for that view. But it does not work on the "old" view, at least not for me.

[+HHL]

6 minutes ago, The Snowdog said:

I don't know if the fix mentioned here works for that view. But it does not work on the "old" view, at least not for me.

See my post from August, 2 in this thread for a solution.

[+MD Crab]

Another quick solution, before printing copy the GC number and paste it into the note. 

[+niraD]

On 10/5/2023 at 8:56 AM, HHL said:

See my post from August, 2 in this thread for a solution.

52 minutes ago, MD Crab said:

Another quick solution, before printing copy the GC number and paste it into the note. 

 

Just a quibble, these are not solutions. They are workarounds.

 

A true solution would fix the problem so that the GC code isn't cut off when users just print the page using their browsers' normal print functions.

[+Hügh]

32 minutes ago, niraD said:

Just a quibble, these are not solutions.

 

I'm not sure why you quote @HHL and use the word "workaround". To me, it looks like a reasonable solution. You use the print option, which was designed for printing:

 

 

If you then use Ctrl-P, the page prints fine because it is generated to be printer-friendly. In fact, I can set the paper size to A4 paper, and do weird things like set the margin to 3 inches, and it adjusts perfectly fine:

 

 

38 minutes ago, niraD said:

using their browsers' normal print functions.

 

I think there's a limit to when we can expect. Trying to have the cache listing page (which has multiple columns, an interactive map, dynamic content, etc.) print perfectly on every browser & printer would be a headache for the engineers. That's why they offer a print view which is simplified so that it prints fine.

[+niraD]

1 hour ago, Hügh said:

I'm not sure why you quote @HHL and use the word "workaround".

Once again: A true solution would fix the problem so that the GC code isn't cut off when users just print the page using their browsers' normal print functions.

[+The Snowdog]

So it looks like this has been fixed, sort of... the GC is now well away from the right margin but at least you can see all of it!

[+The Snowdog]

LOL I spoke too soon, it looks good in print preview but still actually prints incorrectly.

[+HHL]

5 hours ago, The Snowdog said:

LOL I spoke too soon, it looks good in print preview but still actually prints incorrectly.

As said often before: DO NOT USE YOUR BROWSER'S PRINT COMMAND!

Use the Groundspeak print link from the cache page. They know best how to print the page in a correct manner.

 

Hans

Edited November 14, 2023 by HHL

[+The Snowdog]

As is apparent from my photos, I use the "old" page view (for a varitey of reasons), which does not have a "print" link.

 

The browser's print command should print the page (or any web page) as it is displayed. Using css to alter the way a page is printed, other than on a page that is specifically designed to be printed, is generally frowned upon in modern web design. My guess is that there is something awry with the print.css page the "old" page is seeing. 

Edited November 18, 2023 by The Snowdog

[+arisoft]

 

9 hours ago, The Snowdog said:

As is apparent from my photos, I use the "old" page view (for a varitey of reasons), which does not have a "print" link.

 

How old page view are you using? The print link above has been on the top of the description as far as I can remember.

Edited November 19, 2023 by arisoft

[Moun10Bike]

17 hours ago, The Snowdog said:

As is apparent from my photos, I use the "old" page view (for a varitey of reasons), which does not have a "print" link.

 

There is no "old" cache page view (well, you could say the one version we have is "old," as it is some of the most ancient code used on the site). Are you instead running user scripts that might be stripping down the details on the page?

[+The Snowdog]

Of course there is. And every time I go to the main page it tells me "An updated version of this page is available." I never accept it, as I do not care for the associated cache page view. I do not run any scripts, as I use many different computers and I want them to all be the same. Next time I am at a geo friend's house I will post side by side pics of the cache page view I have, and the one she has (through the updated dashboard). They are quite a bit different.

Edited November 19, 2023 by The Snowdog

[+Bl4ckH4wkGER]

The cache details page you want to print is the same, regardless of whether you access it from the old dashboard or the newer dashboard. Hard to call it new when it's been around since 2017.

[Moun10Bike]

1 hour ago, The Snowdog said:

Of course there is. And every time I go to the main page it tells me "An updated version of this page is available." I never accept it, as I do not care for the associated cache page view. I do not run any scripts, as I use many different computers and I want them to all be the same. Next time I am at a geo friend's house I will post side by side pics of the cache page view I have, and the one she has (through the updated dashboard). They are quite a bit different.

 

You are talking about the dashboard. Yes, there is a "new" version of that (from 2017), but there is only one version of the cache details page, which is what we are talking about here.

[+The Snowdog]

3 hours ago, Moun10Bike said:

 

You are talking about the dashboard. Yes, there is a "new" version of that (from 2017), but there is only one version of the cache details page, which is what we are talking about here.

 

Well now I am totally confused, as I was absolutely convinced that her details page under the new dashboard (a) looked completely different from mine and (b) had a "print this page" link somewhere. But I just connected to her via Zoom and her details page now looks just like mine. And no "print" link. I could swear that used to be there, and that it gave you the choice of the number of logs to print, but I don't see it now. I thought it might be the browser (she is Internet Explorer reluctantly moved to Edge, I am Chrome) but nope they look just the same. I do know that her old printouts (I have a bunch of them from back in our puzzle solving days) do look completely different from mine; mine look just like the web page (old ones have the GC at the upper right corner in the correct position, then it got shifted halfway off the printed page some years ago) and hers have a somewhat different layout and lots more white space. Yes I have so many print outs of web pages... So I will crawl back into hiding and think about all this some more.

[+arisoft]

Try to print this https://www.geocaching.com/seek/cdpf.aspx?guid=10406b53-fde6-4ec7-b0f0-3d48cb87a9f8

 

If it works you can print any cache using the same link but you must use the "guid" code of the cache in the end of the link to print them.