-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'make html' generates correct IMG, but 'make publish' does not #69
Comments
What HTML do you get when you run |
I end up with this:
|
This is really unexpected. If you could set up a minimal project that reproduces this problem and post it here, it would help me finding its cause. |
Unfortunately, I cannot reproduce this with a minimal project. It definitely requires my full environment. That said, I'm quite willing to test a debug version of the plugin that prints more verbose output, if that would be helpful. |
When you have a chance, pull and checkout branch
Please report what you are getting. |
I'm currently using image-process from a pip install inside of a virtenv. If I pull your branch locally, and then (from inside my virtenv) run |
Yes; you will also need to add the path to the plugin to your
|
I did as you requested. I'm attaching the output for all the image_process DEBUG output. |
It looks like the HTML received by image_process does not contain values in the You should now see something like this:
I am guessing that the I am not sure why this is happening, but it happens before image_process does its work. |
Seems that you're right, the src attribute is missing. This makes no sense to me either. |
I'm running pelican-4.8.0 with pelican-image-process-3.0.3. My pelicanconf.py has:
and my markdown files have code similar to the following:
When I run 'make html', the generated HTML has the correct expected code such as:
However, when I run 'make publish' its as if the image-process plugin isn't used at all, and I end up with the full size images all the time. There's nothing in publishconf.py related to the plugin.
I'm confused why this isn't working correctly.
The text was updated successfully, but these errors were encountered: