I have a problem with wkhtmltoimage 12.4 and the newest alpha version. I tried to save H&M webpage, but I only get a little bar instead full webpage. I tried use many of switches to change settings but nothing works. Is there any solution for achieve correctly webpage in png format? Thanks very much.
That is saved website...
Related
I have a blank Firefox Add-On I made using the Getting Started Tutorial. When I run my extension using jpm run I observe the following.
If I navigate to any image it appears like this (image is displayed nicely in the centre):
However, I have the same image store in my extension under: ./data/test.jpg. When I navigate to resource://my-addon/data/test.jpg I get the following blank page:
The image is there, because if I hover over it in the inspector, it shows:
Am I doing something wrong, missing something in the docs about rendering images or is there a bug with how images are being rendered from the extension?
Include the self and then do
console.log(seld.data.url(''))
This will give you the id of your addon. It is very likely not my-addon it will be something like: jid1-4GP7z3tkUd3Tzg#jetpack - so your path to your image will be resource://jid1-4GP7z3tkUd3Tzg#jetpack/data/test.jpg.
I copied and pasted the Three.js code given here into an HTML file and downloaded the three.js package from the website, and configured the <script> tag to point to the location of the file three.min.js.
Nonetheless, when I open the HTML file, it displays a blank white screen.
What am I missing?
well I tryed the exact same thing and I'm seeing the wireframe cube rotating on screen. A few things to try.
1) drop the three.min.js right in the root folder and copy/paste the example code again without any alterations.
2) did you get the three.min.js from the zip package under the build directory? Or did you navigate the git repo and copy/paste it? If copy/paste was used be sure to click the "Raw" button to get the code without the wrapper HTML.
3) try the latest Firefox or Chrome browsers first. If it works there but not in say Safari, there are a few steps you need to take to enable WebGL in Safari first.
4) your video card may be blacklisted due to driver incompatibilities.
If none of these help, then post up the code, where you got the Three.js package, what browser and video card your using and I'll see what else I can do to help :)
I had the same problem. Windows hides the file extensions by default. I change it in folder options and it worked.
I often "print" some webpages into pdf files. Therefore I created an own stylesheet for that webpages so I have only the text I need (I'm using the addon stylish for it).
The problem: If I save the page to a pdf file, it becomes relatively huge. Example: I copied the text to LibreOffice and exported it to a pdf file. The result: about 100kb. With Firefox: 1.8 MB!! And it's only text! (I need that small smize, because I have to email the files)
Does anyone know how I can reduce those files? Maybe with ghostscript or any other commandline-tool?
EDIT:
Sorry, forgot to say: I'm using a Mac!
OMG, I can't believe it!!! I found the solution: Removing the original stylesheets (manually with Firebug or with a greasemonkey script) of the page was the trick. I don't know, where the bug is (Firefox or Mac OS)... it seems, that the background-images of whatever are saved into the pdf, altough they are completely hidden via my stylesheet.
Thanks for your help!
I have a logo that shows up in Safari but in Chrome it appears as a broken link and simply does not show up at all in Firefox.
<img src="images/logo-01.png"/>
I have re-uploaded it many times and have even tried alternative paths and file names.
anyone know how i might be screwing this up?
I ran into this same problem. For me, it turns out the image was corrupt. If i tried to open the png file up in photoshop, i would get an error saying it could not parse the file.
For whatever reason, safari could display the corrupt file, but chrome could not. This is how i fixed my issue. I noticed "preview" on my macbook could open the file fine. If you are using windows, possibly try paint or gimp or some other program besides photoshop.
I downloaded the corrupt file onto my macbook, opened it with preview (open with > preview)
In the preview app, go to file > duplicate, which makes a copy of your image
Save that duplicated image
As a test, i tried opening that new copied image in photoshop and i was able to!
Upload new file to website. I was able to view the image in chrome now.
Hope that helps anyone who ran into the same problem.
It could be an issue with your file structure. Right now your links are using relative paths (e.g. href="index.html"). This is fine if the file you're referencing is in the same directory as the current page file. But if your current page is located elsewhere, like in a 'pages' directory or something, then you need to tell the links to start from the site root. That would look like href="/index.html" (note the slash). So for the image, you'd have:
<img src="/images/logo-01.png"/>
I am using fckEditor as text editor. When i upload images thru it the images were uploaded to app/webroot/fckeditor/images.
And when they're embedded it looks like
/fckfiles/SalmonSashimi.jpg
Until now it looks right.
But the image doesn't appear.
So when I browse the image directly, at here
http://www.in-culture.info/fckfiles/SalmonSashimi.jpg
instead of displaying the URL, Cake interrupts the image call and trying to render it in a layout. I often face this error when I point .html file for iframe scroller and .xml file for flash embedding. This is really embarrassing
You can see the page here
http://www.in-culture.info/events/view/42
That image should appear before the text - "More" dont appear for short text.
Thanks for you help.
Try to change the path where the images are saved. Instead of
/app/webroot/fckeditor/images
try to change to
/app/webroot/img/fckeditor/
I believe that it's possible.
It's resolved now.
It was not cake's fault.
I pointed incomplete absolute path at FckEditor so it didn't upload the files well.
However the uploader mistakenly passes the "OK" so the HTML tries to display it.
So cake tries to render something, as usual, when there is no physical file.
I spent about 10 hours to resolve this.
Now I don't hate cake as I did a few hours ago. (: :)