#102: Use HTTP response codes correctly
------------------------+---------------------------------------------------
Reporter: dom | Owner: dom
Type: defect | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
------------------------+---------------------------------------------------
For example, if I try to visit action=about when that action isn't
defined, I should get an HTTP 404 or similar, rather than an HTML message
about node not being found.
--
Ticket URL: <http://dev.openguides.org/ticket/102>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#92: Integrate with SpamMonkey
-------------------------+--------------------------------------------------
Reporter: ivorw | Owner: dom
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
I have released [http://search.cpan.org/~ivorw/CGI-Wiki-Plugin-SpamMonkey/
CGI::Wiki::Plugin::SpamMonkey] to CPAN. This is an alpha release, as I am
not familiar with SpamAssassin and SpamMonkey rules, so more work needs to
be done here potentially.
The code in OpenGuides can be made to do a spam check for all commits
(previews also, probably), and redirect to a static HTML page if spam is
detected.
--
Ticket URL: <http://dev.openguides.org/ticket/92>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#85: Custom user stylesheets
------------------------+---------------------------------------------------
Reporter: ivorw | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: svn | Severity: normal
Keywords: |
------------------------+---------------------------------------------------
I think it would be really useful if people could set their own CSS url in
user prefs. This would make developing look & feel so much easier.
However, I'm wondering if we want the user CSS in addition to the site one
or instead.
What do others think?
--
Ticket URL: <http://dev.openguides.org/ticket/85>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#132: Standardise pages
-------------------------+--------------------------------------------------
Reporter: cds | Owner: dom
Type: enhancement | Status: new
Priority: low | Milestone:
Component: openguides | Version: svn
Severity: trivial | Keywords:
-------------------------+--------------------------------------------------
Different pages seem to use templates differently - the history pages
doesn't have a #content - the edit page doesn't even have a navbar! It
would be a lot easier to customise if it was all standardised.
--
Ticket URL: <http://dev.openguides.org/ticket/132>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#79: Strip out HTML in node names
-------------------+--------------------------------------------------------
Reporter: dom | Owner: dom
Type: defect | Status: new
Priority: high | Component: openguides
Version: svn | Severity: normal
Keywords: |
-------------------+--------------------------------------------------------
A new spamming ploy is to use <a href ... node names. This results in much
easier linkspamming and should be filtered out.
--
Ticket URL: <http://dev.openguides.org/ticket/79>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#78: deleting versions out of order results in inconsistency
-------------------+--------------------------------------------------------
Reporter: dom | Owner: dom
Type: defect | Status: new
Priority: normal | Component: openguides
Version: 0.51 | Severity: normal
Keywords: |
-------------------+--------------------------------------------------------
Just a quick one to remind me to look in more detail. If I delete version
2 out of 3 of a node, the comments end up being inconsistent. Bug in the
delete function I guess.
--
Ticket URL: <http://dev.openguides.org/ticket/78>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#160: Tidy up after hackfest and do a release
------------------------+---------------------------------------------------
Reporter: dom | Owner: dom
Type: task | Status: new
Priority: high | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
------------------------+---------------------------------------------------
Just that.
--
Ticket URL: <http://dev.openguides.org/ticket/160>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project