The following warnings occurred:
Warning [2] Undefined array key "avatartype" - Line: 783 - File: global.php PHP 8.1.31 (Linux)
File Line Function
/global.php 783 errorHandler->error
/printthread.php 16 require_once
Warning [2] Undefined array key "avatartype" - Line: 783 - File: global.php PHP 8.1.31 (Linux)
File Line Function
/global.php 783 errorHandler->error
/printthread.php 16 require_once
Warning [2] Undefined variable $newpmmsg - Line: 40 - File: global.php(841) : eval()'d code PHP 8.1.31 (Linux)
File Line Function
/global.php(841) : eval()'d code 40 errorHandler->error
/global.php 841 eval
/printthread.php 16 require_once
Warning [2] Undefined array key "style" - Line: 909 - File: global.php PHP 8.1.31 (Linux)
File Line Function
/global.php 909 errorHandler->error
/printthread.php 16 require_once
Warning [2] Undefined property: MyLanguage::$lang_select_default - Line: 5024 - File: inc/functions.php PHP 8.1.31 (Linux)
File Line Function
/inc/functions.php 5024 errorHandler->error
/global.php 909 build_theme_select
/printthread.php 16 require_once
Warning [2] Undefined array key "additionalgroups" - Line: 7162 - File: inc/functions.php PHP 8.1.31 (Linux)
File Line Function
/inc/functions.php 7162 errorHandler->error
/inc/functions.php 5044 is_member
/global.php 909 build_theme_select
/printthread.php 16 require_once
Warning [2] Undefined array key 1 - Line: 1415 - File: inc/functions.php PHP 8.1.31 (Linux)
File Line Function
/inc/functions.php 1415 errorHandler->error
/inc/functions.php 1370 fetch_forum_permissions
/printthread.php 76 forum_permissions
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.1.31 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.1.31 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.1.31 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.1.31 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.1.31 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.1.31 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.1.31 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.1.31 (Linux)
File Line Function
/printthread.php 165 errorHandler->error



Form Tools
Submission Accounts module: Feature Suggestions - Printable Version

+- Form Tools (https://forums.formtools.org)
+-- Forum: Form Tools (https://forums.formtools.org/forumdisplay.php?fid=1)
+--- Forum: Feature Suggestions (https://forums.formtools.org/forumdisplay.php?fid=7)
+--- Thread: Submission Accounts module: Feature Suggestions (/showthread.php?tid=89)



Submission Accounts module: Feature Suggestions - Ben - Mar 27th, 2009

Please post all feature suggestion for this module in this thread. I take these very seriously, so it's worth posting them!

To get the ball rolling... here's what's top of my list:

  1. Be able to assign Views to menu items. That way you can both provide a tab-based UI for the form data (by having one or more Views that have tabs to separate the data) and a page-based way to view the data; i.e. the different Views would be
  2. Be able to choose between a visible View based on custom criteria. e.g. if "is_approved" = "Yes", display View X. Otherwise, display View Y. This would be handy for situations where you want to prevent fields being editable AFTER it's been approved (or whatever).
  3. Be able to redirect users to custom message upon login. e.g. if 'is_approved"="no", they'd fail to login, but they'd see a message explaining why they were rejected.
  4. Hooks! Modules should be able to define their own hooks which trigger custom events. This would be really handy for this module: it could trigger custom code to approve the submission, or maybe mark it as complete. But it really requires hook support; don't want to have to hardcode separate mechanism on a per-module basis.
  5. Be able to define custom BLURB in and around the displayed fields / pages. (This will probably be a separate module associated with the View, though...). That way, introductory paragraphs, explanatory blurb before or after fields. As Form Tools migrates closer to non-technical users (as it's doing with this module), we need to simplify everything as much as possible.



RE: Feature Suggestions - Ben - Mar 27th, 2009

Option to map submissions from separate forms. So a single user could log in and view/edit information from multiple forms.


RE: Feature Suggestions - stevenheidel - May 14th, 2009

(Mar 27th, 2009, 9:58 AM)Ben Wrote:
  1. Be able to choose between a visible View based on custom criteria. e.g. if "is_approved" = "Yes", display View X. Otherwise, display View Y. This would be handy for situations where you want to prevent fields being editable AFTER it's been approved (or whatever).

BUMP! I dreamt up an idea where we could use formtools as an election tool. One of the fields has a riding info in it, and if it could be used to show a particular view that had a voting form on it, this would be awesome.


RE: Submission Accounts module: Feature Suggestions - sogreen - Feb 11th, 2011

Is there a way to allow users through the Submission Accounts module to see more than 1 entry? Here's why...

I would like to use formtools to allow parents to submit their information for the school directory online. I'm using the Submission Accounts Module but the problem is that many parents have more than 1 student attending the school. It would be nice if they logged into their account and were able to view all entries with the same email provided and/or had the option to add/remove more entries using their email address.

Right now I have it set up so parents must choose a separate username for each student. I am not sure how the password retrieval will work though since some emails will be used more than once.

Do you have any suggestions on how I could improve my form?