| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In test, set up the post-commit hook for more realism (and bugs!).
To make wrappers work in test, set PERL5LIB, and allow the wrappee's
path to be overridden. Meta-test that post-commit is really hooked
up by verifying that content is getting generated in destdir.
About the longstanding bug, which as far as I know was harmless:
CVS can't operate outside a srcdir, so we're always setting $CWD.
"local $CWD" restores the previous value when we go out of scope.
Usually that's correct. But if we're removing the last file from a
directory, the post-commit hook will exec in a working directory
that's about to not exist (CVS will prune it).
The fix: chdir() manually in cvs_runcvs(), so we can selectively
not chdir() back.
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
dynamic cgi pages, which cannot use trail anyway.
This seemed to be due to the pagetemplate hook calling prerender. I've
observed this making it take *minutes* for the signin page to be displayed.
ltracing ikiwiki showed it was matching pagespecs a lot.
It may be that this is still a speed pain point when rendering pages, not
just for CGI. So more work may be needed here.
|
| | | |
|
| | | |
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since trail members are explicitly rebuilt if the information used for
their prev/up/next boxes changes, they don't need another dependency
on the trail itself. (If the trail disappears, it will disappear from
the member's member_to_trails entry, causing a rebuild; so the add_depends
is redundant.)
Similarly, since trail members are explicitly rebuilt if their next
or previous item, or its title, changes, the presence dependencies on the
next and previous items are redundant.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the title of a trail changes, each member of that trail must be
rebuilt, for its prev/up/next box to reflect the new title.
If the title of a member changes, its next and previous items (if any)
must be rebuilt, for their prev/up/next boxes to reflect the new title.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the unlikely event that the ordered contents of a trail have changed
without the TRAILS or TRAILLOOP template variables being evaluated
(for instance, all trail directives are removed from a former trail
that uses a custom pagetemplate that doesn't contain TRAILS), we might
get here without having already called prerender.
|
| | |/ |
|
| | |
| |
| |
| | |
smcv please note this introduces another bug, which I've opened
|
| | |
| |
| |
| |
| |
| |
| | |
don't go on and --refresh.
This way, if a previous aggregation job is running, we don't add additional
load doing work that job will do anyway.
|
| | | |
|
| | |
| |
| |
| | |
All existing tests pass.
|
| | |
| |
| |
| | |
selected in all browsers.
|
| | | |
|
| | |
| |
| |
| | |
12fa9c031f7a9dc25dba628aa91fc347586e4ab6 porported to fix this, but failed
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Try to avoid a situation in which so many ikiwiki cgi wrapper programs are
running, all waiting on some long-running thing like a site rebuild, that
it prevents the web server from doing anything else. The current approach
only avoids this problem for GET requests; if multiple cgi's run GETs on a
site at the same time, one will display a "please wait" page for a
configurable number of seconds, which then redirects to retry. To enable
this protection, set cgi_overload_delay to the number of seconds to wait.
This is not enabled by default.
|
| | |
| |
| |
| | |
(cherry picked from commit 1636da85d82644d923042c870aaedc5a29754aa6)
|
| | |
| |
| |
| | |
(cherry picked from commit 9d550817ca546d1dd30a21cebad6093d1f3bacad)
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
this simplifies the code, make the configuration more intuitive, at
the cost of making the labels on the layers automatically generated
and therefore less customizable
|
| | | |
|
| | |
| |
| |
| | |
for google maps to work, an API key needs to be added to the configuration
|
| | | |
|
| | |
| |
| |
| | |
(cherry picked from commit 519d35368e2f1e7fe1fce577fe7d71ef9bd5c07e)
|
| | |
| |
| |
| | |
(cherry picked from commit 6f684cd412e6d93f943c1fa5d8dac91caa138be0)
|
| | |
| |
| |
| |
| |
| |
| |
| | |
will_render() before first call to urlto().
Fixes
http://ikiwiki.info/bugs/osm_linkto__40____41___usage_breaks_map_rendering/
(cherry picked from commit 691312225789ff6cd5e3fcc4979c076791d67452)
|
| | | |
|
| | | |
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When set to true, let each mirror's ikiwiki CGI find out the correct target page
url themselves.
This resolves the usecase described on
[[todo/mirrorlist_with_per-mirror_usedirs_settings]].
Signed-off-by: intrigeri <intrigeri@boum.org>
|
| | | |
| | |
| | |
| | |
| | | |
(Worked ok in my tests w/o this, but not sure I tested every case,
and this is correct.)
|
| | |/
| |
| |
| | |
Thanks, Raúl Benencia
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
At some point I changed the storage of trail members' membership
and forgot to update this use.
(It turns out to be rather difficult to reach this code, possibly even
impossible: it only applies if a member somehow ceases to match the
trail's pagespec without either the trail or the member changing.)
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| | |
Reworded template, which also called the commit message a "comment".
|
| | |\ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |\ \ |
|