#183: map index should be more intelligent
------------------------+---------------------------------------------------
Reporter: bob | Owner: dom
Type: defect | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
------------------------+---------------------------------------------------
the map index should make more intelligent decisions about its centre and
zoom level
--
Ticket URL: <http://dev.openguides.org/ticket/183>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#262: Recent javascript changes break parsing by Test::HTML::Content
------------------------+---------------------------------------------------
Reporter: dom | Owner: Nobody
Type: defect | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
------------------------+---------------------------------------------------
{{{
HTML parser error : Element script embeds close tag
$("#pick_locale").html("<a
href='javascript:pick_locale()'>pick Locale</a>
^
HTML parser error : Element script embeds close tag
$("#pick_category").html("<a href='javascript:pick_category()'>pick
Category
^
}}}
--
Ticket URL: <http://dev.openguides.org/ticket/262>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#248: Implement Content-Type negotiation for RDF output (aka Nicer URIs)
-------------------------+--------------------------------------------------
Reporter: earle | Owner: Nobody
Type: enhancement | Status: new
Priority: low | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
Context: [http://norman.walsh.name/2005/06/19/httpRange-14 Norman Walsh
explains "httpRange-14"]
If a URI is requested of us, we should negotiate with the client
application using whatever Accept: header it offers. Example:
Request URI: http://openguides.example.org/Somewhere
If the client requests Text/HTML (ie, a human using a browser), we should
303 (See Other) redirect to http://openguides.example.org/page/Somewhere
If the client requests Application/RDF+XML, we should 303 (See Other)
redirect to http://openguides.example.org/rdf/Somewhere
The RDF output's rdf:about value will need to have the URI inserted thus:
{{{
<rdf:Description rdf:about="http://openguides.example.org/Somewhere">
<!-- everything else here -->
</rdf:Description>
}}}
--
Ticket URL: <http://dev.openguides.org/ticket/248>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#249: Static rendering
-------------------------+--------------------------------------------------
Reporter: earle | Owner: Nobody
Type: enhancement | Status: new
Priority: low | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
Idea: rejig the code to static render ("bake") pages. This could result in
a significant load reduction on any busy server using OpenGuides.
How to:
1) Move the rendering step from page load time to save time.
2) When a user saves a page, channel the output to a file.
3) Redirect the user to the file.
Some template adjustment will be needed to the base URL for inter-page
links.
I think dynamic rendering is fine to be kept for historic versions of
pages as they're rarely requested, and to save static copies of all of
them would be unnecessary.
--
Ticket URL: <http://dev.openguides.org/ticket/249>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#196: Need "revert all changes by x" tool and "revert guide to state at yyyy-mm-
dd hh:mm" tool
------------------------+---------------------------------------------------
Reporter: nick | Owner: dom
Type: defect | Status: new
Priority: high | Milestone:
Component: openguides | Version: svn
Severity: major | Keywords: spam commandline
------------------------+---------------------------------------------------
To deal with spam attacks, we need the following two tools:
* revert all changes by username (be that a name or a ip)
* revert all changes since a certain date
For the former, grab node id and version, delete those from content and
metadata, roll node back one version, then copy content over.
For latter, grab last node id and version before date, delete all versions
after on metadata and content, roll node back to last version before data,
then copy content over.
--
Ticket URL: <http://dev.openguides.org/ticket/196>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#195: Further discussion of location of common category/locale stuff
------------------------+---------------------------------------------------
Reporter: dom | Owner: dom
Type: task | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
------------------------+---------------------------------------------------
Kake things the common cat/locales should be in the navbar; this possibly
conflicts with design work done by Torchbox. We should try and discuss the
best way to go forward in conjunction with finding out if we are likely to
get anything usable out of Torchbox.
--
Ticket URL: <http://dev.openguides.org/ticket/195>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#185: admin audit trail
-------------------------+--------------------------------------------------
Reporter: bob | Owner: dom
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
currently admins can do stuff with no audit trail or accountability.
admin rights should be based on user credentials not just a password.
admin actions should log somewhere.
--
Ticket URL: <http://dev.openguides.org/ticket/185>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#275: Category maps
-------------------------+--------------------------------------------------
Reporter: dom | Owner: Nobody
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
A request from a user has highlighted the fact that we don't link to maps
(;format=map) from category pages. Perhaps we could, as these are quite
useful.
--
Ticket URL: <http://dev.openguides.org/ticket/275>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project