Troubleshooting: When Your Site Homepage Does Not Accept Arigato PRO Signups

This is quite a common problem with sites that run WordPress but have their homepage made as landing page with other plugin or just built as static page. Arigato PRO has a “Squeeze page” option and we strongly recommend it. But if for some reason you use a a static squeeze page, or other squeeze page that does not run the normal WordPress routines you may have a problem with Arigato form sign-ups not being processed.

The solution to this is very simple: point the Arigato PRO form action attribute to a post created with your WordPress blog instead to the homepage.

So your Arigato PRO form opening HTML tag will look something like:

<form action=”” method=”post”>

That’s it.

WatuPRO: Cleanup Database Space

By default WatuPRO stores every user’s answer to every question in your database. This allows us to show you this data any time and perform useful reports on it. As the time goes and you are collecting a lot of data from many users and quizzes, your database can become really big. This might be a problem if you are using a shared host or other way limited resources.

So here is what you can do. Have in mind that any solution that reduces data means this data will no longer be available to you and will no longer participate in reports.

When Your Database Is Already Large

If you have not prevented the database from growing and already have too much of it, you will need to clean it up. There are several options:

a) Deleting whole quizzes. If there are quizzes you no longer need, and don’t need the stats from them, you can simply delete them. This will save most space but obviously isn’t ideal in most cases.

b) Delete user submitted data on the quiz. You can save a lot of space by doing this. Go to Quizzes -> View Results and you’ll see a checkbox at the bottom: “Show me a button to cleanup all submitted data on this quiz.”. Click on it, then click on “Cleanup all data” button.
You can do this on every quiz on which you don’t need the data.

c) Blank out data on a quiz. Blanking out the data will save less DB space, but will leave the points, grades, percentage correct answers etc. This way most of your reports and stats will remain unchanged and you’ll still have less used DB space.

Preventing Too Much Data

As usual prevention is easier than cure. Depending on how much of the user submitted data you need, you have several options to reduce DB space usage:

a) Don’t store any data. This is configurable on per-quiz basis. You need to go to Edit Quiz -> Advanced Settings tab and select the following option:

” Don’t store any data / results of this quiz in the database. “

That’s it.

b) Automatically cleanup or blank out data. This option is global and affects all quizzes so be careful with it. It’s available on your WatuPRO Settings page:


You can for example choose to cleanup only data older than 30 days, or 180 days etc.

[WatuPRO] Don’t Display Already Answered Questions To Logged In User

This feature requires Watu PRO version or newer and can be used on quizzes that pull random questions from a pool of questions. The pool can be the same quiz or reused questions from other quizzes. The idea is that when user retakes the quiz they won’t see questions already answered in a previous attempt (even if same question was used in another quiz).

The setting will be available on quizzes that meet ALL of the following criteria:

  • The quiz requires user log in
  • The quiz pulls random questions
  • The quiz allows either one attempt or a specified number of attempts but does not allow unlimited attempts. (Because if you allow unlimited attempts the user will eventually see all questions and end up with an empty quiz)

Be careful with this setting and the number of attempts you allow on a quiz. If the user answers all the questions in previous attempts, they will again end up with a quiz with no questions at some point. It is you responsibility to avoid this by controlling the number of questions and number of attempts. Especially watch out for cases when multiple quizzes reuse the same pool of questions.