Hi Prig,
Ah, interesting.
Are you running v1.0.0 of the module? If so, ignore the last four errors - that was a glitch in the script. If you're running 1.0.1, try uninstalling the Extended Client Fields module and re-installing it. For some reason, the tables don't exist.
The first error, however, looks like a real issue. That column was updated in an early version of the 2.0.0 Beta.
Do you have access to phpMyAdmin, or a tool that lets you run queries on your database? If so, log in, select your Form Tools database and run this query. Note: you'll need to replace *** with the prefix for your tables. e.g. the table name would be ft_hooks or ft2_hooks or something.
That should fix up this problem.
However, I don't think this should cause any dropped permissions....
You are running 2.0.4 now, correct?
- Ben
Ah, interesting.
Are you running v1.0.0 of the module? If so, ignore the last four errors - that was a glitch in the script. If you're running 1.0.1, try uninstalling the Extended Client Fields module and re-installing it. For some reason, the tables don't exist.
The first error, however, looks like a real issue. That column was updated in an early version of the 2.0.0 Beta.
Do you have access to phpMyAdmin, or a tool that lets you run queries on your database? If so, log in, select your Form Tools database and run this query. Note: you'll need to replace *** with the prefix for your tables. e.g. the table name would be ft_hooks or ft2_hooks or something.
Code:
ALTER TABLE ***hooks
CHANGE action_location action_location VARCHAR(100) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL
That should fix up this problem.
However, I don't think this should cause any dropped permissions....
You are running 2.0.4 now, correct?
- Ben