Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1342557

    Hi,
    We are working with custom made enfold elements for a long time. We often have problems with the tiny_mce field.
    I created two tiny_mce fields in a custom element:

    array(
                        'name' => __('Immer sichtbarer Text', 'avia_framework'),
                        'desc' => __('Enter some content for this textblock', 'avia_framework'),
                        'id' => 'visible_text',
                        'type' => 'tiny_mce',
                        'std' => __('', 'avia_framework'),
                        'tmpl_set_default' => false
                    ),
    
                    array(
                        'name' => __('Eingeklappter Text', 'avia_framework'),
                        'desc' => __('Enter some content for this textblock', 'avia_framework'),
                        'id' => 'hidden_text',
                        'type' => 'tiny_mce',
                        'std' => __('', 'avia_framework'),
                        'tmpl_set_default' => false
                    ),

    If I edit the content of one of the fields and add a bold text and save the page everything is fine in the frontend but in the backend in the visual view of the tiny_mce field the bold text isn’t visible any more but <strong>Text</strong> is visible as code. If I save again the frontend text is also wrong because I the the html tags. What’s the problem?

    Here is the complete code for the element: https://pastebin.com/Ptn91vBU

    All the best,
    Patrick

    #1342706

    Hey Patrick,

    Thank you for using Enfold.

    Using multiple tinyMCE in one popup is not supported by Enfold (out of the box). Enfold always binds the logic to ‘content’ of shortcode.

    It is rather tricky to implement multiple tinyMCE- and I’m not even sure that it is possible without heavy changes to Enfold core.
    I implemented a solution in another project – but this is not based on ALB elements.

    Best regards,
    Günter

    #1344723

    Hi Günter,

    That’s what I thought :/ Thanks for your answer. So I’ll have to use a normal textfield.

    All the best,
    Patrick

    #1344736

    Hi Patrick,

    Thanks for the update. Please let us know if you should need any further help on the topic or if we can close it.

    Best regards,
    Rikard

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.