By Michael.JBuild your own forms for your members, supporting alerts for pm, email and topics. Integrate with the registration form or add forms into widget areas throughout your forum.
Keep up to date with DevFuse mod development and releases.
Integrate with the registration form. Export displayed form logs to csv files. Toggle on and off other custom fields within a form. Optional confirmation email to let members know there message was received. Send reply emails within the Form Manager Quick preview feature for form logs. Per form option for rules or instructions for each form. Submit time wait feature, set how long each member group must wait before resubmitting a form. Per form permissions for who can view and submit to a form. And also who can view any form logs. Per member group option to bypass captcha. Per form option to send out personal messages when new form submissions are made. Per form option to send out emails when new form submissions are made. Per form option to create a forum topic when new form submissions are made.
386 purchases 1,323 downloads
By HeadStandCustom Fields anywhere and everywhere.
The Template System allows you to customize anything in the suite - forums, calendars, gallery categories, blogs, etc - and to create forms for the user to populate when posting new content.
Create custom fields Group custom fields into Sets for individual containers (e.g. forums) Customize the layout of the field values when viewing content Allow multiple Sets per container to give users a choice of which form to populate Mark individual fields as required - preventing users from creating content without populating the additional fields By default, you can add
Custom fields when creating topics Custom fields when creating calendar events Custom fields when posting blog entries Custom fields when uploading images to the gallery Custom fields when submitting downloads files Note that the system will detect other areas of the site (depending on the 3rd-party modifications you have installed) and will allow you to place custom fields in those areas. However, support for those areas is not guaranteed.
Fields can be created for individual areas or shared across multiple areas. (Example: I can create TextFieldA for topics, or I can have TextFieldA available for both topics and blogs.)
Different fields can be used for different items within each area. (Example: TextFieldA is visible for Forum1, but DropdownA is visible in Forum2.)
Fields can be grouped differently for different areas. (Example: Forum1 will have TextFieldA, but Blog1 will have TextFieldA and DropdownA.)
81 purchases 422 downloads
Those of you doing serious custom work or jumping into other clients Pages installations to design, patch, change things in templates - especially heavily customized forms - probably want easy access to the database field id numbers.
Here you go.
Version 2 adds in database category IDs on that view as well.
Just as useful.
How does this work?
During the indexing process for an IPS Pages database record the field you have flagged as "Content" is processed by the IPS indexing method. After that is complete, this plugin checks that the overall item is indeed a Pages database record and looks for text, text area, and editor fields that are also a part of the record. If those fields have been flagged by you with this plugin to be included in the search index those areas are then collected, stripped of HTML elements to retain only the pure text content (Editor fields only), and then appended to the end of the initial indexed data (that field you have marked as "Content").
That field content is now in the search index and, naturally, searchable!
For example if a Pages database content element consists of "Today is a good day to die!", and you have an additional text field where you allow someone to enter a day of some kind, for example, "Penguin Awareness Day", if you flagged that extra field as searchable, the indexed text for this content item will be:
Today is a good day to die! Penguin Awareness Day Without the ability to flag these extra fields as searchable and then append their contents on to the content item search data entry, searches for Penguin Awareness Day will return nothing at all, which makes the use of Pages databases much less useful when you can only search for the fields flagged Title and Content.
When does this actually apply?
When records are saved (initial creation) and when edited of course. Also during search index rebuilds.
What happens if I remove this plugin or disable it?
Those additional fields will no longer be indexed. Any of those fields previously indexed with records will remain in the index until the record is edited again or you rebuild the search index. On edit or re-index, that additional appended text will not be indexed.
I can't stop you or your other admins from doing... interesting things. This plugin does EXACTLY what it says, no more, no less. The plugin also is not psychic so when one of your admins decides to do some server work and disables this (and other plugins) but people are still making entries on the front end into a Pages database where you had extra fields marked as searchable the result will be pretty much what you expect...
What happens if IPS decides to finally include this functionality themselves?
Remove this plugin, do whatever is required of the new IPS functionality, rebuild the search index. This plugin only appends the additional text to the search index entry (which for Pages database records is whatever the content of the field flagged as "content" is, minus HTML code) and makes no actual changes to the record content itself.
Why hasn't this been included by IPS before?
Appending specifically? Permissions. Searchable fields in general? A structural challenge with the overall IPS content model.
Every database field can have custom permissions. For example, you can create a bug tracker where there are publicly viewable fields and then other fields that only staff can see. However, there is only a single search index content entity that is searched - not separate searchable entries for every field. That means that every field you append to the search index with this plugin MUST be a field you want everyone to be able to see and search. When viewing a record those field permissions will of course apply, but with this information appended to the single searchable index entry you risk the chance that a search result will display with that formerly staff-only field and now everyone will know your admins are calling other members "buttheads" or worse. Be careful!
For IPS to solve this, they would need to treat all additional text, editor, and text area fields as totally separate entities to be inserted into the search index. The management of that endeavor will require some engineering - it's doable but requires some choices to be made along with how to present the final search result. We didn't get additional searchable fields in the 3x line, not with the initial 4.0.x hotness, and with 4.3, 4.4, 4.5 now it still appears to be a distant dream. I got tired of waiting. For my use case I can write a custom app and deal with the problem my way, or I can just use Pages, append the two text fields I need searchable to the main content field with this plugin, and call it a day.
Looking at filtering out content from being indexed by entering a regex equation. If the content of the field matches your regex, this plugin will not append it to the search index entry. This will cut down on search index spam if the text fields you are appending often contain repetitive entries and you'd rather just index out the more unique ones. Maybe numbers?
August 2020 EDIT: Those are still on the table but with only four purchases all these years it's not a priority. If someone wants to throw some money at me to sponsor those features feel free. I actually use the regex tweak on one site but it's currently a simple hardcoded hack.
OK, great, but I already have a massive Pages database. I installed this and set the fields I wanted to be indexed in this database. I get that new records going forward will have the field values added to the search index but what about old records?
For Invision Community 4.4 and above, with PSTF 2 and above, you can now click on the plugin settings and fire off a re-index process for the database you select. 4.3 or lower users on an older version will need to manually edit and save (that's all, just open/close) each record to force the new indexing or rebuild your entire community via the search settings in the ACP.
PSTF version 2 is for Invision Community 4.4 exclusively - do not use on lower versions!
PSTF version 3 is for Invision Community 4.5, though it should work on 4.4 as well (untested)
$20 to buy, $5 every 6 months renew
12 purchases 38 downloads
By A ZayedThis plugin uses validator.pizza API to validate users email address during registration and during personal email change.
The plugin checks if the email is:
Disposable (10 minutes emails... etc.) Alias Many thanks for @Wolf for sponsoring the development of this plugin.
I'm up for any recommendations or suggestions to improve plugin action.
21 purchases 42 downloads
By Michael.JSet a custom primary member group during signup based on selected profile fields.
Features: Set the member group that new members will be assigned to if a profile field is filled out. Set the member group that new members will be assigned to if a profile field field matches a selected value. Full registration form required for plugin to operate and only 1 primary group upgrade supported! Keep up to date with DevFuse mod development and releases.
3 purchases 4 downloads
By Michael.JThis plugin allows you to select which custom profile fields require unique value/content when members edit their profiles. So that multiple members can not have the same profile field value.
Select any custom profile field to require unique content. Set which member groups can be exempt from the unique value requirement. Supports custom profile fields placed on the register form. Choose between an exact match or contains match when checking fields for unique content. Keep up to date with DevFuse mod development and releases.
12 purchases 23 downloads
This tiny plugin will send focus to the TOPIC TITLE field when you're trying to start a new topic.
This plugin will make the image record required when submitting a record in Pages.
Apply in databases (to choose) Apply to (groups)
Application allows you to:
impose limits on the number of words or characters which the editor content must contain before the content can be submitted in addition, the number of links/videos/emojis/spoilers/images can also be monitored settings can be imposed on a group basis, meaning that one group can have different limits to others, or have no limits at all settings are then imposed on an app basis (Forums/Calendar/Pages), and can target all or some of the elements within those apps Please note the following:
If you require support then please post in the provided support topic. Do not use PM and do not use the review functionality.
18 purchases 114 downloads
This plugin adds another email address field on the new member registration form for the user to confirm the email address.
On submission, if the two email fields do not match the registration will not process and the form will reappear with a message indicating those two email addresses did not match.
The remaining fields and choices will still retain previously filled in information. The user will just need to correct the email addresses and re-submit.
This DOES work with the register after posting feature. When the user enters their email address and post content and then hits save, they are taken to the usual user registration form with the email address field pre-filled with their entry. The confirm email field is beneath, and works, as expected.
This validation occurs AFTER a user submits the registration form, not via jQuery live on the form after they enter both email addresses.
Also important: Users of IPS Commerce can require purchases of items on registration, the user registration form created by Commerce for checkout purposes does NOT get this email validation form field, and likely never will (reasons...). Feel free to lobby IPS for a built-in email validation field!
Version 2 is for Invision Community 4.4 and above exclusively. Confirmed working with 4.5
For 4.3.6 and lower please use version 1.
This is a free resource, written a long while back, with the expectation that IPS would build in this feature themselves eventually.
By newbie LACThis plugin restore topic description
50 purchases 155 downloads
This plugin will limit the Support Request titles to a specific number of characters of your choice.
Places to work: Either Frontend AdminCP Number of characters
By newbie LACThis plugin will show custom profile fields in selected forums.
36 purchases 86 downloads
By InvisionHQIT WORKS FOR 4.5
Lets you set up some default text that will be filled in for all new topics in specified forums. You can define the default Topic Title and initial post content. People posting new topics in forums where this is active will be able to alter this text, but it is useful to provide a common template for specific types of topics.
NOTICE: if you have purchased this plugin for IPBv3.x drop me a pm so i can add you to the file ( Make sure you have an active purchase ).
FOR IP.Board 3.x: https://community.invisionpower.com/files/file/5383-pre-defined-topic-fields/
126 purchases 309 downloads
By slushpuppehThis plugin allows you to set a message on the registration page for your users.
Full editor support for easy editing
4 purchases 8 downloads
Album Link Field
The album link field is a plugin which adds a new custom field to your cms databases called "Album Link". The album link field allows you to link albums to your database records.
You can configure the field to allow the selection of existing albums, or to allow the creation of a new album in a specific category, or both.
Built for IPS Pages / CMS Link existing gallery albums with records Allow new albums to be created and linked on the fly Record workflow and image upload workflow are chained together Built-in mini-album display on records pages Built-in "linked" content display on album pages Set custom permissions for linked albums Control album placement categories
18 purchases 33 downloads
Will automatically check the option Request RSVP on event post screen.
This plugin will change the behavior of all password fields on IPS4, allowing the administrator to set the minimum length for the passwords. IPS4 default is 3 characters, this plugin will allow you to alter this.
This does work alongside the built-in IPS password strength meter just fine.
It will change the length in all places that uses password, like:
Registration screen Account Settings -> Password etc. Notes:
Existing Users: No changes to their existing passwords. If their password is reset or they change it themselves the new password length requirements will apply. New Users: Required to use the new password length when they create their account.