Support

Account

Register Login

Home › Forums › Search › Search Results for 'Wysiwyg'

Search Results for 'Wysiwyg'

reply

  • Thanks for the rapid reply.

    There are additional issues with using the WYSIWYG as it often wraps html in additional P and img tags whereby i just want the URL.

    I was going to take a look at actually hooking into the other dialogue so that NSM also get’s hooked in (or vice versa).

  • Hi @Joe

    Looks like you are missing a semicolon in your code.

  • Hi @phil.fuse

    Currently the ACF image field does not support the sidebar tabs, so your best bet is to use a WYSIWYG field and insert the image into that.

    The WYSIWYG field contains the media button with no limitations.

    Hope that helps.

    Thanks
    E

  • Hi @thecorkboard

    The comment metabox should not be interfering with WP loading the WP Editor JS, so I’m not sure what the real issue is here.

    My bet is that you have a plugin that is causing the error. The plugin would most likely have some sort of functionality to do with comments.

    Perhaps you can test by disabling all plugins?

  • Hi @TripleM

    Thanks for the bug report. It seems that because ACF creates a hidden WYSIWYG on the page (required for the WYSIWYG to work), the active editor variable is being set to this hidden field instead of the main content area…

    If you were to first click in the main WYSIWYG, then click the shortcode button, does it work correctly?

  • Hi Joe,

    You could try this to strip out all HTML tags. Might be good to do this for RSS:

    <?php $steps = get_field(‘step’); ?>
    <?php if($steps) { ?>
    <p>Directions: </p>
    <div>
    <?php foreach($steps as $step) { ?>
    <p><?php echo strip_tags($step[‘add_step’]); ?></p>
    <?php } ?>
    </div>
    <?php } ?>

    Here’s the documentation: http://php.net/manual/en/function.strip-tags.php

  • Hi @tirussell

    I see.

    Thanks for the screenshots. I think CSS for the WYSIWYG content is a great feature to add, I’ll look into it in the future.

    Cheers
    E

  • Sure! In the example below what I want to do is have the “Sidebar Area 1” in the third screencap have a restrained width that matches the width of the side bar that gets rendered on the front end. That way, contributors won’t have to guess where line breaks will be.

    These should open full-size in new windows if I’ve done it right:

  • Hi @CakeAndEatItDesigns

    I wasn’t aware of this issue. I’ll check it out and get back to you

    Thanks
    E

  • Hi @tirussell

    Are you able to attach some screenshots to aid your request?

    Thanks
    E

  • Hi @figureone

    I will be adding in the extra filter soon, but just to reply to your statement about filter timings, you can infact hook in BEFORE the core update_value filter.

    ACF hooks into this on line 26 of _functions.php with a priority of 5. You can hook in before 5 and run beforehand!

    Thanks
    E

  • Hi @leaksterrr

    I am 100% sure that you can have multiple paragraphs of text within a WYSIWYG field. I have written many blog articles which multiple paragraphs.

    Perhaps you need to not use the HTML tab? When you write your paragraph and then hit enter, do you get a paragraph space between the blocks of text?

    What do you get when you render the value on the page with the_field?

    Do the paragraph tags appear?

    Please note that WP will stip out p tags when it saves the value and then add them back in when you render it. Perhaps this is the issue?

  • Ok, here goes for a more in depth explanation.

    In the standard content editor when you go to insert media and upload an image. You are able to add caption text to the image. Once you click the insert into post button this text is displayed in the editor under the image as a caption(and then on the frontend it displays as a caption as well).

    When I switch to the text view on the standard editor I can see a caption shortcode wrapped around the image.

    However, when I am using a WYSIWYG field from ACF and I click insert media and upload an image, the caption doesn’t get added to WYSIWYG editor.

    And I don’t see the caption shortcode if I view the text version of the WYSWIG editor.

    Does that help any? Let me know if there is more information you need. Thanks for the help! And thanks for the plugin, it is the most useful plugin in my toolkit!

  • Hi,
    I’m having the same problem with what I think is the same line of code (#188) in the _functions.php file.

    In my case, the backslashes get stripped from plain text fields where I need to store regular expressions.

    Your suggestion about hooking to the ‘update_field’ filter won’t work because you are calling streepslashes_deep() BEFORE the apply_filters() call.

    I think the option of the backend filter is a quick one, but it may also be useful to pass more info to the filter, e.g., the field type and name, field group, etc., so the programmer can have more context info in order to make the decision either to return false or true.

    Thanks in advance,

    Adrián

  • Hi @CakeAndEatItDesigns

    Thanks for the bug report. Are you able to explain the issue with more detail? Perhaps with a screencast or screenshots to show the issue?

    Thanks
    E

  • Field Order
    Field Label
    Field Name
    Field Type

    1 Standard (javascript:;)

    standard
    Checkbox

    2 Course Description (javascript:;)

    course_description
    Wysiwyg Editor

    3 Learning Outcomes (javascript:;)

    learning_outcomes
    Repeater

    4 Target Audiences (javascript:;)

    target_audiences
    Checkbox

    5 Format (javascript:;)

    format
    Checkbox

    6 Grades (javascript:;)

    grades
    Checkbox

    7 Pre-Requisites (javascript:;)

    prerequisites
    Post Object

    8 Recommended & Related Courses (javascript:;)

    related_courses
    Post Object

    9 Next Steps (javascript:;)

    next_steps
    Post Object

    10 Agenda (javascript:;)

    downloads
    Repeater

    11 Recommended Resources (javascript:;)

    resources
    Repeater

    12 Specials (javascript:;)

    specials
    Wysiwyg Editor

    13 Item Number (javascript:;)

    item_number
    Number

    14 Price (javascript:;)

    price
    Text

    15

    Text

    Drag and drop to reorder
    + Add Field (javascript:;)

    Location
    Rules

    Create a set of rules to determine which edit screens will use these advanced custom fields

    Show this field group if
    Post TypeLogged in User TypePagePage TypePage ParentPage TemplatePostPost CategoryPost FormatPost StatusPost TaxonomyAttachmentTermUser
    is equal tois not equal to
    postpagecoursewpcf7_contact_formslide
    and (http://mathsolutions.com/wp-admin/post.php?post=2296&action=edit#)

    or
    Add rule group (http://mathsolutions.com/wp-admin/post.php?post=2296&action=edit#)

    Options
    Order No.

    Field groups are created in order
    from lowest to highest

    Position
    High (after title)
    Normal (after content)
    Side

    Style
    No Metabox
    Standard Metabox

    Hide on screen

    Select items to hidethem from the edit screen

    If multiple field groups appear on an edit screen, the first field group’s options will be used. (the one with the lowest order number)

    Content Editor
    Excerpt
    Custom Fields
    Discussion
    Comments
    Revisions
    Slug
    Author
    Format
    Featured Image
    Categories
    Tags
    Send Trackbacks

  • Hi @wpUXsolutions

    Thanks for the info, much appreciated.

  • Hi Elliot.

    Unfortunately, I didn’t have too much time to really find what causes the problem. I just compared the final HTML codes of the ACF Option page: with active Formidable and without. I found that we miss those scripts when Formidable is on. It re-declares the scripts somehow.

    Since I needed some fast temporary solution, I just linked those 2 scripts “manually”. By and large, we miss some other scripts too when Formidable is on, but since these two were enough to make link button work, I stopped on them. I also don’t know where ACF registers these two or maybe WP itself does this for all admin pages? When I have more time, I will study this problem more carefully.

    Sorry for not being too helpful.

  • Hi @wpUXsolutions

    Thanks for the code and solution. Can you elaborate more on how this resolves the issue?

    Thanks
    E

  • Hi @gminc

    Thanks for the bug report.

    The ACF gallery field uses the native WP media popup to display the field data, then it uses CSS to hide the usual main / side bar layout and only show the sidebar.

    The issue may be that the WP popup contains a bug in regards to user permissions, so can you open up the normal WP popup (via the_content WYSIWYG) and try to edit the image in question using different user accounts?

    Does the WP popup allow you to edit the image?

    Thanks
    E

  • Temporary solution:

    add_action( 'admin_init', 'wpuxss_admin_scripts' );
function wpuxss_admin_scripts() 
{	
	global $pagenow;
	
	if (( $pagenow == 'admin.php' ) && ($_GET['page'] == 'acf-options') ) 
	{		
		wp_enqueue_script( 'wplink', home_url('/wp-includes/js/wplink.js') );
		wp_enqueue_script( 'popup', home_url('/wp-includes/js/tinymce/plugins/wpdialogs/js/popup.js') );	
	}
}

  • Hello Elliot,

    I am experiencing similar problem with ACF 4.2.2 (Option page 1.2.0) right now. When I deactivate Formidable 1.07.01 the problem is gone. The problem is only for Options page and for WYSIWYG link button.

    Uncaught TypeError: Object [object Object] has no method 'wpdialog'
    in the wp-includes/js/tinymce/wp-tinymce.php line 24

  • Good man! – I will test it out when I’m back on that project… cheers for that – appreciate the response.

  • Hi @rockethouse

    Just wanted to follow up and let you know I have made some changes to the WYSIWYG field in hope that it will solve your original issue.

    All the add_filter functions for acf_the_content have been moved to the root of the wysiwyg field file, so you should be able to unhook them in your functions.php file.

  • Awesome, I think a back-end filter would be fine, since trying to describe what’s going on here in a UI option might be difficult for nontechnical users to understand.

    For the short term, I’m covered by simply commenting out the stripslashes_deep() call in the ACF code, so it’s not a big rush. Let me know when the filter makes it into core, though! At that point I can roll out a custom filter in all of my relevant themes.

    Cheers,
    -paul

Viewing 25 results - 1,126 through 1,150 (of 1,299 total)
1 2 3 … 45 46 47 … 50 51 52