"make publish" fails when the plugin attempts to process the first file with images #68
Comments
|
ImageProcess is trying to open an image file, but for some reason, the path it was given points to a directory. The faulty Since you only have problems with |
|
@patrickfournier thanks for the reply. I'm not sure what you mean by How is image-process using/consuming the value of |
|
I was looking at the code of compute_paths(). My impression is that the problem lies there. It uses SITEURL in some cases, so I was wondering if this could be the problem. Another possibility is that one of your image If you are familiar enough with Python, you could try adding some |
|
Thanks. My I inserted So When pelican creates the html, it looks like this: Is that relative path to the images what is causing this to blow up? |
|
Most probably. Try putting a |
|
That change breaks all the image links, as they don't exist via that path.
pix is a subdirectory inside of content. The change that you're suggesting
implies that pix is a directory hanging off of / (but it is not).
…On Mon, Oct 17, 2022 at 6:18 PM Patrick Fournier ***@***.***> wrote:
Most probably. Try putting a / at the start of your image paths:
{: .image-process-large-photo}
{: .image-process-large-photo}
—
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAARLSKIKZNPVI46WH4KFT3WDX3EXANCNFSM6AAAAAARGOO22M>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I use Pelican for my site but unfortunately, I am not in a state where I can test things. However, I saw in my Of course, if you already have a |
|
Setting However, it also results in copying over everything in the |
|
Does setting STATIC_PATHS = ['pix/derivatives'] The way image_process works is that is adds a subdirectory ( |
|
Unfortunately, that doesn't work |
|
I was able to work around this locally by catching |
I'm trying to setup my first pelican based blog on a Fedora Linux system using pelican-4.8.0 with pelican-image-process-3.0.3.
If I run
make htmlormake regenerateeverything works great. However once I'm ready to generate the final production content withmake publishit blows up on the first file that has image references withIsADirectoryError: [Errno 21] Is a directory: '/home/netllama/stuff/llamaland/content/'. That's literally the content directory with all of my markdown files, so I'm not at all sure why this is an issue.I re-ran with --debug:
pelican --debug /home/netllama/stuff/llamaland/content -o /home/netllama/stuff/llamaland/output -s /home/netllama/stuff/llamaland/publishconf.pyand got the following output, but I don't understand why its failing and expecting the content directory to be anything other than a directory:
The text was updated successfully, but these errors were encountered: