Move public interest test question into its own. Use better titles for the other questions about deadlines.

<% @title = "About" %>

Contents

Introduction

Making requests

Privacy policy

FOI officers

Credits

Contact us

If your question isn't answered here, or you just wanted to let us know
    something about the site, contact us.

Introduction to WhatDoTheyKnow #

What is WhatDoTheyKnow for? #

To help you find out inside information about what the UK government
is doing.

How does the site work? #

You choose the public authority that you would like information from, then
write a brief note describing what you want to know. We then send your request
to the public authority. Any response they make is automatically published on the
website for you and anyone else to find and read.

Why would I bother to do this? #

You pay taxes, and then government does things with the money. All sorts of
things that affect your life, from healthcare through to national defence. Some
it does badly, some it does well. The more we find out about how government
works, the better able we are to make suggestions to improve the things that
are done badly, and to celebrate the things that are done well.

Why would the public authority bother to reply? #

Under Freedom of Information (FOI) law, they have to respond. The response
will either contain the information you want, or give a valid legal reason why
it must be kept confidential.

Who makes it? #

WhatDoTheyKnow is created and run by mySociety,
and was initially funded by the JRSST Charitable Trust. mySociety is a project of the
registered charity UK Citizens Online Democracy.
If you like what we're doing, then you can
make a donation.

Making requests #

You're missing the public authority that I want to request from! #

Please contact us with the name of the public authority and,
if you can find it, their contact email address for Freedom of Information requests.

If you'd like to help add a whole category of public authority to the site, we'd love
to hear from you too.

Why must I keep my request focused?#

Please put in your request only what is needed so that someone can
easily identify what information you are asking for. Please do
not include any of the following:

arguments about your cause

statements that could defame or insult others

If you do, we may have to remove your request to avoid problems with
libel law, which is a pain for both you and us. Short, succinct messages
make it easier for authorities to be clear what information you are
requesting, which means you will get a reply more quickly.

If you want information to support an argument or campaign, Freedom of
Information is a powerful tool. Although you may not use this site to
run your campaign, we encourage you to use it to get the information you
need. We also encourage to run your campaign elsewhere - one effective
and very easy way is to <%= link_to 'start your own blog',
"http://wordpress.com/"%>. You are welcome to link to your campaign
from this site in an annotation to your request (you can make
annotations after submitting the request).

Does it cost me anything to make a request?#

Making an FOI request is nearly always free.

Sometimes an authority will reject your request, saying that the cost
of handling it exceeds £600 (for central government) or £450 (for all other
public authorities). At this point you can refine your
request. e.g. it would be much cheaper for an authority to tell you the amount
spent on marshmallows in the past year than in the past ten years.
.

There are other rare cases where an authority may say that they want to charge you, such as for postage
or photocopying.  Either way, don't worry, the authority cannot make a charge unless you have
specifically agreed in advance to pay it. More details from the Information Commissioner.

How quickly will I get a response? #

By law, public authorities must respond promptly to
requests.

Even if they are not prompt, in nearly all cases they must respond within
20 working days. If you had to clarify your request, or they are a school,
or one or two other cases, then they may have more time
(full details).

WhatDoTheyKnow will email you if you don't get a timely response.  You can
then send the public authority a message to remind them, and tell them if they
are breaking the law.

What if I never get a response?#

There are several things you can do if you never get a response.

Sometimes there has been a genuine problem and the authority never
    received the request. It is worth telephoning the authority and politely
    checking that they received the request. It was sent to them by email.

If they have not received it, the problem is most likely due to
    "spam filters". Refer the authority to the measures in the answer
    'I can see a request on WhatDoTheyKnow, but we never got it by email!'
    below.

If you're still having no luck, then you can ask for an internal review,
    and then complain to the Information Commissioner about the authority.
    Read our page 'Unhappy about the response you got?'.

What if I'm not satisfied with the response? #

If you didn't get the information you asked for, or you didn't get it in time,
then read our page 'Unhappy about the response you got?'.

Can you tell me more of the nitty gritty about the process of making requests? #

Have a look at the
access to official information
pages on the Information Commissioner's website.

If you're requesting information from a Scottish public authority,
the process is very similar. There are differences around time
limits for compliance.
See the Scottish
Information Commissioner's guidance for details.

Can I request information about myself? #

No. Requests made using WhatDoTheyKnow are public, made under the Freedom of
Information Act, and cannot help you find information about a private
individual.

If you would like to know what information a public
authority holds about yourself, you should make a "Subject Access Request" in
private using Data Protection law.  The leaflet "How to access your information" (on the Information Commissioner's
website) explains how to do this.

If you see that somebody has included personal information, perhaps
unwittingly, in a request, please contact us
immediately so we can remove it.

I'd like to keep my request secret! (At least until I publish my story) #

WhatDoTheyKnow is currently only designed for public requests. All
responses that we receive are automatically published on the website for anyone
to read.  You should contact the public authority directly if you would like to
make a request in private.  If you're interested in buying a system which helps
you manage FOI requests in secret, then contact us.

Why can I only request information about the environment from some authorities? #

Some public authorities, such as South East Water,
don't come under the Freedom of Information Act, but do come under another law called
the Environmental Information Regulations (EIR).

It's a very similar law, so you make a request
to them using WhatDoTheyKnow in just the same way as an FOI request. The only difference
is that on the page where you write you request, it reminds you that you can only
request "environmental information" and tells you what that means. It is quite broad.

You can, of course, request environmental information from other
authorities. Just make a Freedom of Information (FOI) request as normal. The
authority has a duty to work out if the Environmental Information Regulations
(EIR) is the more appropriate legislation to reply under.

Can I make the same to request to lots of authorities, e.g. all councils? #

We ask you to first send a test version of your request to a few
authorities. Their responses will help you improve the wording of your request,
so that you get the best information when you send the request to all of
the authorities. There is currently no automated system for sending the request
to the other authorities, you must copy and paste it by hand.

I made a request off the site, how do I upload it to the archive?#

WhatDoTheyKnow is an archive of requests made through the site,
and does not try to be an archive of all FOI requests. We'll never support uploading
other requests. For one thing, we wouldn't be able to verify that other
responses actually came from the authority. If this really matters to you,
you can always make the same request again via WhatDoTheyKnow.

Privacy policy #

Who gets to see my email address? #

We will not disclose your email address to anyone unless we are obliged to by law,
or you ask us to. This includes the public authority that you are sending a
request to.  They only get to see an email address
@whatdotheyknow.com which is specific to that request.

If you send a message to another user on the site, then it will reveal your
email address to them. You will be told that this is going to happen.

Will you send nasty, brutish spam to my email address? #

Nope. After you sign up to WhatDoTheyKnow we will only send you emails
relating to a request you made, an email alert that you have signed up for,
or for other reasons that you specifically authorise. We will never give or
sell your email addresses to anyone else, unless we are obliged to by law, or
you ask us to.

Why will my name and my request appear publicly on the site? #

We publish your request on the Internet so that anybody can read it and
make use of the information that you have found.

Your name is tangled up with your request, so has to be published as well.
It is only fair, as we're going to publish the name of the civil servant who
writes the response to your request.  Using your real name also helps people
get in touch with you to assist you with your research or to campaign with you.

By law, you must use your real name for the request to be a valid Freedom of
Information request. See the next question for alternatives if you do not want
to publish your full name.

Can I make an FOI request using a pseudonym? #

Technically, you must use your real name for your request to be a valid Freedom of Information request in law. See this
guidance from the Information Commissioner (January 2009).

However, the same guidance also says it is good practice for the public
authority to still consider a request made using an obvious pseudonym.
You should refer to this if a public authority refuses a request because you
used a pseudonym.

Be careful though, even if the authority follows this good practice, the
pseudonym will probably make it impossible for you to complain to the
Information Commissioner later about the handling of your request.

There are several good alternatives to using a pseudonym.

Use a different form of your name. The guidance says
that "Mr Arthur Thomas Roberts" can make a valid request as "Arthur Roberts",
"A. T. Roberts", or "Mr Roberts", but not as "Arthur" or "A.T.R.".

Women may use their maiden name.

In most cases, you may use any name by which you are "widely known and/or
is regularly used".

Use the name of an organisation, the name of a company, the trading name of
a company, or the trading name of a sole trader.

Ask someone else to make the request on your behalf.

You may, if you are really stuck, ask us to make the request on
your behalf. Please contact us with
a good reason why you cannot make the request yourself and cannot
ask a friend to. We don't have the resources to do this for everyone.

Please do not try to impersonate someone else.

They've asked for my postal address! #

If a public authority asks you for your full, physical address, reply to them saying
that section 8.1.b of the FOI Act asks for an "address for correspondence",
and that the email address you are using is sufficient.

The Ministry of Justice has guidance
on this –
"As well as hard copy written correspondence, requests that are
transmitted electronically (for example, in emails) are acceptable
... If a request is received by email and no postal address is given, the email
address should be treated as the return address."

As if that isn't enough, the Information Commissioner's
Hints for Practitioners say
"Any correspondence could include a request for information. If it is written (this includes e-mail), legible, gives the name of the applicant, an address for reply (which could be electronic), and includes a description of the information required, then it will fall within the scope of the legislation."

No no, they need a postal address to send a paper response! #

If an authority only has a paper copy of the information that you want,
they may ask you for a postal address. To start with, try persuading them
to scan in the documents for you. You can even offer to gift them a scanner, which in that particular case
embarrassed the authority into finding one they had already.

If that doesn't work, and you want to provide your postal address privately
in order to receive the documents, mark your request as "They are going to reply by post", and it will
give you an email address to use for that purpose.

How do you moderate request annotations? #

Annotations on WhatDoTheyKnow are to help
people get the information they want, or to give them pointers to places they
can go to help them act on it. We reserve the right to remove anything else.

Endless, political discussions are not allowed.
Post a link to a suitable forum or campaign site elsewhere.

FOI officer questions #

I just got here from bottom of an FOI request, what is going on? #

WhatDoTheyKnow is a service run by a charity. It helps ordinary members
of the public make FOI requests, and easily track and share the responses.

The FOI request you received was made by someone using WhatDoTheyKnow. You can
simply reply to the request as you would any other request from an individual.
The only difference is that your response will be automatically published on
the Internet.

If you have privacy or other concerns, please read the answers below.
You might also like to read this page from the top to find out more about what
the site does from the point of view of a user. You can also search the
site to find the authority that you work for, and view the status of
any requests made using the site.

Finally, we welcome comments and
thoughts from FOI officers, please get in touch.

Why are you publishing responses to FOI requests? #

We think there are lots of benefits. Most importantly it will encourage the
public to be more interested and involved in the work of government. We
also hope that it will reduce the number of duplicate requests on any
subject that a public body will receive. Given that Freedom of Information
responses contain public information, which anybody could easily request
again from the public authority, we think there should be no reason not to
publish it widely.

Are the people making requests real people? #

Yes. For the purposes of keeping track of responses we use
computer-generated email addresses for each request. However, before
they can send a request, each user must register on the site with a
unique email address that we then verify. You can search this site and
find a page listing all requests that each person has made.

An email isn't a sufficient address for an FOI request! #

Yes it is. This
letter from the ICO to Rother District Council gives guidance on the matter, specifically
in the context of requests made via WhatDoTheyKnow.

Aren't you making lots of vexatious requests? #

WhatDoTheyKnow is not making any requests. We are sending requests on
behalf of our users, who are real people making the requests.

Look at it like this - if lots of different people made requests from
different Hotmail email addresses, then you would not think that Microsoft were
making vexatious requests. It is exactly the same if lots of requests are made
via WhatDoTheyKnow. Moreover, since all requests are public it is much easier
for you to see if one of our users is making vexatious requests.

If that isn't enough for you, the
letter from the ICO to Rother District Council gives some guidance on the matter.

I can see a request on WhatDoTheyKnow, but we never got it by email!#

If a request appears on the site, then we have attempted to send it to
the authority by email. Any delivery failure messages will automatically
appear on the site. You can check the address we're using with the "View FOI
email address" link which appears on the page for the authority. Contact us if there is a better address we can
use.

Requests are sometimes not delivered because they are quietly removed by
"spam filters" in the IT department of the authority. Authorities can make
sure this doesn't happen by asking their IT departments to "whitelist"
any email from @whatdotheyknow.com.
If you ask us we will resend any request,
and/or give technical details of delivery so an IT department can chase
up what happened to the message.

Finally, you can respond to any request from your web browser, without
needing any email, using the "respond to request" link at the bottom of
each request page.

How do you calculate the deadline shown on request pages?#

The Freedom of Information Act says:

A public authority must comply with section 1(1) promptly and
in any event not later than the twentieth working day following the date of
receipt.

The nerdy detail of exactly how weekends are counted, and what happens if
the request arrives out of office hours, is just that - detail. What matters
here is that the law says authorities must respond promptly.

If you've got a good reason why the request is going to take a while to
process, requesters find it really helpful if you can send a quick email with a
sentence or two saying what is happening.

FOI officers often have to do a lot of hard work to answer
requests, and this is hidden from the public. We think it would help everyone
to have more of that complexity visible.

But really, how do you calculate the deadline?#

Please read the answer to the previous question first. Legally, authorities
must respond promptly to FOI requests. If they fail to do that,
it is best if they show the hard work they are doing by explaining what is
taking the extra time to do.

That said, WhatDoTheyKnow does show the maximum legal deadline
for response on each request. Here's how we calculate it.

If the day we deliver the request by email is a working day, we count that
as "day zero", even if it was delivered late in the evening. Days end at
midnight.  We then count the next working day as "day one", and so on up to
20 working days.

If the day the request email was delivered was a non-working day, we count
the next working day as "day one". Delivery is delivery, even if it happened on
the weekend. Some authorities disagree with this, our lawyer disagrees with them.

Requesters are encouraged to mark when they have clarified
their request so the clock resets, but sometimes they get this wrong. If you
see a problem with a particular request, let us know and we'll fix it.

The date thus calculated is shown on requests with the text "By law,
Liverpool City Council should normally have responded by...". There is only
one case which is not normal, see the next question about
public interest test time extensions.

Schools are also a special case, which WhatDoTheyKnow displays differently.

Since June 2009, schools have "20 working days
disregarding any working day which is not a school day, or 60 working days,
whichever is first" (FOI (Time for Compliance with Request) Regulations 2009). WhatDoTheyKnow indicates on requests to schools that the 20 day deadline is only
during term time, and shows them as definitely overdue after 60 working days

If you're getting really nerdy about all this, read the detailed ICO guidance.
Meanwhile, remember that the law says authorities must respond
promptly. That's really what matters.

How do you reflect time extensions for public interest tests?#

The Freedom of Information Act lets authorities claim an indefinite time
extension when applying a public interest test.  Information
Commissioner guidance says that it should only be used in "exceptionally
complex" cases
(FOI Good Practice Guidance No. 4).
WhatDoTheyKnow doesn't specifically handle this case, which is why we use the
phrase "should normally have responded by" when the 20 working day time is
exceeded.

The same guidance says that, even in exceptionally complex cases, no
Freedom of Information request should take more than 40 working days
to answer.  WhatDoTheyKnow displays requests which are overdue by that much
with stronger wording to indicate they are definitely late.

The Freedom of Information (Scotland) Act does not allow such a public
interest extension. WhatDoTheyKnow would like to see the law changed to either
remove the extension from the UK Act, or to reintroduce an absolute time limit
of 40 working days even with the extension (the House of Lords voted
to remove provision for such a time limit during the initial passage
of the UK Act through Parliament).

How can I send a large file, which won't go by email?#

Instead of email, you can respond to a request directly from your web
browser, including uploading a file. To do this, choose "respond to request" at
the bottom of the request's page. Contact us if it
is too big for even that (more than, say, 50Mb).

Why do you publish the names of civil servants and the text of emails? #

We consider what officers or servants do in the course of their employment
to be public information.

Can you take down personal information about me? #

If you see any personal information about you on the site which you'd like
us to remove or hide, then please let us know,
specifying exactly what information you believe to be problematic and why, and
where it appears on the site.

If it is sensitive personal information that has been accidentally
posted, then we will usually remove it. Normally we will only consider
requests to remove personal information which come from the individual
concerned, but for sensitive information we would appreciate anyone
pointing out anything they see.

We consider for various reasons that there is a strong public interest in
retaining the names of officers or servants of public authorities. We will only
remove such names in exceptional circumstances, such as where the disclosure of
a name and position of employment would substantially risk an individual's
safety. If you are such an official and you wish to have your name removed for
such an urgent reason, you must supply us with a request to do so from your
line manager. This request must demonstrate that a risk has been perceived
which outweighs the public interest, and must demonstrate that efforts have
been made to conceal the name on the organisation's own website.

For all other requests we apply a public interest test to decide
whether information should be removed.
 Section 32
of the Data Protection Act 1998 permits us to do this, as the material we
publish is journalistic. We cannot easily edit many types of attachments (such
as PDFs, or Microsoft Word or Excel files), so we will usually ask
that authorities resend these with the personal information removed.

Do you publish email addresses or mobile phone numbers? #

We automatically remove some emails and mobile numbers from responses to requests.
Please contact us if we've missed one.
For technical reasons we don't remove them all from attachments, such as PDFs.

What is your policy on copyright of documents?#

Our Freedom of Information law is "applicant blind", so anyone in the
world can request the same document and get a copy of it.

If you think our making a document available on the internet infringes your
copyright, you may contact us and ask us
to take it down.  However, to save tax payers' money by preventing duplicate
requests, and for good public relations, we'd advise you not to do that.

Credit where credit is due #

Which people made WhatDoTheyKnow? #

Oh, nearly everyone (and maybe you too)!

    Heather Brooke
    (vampy!) has
    been pushing the idea of a UK FOI archive for years now.

    Both Phil Rodgers and Francis Irving
    entered it in a mySociety competition for ideas for public interest websites to build.

    It won,
    and then Chris Lightfoot (RIP :()
    thought up the wheeze of intercepting email responses to requests and
    automatically publishing them.

    Tom Steinberg got the cash to pay for the site from
    a dead chocolate mogul (thank you!) ...

    ... so that Francis Irving, Angie Ahl, Tommy Martin, Louise Crow, Matthew Somerville
    and Tom Steinberg could do the complex mixture of design and coding to build
    what you see today.

    Thanks particularly to Julian Todd (great blog!),
    Francis Davey, and Etienne Pollard for using the site early on and giving
    feedback (and/or legal advice!), and also to all our other users and
    testers.

    The amazing team of volunteers who run the site, answer your support
    emails, maintain the database of public authorities and so much more.
    Thanks to Tony Bowden, John Cross, Adam McGreggor, Alex Skene, Richard Taylor.

    Everyone who has helped look up FOI email addresses.

    We couldn't do any of this without those
    crazy people who volunteer,
    amongst many other things, to do the accounts and fill in our VAT return.

    Finally, all the officers and servants who have answered the many requests
    made through the site. Their diligence, patience and professionalism is
    what has actually made the information that you see here. Thank them for
    helping make Government more transparent.

You're all stars.

Can I help out? #

Yes please! We're built out of our supporters and volunteers.

You can make a donation. We're a registered charity.

Help people find successful requests, and monitor performance of authorities, by
    playing the categorisation game.

Find out FOI email addresses of authorities that we're missing.

Write a blog post about either WhatDoTheyKnow or an interesting request that you've
    found. Post about it on a forum that you frequent. Tell friends about it.

If you're
    a programmer, get the
    source code
    and tell us about patches we can pull. It's made in Ruby on Rails.

Read more about volunteering with mySociety.

<% @title = "About" %>

Contents

Introduction

Making requests

Privacy policy

FOI officers

Credits

Contact us

If your question isn't answered here, or you just wanted to let us know
    something about the site, contact us.

Introduction to WhatDoTheyKnow #

What is WhatDoTheyKnow for? #

To help you find out inside information about what the UK government
is doing.

How does the site work? #

You choose the public authority that you would like information from, then
write a brief note describing what you want to know. We then send your request
to the public authority. Any response they make is automatically published on the
website for you and anyone else to find and read.

Why would I bother to do this? #

You pay taxes, and then government does things with the money. All sorts of
things that affect your life, from healthcare through to national defence. Some
it does badly, some it does well. The more we find out about how government
works, the better able we are to make suggestions to improve the things that
are done badly, and to celebrate the things that are done well.

Why would the public authority bother to reply? #

Under Freedom of Information (FOI) law, they have to respond. The response
will either contain the information you want, or give a valid legal reason why
it must be kept confidential.

Who makes it? #

WhatDoTheyKnow is created and run by mySociety,
and was initially funded by the JRSST Charitable Trust. mySociety is a project of the
registered charity UK Citizens Online Democracy.
If you like what we're doing, then you can
make a donation.

Making requests #

You're missing the public authority that I want to request from! #

Please contact us with the name of the public authority and,
if you can find it, their contact email address for Freedom of Information requests.

If you'd like to help add a whole category of public authority to the site, we'd love
to hear from you too.

Why must I keep my request focused?#

Please put in your request only what is needed so that someone can
easily identify what information you are asking for. Please do
not include any of the following:

arguments about your cause

statements that could defame or insult others

If you do, we may have to remove your request to avoid problems with
libel law, which is a pain for both you and us. Short, succinct messages
make it easier for authorities to be clear what information you are
requesting, which means you will get a reply more quickly.

If you want information to support an argument or campaign, Freedom of
Information is a powerful tool. Although you may not use this site to
run your campaign, we encourage you to use it to get the information you
need. We also encourage to run your campaign elsewhere - one effective
and very easy way is to <%= link_to 'start your own blog',
"http://wordpress.com/"%>. You are welcome to link to your campaign
from this site in an annotation to your request (you can make
annotations after submitting the request).

Does it cost me anything to make a request?#

Making an FOI request is nearly always free.

Sometimes an authority will reject your request, saying that the cost
of handling it exceeds £600 (for central government) or £450 (for all other
public authorities). At this point you can refine your
request. e.g. it would be much cheaper for an authority to tell you the amount
spent on marshmallows in the past year than in the past ten years.
.

There are other rare cases where an authority may say that they want to charge you, such as for postage
or photocopying.  Either way, don't worry, the authority cannot make a charge unless you have
specifically agreed in advance to pay it. More details from the Information Commissioner.

How quickly will I get a response? #

By law, public authorities must respond promptly to
requests.

Even if they are not prompt, in nearly all cases they must respond within
20 working days. If you had to clarify your request, or they are a school,
or one or two other cases, then they may have more time
(full details).

WhatDoTheyKnow will email you if you don't get a timely response.  You can
then send the public authority a message to remind them, and tell them if they
are breaking the law.

What if I never get a response?#

There are several things you can do if you never get a response.

Sometimes there has been a genuine problem and the authority never
    received the request. It is worth telephoning the authority and politely
    checking that they received the request. It was sent to them by email.

If they have not received it, the problem is most likely due to
    "spam filters". Refer the authority to the measures in the answer
    'I can see a request on WhatDoTheyKnow, but we never got it by email!'
    below.

If you're still having no luck, then you can ask for an internal review,
    and then complain to the Information Commissioner about the authority.
    Read our page 'Unhappy about the response you got?'.

What if I'm not satisfied with the response? #

If you didn't get the information you asked for, or you didn't get it in time,
then read our page 'Unhappy about the response you got?'.

Can you tell me more of the nitty gritty about the process of making requests? #

Have a look at the
access to official information
pages on the Information Commissioner's website.

If you're requesting information from a Scottish public authority,
the process is very similar. There are differences around time
limits for compliance.
See the Scottish
Information Commissioner's guidance for details.

Can I request information about myself? #

No. Requests made using WhatDoTheyKnow are public, made under the Freedom of
Information Act, and cannot help you find information about a private
individual.

If you would like to know what information a public
authority holds about yourself, you should make a "Subject Access Request" in
private using Data Protection law.  The leaflet "How to access your information" (on the Information Commissioner's
website) explains how to do this.

If you see that somebody has included personal information, perhaps
unwittingly, in a request, please contact us
immediately so we can remove it.

I'd like to keep my request secret! (At least until I publish my story) #

WhatDoTheyKnow is currently only designed for public requests. All
responses that we receive are automatically published on the website for anyone
to read.  You should contact the public authority directly if you would like to
make a request in private.  If you're interested in buying a system which helps
you manage FOI requests in secret, then contact us.

Why can I only request information about the environment from some authorities? #

Some public authorities, such as South East Water,
don't come under the Freedom of Information Act, but do come under another law called
the Environmental Information Regulations (EIR).

It's a very similar law, so you make a request
to them using WhatDoTheyKnow in just the same way as an FOI request. The only difference
is that on the page where you write you request, it reminds you that you can only
request "environmental information" and tells you what that means. It is quite broad.

You can, of course, request environmental information from other
authorities. Just make a Freedom of Information (FOI) request as normal. The
authority has a duty to work out if the Environmental Information Regulations
(EIR) is the more appropriate legislation to reply under.

Can I make the same to request to lots of authorities, e.g. all councils? #

We ask you to first send a test version of your request to a few
authorities. Their responses will help you improve the wording of your request,
so that you get the best information when you send the request to all of
the authorities. There is currently no automated system for sending the request
to the other authorities, you must copy and paste it by hand.

I made a request off the site, how do I upload it to the archive?#

WhatDoTheyKnow is an archive of requests made through the site,
and does not try to be an archive of all FOI requests. We'll never support uploading
other requests. For one thing, we wouldn't be able to verify that other
responses actually came from the authority. If this really matters to you,
you can always make the same request again via WhatDoTheyKnow.

Privacy policy #

Who gets to see my email address? #

We will not disclose your email address to anyone unless we are obliged to by law,
or you ask us to. This includes the public authority that you are sending a
request to.  They only get to see an email address
@whatdotheyknow.com which is specific to that request.

If you send a message to another user on the site, then it will reveal your
email address to them. You will be told that this is going to happen.

Will you send nasty, brutish spam to my email address? #

Nope. After you sign up to WhatDoTheyKnow we will only send you emails
relating to a request you made, an email alert that you have signed up for,
or for other reasons that you specifically authorise. We will never give or
sell your email addresses to anyone else, unless we are obliged to by law, or
you ask us to.

Why will my name and my request appear publicly on the site? #

We publish your request on the Internet so that anybody can read it and
make use of the information that you have found.

Your name is tangled up with your request, so has to be published as well.
It is only fair, as we're going to publish the name of the civil servant who
writes the response to your request.  Using your real name also helps people
get in touch with you to assist you with your research or to campaign with you.

By law, you must use your real name for the request to be a valid Freedom of
Information request. See the next question for alternatives if you do not want
to publish your full name.

Can I make an FOI request using a pseudonym? #

Technically, you must use your real name for your request to be a valid Freedom of Information request in law. See this
guidance from the Information Commissioner (January 2009).

However, the same guidance also says it is good practice for the public
authority to still consider a request made using an obvious pseudonym.
You should refer to this if a public authority refuses a request because you
used a pseudonym.

Be careful though, even if the authority follows this good practice, the
pseudonym will probably make it impossible for you to complain to the
Information Commissioner later about the handling of your request.

There are several good alternatives to using a pseudonym.

Use a different form of your name. The guidance says
that "Mr Arthur Thomas Roberts" can make a valid request as "Arthur Roberts",
"A. T. Roberts", or "Mr Roberts", but not as "Arthur" or "A.T.R.".

Women may use their maiden name.

In most cases, you may use any name by which you are "widely known and/or
is regularly used".

Use the name of an organisation, the name of a company, the trading name of
a company, or the trading name of a sole trader.

Ask someone else to make the request on your behalf.

You may, if you are really stuck, ask us to make the request on
your behalf. Please contact us with
a good reason why you cannot make the request yourself and cannot
ask a friend to. We don't have the resources to do this for everyone.

Please do not try to impersonate someone else.

They've asked for my postal address! #

If a public authority asks you for your full, physical address, reply to them saying
that section 8.1.b of the FOI Act asks for an "address for correspondence",
and that the email address you are using is sufficient.

The Ministry of Justice has guidance
on this –
"As well as hard copy written correspondence, requests that are
transmitted electronically (for example, in emails) are acceptable
... If a request is received by email and no postal address is given, the email
address should be treated as the return address."

As if that isn't enough, the Information Commissioner's
Hints for Practitioners say
"Any correspondence could include a request for information. If it is written (this includes e-mail), legible, gives the name of the applicant, an address for reply (which could be electronic), and includes a description of the information required, then it will fall within the scope of the legislation."

No no, they need a postal address to send a paper response! #

If an authority only has a paper copy of the information that you want,
they may ask you for a postal address. To start with, try persuading them
to scan in the documents for you. You can even offer to gift them a scanner, which in that particular case
embarrassed the authority into finding one they had already.

If that doesn't work, and you want to provide your postal address privately
in order to receive the documents, mark your request as "They are going to reply by post", and it will
give you an email address to use for that purpose.

How do you moderate request annotations? #

Annotations on WhatDoTheyKnow are to help
people get the information they want, or to give them pointers to places they
can go to help them act on it. We reserve the right to remove anything else.

Endless, political discussions are not allowed.
Post a link to a suitable forum or campaign site elsewhere.

FOI officer questions #

I just got here from bottom of an FOI request, what is going on? #

WhatDoTheyKnow is a service run by a charity. It helps ordinary members
of the public make FOI requests, and easily track and share the responses.

The FOI request you received was made by someone using WhatDoTheyKnow. You can
simply reply to the request as you would any other request from an individual.
The only difference is that your response will be automatically published on
the Internet.

If you have privacy or other concerns, please read the answers below.
You might also like to read this page from the top to find out more about what
the site does from the point of view of a user. You can also search the
site to find the authority that you work for, and view the status of
any requests made using the site.

Finally, we welcome comments and
thoughts from FOI officers, please get in touch.

Why are you publishing responses to FOI requests? #

We think there are lots of benefits. Most importantly it will encourage the
public to be more interested and involved in the work of government. We
also hope that it will reduce the number of duplicate requests on any
subject that a public body will receive. Given that Freedom of Information
responses contain public information, which anybody could easily request
again from the public authority, we think there should be no reason not to
publish it widely.

Are the people making requests real people? #

Yes. For the purposes of keeping track of responses we use
computer-generated email addresses for each request. However, before
they can send a request, each user must register on the site with a
unique email address that we then verify. You can search this site and
find a page listing all requests that each person has made.

An email isn't a sufficient address for an FOI request! #

Yes it is. This
letter from the ICO to Rother District Council gives guidance on the matter, specifically
in the context of requests made via WhatDoTheyKnow.

Aren't you making lots of vexatious requests? #

WhatDoTheyKnow is not making any requests. We are sending requests on
behalf of our users, who are real people making the requests.

Look at it like this - if lots of different people made requests from
different Hotmail email addresses, then you would not think that Microsoft were
making vexatious requests. It is exactly the same if lots of requests are made
via WhatDoTheyKnow. Moreover, since all requests are public it is much easier
for you to see if one of our users is making vexatious requests.

If that isn't enough for you, the
letter from the ICO to Rother District Council gives some guidance on the matter.

I can see a request on WhatDoTheyKnow, but we never got it by email!#

If a request appears on the site, then we have attempted to send it to
the authority by email. Any delivery failure messages will automatically
appear on the site. You can check the address we're using with the "View FOI
email address" link which appears on the page for the authority. Contact us if there is a better address we can
use.

Requests are sometimes not delivered because they are quietly removed by
"spam filters" in the IT department of the authority. Authorities can make
sure this doesn't happen by asking their IT departments to "whitelist"
any email from @whatdotheyknow.com.
If you ask us we will resend any request,
and/or give technical details of delivery so an IT department can chase
up what happened to the message.

Finally, you can respond to any request from your web browser, without
needing any email, using the "respond to request" link at the bottom of
each request page.

You've calculated our deadline wrongly!#

The Freedom of Information Act says:

A public authority must comply with section 1(1) promptly and
in any event not later than the twentieth working day following the date of
receipt.

The nerdy detail of exactly how weekends are counted, and what happens if
the request arrives out of office hours, is just that - detail. What matters
here is that the law says authorities must respond promptly.

If you've got a good reason why the request is going to take a while to
process, requesters find it really helpful if you can send a quick email with a
sentence or two saying what is happening.

FOI officers often have to do a lot of hard work to answer
requests, and this is hidden from the public. We think it would help everyone
to have more of that complexity visible.

But really, you calculated it wrong!#

Please read the answer to the previous question first. Legally, authorities
must respond promptly to FOI requests. If they fail to do that,
it is best if they show the hard work they are doing by explaining what is
taking the extra time to do.

That said, WhatDoTheyKnow does show the maximum legal deadline
for response on each request. Here's how we calculate it.

If the day we deliver the request by email is a working day, we count that
as "day zero", even if it was delivered late in the evening. Days end at
midnight.  We then count the next working day as "day one", and so on up to
20 working days.

If the day the request email was delivered was a non-working day, we count
the next working day as "day one". Delivery is delivery, even if it happened on
the weekend. Some authorities disagree with this, our lawyer disagrees with them.

Requesters are encouraged to mark when they have clarified
their request so the clock resets, but sometimes they get this wrong. If you
see a problem with a particular request, let us know and we'll fix it.

The date thus calculated is shown on requests with the text "By law,
Liverpool City Council should normally have responded by...". There is only
one case which is not normal.

The Freedom of Information Act lets authorities claim an indefinite time
extension when applying a public interest test.  Information
Commissioner guidance says that it should only be used in "exceptionally
complex" cases
(FOI Good Practice Guidance No. 4).
WhatDoTheyKnow doesn't specifically handle this case, which is why we
use the word "normally".

The same guidance says that, even in exceptionally complex cases, no
Freedom of Information request should take more than 40 working days
to answer.  WhatDoTheyKnow displays requests which are overdue by that much
with stronger wording to indicate they are definitely late.

The Freedom of Information (Scotland) Act does not allow such a public
interest extension. WhatDoTheyKnow would like to see the law changed to either
remove the extension from the UK Act, or to reintroduce an absolute time limit
of 40 working days even with the extension (the House of Lords voted
to remove provision for such a time limit).

Schools are also a special case, which WhatDoTheyKnow displays differently.

Since June 2009, schools have "20 working days
disregarding any working day which is not a school day, or 60 working days,
whichever is first" (FOI (Time for Compliance with Request) Regulations 2009). WhatDoTheyKnow indicates on requests to schools that the 20 day deadline is only
during term time, and shows them as definitely overdue after 60 working days

If you're getting really nerdy about all this, read the detailed ICO guidance.
Meanwhile, remember that the law says authorities must respond
promptly. That's really what matters.

How can I send a large file, which won't go by email?#

Instead of email, you can respond to a request directly from your web
browser, including uploading a file. To do this, choose "respond to request" at
the bottom of the request's page. Contact us if it
is too big for even that (more than, say, 50Mb).

Why do you publish the names of civil servants and the text of emails? #

We consider what officers or servants do in the course of their employment
to be public information.

Can you take down personal information about me? #

If you see any personal information about you on the site which you'd like
us to remove or hide, then please let us know,
specifying exactly what information you believe to be problematic and why, and
where it appears on the site.

If it is sensitive personal information that has been accidentally
posted, then we will usually remove it. Normally we will only consider
requests to remove personal information which come from the individual
concerned, but for sensitive information we would appreciate anyone
pointing out anything they see.

We consider for various reasons that there is a strong public interest in
retaining the names of officers or servants of public authorities. We will only
remove such names in exceptional circumstances, such as where the disclosure of
a name and position of employment would substantially risk an individual's
safety. If you are such an official and you wish to have your name removed for
such an urgent reason, you must supply us with a request to do so from your
line manager. This request must demonstrate that a risk has been perceived
which outweighs the public interest, and must demonstrate that efforts have
been made to conceal the name on the organisation's own website.

For all other requests we apply a public interest test to decide
whether information should be removed.
 Section 32
of the Data Protection Act 1998 permits us to do this, as the material we
publish is journalistic. We cannot easily edit many types of attachments (such
as PDFs, or Microsoft Word or Excel files), so we will usually ask
that authorities resend these with the personal information removed.

Do you publish email addresses or mobile phone numbers? #

We automatically remove some emails and mobile numbers from responses to requests.
Please contact us if we've missed one.
For technical reasons we don't remove them all from attachments, such as PDFs.

What is your policy on copyright of documents?#

Our Freedom of Information law is "applicant blind", so anyone in the
world can request the same document and get a copy of it.

If you think our making a document available on the internet infringes your
copyright, you may contact us and ask us
to take it down.  However, to save tax payers' money by preventing duplicate
requests, and for good public relations, we'd advise you not to do that.

Credit where credit is due #

Which people made WhatDoTheyKnow? #

Oh, nearly everyone (and maybe you too)!

    Heather Brooke
    (vampy!) has
    been pushing the idea of a UK FOI archive for years now.

    Both Phil Rodgers and Francis Irving
    entered it in a mySociety competition for ideas for public interest websites to build.

    It won,
    and then Chris Lightfoot (RIP :()
    thought up the wheeze of intercepting email responses to requests and
    automatically publishing them.

    Tom Steinberg got the cash to pay for the site from
    a dead chocolate mogul (thank you!) ...

    ... so that Francis Irving, Angie Ahl, Tommy Martin, Louise Crow, Matthew Somerville
    and Tom Steinberg could do the complex mixture of design and coding to build
    what you see today.

    Thanks particularly to Julian Todd (great blog!),
    Francis Davey, and Etienne Pollard for using the site early on and giving
    feedback (and/or legal advice!), and also to all our other users and
    testers.

    The amazing team of volunteers who run the site, answer your support
    emails, maintain the database of public authorities and so much more.
    Thanks to Tony Bowden, John Cross, Adam McGreggor, Alex Skene, Richard Taylor.

    Everyone who has helped look up FOI email addresses.

    We couldn't do any of this without those
    crazy people who volunteer,
    amongst many other things, to do the accounts and fill in our VAT return.

    Finally, all the officers and servants who have answered the many requests
    made through the site. Their diligence, patience and professionalism is
    what has actually made the information that you see here. Thank them for
    helping make Government more transparent.

You're all stars.

Can I help out? #

Yes please! We're built out of our supporters and volunteers.

You can make a donation. We're a registered charity.

Help people find successful requests, and monitor performance of authorities, by
    playing the categorisation game.

Find out FOI email addresses of authorities that we're missing.

Write a blog post about either WhatDoTheyKnow or an interesting request that you've
    found. Post about it on a forum that you frequent. Tell friends about it.

If you're
    a programmer, get the
    source code
    and tell us about patches we can pull. It's made in Ruby on Rails.

Read more about volunteering with mySociety.


load geoplugin dynamically with YUI3 to avoid blocking

<% form_tag :action=> "signup" do -%>

<% if @error_tos%>

<%=t("madb_error_saving_account")%>

<% if @error_tos %>

<%=t("tos_acceptance_needed")%>

<%end%>

<% end -%>

    <%= country_select "account", "country", { t("madb_choose") => 0}%>

<%= t("madb_administrator_user")%>

<% if @user.errors.count>0 %>

<%=t("madb_error_saving_user")%>

    <% done = [] %>
    <% @user.errors.each do |attr,e| %>
      <% next if done.include? e %>
      <% done.push e %>

<%= t(e) %>

    <% end %>

<%end%>

    <%= t("madb_login_email") %>:

    <%= text_field "user", "login", :size => 30 %>

<%if false %>
    <%= t("madb_email_confirmation") %>:

    <%= text_field "user", "login_confirmation", :size => 30 %>

<% end %>
    <%= t("madb_choose_password_creation") %>:

    <%= password_field "user", "password", :size => 30, :value => "" %>

    <%= t("madb_confirm_password_creation") %>:

    <%= password_field "user", "password_confirmation", :size => 30, :value => "" %>

    <input type="checkbox" name="tos_accepted" ><%= t("madb_tos_accepted")%>

      <%= submit_tag t("madb_signup") %>

<% end -%>


forgot this file for last commit (improving travel segment display text)

<%= @page_title %>

<%= render :partial => 'fix_include_profiles' %>
<%  i = 0
    @highlight_ts_ids = @travel_segments.to_a.collect{ |ts| ts.id }
%>
<% @travel_segments_hash.each_pair do |ts,p| %>

    <%= ts.long_desc %>
    <%- @highlight_ts_id = ts.id -%>

  <%= render :partial => 'itinerary_profiles', :object => p %>

<% end -%>

<%= @page_title %>

<%= render :partial => 'fix_include_profiles' %>
<%  i = 0
    @highlight_ts_ids = @travel_segments.to_a.collect{ |ts| ts.id }
%>
<% @travel_segments_hash.each_pair do |ts,p| %>

    <% if !@include_profiles %>
      <%= ts.long_desc %>
    <% else %>
      <%= ts.short_desc %>
      <% @highlight_ts_id = ts.id %>
    <% end %>

    <%= render :partial => 'itinerary_profiles', :object => p %>

<% end -%>


Fix bug introduced in commit 049198b

Fix bug introduced in commit 049198b

<%
    # Construct the main text of the mail
    main_text = ''
    for track_thing, alert_results, xapian_object in @email_about_things
        main_text += track_thing.params[:title_in_email] + "\n"
        main_text += ("=" * track_thing.params[:title_in_email].size) + "\n\n"
        @highlight_words = xapian_object.words_to_highlight
        for result in alert_results.reverse
            if result[:model].class.to_s == "InfoRequestEvent"
                event = result[:model]

                # Request title - only add title if we're not tracking a request.
                # e.g. -- Address and opening times of Post Office branches --
                if track_thing.info_request.nil?
                    main_text += "-- " + highlight_words(event.info_request.title, @highlight_words, false) + " --\n"
                end

                # e.g. Julian Burgess sent a request to Royal Mail Group (15 May 2008)
                if event.event_type == 'response'
                    url = main_url(incoming_message_url(event.incoming_message))
                    main_text += _("{{public_body}} sent a response to {{user_name}}", :public_body => event.info_request.public_body.name, :user_name => event.info_request.user_name)
                elsif event.event_type == 'followup_sent'
                    url = main_url(outgoing_message_url(event.outgoing_message))
                    main_text += _("{{user_name}} sent a follow up message to {{public_body}}", :user_name => event.info_request.user_name, :public_body => event.info_request.public_body.name)
                elsif event.event_type == 'sent'
                    # this is unlikely to happen in real life, but happens in the test code
                    url = main_url(outgoing_message_url(event.outgoing_message))
                    main_text += _("{{user_name}} sent a request to {{public_body}}", :user_name => event.info_request.user_name, :public_body => event.info_request.public_body.name)
                elsif event.event_type == 'comment'
                    url = main_url(comment_url(event.comment))
                    main_text += _("{{user_name}} added an annotation", :user_name => event.comment.user.name)
                else
                    raise "unknown type in event_digest " + event.event_type
                end
                main_text += " (" + simple_date(event.created_at) + ")\n"

                # Main text, wrapped, words highlighted with * and indented.
                if event.is_outgoing_message?
                    extract = highlight_and_excerpt(event.outgoing_message.get_text_for_indexing, @highlight_words, 150, false)
                elsif event.is_incoming_message?
                    extract = highlight_and_excerpt(event.incoming_message.get_text_for_indexing_clipped, @highlight_words, 150, false)
                elsif event.is_comment?
                    extract = highlight_and_excerpt(event.comment.body, @highlight_words, 150, false)
                else
                    extract = highlight_and_excerpt(info_request.initial_request_text, @highlight_words, 150, false)
                end
                extract = extract.gsub(/\s+/, ' ')
                main_text += MySociety::Format.wrap_email_body_by_lines('"' + extract + '"').gsub(/\n+$/, "") + "\n"

                # Link to the request/response
                main_text += url + "\n"
                main_text += "\n"
            else
                raise "need to add other types to TrackMailer.event_digest"
            end
        end
        main_text += "\n"
    end

%><%=main_text%><%= _("Alter your subscription")%>
=======================

<% _("Please click on the link below to cancel or alter these emails.") %>
<%=@unsubscribe_url%>

-- <%= _('the {{site_name}} team', :site_name=>site_name) %>

<%
    # Construct the main text of the mail
    main_text = ''
    for track_thing, alert_results, xapian_object in @email_about_things
        main_text += track_thing.params[:title_in_email] + "\n"
        main_text += ("=" * track_thing.params[:title_in_email].size) + "\n\n"
        @highlight_words = xapian_object.words_to_highlight
        for result in alert_results.reverse
            if result[:model].class.to_s == "InfoRequestEvent"
                event = result[:model]

                # Request title - only add title if we're not tracking a request.
                # e.g. -- Address and opening times of Post Office branches --
                if track_thing.info_request.nil?
                    main_text += "-- " + highlight_words(event.info_request.title, @highlight_words, false) + " --\n"
                end

                # e.g. Julian Burgess sent a request to Royal Mail Group (15 May 2008)
                if event.event_type == 'response'
                    url = main_url(incoming_message_url(event.incoming_message))
                    main_text += _("{{public_body}} sent a response to {{user_name}}", :public_body => event.info_request.public_body.name, :user_name => event.info_request.user_name)
                elsif event.event_type == 'followup_sent'
                    url = main_url(outgoing_message_url(event.outgoing_message))
                    main_text += _("{{user_name}} sent a follow up message to {{public_body}}", :user_name => event.info_request.user_name, :public_body => event.info_request.public_body.name)
                elsif event.event_type == 'sent'
                    # this is unlikely to happen in real life, but happens in the test code
                    url = main_url(outgoing_message_url(event.outgoing_message))
                    main_text += _("{{user_name}} sent a request to {{public_body}}", :user_name => event.info_request.user_name, :public_body => event.info_request.public_body.name)
                elsif event.event_type == 'comment'
                    url = main_url(comment_url(event.comment))
                    main_text += _("{{user_name}} added an annotation", :user_name => event.comment.user_name)
                else
                    raise "unknown type in event_digest " + event.event_type
                end
                main_text += " (" + simple_date(event.created_at) + ")\n"

                # Main text, wrapped, words highlighted with * and indented.
                if event.is_outgoing_message?
                    extract = highlight_and_excerpt(event.outgoing_message.get_text_for_indexing, @highlight_words, 150, false)
                elsif event.is_incoming_message?
                    extract = highlight_and_excerpt(event.incoming_message.get_text_for_indexing_clipped, @highlight_words, 150, false)
                elsif event.is_comment?
                    extract = highlight_and_excerpt(event.comment.body, @highlight_words, 150, false)
                else
                    extract = highlight_and_excerpt(info_request.initial_request_text, @highlight_words, 150, false)
                end
                extract = extract.gsub(/\s+/, ' ')
                main_text += MySociety::Format.wrap_email_body_by_lines('"' + extract + '"').gsub(/\n+$/, "") + "\n"

                # Link to the request/response
                main_text += url + "\n"
                main_text += "\n"
            else
                raise "need to add other types to TrackMailer.event_digest"
            end
        end
        main_text += "\n"
    end

%><%=main_text%><%= _("Alter your subscription")%>
=======================

<% _("Please click on the link below to cancel or alter these emails.") %>
<%=@unsubscribe_url%>

-- <%= _('the {{site_name}} team', :site_name=>site_name) %>


Changed TZInfo::TimeZone.all to ActiveSupport::Timezone.all =>  all tests and specs pass - but still need to fix routing errors when running application

<% content_for :action_nav do %>

<%= link_to "General", '#general' %>

<%= link_to "Spam Prevention", '#spam' %>

<%= link_to "Comments", '#spam' %>

<%= link_to "Publishing", '#publish' %>

    <% if ActionController::Base.perform_caching -%>

<%= link_to 'Caches', :controller => '/admin/cached_pages' %>

    <% end -%>

<% end %>

<% form_for :site, :url => { :action => "update" } do |f| %>

General site settings

Website title

<%= f.text_field :title %>

Website subtitle

<%= f.text_field :subtitle %>

      Administrator email
      Shown in emails sent from your site

<%= f.text_field :email %>

Website Timezone

<%= select_tag 'site_timezone', options_for_select(['UTC'] + ActiveSupport::TimeZone.all.map{|tz| [tz.to_s, tz.name]}.sort, @site.timezone.name), :name => 'site[timezone]' %>

      Site language
      Used to specify language in your site feeds

<%= f.text_field :lang %>

      Current Theme Path
      This is the path to the current template in /themes/site-<%= site.id %>.  Be careful with this setting!

      <%= f.text_field :current_theme_path %>
    <% unless site.theme.name == site.current_theme_path -%>
      This setting is incorrect, set it to a valid theme path.
    <% end -%>

Spam prevention

At the moment Mephisto uses <%= link_to 'Akismet', 'http://akismet.com' %> to automatically handle spam.  If you leave out the Akismet settings, you can moderate new comments from the Overview.

Akismet API Key

<%= f.text_field :akismet_key %>

Blog url

<%= f.text_field :akismet_url %>

Comments

<%= f.select :comment_age, comment_expiration_options %>

      <%= f.check_box 'approve_comments' %> Approve and publish all comments automatically.

Publishing and Reading

      Comments filter

When comments are posted, they use this markup

      <select name="site[filter]">
        <%= options_for_select(filter_options, site.filter) %>
      </select>

      Articles per page

Default article limit for search/tag pages.

<%= f.text_field :articles_per_page, :class => 'tiny' %>

      Search area url

<%= f.text_field :search_path %>

      Tag area url

<%= f.text_field :tag_path %>

    <% if @layouts.any? -%>

      Tag area layout

      <select name="site[tag_layout]">
        <%= options_from_templates_for_select(@layouts, @site.tag_layout) %>
      </select>

    <% end -%>

      Article url style

Use the :year, :month, :day, :permalink, and :id in place of actual article values.

<%= f.text_field :permalink_style %>

<%= submit_tag 'Save and apply settings' %>

<% end %>

<% content_for :action_nav do %>

<%= link_to "General", '#general' %>

<%= link_to "Spam Prevention", '#spam' %>

<%= link_to "Comments", '#spam' %>

<%= link_to "Publishing", '#publish' %>

    <% if ActionController::Base.perform_caching -%>

<%= link_to 'Caches', :controller => '/admin/cached_pages' %>

    <% end -%>

<% end %>

<% form_for :site, :url => { :action => "update" } do |f| %>

General site settings

Website title

<%= f.text_field :title %>

Website subtitle

<%= f.text_field :subtitle %>

      Administrator email
      Shown in emails sent from your site

<%= f.text_field :email %>

Website Timezone

<%= select_tag 'site_timezone', options_for_select(['UTC'] + TZInfo::Timezone.all.map{|tz| [tz.to_s, tz.name]}.sort, @site.timezone.name), :name => 'site[timezone]' %>

      Site language
      Used to specify language in your site feeds

<%= f.text_field :lang %>

      Current Theme Path
      This is the path to the current template in /themes/site-<%= site.id %>.  Be careful with this setting!

      <%= f.text_field :current_theme_path %>
    <% unless site.theme.name == site.current_theme_path -%>
      This setting is incorrect, set it to a valid theme path.
    <% end -%>

Spam prevention

At the moment Mephisto uses <%= link_to 'Akismet', 'http://akismet.com' %> to automatically handle spam.  If you leave out the Akismet settings, you can moderate new comments from the Overview.

Akismet API Key

<%= f.text_field :akismet_key %>

Blog url

<%= f.text_field :akismet_url %>

Comments

<%= f.select :comment_age, comment_expiration_options %>

      <%= f.check_box 'approve_comments' %> Approve and publish all comments automatically.

Publishing and Reading

      Comments filter

When comments are posted, they use this markup

      <select name="site[filter]">
        <%= options_for_select(filter_options, site.filter) %>
      </select>

      Articles per page

Default article limit for search/tag pages.

<%= f.text_field :articles_per_page, :class => 'tiny' %>

      Search area url

<%= f.text_field :search_path %>

      Tag area url

<%= f.text_field :tag_path %>

    <% if @layouts.any? -%>

      Tag area layout

      <select name="site[tag_layout]">
        <%= options_from_templates_for_select(@layouts, @site.tag_layout) %>
      </select>

    <% end -%>

      Article url style

Use the :year, :month, :day, :permalink, and :id in place of actual article values.

<%= f.text_field :permalink_style %>

<%= submit_tag 'Save and apply settings' %>

<% end %>


Move closing bracket to end of string, only want to translate text.

<%=_('Show only...')%>

<%=_('Beginning with') %>

        <%= render :partial => 'alphabet' %>

    <% first_row = true %>
    <% for row in PublicBodyCategories::get().with_headings() %>
        <% if row.instance_of?(Array) %>

            <%= link_to_unless (@tag == row[0]), row[1], list_public_bodies_url(:tag => row[0]) %>

        <% else %>
            <% if not first_row %>

            <% else %>
                <% first_row = false %>
            <% end %>

<%=h row%>

        <% end %>
    <% end %>
    <% if not first_row %>

    <% end %>
    <%= render :partial => "list_sidebar_extra" %>

<% @title = @description.empty? ? _("Public authorities") : _("Public authorities - {{description}}", :description => @description) %>

<%= _('Public authorities') %>

<% form_tag(list_public_bodies_default_url, :method => "get", :id=>"search_form") do %>

  <%= text_field_tag(:public_body_query, params[:public_body_query]) %>
  <%= submit_tag(_("Search")) %>

<% end %>

<%= n_('Found %d public authority %s', 'Found %d public authorities %s', @public_bodies.total_entries) % [@public_bodies.total_entries, @description] %>

<%= render :partial => 'body_listing', :locals => { :public_bodies => @public_bodies } %>

  <%= will_paginate(@public_bodies) %>

  <%= link_to _("Can't find the one you want?"), help_requesting_path + '#missing_body' %>

<%=_('Show only...')%>

<%=_('Beginning with') %>

        <%= render :partial => 'alphabet' %>

    <% first_row = true %>
    <% for row in PublicBodyCategories::get().with_headings() %>
        <% if row.instance_of?(Array) %>

            <%= link_to_unless (@tag == row[0]), row[1], list_public_bodies_url(:tag => row[0]) %>

        <% else %>
            <% if not first_row %>

            <% else %>
                <% first_row = false %>
            <% end %>

<%=h row%>

        <% end %>
    <% end %>
    <% if not first_row %>

    <% end %>
    <%= render :partial => "list_sidebar_extra" %>

<% @title = @description.empty? ? _("Public authorities") : _("Public authorities - {{description}}", :description => @description) %>

<%= _('Public authorities') %>

<% form_tag(list_public_bodies_default_url, :method => "get", :id=>"search_form") do %>

  <%= text_field_tag(:public_body_query, params[:public_body_query]) %>
  <%= submit_tag(_("Search")) %>

<% end %>

<%= n_('Found %d public authority %s', 'Found %d public authorities %s', @public_bodies.total_entries) % [@public_bodies.total_entries, @description] %>

<%= render :partial => 'body_listing', :locals => { :public_bodies => @public_bodies } %>

  <%= will_paginate(@public_bodies) %>

  <%= link_to _("Can't find the one you want?", help_requesting_path + '#missing_body') %>


Changed the drop down box for 'reminder hrs.' to contain values '[8, 8],[16, 16],[24, 24],[32, 32],[40, 40],[48, 48],[56, 56],[64, 64],[72, 72],[80, 80],[88, 88],[96, 96]'

git-svn-id: f67d969b640da65cb7bc1d229e09fd6d2db44ae1@722 392d7b7b-3f31-0410-9dc3-c95a9635ea79

Editing assignment

<%= start_form_tag({:action => 'update', :id => @assignment, :review_limit => @limits[:review], :metareview_limit => @limits[:metareview], :teammate_limit => @limits[:teammate], :feedback_limit => @limits[:feedback]},:onsubmit => 'return checkForm();') %>
  <%= render :partial => 'content' %>

  <%= render :partial => 'rubrics' %>

Deadlines for chapter 1

        Deadline type
        Date & time
        Submission allowed
        Review allowed
        Resubmission allowed
        Re-review allowed
        Review of review allowed
		Reminder (hrs)

  <% 	i = 0;
        duedates = @assignment.due_dates
        duedates.sort! {|a,b| a.due_at <=> b.due_at}

		for @due_date in duedates

		      if  @due_date.deadline_type_id == 1
		         heading = "Submission deadline"
		      end
		      if  @due_date.deadline_type_id == 2
		         heading = "Review deadline"
		      end
		      if  @due_date.deadline_type_id == 3
		         heading = "Resubmission deadline"
		      end
		      if  @due_date.deadline_type_id == 4
		         heading = "Re-review deadline"
		      end
		      if  @due_date.deadline_type_id == 5
		         heading = "Review of review deadline"
		      end

		 %>

		<%= heading%>
		<%= text_field 'due_date[]', 'due_at', :size=>30%>
		<%= select('due_date[]', 'submission_allowed_id', [ ['No', 1],['Late', 2],['OK', 3]])%>
		<%= select('due_date[]', 'review_allowed_id', [ ['No', 1],['Late', 2],['OK', 3]])%>
		<%= select('due_date[]', 'resubmission_allowed_id', [ ['No', 1],['Late', 2],['OK', 3]])%>
		<%= select('due_date[]', 'rereview_allowed_id', [ ['No', 1],['Late', 2],['OK', 3]])%>
		<%= select('due_date[]', 'review_of_review_allowed_id', [ ['No', 1],['Late', 2],['OK', 3]])%>
		<%= select('due_date[]', 'threshold', [ [8, 8],[16, 16],[24, 24],[32, 32],[40, 40],[48, 48],[56, 56],[64, 64],[72, 72],[80, 80],[88, 88],[96, 96]])%>
		<%= hidden_field('due_date[]', 'flag', 'value' => 0)%>

	<% 	i += 1;
		end %>

  Number of {weeks, days} between submission of successive chapters:
  <input type="text" id="weeks" name ="weeks" maxlength="2" size="3" value="<%=@weeks%>"/> week(s)
  <input type="text" id="days" name ="days" maxLength="2" size="3" value="<%=@days%>"/> day(s)

    <%= submit_tag "Save assignment" %>
<%= end_form_tag %>

<%= render :partial => '/shared_scripts/back' %>

Editing assignment

<%= start_form_tag({:action => 'update', :id => @assignment, :review_limit => @limits[:review], :metareview_limit => @limits[:metareview], :teammate_limit => @limits[:teammate], :feedback_limit => @limits[:feedback]},:onsubmit => 'return checkForm();') %>
  <%= render :partial => 'content' %>

  <%= render :partial => 'rubrics' %>

Deadlines for chapter 1

        Deadline type
        Date & time
        Submission allowed
        Review allowed
        Resubmission allowed
        Re-review allowed
        Review of review allowed
		Reminder (hrs)

  <% 	i = 0;
        duedates = @assignment.due_dates
        duedates.sort! {|a,b| a.due_at <=> b.due_at}

		for @due_date in duedates

		      if  @due_date.deadline_type_id == 1
		         heading = "Submission deadline"
		      end
		      if  @due_date.deadline_type_id == 2
		         heading = "Review deadline"
		      end
		      if  @due_date.deadline_type_id == 3
		         heading = "Resubmission deadline"
		      end
		      if  @due_date.deadline_type_id == 4
		         heading = "Re-review deadline"
		      end
		      if  @due_date.deadline_type_id == 5
		         heading = "Review of review deadline"
		      end

		 %>

		<%= heading%>
		<%= text_field 'due_date[]', 'due_at', :size=>30%>
		<%= select('due_date[]', 'submission_allowed_id', [ ['No', 1],['Late', 2],['OK', 3]])%>
		<%= select('due_date[]', 'review_allowed_id', [ ['No', 1],['Late', 2],['OK', 3]])%>
		<%= select('due_date[]', 'resubmission_allowed_id', [ ['No', 1],['Late', 2],['OK', 3]])%>
		<%= select('due_date[]', 'rereview_allowed_id', [ ['No', 1],['Late', 2],['OK', 3]])%>
		<%= select('due_date[]', 'review_of_review_allowed_id', [ ['No', 1],['Late', 2],['OK', 3]])%>
		<%= select('due_date[]', 'threshold', [ [1, 1],[2, 2],[3, 3],[4, 4],[5, 5],[6, 6],[7, 7],[8, 8],[9, 9],[10, 10],[11, 11],[12, 12]])%>
		<%= hidden_field('due_date[]', 'flag', 'value' => 0)%>

	<% 	i += 1;
		end %>

  Number of {weeks, days} between submission of successive chapters:
  <input type="text" id="weeks" name ="weeks" maxlength="2" size="3" value="<%=@weeks%>"/> week(s)
  <input type="text" id="days" name ="days" maxLength="2" size="3" value="<%=@days%>"/> day(s)

    <%= submit_tag "Save assignment" %>
<%= end_form_tag %>

<%= render :partial => '/shared_scripts/back' %>


class not style

class not style

git-svn-id: 63e5431e33a10c4701b329fb6d8e0744110cb91e@148 c2b4ead4-481d-0410-ac63-b02590f85e3f

News Articles

Title
Versions
Source

<% @articles.each do |article| %>

<% if article.versions_count > 1 %>
<%= link_to h(truncate(article.latest_title,75)), { :action => :diff, :id => article.id,
  :version_a => article.versions_count - 1,
  :version_b => article.versions_count - 2 }, :title => "#{h(article.latest_title)}, first published #{article.created_at}" %>
<% else %>
<span title="<%= "#{h(article.latest_title)}, first published #{article.created_at}" %>"><%= h(truncate(article.latest_title,75)) %>
<% end %>
<%= article.versions_count %>
<%= article.source %>

<% end %>

<%= render :partial => 'partials/paginator', :locals => { :paginator => @articles_pages } %>


Modified _selectTable code

Modified _selectTable code

git-svn-id: f67d969b640da65cb7bc1d229e09fd6d2db44ae1@243 392d7b7b-3f31-0410-9dc3-c95a9635ea79

<% if elements.length > 0 %>
<form id="tableForm" name="tableForm" method="post">

    <% for definition in column_definitions %>
	   <%= definition[:name] %>
    <% end %>

  <% for element in elements %>

        <input id="item" name="item[<%= element.id %>]" type="checkbox" value="<%= element.id %>" />

	 <% for definition in column_definitions %>

     <% if definition[:type] == "display" %>
       <%= element[definition[:field].to_sym] %>
     <% elsif definition[:type] == "fetch" %>
       <%= element.get_field(definition[:field]) %>
     <% else %>
         <%
            disabled = false
            if definition[:disabled] != nil
              disabled = element[definition[:disabled].to_sym]
            end
         %>
         <input id="<%= definition[:action] %>"
                name="<%= definition[:action] %>"
                value="<%= definition[:name] %>" type="radio"
                onClick="submitAction('tableForm', '<%= url_for(:controller => definition[:controller], :action => definition[:action], :id => element.id,:edit => nil, :list => nil) %>');"/>
       	 <% if definition[:hidden] %>
       	 <%= hidden_field_tag(definition[:hidden][:name], definition[:hidden][:id]) %>
       	 <% end %>
     <% end %>

     <% end %>

  <% end %>

Check All | Uncheck All

With selected: <a href="" onClick="submitAction('tableForm','<%= url_for(:controller => definition[:controller], :action => 'delete_selected', :edit => nil, :list => nil) %>')">Delete
<%= end_form_tag %>
<% end %>

<% if elements.length > 0 %>

<% for definition in column_definitions %>
	<%= definition[:name] %>
<% end %>

<% for element in elements %>

  <% for definition in column_definitions %>

     <% if definition[:type] == "display" %>
       <%= element[definition[:field].to_sym] %>
     <% elsif definition[:type] == "fetch" %>
       <%= element.get_field(definition[:field]) %>
     <% else %>
       <%= start_form_tag ({:controller => definition[:controller], :action => definition[:action]}, {:method => 'post'} ) %>
         <%
            disabled = false
            if definition[:disabled] != nil
              disabled = element[definition[:disabled].to_sym]
            end
         %>
       	 <%= radio_button_tag definition[:action], definition[:name], false, :onClick => 'this.checked = false;submit();' %>
       	 <% if definition[:hidden] %>
       	    <%= hidden_field_tag(definition[:hidden][:name], definition[:hidden][:id]) %>
       	 <% end %>
       	 <%= hidden_field_tag ('id', element.id) %>
       <%= end_form_tag %>
     <% end %>

  <% end %>

<% end %>

<% end %>


Always link to the latest version of the FOI act

<% @title = "About" %>

<%= render :partial => 'sidebar' %>

Introduction to <%= site_name %>

What is  <%= site_name %> for?

How does the site work?

Why would I bother to do this?

Why would the public authority bother to reply?

Who makes <%= site_name %>?

How can I keep up with news about <%= site_name %>?

What is  <%= site_name %> for? #

To help you find out inside information about what the Australian government
  is doing.

How does the site work? #

You choose the public authority that you would like information from, then
  write a brief note describing what you want to know. We then send your request
  to the public authority. Any response is automatically published on the
  website for you and anyone else to find and read.

Why would I bother to do this? #

You pay taxes, and then government does things with the money. All sorts of
  things that affect your life, from healthcare through to national defence. Some
  it does badly, some it does well. The more we find out about how government
  works, the better able we are to make suggestions to improve the things that
  are done badly, and to celebrate the things that are done well.

Why would the public authority bother to reply? #

Under the Freedom of Information Act 1982, or FOI for short, all public authorities have to respond. The response
  will either contain the information you want, or give a valid legal reason why
  it must be kept confidential.

Who makes <%= site_name %>? #

<%= site_name %> is a project of the OpenAustralia Foundation, a charity, and was developed with software by the UK organisation mySociety. It was made possible by a donation from Guy King. If you like what we're doing, then you can make a donation.

How can I keep up with news about <%= site_name %>? #

We have a blog and a twitter feed.

Next, read about making requests -->


Rename "There are ### entries in the page cache" to remove the word "page"

git-svn-id: 70ab0960c3db1cbf656efd6df54a8f3de72dc710@860 820eb932-12ee-0310-9ca8-eeb645f39767

<% @page_heading = 'Blog settings' %>

  <%= start_form_tag :action => 'update'%>

Which settings group would you like to edit?

General Settings

Text Filter

Spam Protection

Resource Defaults

Cache

General Settings

      Blog name:
      <input name="setting[blog_name]" id="blog_name" type="text" value="<%=h config_value(:blog_name) %>" />

      Blog subtitle:
      <input name="setting[blog_subtitle]" id="blog_subtitle" type="text" value="<%=h config_value(:blog_subtitle) %>" />

      <input name="setting[default_allow_comments]" id="default_allow_comments" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:default_allow_comments)%> />
      <input name="setting[default_allow_comments]" type="hidden" value="0"/>
        Enable comments by default

      <input name="setting[default_allow_pings]" id="default_allow_pings" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:default_allow_pings)%> />
      <input name="setting[default_allow_pings]" type="hidden" value="0"/>
        Enable Trackbacks by default

      Display
      <input name="setting[limit_article_display]" size="4" id="limit_article_display" type="text" value="<%= config_value(:limit_article_display) %>" /> articles on my homepage by default.

      Display
      <input name="setting[limit_rss_display]" size="4" id="limit_rss_display" type="text" value="<%= config_value(:limit_rss_display) %>" /> articles in my rss feed by default.

      <input name="setting[show_extended_on_rss]" id="show_extended_on_rss" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:show_extended_on_rss)%> />
      <input name="setting[show_extended_on_rss]" type="hidden" value="0"/>
        Show full article on rss feed

Should the blog show mailto: links to your email address?

<input name="setting[link_to_author]" id="link_to_author" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:link_to_author)%> /><input name="setting[link_to_author]" type="hidden" value="0"/> Enable E-Mail public display

Should the blog use of the Globally Recognized Avatar (Gravatar) service in comments?

      <input name="setting[use_gravatar]" id="use_gravatar" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:use_gravatar) %> />
      <input name="setting[use_gravatar]" type="hidden" value="0"/>
      Enable Gravatar integration

Would you like to include your latitude and longitude in your blog's HTML pages? See GeoURL for details.
Example: <tt>47.774,-122.201</tt>

      Latitude, Longitude:
      <input name="setting[geourl_location]" size="20" id="geourl_location" type="text" value="<%= config_value(:geourl_location) %>" />

Should Typo send trackbacks to websites that you link to?  This should be disabled
       for private blogs, as it will leak non-public information to sites that you're discussing.
       For public blogs, there's no real point in disabling this.

      <input name="setting[send_outbound_pings]" id="send_outbound_pings" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:send_outbound_pings)%> />
         <input name="setting[send_outbound_pings]" type="hidden" value="0"/>
           Send trackbacks to external sites

      URLs to ping automatically:

      <textarea name="setting[ping_urls]" id="ping_urls" rows="5" cols="50"><%=h config[:ping_urls] %></textarea>

<%= save("Save My Settings") %>

Text Filter

Typo supports a number of text filtering options.  To add new filters, see the "filters" tab on the toolbar above.

        <select name="setting[text_filter]" id="text_filter">
          <%= options_for_select text_filter_options, TextFilter.find_by_name(config_value(:text_filter)) %>
        </select>
        Article filter

        <select name="setting[comment_text_filter]" id="comment_text_filter">
        <%= options_for_select text_filter_options, TextFilter.find_by_name(config_value(:comment_text_filter)) %>
        </select>
        Comments filter

<%= save("Save My Settings") %>

Notification

Typo can notify you when new articles or comments are posted

      Email address to use in From: field when Typo sends mail:
      <input name="setting[email_from]" size="20" id="email_from" type="text" value="<%= config_value(:email_from) %>" />

      Jabber account to use when sending Jabber notifications:
      <input name="setting[jabber_address]" size="20" id="jabber_address" type="text" value="<%= config_value(:jabber_address) %>" />

      Password for Jabber account:
      <input name="setting[jabber_password]" size="20" id="jabber_password" type="password" value="<%= config_value(:jabber_password) %>" />

<%= save("Save My Settings") %>

Spam Protection

Enabling spam protection will make typo compare the IP address of posters as well as the contents of their posts against local and remote blacklists. Good defense against spam bots.

          <input name="setting[sp_global]" id="sp_global" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:sp_global)%> /><input name="setting[sp_global]" type="hidden" value="0"/>
          Enable spam protection

          <input name="setting[sp_allow_non_ajax_comments]" id="sp_allow_non_ajax_comments" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:sp_allow_non_ajax_comments)%> />
          <input name="setting[sp_allow_non_ajax_comments]" type="hidden" value="0" />
          Allow non-ajax comments

(Spam bots usually don't know anything about ajax comments)

          Disable comments after
          <input name="setting[sp_article_auto_close]" size="4" id="sp_article_auto_close" type="text" value="<%= config_value(:sp_article_auto_close) %>" /> days

(Set to 0 to never disable comments)

Typo will automatically reject comments and trackbacks which contain over a certain amount of links in them.

          Max URLs:
          <input name="setting[sp_url_limit]" size="4" id="sp_url_limit" type="text" value="<%= config_value(:sp_url_limit) %>" /> links

(Set to 0 to never reject comments)

<%= save("Save My Settings") %>

Resource Defaults

          The below settings act as defaults when you choose to publish an enclosure with iTunes metadata.

          Author:
          <input name="setting[itunes_author]" size="25" id="itunes_author" type="text" value="<%= config_value(:itunes_author) %>" />

          Subtitle:
          <input name="setting[itunes_subtitle]" size="25" id="itunes_subtitle" type="text" value="<%= config_value(:itunes_subtitle) %>" />(setting for channel)

        Summary:(setting for channel)

          <textarea name="setting[itunes_summary]" cols="40" rows="3"><%= config_value(:itunes_summary) %></textarea>

          Email:
          <input name="setting[itunes_email]" size="25" id="itunes_email" type="text" value="<%= config_value(:itunes_email) %>" />  Not Published by Apple

          Optional Name:
          <input name="setting[itunes_name]" size="25" id="itunes_name" type="text" value="<%= config_value(:itunes_name) %>" />  Not Published by Apple

          Copyright Information:
          <input name="setting[itunes_copyright]" size="25" id="itunes_copyright" type="text" value="<%= config_value(:itunes_copyright) %>" />

          Explicit:
          <input name="setting[itunes_explicit]" id="itunes_explicit" type="checkbox"  value="1" <%= 'checked="checked"' if config_value(:itunes_explicit)%> /><input name="setting[itunes_explicit]" type="hidden" value="0" />

<%= save("Save My Settings") %>

Cache

   <%= link_to 'Empty Fragment Cache', :controller => 'cache', :action => 'sweep' %>

   <%= link_to 'Rebuild cached HTML', :controller => 'cache', :action => 'sweep_html' %>

There are <%= @page_cache_size %> entries in the cache

    <%= save("Save My Settings") %>

  <%= end_form_tag %>

<% @page_heading = 'Blog settings' %>

  <%= start_form_tag :action => 'update'%>

Which settings group would you like to edit?

General Settings

Text Filter

Spam Protection

Resource Defaults

Cache

General Settings

      Blog name:
      <input name="setting[blog_name]" id="blog_name" type="text" value="<%=h config_value(:blog_name) %>" />

      Blog subtitle:
      <input name="setting[blog_subtitle]" id="blog_subtitle" type="text" value="<%=h config_value(:blog_subtitle) %>" />

      <input name="setting[default_allow_comments]" id="default_allow_comments" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:default_allow_comments)%> />
      <input name="setting[default_allow_comments]" type="hidden" value="0"/>
        Enable comments by default

      <input name="setting[default_allow_pings]" id="default_allow_pings" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:default_allow_pings)%> />
      <input name="setting[default_allow_pings]" type="hidden" value="0"/>
        Enable Trackbacks by default

      Display
      <input name="setting[limit_article_display]" size="4" id="limit_article_display" type="text" value="<%= config_value(:limit_article_display) %>" /> articles on my homepage by default.

      Display
      <input name="setting[limit_rss_display]" size="4" id="limit_rss_display" type="text" value="<%= config_value(:limit_rss_display) %>" /> articles in my rss feed by default.

      <input name="setting[show_extended_on_rss]" id="show_extended_on_rss" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:show_extended_on_rss)%> />
      <input name="setting[show_extended_on_rss]" type="hidden" value="0"/>
        Show full article on rss feed

Should the blog show mailto: links to your email address?

<input name="setting[link_to_author]" id="link_to_author" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:link_to_author)%> /><input name="setting[link_to_author]" type="hidden" value="0"/> Enable E-Mail public display

Should the blog use of the Globally Recognized Avatar (Gravatar) service in comments?

      <input name="setting[use_gravatar]" id="use_gravatar" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:use_gravatar) %> />
      <input name="setting[use_gravatar]" type="hidden" value="0"/>
      Enable Gravatar integration

Would you like to include your latitude and longitude in your blog's HTML pages? See GeoURL for details.
Example: <tt>47.774,-122.201</tt>

      Latitude, Longitude:
      <input name="setting[geourl_location]" size="20" id="geourl_location" type="text" value="<%= config_value(:geourl_location) %>" />

Should Typo send trackbacks to websites that you link to?  This should be disabled
       for private blogs, as it will leak non-public information to sites that you're discussing.
       For public blogs, there's no real point in disabling this.

      <input name="setting[send_outbound_pings]" id="send_outbound_pings" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:send_outbound_pings)%> />
         <input name="setting[send_outbound_pings]" type="hidden" value="0"/>
           Send trackbacks to external sites

      URLs to ping automatically:

      <textarea name="setting[ping_urls]" id="ping_urls" rows="5" cols="50"><%=h config[:ping_urls] %></textarea>

<%= save("Save My Settings") %>

Text Filter

Typo supports a number of text filtering options.  To add new filters, see the "filters" tab on the toolbar above.

        <select name="setting[text_filter]" id="text_filter">
          <%= options_for_select text_filter_options, TextFilter.find_by_name(config_value(:text_filter)) %>
        </select>
        Article filter

        <select name="setting[comment_text_filter]" id="comment_text_filter">
        <%= options_for_select text_filter_options, TextFilter.find_by_name(config_value(:comment_text_filter)) %>
        </select>
        Comments filter

<%= save("Save My Settings") %>

Notification

Typo can notify you when new articles or comments are posted

      Email address to use in From: field when Typo sends mail:
      <input name="setting[email_from]" size="20" id="email_from" type="text" value="<%= config_value(:email_from) %>" />

      Jabber account to use when sending Jabber notifications:
      <input name="setting[jabber_address]" size="20" id="jabber_address" type="text" value="<%= config_value(:jabber_address) %>" />

      Password for Jabber account:
      <input name="setting[jabber_password]" size="20" id="jabber_password" type="password" value="<%= config_value(:jabber_password) %>" />

<%= save("Save My Settings") %>

Spam Protection

Enabling spam protection will make typo compare the IP address of posters as well as the contents of their posts against local and remote blacklists. Good defense against spam bots.

          <input name="setting[sp_global]" id="sp_global" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:sp_global)%> /><input name="setting[sp_global]" type="hidden" value="0"/>
          Enable spam protection

          <input name="setting[sp_allow_non_ajax_comments]" id="sp_allow_non_ajax_comments" type="checkbox" value="1" <%= 'checked="checked"' if config_value(:sp_allow_non_ajax_comments)%> />
          <input name="setting[sp_allow_non_ajax_comments]" type="hidden" value="0" />
          Allow non-ajax comments

(Spam bots usually don't know anything about ajax comments)

          Disable comments after
          <input name="setting[sp_article_auto_close]" size="4" id="sp_article_auto_close" type="text" value="<%= config_value(:sp_article_auto_close) %>" /> days

(Set to 0 to never disable comments)

Typo will automatically reject comments and trackbacks which contain over a certain amount of links in them.

          Max URLs:
          <input name="setting[sp_url_limit]" size="4" id="sp_url_limit" type="text" value="<%= config_value(:sp_url_limit) %>" /> links

(Set to 0 to never reject comments)

<%= save("Save My Settings") %>

Resource Defaults

          The below settings act as defaults when you choose to publish an enclosure with iTunes metadata.

          Author:
          <input name="setting[itunes_author]" size="25" id="itunes_author" type="text" value="<%= config_value(:itunes_author) %>" />

          Subtitle:
          <input name="setting[itunes_subtitle]" size="25" id="itunes_subtitle" type="text" value="<%= config_value(:itunes_subtitle) %>" />(setting for channel)

        Summary:(setting for channel)

          <textarea name="setting[itunes_summary]" cols="40" rows="3"><%= config_value(:itunes_summary) %></textarea>

          Email:
          <input name="setting[itunes_email]" size="25" id="itunes_email" type="text" value="<%= config_value(:itunes_email) %>" />  Not Published by Apple

          Optional Name:
          <input name="setting[itunes_name]" size="25" id="itunes_name" type="text" value="<%= config_value(:itunes_name) %>" />  Not Published by Apple

          Copyright Information:
          <input name="setting[itunes_copyright]" size="25" id="itunes_copyright" type="text" value="<%= config_value(:itunes_copyright) %>" />

          Explicit:
          <input name="setting[itunes_explicit]" id="itunes_explicit" type="checkbox"  value="1" <%= 'checked="checked"' if config_value(:itunes_explicit)%> /><input name="setting[itunes_explicit]" type="hidden" value="0" />

<%= save("Save My Settings") %>

Cache

   <%= link_to 'Empty Fragment Cache', :controller => 'cache', :action => 'sweep' %>

   <%= link_to 'Rebuild cached HTML', :controller => 'cache', :action => 'sweep_html' %>

There are <%= @page_cache_size %> entries in the page cache

    <%= save("Save My Settings") %>

  <%= end_form_tag %>