{"id":15938,"date":"2021-03-19T09:10:34","date_gmt":"2021-03-19T13:10:34","guid":{"rendered":"https:\/\/carleton.ca\/webservices\/?p=15938"},"modified":"2026-03-24T13:32:04","modified_gmt":"2026-03-24T17:32:04","slug":"when-to-delete-a-form","status":"publish","type":"post","link":"https:\/\/carleton.ca\/webservices\/2021\/when-to-delete-a-form\/","title":{"rendered":"When to delete a form"},"content":{"rendered":"\n
\n
\n\n
\n
\n
\n

\n When to delete a form\n <\/h1>\n \n \n <\/header>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n<\/section>\n\n\n\n

In our latest Pulitzer-prize winning article, we outlined the need to add CAPTCHA fields to your forms<\/a> as soon as possible. We mentioned how to request that CAPTCHA be switched on for your website, and how to add CAPTCHA to your forms.<\/p>\n\n\n\n

When it comes to adding the CAPTCHA field to your forms, the number one consideration for how long this will take is how many forms on your site are in use and how many aren’t. Some sites have 250 forms. Some have one. (Pro-tip: by having only one you are very very lucky.)<\/p>\n\n\n\n

If you eliminate a lot of these forms before<\/em> adding CAPTCHA to them, you will save a lot of needless clicks. You don’t have to delete any forms – you can switch them off (we’ll show you how below) so if it turns out there was a form your department really needed then you can switch it back on. (And by turning the form off you are preserving all the entries that have previously been submitted to that form.)<\/p>\n\n\n\n

How can you tell which forms are in use?<\/h2>\n\n\n\n

Corporate memory<\/h3>\n\n\n\n

This is the best way by far: do you or your colleagues remember building this particular form? If so, was it in 2012 for a specific occasion? If that is the case maybe it can be deleted or switched off. Ask around, especially if you are in a big department!<\/p>\n\n\n\n

Clues in the naming<\/h3>\n\n\n\n

Remember that event we all worked on in 2013? No, me neither. It is, however, memorialized in the name of that form (My Event Registration 2013)<\/strong>. That is a big clue. Some forms are used seasonally every year so be certain to not delete that. But the big clue is the date – most forms used annually either have the latest date (My Event Registration 2021) <\/strong>or no date at all (My Event<\/strong>). Similarly, if you have a form from two years called Department’s 60th Anniversary Dinner <\/strong>it can probably go.<\/p>\n\n\n\n

Testing Testing<\/h3>\n\n\n\n

Speaking of naming, if you look through the list of forms on your site in the back end (by clicking on Forms<\/strong> on the left-hand navigation menu) you might see forms called, for example, Test form, Test, Test 1, Test 2, Test(1), Test_new, <\/strong>etc. (All these examples are sadly from the Web Services website!) Guess what? They can probably go. Check with your colleagues and then switch them off or delete them. (It’s no excuse but the reason we had 22<\/strong> test forms in the back end of the Web Services site is that we do a lot of work on forms and have<\/em> to test them somewhere!)<\/p>\n\n\n\n

Look at your site<\/h3>\n\n\n\n

If you have a relatively small website then the quickest way to discern if a form is in use is the see it on a page in the front end. Theoretically (looks accusingly over his reading glasses at the crowd) all your pages should be live and visible so take a look at each and note the ones with forms on.<\/p>\n\n\n\n

Cobwebs?<\/h3>\n\n\n\n

Are some forms simply gathering dust? Look again at the list of forms in the back end of your website. There is a column marked Entries<\/strong>. If a form is from more than the most recent months and it has just a few entries, then it is a good candidate to be switched off. If it one of the earlier forms built on your site (look at the ID<\/strong> column to discern this: lower the number = the older the form) then click on Entries <\/strong>to see when the last entry was received. If it was 2010 then that form can probably go.<\/p>\n\n\n\n

\"A<\/figure>\n\n\n\n
\"As<\/figure>\n\n\n\n
\"A<\/figure>\n\n\n\n
\"As<\/figure>\n\n\n\n

What to do with old forms<\/h2>\n\n\n\n

Once you have identified which forms are no longer needed, you have to decide what to do with them. You have two choices: delete them or switch them off. (If you thought there was a third choice: Keep the form then you are wrong – that is NOT an option!)<\/p>\n\n\n\n

Switching off<\/h3>\n\n\n\n

The main advantage of switching off a form rather than deleting it is that if for some reason a colleague was keeping for that form for re-use in the near future then you haven’t forced them to reinvent the wheel next time they need it. Additionally, if you switch a form off then you keep the records of all the submissions made to that form.<\/p>\n\n\n\n

The process to switch off a form couldn’t be easier: next to every form in the list is a small switch graphic. Click on that and the switch will go from green to grey.<\/p>\n\n\n\n

\"List<\/figure>\n\n\n\n

Deleting<\/h3>\n\n\n\n

You have consulted with your colleagues and they all agree a form can go? Then hover over the form name and click on Trash<\/strong>.<\/p>\n\n\n\n

WAIT! Before you do that: if you have any hesitancy don’t forget you can download all the entries<\/a> for that form before you delete it.<\/p>\n\n\n\n

Finally, don’t forget…<\/h2>\n\n\n\n

…to request we switch on CAPTCHA<\/a> for you so you can go through the few remaining forms on your site and add the CAPTCHA field.<\/p>\n","protected":false},"excerpt":{"rendered":"

In our latest Pulitzer-prize winning article, we outlined the need to add CAPTCHA fields to your forms as soon as possible. We mentioned how to request that CAPTCHA be switched on for your website, and how to add CAPTCHA to your forms. When it comes to adding the CAPTCHA field to your forms, the number […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[369,390,391],"tags":[],"class_list":["post-15938","post","type-post","status-publish","format-standard","hentry","category-carleton-cms","category-keep","category-rewrite"],"acf":{"cu_post_thumbnail":""},"_links":{"self":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/15938","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/comments?post=15938"}],"version-history":[{"count":1,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/15938\/revisions"}],"predecessor-version":[{"id":20557,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/posts\/15938\/revisions\/20557"}],"wp:attachment":[{"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/media?parent=15938"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/categories?post=15938"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/carleton.ca\/webservices\/wp-json\/wp\/v2\/tags?post=15938"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}