- This topic has 4 replies, 2 voices, and was last updated 2 years, 1 month ago by Tom.
April 10, 2020 at 1:36 pm #1234468Mosche
I’m working on a project and have bumped into the following issue.
– GP Premium
– Elementor Pro
– Advanced Custom Fields
I have several custom post types that I’ve created.
And I’ve extended Custom fields using Advanced Custom Fields
I use Elementor Pro to create the single page and archive page templates.
So far so good.
Everything works “visually”. With that I mean, you can see all the components after using this method.
I “see” all the values in the right place on single and archive pages.
The issue is that I also have to print the CPT’s
And this does not work.
I get blank pages. And I also get the sense it’s trying to print tablet or mobile version.
This is what I think is happening.
Generally when I press print. [Because it does work normally on posts and pages.]
It prints everything that’s in the “content” area.
The part you normally write in, in the editor section.
But for my project I don’t use those at all.
All the fields are outside of the editor box.
I’m surprize no one has brought up this issue before.
I looked for an answer before posting this question.
Anything I can do about it?
Has this issue been raised before and I simply couldn’t find it.
MoscheApril 10, 2020 at 4:55 pm #1234607TomLead DeveloperLead DeveloperApril 10, 2020 at 5:00 pm #1234612Mosche
What is the email where I can send you the login. To take a look. The site is still hidden from the public.
A quick update.
I used Elementor’s own hello world with the same result.
So it’s likely something with Elementor.
But you can take a look, and see for yourself.
MoscheApril 10, 2020 at 6:09 pm #1234637Mosche
I found the culprit. I was using a plugin called.
[Click to Print]
Which appearantly does not work well with custom post types.
I’ve contacted the developer to take a look and add that functionality.
I’m marking this ticket as resolved as it is not a GP issue.
MoscheApril 11, 2020 at 10:18 am #1235435
- You must be logged in to reply to this topic.