Skip to content
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

summary: Math inside the summary breaks it #784

Closed
sanklamm opened this issue Sep 22, 2016 · 3 comments
Closed

summary: Math inside the summary breaks it #784

sanklamm opened this issue Sep 22, 2016 · 3 comments

Comments

@sanklamm
Copy link

When I have a bit of math (wrapped with $-signs) around the summary block, the <!-- PELICAN_BEGIN_SUMMARY --> and END_SUMMARY get ignored.

An example:

## Problem

> The sum of the squares of the first ten natural numbers is,
> $\qquad 1^2 + 2^2 + ... + 10^2 = 385$
> The square of the sum of the first ten natural numbers is,
> $\qquad (1 + 2 + ... + 10)^2 = 55^2 = 3025$
> Hence the difference between the sum of the squares of the first ten natural numbers and the square of the sum is $3025 − 385 = 2640$.
<!-- PELICAN_BEGIN_SUMMARY -->
> Find the difference between the sum of the squares of the first one hundred natural numbers and the square of the sum.
<!-- PELICAN_END_SUMMARY -->

## Next headline

Some text.
@jerryasher
Copy link

jerryasher commented Jan 29, 2017

As food for thought, I am seeing the pelican-open_graph plugin break how a page is rendered IF the content contains a reference to a relative path using {filename} notation. And I think that is also related to the summary memoization.

whiskyechobravo/pelican-open_graph#10

The pelican-open_graph plugin operates when the signal content_object_init is sent.
It tries to obtain the summary.
But if the content contains a line like:

![a pelican appears]({filename}/images/pelican.jpg "a pelican appears") 

this message will be generated when the summary is requested:

WARNING: Unable to find `/images/pelican.jpg`, skipping url replacement.

And indeed, in the final rendered html, the reference will be broken and so the image will be given the wrong url.

@danmackinlay
Copy link
Contributor

Is this fixed by #830?

@justinmayer
Copy link
Member

Perhaps addressed via merged PR #973. If not, please comment here and I'll re-open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants