| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
* Rename --getctime to --gettime. (The old name still works for
backwards compatability.)
* --gettime now also looks up last modification time.
* Add rcs_getmtime to plugin API; currently only implemented
for git.
|
| |
|
|
|
|
|
|
|
| |
The pagetemplate hook may be called multiple times, for example when pages
are inlined into a page. Sidebars were being calculated each time that
happened, only to be thrown away when the final pagetemplate hook was
called. Avoid this unnecessary work.
Remove stored sidebar content on use to save some memory.
|
| | |
|
| |
|
|
| |
Commit b7351daacd0d4a041a51b43d99b7bf589de54f53 introduced the bug.
|
| | |
|
| |
|
|
|
|
|
| |
This way, the example blog always has a sidebar on the index page,
but not the overhead of sidebars on all the other pages. And if a
user wants to, they can enable global_sidebars to switch to sidebars on
every page.
|
| | |
|
| |
|
|
| |
on a page.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* pagestats: Class parameter can be used to override default class for
custom styling.
* pagestats: Use style=list to get a list of tags, scaled by use like
in a tag cloud. This is useful to put in a sidebar.
* Rework example blog front page.
|
| |
|
|
| |
which pages to include on the calendar archive pages. (The pagespec can still also be specified on the ikiwiki-calendar command line.)
|
| |
|
|
| |
so filter out such a misconfiguration.
|
| |\
| |
| |
| |
| | |
Conflicts:
IkiWiki/Plugin/meta.pm
|
| | |
| |
| |
| |
| |
| | |
This makes them consistent with the rest of the meta keys. A wiki rebuild
will be needed on upgrade to this version; until the wiki is rebuilt,
double-escaping will occur in the titles of pages that have not changed.
|
| | |
| |
| |
| | |
master language.
|
| | | |
|
| | |
| |
| |
| | |
Rebuild can be needed sometimes, but not always, so undef.
|
| |\ \
| | |
| | |
| | |
| | | |
Conflicts:
debian/NEWS
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Joey pointed out that sort=x usually takes a sort order.
|
| | | |
| | |
| | |
| | |
| | | |
I've left meta_title in, undocumented, as a possible replacement for
sort=title in IkiWiki 4.0 or something.
|
| | | |
| | |
| | |
| | |
| | | |
Also rename cmpspec_translate (internal function) to sortspec_translate
for consistency.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This allows correct sorting of titles, names, etc., with:
[[!meta title="David Bowie" sort="Bowie, David"]]
[[!meta title="The Beatles" sort="Beatles, The"]]
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
|
| | | |
| | |
| | |
| | |
| | | |
Jon was worried about the backwards-compatibility break involved in making
tagged() not match non-tag links, but Joey seems less concerned about it.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The meta title data set by comments needs to be encoded the same way that
meta encodes it. (NB The security implications of the missing encoding
are small.)
Note that meta's encoding of title, description, and guid data, and not
other data, is probably a special case that should be removed. Instead,
these values should be encoded when used. I have avoided doing so here
because that would mean forcing a wiki rebuild on upgrade to have the data
consitently encoded.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Variable renamed to be a bit more self-explanatory.
Probably more idiomatic perl to not use a hash ref when a hash can be used.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The output of "bzr log" seems to have changed a bit, so we change the
parsing accordingly. This has not been tested with earlier versions of
bzr.
Several problems seemed to occur, all in the bzr_log subroutine:
1. The @infos list would contain an empty hash, which would confuse the
rest of the program.
2. This was because bzr_log would push an empty anonymous hash to the
list whenever it thought a new record would start.
3. However, a new record marker (now?) also happens at th end of bzr log
output.
4. Now we collect the record to a hash that gets pushed to the list only
if it is not empty.
5. Also, sometimes bzr log outputs "revno: 1234 [merge]", so we catch only
the revision number.
6. Finally, there may be non-headers at the of the output, so we ignore
those.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
pages in the wiki.
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Colons are not allowed at the start of urls, because it can be interpreted
as a protocol, and allowing arbitrary protocols can be unsafe
(CVE-2008-0809). However, this check was too restrictive, not allowing
use of eg, "video.ogv?t=0:03:00/0:04:00" to seek to a given place in a
video, or "somecgi?foo=bar:baz" to pass parameters with colons.
It's still not allowed to have a filename with a colon in it (ie
"foo:bar.png") -- to link to such a file, a fully qualified url must be
used.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
pagespec_translate may set $@ if it fails to parse a pagespec, but
due to memoization, this is not reliable. If a memoized call is repeated,
and $@ is already set for some other reason previously, it will remain
set through the call to pagespec_translate.
Instead, just check if pagespec_translate returns undef.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
To review, tcc does not really use environ, so you have to use clearenv
there. But POSIX, in their wisdom, didn't standardise clearenv yet,
so on FreeBSD, one still needs to manipulate environ on their own.
(If you use tcc on FreeBSD, this may leave you unsatisfied.)
|
| | |
| |
| |
| | |
problem reported by viric
|
| | | |
|
| | |
| |
| |
| | |
called by attachment plugin.
|