Custom Query (298 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (28 - 30 of 298)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Ticket Resolution Summary Owner Reporter
#198 wontfix Banned word list content filtering Nobody Dominic Hargreaves
Description

We need some simple banned word content filtering.

Earle has submitted the attached as a start on this, which is probably half-there, but really this should be done in Wiki::Toolkit as a pre-write plugin?

To be discussed post 0.59.

#123 fixed Bogus warnings about duplicate IDs in HTML templates Dagfinn Ilmari Mannsåker Dominic Hargreaves
Description

With Test::HTML::Content installed, we get some warnings that have probably been around for ages:

t/27_geo_data_edit_form............ok 12/18element textarea: validity error : ID content already defined
    <td><textarea name="content" id="content" rows="21" cols="70" wrap="virtual"
                                                                               ^
element textarea: validity error : ID content already defined
    <td><textarea name="content" id="content" rows="21" cols="70" wrap="virtual"
                                                                               ^
element textarea: validity error : ID locales already defined
              <td><textarea name="locales" id="locales" rows="5" cols="70"></tex
                                                                          ^
element textarea: validity error : ID categories already defined
              <td><textarea name="categories" id="categories" rows="5" cols="70"
                                                                               ^
element select: validity error : ID edit_type already defined
        <select name="edit_type" id="edit_type">
                                               ^

etc etc.

#18 wontfix Break down address into separate fields Nobody IVORW@…
Description

Fri Oct 14 03:19:20 2005 IVORW - Ticket created [Reply] [Comment]

Subject: Break down address into separate fields

Currently, OG has two fields which are configured at guide level: country and city. This is not flexible enough, and can't cope with circumstances like "The Tourist Engineer".

While still retaining a metadata field called "address" containing "Foobar House, 2 Foobar Crescent" and suchlike, I propose the following configurable metadata fields:

town city county state country

Each of these is configured at the guide level to be one of the following:

  • A metadata field
  • Turned off
  • Forced to be a particular value e.g. London

In the latter case, the edit page presents a checkbox against the forced value. This will enable us to have addresses in "Richmond, Surrey" in the London guide for example.

Download (untitled) 706b

Sun Oct 30 10:05:39 2005 IVORW - Correspondence added [Reply] [Comment]

Starting to work on this one. Please let me know of any relevant points.

Download (untitled) 72b

Sun Oct 30 14:08:25 2005 IVORW - Correspondence added [Reply] [Comment]

A patch is ready (attached)

Download (untitled) 28b

Download rt15051.patch 13.1k

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Note: See TracQuery for help on using queries.