Integrate search with TracFormsPlugin

[Rich Harkins]

Add support to index all forms in the database with some means to wiki-ize the results and pages that contain the results.

[Steffen Hoffmann]

Why is this a high, even critical defect, if not worked on for two years. Come on, be reasonable.

Nevertheless sort of a [[ListForms(count|list|table)]] and [[FormsQuery(who=$USER)]] macro, or even a forms:<identifier> resource link could be useful additions to this plugin.

[Steffen Hoffmann]

I've done some more code reading and i.e. found out, that there is already an unique form index value.

Nevertheless before I'll succeed with implementing a proper !ISearchSource there is considerably more ground work to be done. I'm in the process of creating

• helper functions for converting TracForm id's to context and vice versa,
• a generic TracForm object,
• some permissions to restrict relevant operations

and more...

[Steffen Hoffmann]

This has been my first time dealing with the Trac resource topic for real.

I've a preliminary working ISearchSource provider, that I'll commit to trunk soonish. I'm just still struggling with a creating a proper Form object and related resource. The other related ideas about some additional TracWiki macros may get postponed afterwards.

[Steffen Hoffmann]

(In [10010]) TracFormsPlugin: Add api.py missing from [10002] and add a TracForm resource, refs #3445 and #3500.

The new Trac resource 'form' is a prerequisite for introducing permissions and subsequent stuff relying on permission checks.

[Steffen Hoffmann]

(In [10011]) TracFormsPlugin: Add basic TracForm permissions, refs #3445 and #3500.

Note: Only users with 'TRAC_ADMIN' permision will see 'Update Form' buttons, until you add at least 'FORM_EDIT_VAL' permission to the relevant groups and/or users. This is a prerequisite for other stuff relying on permission checks too.

[Steffen Hoffmann]

(In [10012]) TracFormsPlugin: Add ISearchSource capabilities to TracForm , refs #3500.

Now you're able to find form field content without opening the (parent) resource, where the TracForm has been embedded and get search results with a direct link to that resource too. Suggestions welcome, how to improve the current, slightly rough form content representation for the search results page.

[Steffen Hoffmann]

Replying to hasienda:

Nevertheless sort of a [[ListForms(count|list|table)]] and [[FormsQuery(who=$USER)]] macro, or even a forms:<identifier> resource link could be useful additions to this plugin.

I've created #8749 and #8750 for a follow-up development accordingly.

[Steffen Hoffmann]

manual correction due to a bad ticket reference: second link should have been 3500, not 3550

(In [10143]): TracFormsPlugin: Releasing version 0.3, pushing development to 0.4, closes #3445, #3500, #3741, #4759 and #8258, refs #3388 and #6993.

This is a major release requiring a Trac environment upgrade.

While the parser logic remains unchanged, there is a lot new supplementary funcionality to make TracForms behave more like the existing Trac core resources (ticket, wiki, attachment, ...).

This version performs a series of non-trivial db schema changes, that especially may leave traces of stale forms (i.e. recorded for wiki pages, that don't exist anymore). So please make sure to read the changelog, BACKUP your environment(s) before installing this version as usual and check the new db tables forms, forms_fields and forms_history after upgrading.