| Age | Commit message (Collapse) | Author |
|---|
|
This allows per-form/feedlink group customization without having to
resort to counting.
(cherry picked from commit b134feb0dc2d9a8ff7ae447537fa8bc02811aabd)
|
|
Second (forgotten) half of bb8f76a4a04686def8cc6f21bcca80cb2cc3b2c9.
This ensures that the link URL and page title in the feed are the
correct ones.
|
|
3.20101231.
|
|
|
|
With the previous logic, same-level items would go down one level and
then again up one level closing and re-opening UL tags each time. The
resulting redundant lists caused whitespace layout issues in the
rendered pages.
Adjust the "moving up?" logic to check if the current item base is
different from the previous item _base_. Adjust the "going down?" logic
by moving it to an earlier phase and checking for (1) parent item not being
what it should be and (2) remaining bits; the root is grown unconditionally as
long as (2) is verified.
|
|
Conflicts:
t/tag.t
|
|
|
|
Assume the aggregated content is only going to be in one of the
directories, and so stop if it's successfully removed from the
transientdir.
|
|
|
|
|
|
|
|
Problem was this: websetup loads all plugins, but does not checkconfig
them. So, htmltidy's recently added configurable command setting was unset;
this resulted in its sanitize hook failing; the sanitize hook is called
when a sidebar was enabled, and this caused the sidebar to not display.
I put in a fix, but the underlying problem is that websetup loads all
plugins but leaves them in an unconfigured and possibly broken state while
trying to display its forms.
Probably the long-term fix is to have it cache the original hook states from
before loading the plugins, and restore it after getting their configuration.
Or, even to get the configuration using a subprocess, as plugins may do things
outside the hook system.
|
|
|
|
|
|
|
|
blogspam_pagespec to do other matches against who the user is.
|
|
|
|
properly this time
|
|
This reverts commit 5d3998555ffbeb1c20b84dd4cdc46c825c07bec8.
That broke posting via blog form.
|
|
|
|
|
|
As with the tag plugin, for the moment keep the old behaviour in the test.
|
|
|
|
- Migrate the set of deletions to the {autofile} set, since it has
more or less the same effect. This affects the "deleted" case in the
test.
- If a page has just been deleted, add it as an autofile anyway: by
the time gen_autofile is called, it'll be in the list of deleted files,
so it'll just be added to {autofile}. This affects the "gone" case
in the test.
- Behaviour change: we don't forget that a page with no reason to be
re-created was deleted. This affects the 'expunged' and 'reinstated'
cases in the test.
|
|
This does cause a minor regression: index pages are now committed
individually rather than being a single commit per rebuild.
This also means the autoindex regression test needs to trigger the
autofile generation pass.
|
|
underlay.
Skip fixing links in such pages. The user will get a list of pages that
still link to the old page.
|
|
Values have to be checked against wiki_file_regexp, not just file_pruned.
Audited the rest of the code base for similar problems, found none.
|
|
|
|
|
|
|
|
|
|
|
|
For the moment, have the tag test keep the old behaviour.
|
|
This means we don't need to import Cwd and use abs_path.
|
|
|
|
|
|
This can contain auto-generated things, like tag pages; if edited
they'll automatically migrate into source code control.
|
|
|
|
The default templates are also updated to make use of this information.
The rel="alternate" attribute is also inserted, for completeness.
(cherry picked from commit 618ade535e6a7967a510d9e210edaef3d37cc9bc)
|
|
|
|
|
|
cgitemplate is a modified misctemplate that takes an optional cgi object
and uses it to set the baseurl, and also optionally the forcebaseurl,
if a page is provided.
If no cgi object is provided, it will fall back to using $config{url}.
I expect this will only be needed in exceptional cases where
that doesn't much matter, such as cgierror().
showform uses cgitemplate, so there is no more need for showform_preview.
|
|
This way, do=goto will go to the page relative to
the current location, while the permalinks in feeds
will be absolute (unless an url is not configured at all).
|
|
|
|
|
|
|
|
permalinks always need to be full urls
|
|
|
|
This was I think a relic from when BASEURL was used in more templates than
use it now.
|
|
Was broken (in theory) by baseurl changes in last release.
|
