Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncaught ReferenceError: label is not defined on multilingual environment #115

Open
shaneonabike opened this issue Feb 22, 2022 · 3 comments

Comments

@shaneonabike
Copy link

I seem to have come across a strange issue when creating new blocks.

Reproduce:

  1. Setup a multilingual environment
  2. Create a new Layout
  3. Create a new block
  4. Change the title to something help, for example Contact Details
  5. Add one custom field, demographics fields (i.e. Gender and Date of Birth)
  6. Save
  7. Drag and drop it into your blocks setting and expand or Edit the block

What happens:

You can no longer edit the new block and/.or add fields into the newly created block. The error I get in my browser console is

Uncaught ReferenceError: label is not defined
    at eval (eval at <anonymous> (lodash.min.js:75:591), <anonymous>:3:477)
    at Object.render (backbone.marionette.js?r=HV6uc:1231:12)
    at child.render (backbone.marionette.js?r=HV6uc:1457:36)
    at child.r [as render] (lodash.min.js:25:62)
    at Marionette.Region.show (backbone.marionette.js?r=HV6uc:910:10)
    at child.onRender (crm.designer.js?r=HV6uc:618:20)
    at child.triggerMethod (backbone.marionette.js?r=HV6uc:565:21)
    at child.render (backbone.marionette.js?r=HV6uc:1462:10)
    at child.render (backbone.marionette.js?r=HV6uc:1920:55)
    at child.r [as render] (lodash.min.js:25:62)

No message appears in the log files.
Selection_007

What you expect:

To be able to edit the fields and all the fields are stored properly.

@shaneonabike
Copy link
Author

Peek 2022-02-22 10-37

@colemanw
Copy link
Member

colemanw commented Mar 3, 2022

@shaneonabike I appreciate the detailed bug report. Unfortunately it's a bit obscure, and the issue is with some older technology (the old profile-builder popup). I'm not sure when/if this will get prioritized, but there is a workaround: instead of relying on the profile-builder popup, you can edit the profile the old way, by going to Administer -> Customize Data & Screens -> Profiles.

@shaneonabike
Copy link
Author

Hi @colemanw yes that's what I ultimately did in order to make it work. I'm not sure it's that obscure but is there a way to just disable this feature maybe? Then it would force folks to use the actual Profile as you suggest to add it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants