#169: Printer friendly option
-------------------------+--------------------------------------------------
Reporter: ivorw | Owner: dom
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
It would be nice to have an option for viewing OpenGuides pages without
the navbar, search box, etc. suitable for printing out and giving to
people. Other sites have this.
I suggest index.cgi?id=page_name;format=print
--
Ticket URL: <http://dev.openguides.org/ticket/169>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#201: There should be an admin option to make preview above edit form default to
"on".
-------------------------+--------------------------------------------------
Reporter: Kake | Owner: Kake
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
At the moment, the preview appears below the edit form by default.
Although this can be swapped over in the user preferences, it can be
confusing to new users who haven't discovered the preferences yet. We
should add an admin config option so admins can choose to have their guide
default to "preview above edit form" unless a user chooses otherwise.
(Although this rearrangement could be accomplished in CSS, with suitable
rearrangement of the edit form to use <div>s instead of tables, I think
it's better to do it with conditional logic in the code/templates, since
that lets us integrate it with the user preference.)
--
Ticket URL: <http://dev.openguides.org/ticket/201>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#225: Prefs page needs test
------------------------+---------------------------------------------------
Reporter: ilmari | Owner: ilmari
Type: defect | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: minor | Keywords:
------------------------+---------------------------------------------------
There are currently no tests to make sure that the prefs page reflects the
contents of the user's prefs cookie.
--
Ticket URL: <http://dev.openguides.org/ticket/225>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#231: Use osm tiles
-----------------------------------+----------------------------------------
Reporter: dom | Owner: dom
Type: defect | Status: new
Priority: normal | Milestone:
Component: oxford.openguides.org | Version: svn
Severity: normal | Keywords:
-----------------------------------+----------------------------------------
Rather then the old demo tiles from the mapnik server, use tile.osm tiles
as per demo at
http://media.mapnik.org/oxford-osm.html
(ultimately, work this into the main distribution)
--
Ticket URL: <http://dev.openguides.org/ticket/231>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#202: Edit form should have an internal anchor link to let people jump below the
preview to the edit form.
-------------------------+--------------------------------------------------
Reporter: Kake | Owner: Kake
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
-------------------------+--------------------------------------------------
In cases where the preview is displayed above the edit form, there should
be a link at the top to let people jump down the page to the edit form.
If an admin doesn't want it, they can turn it off with CSS.
--
Ticket URL: <http://dev.openguides.org/ticket/202>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#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
#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