#72: Node renaming tool
---------------------------------------+------------------------------------
Reporter: earle | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Keywords: utilities, database, admin |
---------------------------------------+------------------------------------
There should be a tool for admins to rename nodes. As I see it the steps
of doing so are:
{{{
#!html
<ol>
<li>Pick node, new node name.</li>
<li>Get error if new name exists. Otherwise, confirm rename yes/no.</li>
<li>All node data, metadata gets copied with new name.</li>
<li>For each node in the metadata shown as linking to the old node, copy
the content, replace the old name with new in the content and save
it.</li>
<li>Replace occurrences of old name with new in link metadata just
mentioned.</li>
<li>Delete all node data for old node.</li>
<li>Display confirmation.</li>
</ol>
}}}
--
Ticket URL: <http://dev.openguides.org/ticket/72>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#60: Default node content
------------------------+---------------------------------------------------
Reporter: dom | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Keywords: |
------------------------+---------------------------------------------------
We should prepopulate some choice nodes with some skeletal text to make
the initial install less intimidating (especially the home page and those
linked in the navbar).
--
Ticket URL: <http://dev.openguides.org/ticket/60>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#90: Google Maps tests
------------------------+---------------------------------------------------
Reporter: dom | Owner: dom
Type: defect | Status: new
Priority: normal | Milestone: 0.53
Component: openguides | Version: svn
Severity: normal | Keywords:
------------------------+---------------------------------------------------
The Google maps stuff in general needs some unit tests.
--
Ticket URL: <http://dev.openguides.org/ticket/90>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#81: Make "Category" and "Locale" prefixes in autogenerated nodes optional or
customisable
------------------------+---------------------------------------------------
Reporter: grimoire | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: 0.51 | Severity: normal
Keywords: |
------------------------+---------------------------------------------------
I believe that having "Category" and "Locale" prefixed to the name of a
node is redundant and counterintuitive for users. A node is a category if
it is in category Category, and a locale if it is in category Locale.
Also, my Guide is becoming full of redirects from Locale Foo to Foo, and
Category Bar to Bar (and occasionally from both Locale Foo and Category
Foo to Foo).
Several places in the OpenGuides code seem to require that locales and
categories have node names prefixed with this information, so it's easier
said than done, sadly.
--
Ticket URL: <http://dev.openguides.org/ticket/81>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#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