[Solved] Form builder and Front End Users conflict.

[richart]

Hi all,

I am receiving the following error:

Warning: Parameter fbrp_callcount is not known by module FrontEndUsers dropped in /home/content/r/a/y/suppo/html/lib/misc.functions.php on line 1359

I placed a form inside a registered only protected page and I have the feeling it is cause this error to appear any thoughts on what I can do?

Thanks

[richart]

It seems to work but i just want to hide the error message as it will confuse users, any ideas anyone?

[vilkis]

Hi,
You have to provide more information (e.g. versions of your CMSMS and modules). I have a question: is a call of FrontEndUsers module placed after {content} in your template?

Vilkis

[richart]

Info that i think may be important to know: apache, php 4; CMS Made Simple 1.5.3 "Arecibo", FormBuilder 0.5.11, FrontEndUsers 1.6.2, CustomContent 1.5.2.

My template has this code:

Code: Select all

{if $customcontent_loggedin > 0}
  {content}
{cms_module module=FrontEndUsers form="logout"}
{else}
  <h3>You must be logged in to view this information</h3>
{cms_module module=FrontEndUsers nocaptcha="1"}
{/if}

and this is in the page:

Code: Select all

{cms_module module='FormBuilder' form='Song'}

[vilkis]

It is old bug of CMSMS, but I have not found a solution for this yet... (calgay1000 ignored my notification about it ,moreover, he deleted my solution as it was not ideal) I just can say if you reorder  {content} and {cms_module module=FrontEndUsers form="logout"} in such a manner:

Code: Select all

{cms_module module=FrontEndUsers form="logout"}
{content}

the warning should disapear.
Please, confirm it.
Vilkis

[richart]

Thanks it works! The logic seems somewhat strange though, placing the {content} tag outside of the conditions?

[vilkis]

Fine, your case lets me to illustrate  a bug. I will submit it in the forge.
The problem is that each time CMSMS calculates available non inline modules in page (template plus content) without knowing how much modules were in page from what the request comes. So, when in next page an additional module appears (as in your case after login a formbuilder module) the parameters go to wrog module (in your case FrontEndUsers parameters go to coming FormBuilder after user logins).


Vilkis

[RonnyK]

I always check using....

{cms_module module=CustomContent}
{if $ccuser->loggedin()}

So not the full customcontent_....

Ronny

[Sonya]

moreover, he deleted my solution as it was not ideal)

Vilkis, can you please share your "not ideal" solution. I have a conflict FormBuilder + JQueryTools. I can not change the order of module calls since JQuery must be called in the header section.

After submitting a Form I get:

Code: Select all

Warning: Parameter fbrp_callcount is not known by module JQueryTools dropped in /xxxxxxxxxxxxx/lib/misc.functions.php on line 1359
.......
+ Warning for each field in Form Builder

Thank you,
Sonya

[vilkis]

Hi,
I think that my solution will  not work for you - it is really wrong and it helps in very special cases.
Vilkis

[vilkis]

I found a new solution but it is also a hack of CMSMS core...

Vilkis

[vilkis]

It is posted there - http://forum.cmsmadesimple.org/index.ph ... 892.0.html

Vilkis

[garyt]

I am having similar problems but seems to be a conflict between the forms and the Menumanager.

The error is:

Warning: Parameter feu_input_username is not known by module MenuManager dropped in .../lib/misc.functions.php on line 1359

Warning: Parameter feu_input_password is not known by module MenuManager dropped in .../lib/misc.functions.php on line 1359

Warning: Parameter submit is not known by module MenuManager dropped in .../lib/misc.functions.php on line 1359

I noticed a similar error on this site:

http://www.cmsmadesimple.org/moduleinte ... eturnid=64

Any thoughts?

[Foaly*]

Quick solution is to add a @ in at the beginning of the mentioned lines.

[vilkis]

garyt,
does it happen after FEU user login? Can you provide more information - what is your template?
Vilkis