Hello ...
We are having extreme difficulty with our public add and modify forms.
GT staff: can you help out here please? Everything is explained below ...
----------------------------------------------------------------
Background:
All our links are in multiple categories.
The editors -- not the users -- select the categories, based on a thorough review of the link.
The categories are not an afterthought for the link -- they are core information, just like the description.
Failure to specify a category is not an error for us. In the Add form it is irrelevant, but in the Modify form it is a requirement that users cannot mess with the category set, which represent significant editorial work.
db_gen_category_list must be set to Yes -- because it determines the display of categories in the Admin interface
----------------------------------------------------------------
Add.pm
The Problem:
By default, Add.pm requires a category input, something we do not need or want.
The Solution:
Either disable the category input, or pass the current category as a hidden input (as happens when db_gen_category_list is set to No).
Our temporary workaround is an edit at line 191 of Add.pm: replace if ($CFG->{db_gen_category_list}) with if (0). This has the same effect as db_gen_category_list = No. The editors can then treat the category as a suggestion.
----------------------------------------------------------------
Modify.pm
The Problem:
This is a major bug -- the modify form can have only one input field for CatLinks.CategoryID, so when the user submits it, essential information about the link (all the other categories) is destroyed. Effectively, Modify.pm cannot be used as the damage caused is greater than the benefit.
The Solution:
Disable category input completely, so that when Admin or Editors validate the modified link the original CatLinks.CategoryID set remains intact.
We have no workaround.
However, we think this might not be too difficult to fix. All we need to do is circumvent the code in Modify.pm which rejects submissions which do not specify a category. But we can't figure out where it happens.
We are having extreme difficulty with our public add and modify forms.
GT staff: can you help out here please? Everything is explained below ...
----------------------------------------------------------------
Background:
All our links are in multiple categories.
The editors -- not the users -- select the categories, based on a thorough review of the link.
The categories are not an afterthought for the link -- they are core information, just like the description.
Failure to specify a category is not an error for us. In the Add form it is irrelevant, but in the Modify form it is a requirement that users cannot mess with the category set, which represent significant editorial work.
db_gen_category_list must be set to Yes -- because it determines the display of categories in the Admin interface
----------------------------------------------------------------
Add.pm
The Problem:
By default, Add.pm requires a category input, something we do not need or want.
The Solution:
Either disable the category input, or pass the current category as a hidden input (as happens when db_gen_category_list is set to No).
Our temporary workaround is an edit at line 191 of Add.pm: replace if ($CFG->{db_gen_category_list}) with if (0). This has the same effect as db_gen_category_list = No. The editors can then treat the category as a suggestion.
----------------------------------------------------------------
Modify.pm
The Problem:
This is a major bug -- the modify form can have only one input field for CatLinks.CategoryID, so when the user submits it, essential information about the link (all the other categories) is destroyed. Effectively, Modify.pm cannot be used as the damage caused is greater than the benefit.
The Solution:
Disable category input completely, so that when Admin or Editors validate the modified link the original CatLinks.CategoryID set remains intact.
We have no workaround.
However, we think this might not be too difficult to fix. All we need to do is circumvent the code in Modify.pm which rejects submissions which do not specify a category. But we can't figure out where it happens.
Multiple categories, Add.pm, Modify.pm : major problems