Forms module - part of the menu is missing

Laura Agnello asked on May 13, 2019 09:02

Hello,

I have an issue with one of our websites. Since we upgraded the Kentico Version from 11.0 to 12.0, two features from the Forms module menu are no more visible.

Those features are :

  • Form builder
  • Field editor

They won't show anymore in the left collapsible menu (being connected as anyone, even the global admin account). BUT even though they are not visible in the left menu, if we use the correct URL (ex: ourwebsite.com/CMSModules/BizForms/Tools/BizForm_Edit_Fields.aspx?formid=ID&objectid=ID) to access the feature, it does work !

I checked the permissions for the module and they're all correctly set.

Have you got any ideas what the issue might be ? Thanks in advance.

Correct Answer

Dawid Jachnik answered on May 15, 2019 10:02

Hello Laura,

There could be a problem in upgrade somewhere. Maybe you miss to update some of the files? Does the macro EditedObject.FormDevelopmentModel displays something? You can always do EditedObject.FormDevelopmentModel.ToInt(0) == 0 ;)

0 votesVote for this answer Unmark Correct answer

Recent Answers


Dmitry Bastron answered on May 13, 2019 11:27

Hi Laura,

Do you have Forms module assigned to your site? Please check the following: Image Text

You can also try to disable-enable Forms module for the website and perform a full page reload of admin area.

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on May 13, 2019 13:31

Are there any errors in the Event log? Have you tried re-signing macros?

0 votesVote for this answer Mark as a Correct answer

Laura Agnello answered on May 13, 2019 13:46

Hello Dmitry,

The Forms module was correctly assigned to the right site.

Disabling / enabling it again didn't change anything :(

0 votesVote for this answer Mark as a Correct answer

Laura Agnello answered on May 13, 2019 14:31

Hello Juraj,

Nothing appears in the event log related to that issue. We tried re-signing macros but this didn't work either.

I was wondering if the migration might was the cause or atleast part of the problem, but there was no upgrade error message after we upgraded from v11 to v12 either, so I'm out of ideas

0 votesVote for this answer Mark as a Correct answer

David te Kloese answered on May 13, 2019 15:04

Not sure it's related (as most feature should work), but did you by any chance change license level? Say BASE instead of EMS or have any other temporarily or different level licenses in place?

0 votesVote for this answer Mark as a Correct answer

Dawid Jachnik answered on May 13, 2019 15:28

Hello Laura, Does this features work page types? If yes, please go to Modules > Forms > User interface and check visibility condition. By default you should have

CurrentUser.IsAuthorizedPerResource("cms.form", "ReadForm") && EditedObject.FormDevelopmentModel == 0

if you have other, please update it to the correct version. You can also try to remove condition and check if this problem is related to the condition.

Check the following screenshot https://prnt.sc/nny9re

1 votesVote for this answer Mark as a Correct answer

Laura Agnello answered on May 14, 2019 09:01

Hello,

When we remove the right part of the Macro in the visibility condition given by Dawid : EditedObject.FormDevelopmentModel == 0 Both of the features are visible again.

I guess that's a temporary fix but I'm wondering why the property FormDevelopmentModel of the edited form has not the right value ?

0 votesVote for this answer Mark as a Correct answer

Dawid Jachnik answered on May 14, 2019 09:14 (last edited on May 14, 2019 09:20)

Hello Laura,

it seems that's something went wrong during upgrading. Please check CMS_Form table in the database and check if it contains column FormDevelopmentModel, if yes it should be set by default to 0

EDIT: If there's no column I would suggest to review the whole upgrading process. And if you're sure thats only this. You can execute sql code from upgrade

-- Update table [CMS_Form]
ALTER TABLE [CMS_Form]
ADD
    [FormDevelopmentModel] [int] NOT NULL
CONSTRAINT [DEFAULT_CMS_Form_FormDevelopmentModel]
    DEFAULT ((0))
WITH VALUES

GO

-- Update table [CMS_Form]
ALTER TABLE [CMS_Form]
ADD
    [FormBuilderLayout] [nvarchar] (max) NULL;


GO
1 votesVote for this answer Mark as a Correct answer

David te Kloese answered on May 14, 2019 09:47

Keep in mind, as Dawid mentioned, if you miss this SQL column something failed during upgrade. But more important; If this failed and you didn't see, what else did fail? So if possible I'd check all Database adjustments and verify they are done or redo them!

1 votesVote for this answer Mark as a Correct answer

Laura Agnello answered on May 14, 2019 11:07

Hello Dawid and David,

Thank you for your suggestions.

I just checked it out and the column "FormDevelopmentModel" does exist in the DataBase and all the forms have the value of that column set to "0". That's why I don't really get why removing the right part of the macro would make it visible again.

Would it be possible that either the macro has a problem (because of the upgrade?) or that we didn't re-sign macros correctly ?

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.