| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
|
| |
%links is populated even for just-deleted pages, so %pagesources
should be used for such tests instead.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bestlink was looking at whether %links existed for a page in order to tell
if the page exists, but just-deleted pages still have entries in there (for
reasons it may be best not to explore). So bestlink would return
just-deleted pages. Instead, make bestlink use %pagesources.
Also, when finding a deleted page, %pagecase was not cleared of that page.
This, again, made bestlink return just-deleted pages. Now that is cleared.
Fixing bestlink exposed another issue though. The backlink calculation code
uses bestlink. So when a page was deleted, no backlinks to it are found,
and pages that really did backlink to it were not updated, and had broken
links.
To fix that, the code that actually removes deleted pages had to be split
out from find_del_files, so it can run a bit later. It is run just after
backlinks are calculated. This way, backlink calculation still sees the
deleted pages, but everything afterwards does not.
However, it does not address the original bug report that started this
whole thing, [[bugs/bestlink_returns_deleted_pages]]. Because there
bestlink is run in the needsbuild hook. And that happens before backlink
calculation, and so bestlink still returns deleted pages then. Also in the
scan hook.
If bestlink needs to work consistently during those hooks, a more involved
fix will be needed.
|
| | |
|
| | |
|
| |
|
|
| |
pretty-printed dates, using the same formatting as used for page modification date display, etc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
include feeds.
Speedup of about 25% for small inlines; could be much larger for inlines of
many, or complex pages.
Not bloating memory with excessive memoization data was the key to this.
The method chosen does not squeeze out every erg of speed possible when
inlines are nested, but that's rare. It uses less memory than other
optimisation hacks (I'm looking at you,
f937c1fb8074a512d8bb788fa275f5e90595cd47 !) already used in inline.pm.
|
| |
|
|
| |
value. (Thanks, NicolasLimare)
|
| |
|
|
|
|
|
| |
Unlike generic meta foo tags, meta description is known to be safe, so can
be special cased to be allowed despite the html scrubber. This makes meta
description much more useful, since it is otherwise limited to being used
by other plugins like map.
|
| |
|
|
|
| |
With the htmlscrubber disabled, it was adding a <meta name=title>
tag for the title, which is pointless.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
My experience is that when inlines are nested, the old behavior of
generating feeds for the nested inlines was never really desired. Since the
feeds were numbered sequentially, the numbers could easily change, and it did
not make sense to subscribe to or use those feeds. And generating those nested
feeds often meant a lot of unnecessary calculation, and data being written.
So, I dropped them.
Looking back, nested feeds originally were a free side effect of properly
handing multiple feeds on one page. Of course, that is still supported.
|
| | |
|
| |
|
|
| |
when ikiwiki needs authentication, rather than for any access to the cgi/wiki.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that is closer to a page.
I chose not to have it override style.css, because style.css is not really
intended to be edited; the one from the underlay is intended to be used as
a base that local.css overrides.
I chose to use a plugin rather than changing the default behavior, both
because I didn't want to have to worry about possibly breaking backwards
compatability (though this seems unlikely), and because it seemed cleaner
to not include style template parameters in the main page template code.
I suppose someone might want a way to not override the toplevel
local.css, but instead include it as well as foo/local.css. Probably the
best way to do that would be to have foo/local.css @import ../local.css
(modulo browser compatability issues). Alternatively, edit page.tmpl
to always include the toplevel local.css, or swap out this plugin for
another one.
|
| |
|
|
| |
template is filled out. This improves the search plugin's indexing, since it will not include navigational elements from the page template or sidebar.
|
| |
|
|
| |
not configured.
|
| | |
|
| |
|
|
| |
search works correctly for wikis that are located in subdirectories of domains.
|
| |
|
|
|
|
|
|
|
| |
When redirecting to a page, ie, after editing, ensure that the url is
uri-encoded. Most browsers other than MSIE don't care, but it's the right
thing to do.
The known failure case involved editing a page that had utf-8 in the name
using MSIE.
|
| |
|
|
| |
blogspam.net.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
using a template that does not include page content.
|
| | |
|
| |
|
|
| |
(cherry picked from commit 13e9383b48857daa206387f3486eb00e3b171a68)
|
| |
|
|
| |
files if a sourcedir of "./" was specified.
|
| | |
|
| |
|
|
|
|
|
|
| |
for a wikilink (including eg, leading slashes).
Before, the htmllink would display the link to the template as if it were a
wikilink, but what was stored was not, which could lead to confusing
situations.
|
| |
|
|
|
| |
This sometimes caused infinite recursion when rebuilding a wiki
with po files.
|
| | |
|
| |
|
|
| |
Don't generate inlined page content if the template does not use it.
|
| | |
|
| | |
|
| |
|
|
|
| |
This does mean the year calendars depend on existence of all posts made in
the year and have to be updated.
|
| | |
|
| |
|
|
|
| |
This avoids all calendars rebuilding when a new page is added
that will only show in one of them.
|
| |
|
|
|
| |
The names in the documentation were completly different, but
also seemed better chosen than the names in the code.
|
| |
|
|
|
|
| |
git log --follow seems to sometimes show merges from before the file was
ever created. So, skip them, a file shouldn't be first created during a
merge anyway.
|
| |
|
|
| |
Meh, git.
|
| |\
| |
| |
| |
| | |
Conflicts:
debian/changelog
|
| | |
| |
| |
| |
| |
| | |
This will be a bit more expensive, but --getctime does not need to be fast.
And getting the real creation time a very useful when untangling blog
histories that involve renames.
|
| | | |
|
| | |
| |
| |
| |
| | |
This is consistent with the year display, and I think it is less
visually confusing than using the full month names.
|
| | | |
|
| | |
| |
| |
| | |
I broke this recently.
|
| | |
| |
| |
| | |
to an archive page from the wrong year.
|