Support

Account

Register Login

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

Search Results for 'Wysiwyg'

reply

  • Anywhere that there is a gallery, it gets set to “text” after the update to PRO. Then I have to go into the custom field and set it back to “gallery”. It finds the content if I do this. Actually, on second look, one gallery kept it’s gallery setting. The one gallery that kept it’s gallery setting is only associated with one page. The other two galleries are for blog posts and a portfolio cpt. So, maybe pages are keeping the gallery and posts are not. All 3 gallery fields in the site are in different custom fields. All 3 have different gallery names, and all custom fields have different titles and post_names – double checked in the database.

    The flexible content is being set to “text” as well. Setting it to “flexible content” creates an empty flexible content area. If I look in the wp_postmeta table, the flexible content fields that were entered with that page by ID are still there, so I suppose if I rebuilt the entire flexible content custom field, it may pick up the data from the database.

    The post_names are all still exactly the same as when the site was running ACF 4, and none of them are repeats.

    It seems that the flexible content and gallery fields are more often than not defaulting to the “text” custom field when the move happens. This may be where the problem is happening? The one repeater that I have on this site associated with a page kept its value.

    The flexible content field I have contains: layout 1: image, text, wysiwyg. layout 2 : post_object. layout 3: image, text. There are 39 total entries associated with this specific page, mixed between the different layouts.

    Please let me know how I can provide you more information to help debug this, thanks so much!

  • The original issue seems to have been resolved for me.

    A new observation regarding compatibility for me now is that paragraph tags are wrapped around the shortcode when I hit a new line in ACF’s WYSIWYG editor. For example:
    <p>[su_row]</p><p>[su_column size="1/3"]</p>

    I’ve also tried manually removing the paragraph tags via the Source Code button in ACF’s WYSIWYG editor, but the paragraph tags remain.

    For the others experiencing this as well, I’m working around it by using Shift+Enter (line breaks) instead of Enter (paragraph).

  • https://github.com/elliotcondon/acf-wordpress-wysiwyg-field/issues/9

    Hi guys.

    Thanks for your patience. I’ll get this field compatible with ACF5 hopefully today

    -elliotcondon

  • Hi,
    I need the text view tab too, but cannot use addons with ACF5.
    I see wordpress-wysiwyg addon works fine with repeater field & ACF4.

  • At the moment I have not tested the field with ACF 5. I will add support when the new version is out of beta perhaps.

    As I wrote in the plugin readme, this is intended for developers who want to build with currencies, there’s currently no WYSIWYG feature (except for two simple shortcodes) and I don’t plan to have any.

    ACF-wise, the field consists of a select field with a list of currencies. When adding the field to a post using ACF, the user can select one or more currencies. When getting the value of the field from a post with get_field(), it will return the currencies selected. Could be useful if you need to associate one or more currencies to a content. Then you can use the rest of PHP functions provided by the plugin to do something else.

  • I have the same issue. I sent a support ticket in.

    This is able to be reproduced by following these steps:
    1 – select any page that has a normal WP content editor and switch the tab to “Text”
    2 – leave that page by selecting pages (this seems to be important, maybe preference is set)
    3 – select a page that has an ACF WYSIWYG editor and notice that it’s text editor, but without any buttons. It’s basically the “html” modal that pops up when you click the html button in ACF’s WYSIWYG full editor.

    WP 3.9.1
    ACF 4.3.8

  • Hi @thesrpr,

    There is a similar thread here, but instead of <br> it’s the p tag: http://support.advancedcustomfields.com/forums/topic/removing-paragraph-tags-from-wysiwyg-fields/

    There are a few filters for this but what I’d recommend is reading up on the preg_replace php function.

    Here’s an example of how I removed p tags and empty spaces with that function:
    <?php echo preg_replace('~\s?<p>(\s|&nbsp;)+</p>\s?~', '', get_sub_field('field_name')); ?>

    You’d need something along these lines:

    <?php echo preg_replace('/(<br>)+$/', '', get_sub_field('field_name')); ?>

    This may not be the perfect solution for you. Also check out str_replace and strip_tags.

  • I’d like to add that I have noticed the issue also appearing with multiple WYSIWYG editors in a repeater field.

  • The disappearing WYSIWYG problem just recurred for me today with a new install of ACF. I’m sure everybody’s working hard on v5 but this is a pretty serious issue – you can’t have a plugin that creates more fields, taking fields out!

    ACF itself is *definitely* the source of the problem – I just removed all plugins and added them back one by one. Even without ACF Repeater and Options, only basic ACF seems to cause #postdivrich to load with display:none; – this seems to originate at the top of post.php itself, but my detective skills are lacking here.

    Overriding #postdivrich { display:none; } in the developer console causes the WYSIWYG to reappear.

    I just tried a hack, hooking on admin_init, where i force the display: block; style with !important, that works.

    
function nim_show_editor(){ ?>
	<style type="text/css">
		#postdivrich {display: block !important;}
	</style> <?php
}
add_action('admin_init', 'nim_show_editor');

  • I was waiting also for a solution. Unfortunately time ran out and i had to find another solution.

    I ditched the Options page plugin and used similar plugin called “Types”.
    Although Types plugin serves the same purpose as ACF i still wanted to use it since it has better options (repeater field, etc).

    The problem was that i wanted to use custom fields in footer or elswhere and still have them translated. Second thing was to keep it simple and aesthetic.

    So i made a custom post type with Types- with Title no WYSIWYG editor.
    http://screencast.com/t/3cmHVL6c
    Then made a new page called “Front page banner translation” – and this page can be targeted in ACF. http://screencast.com/t/kHauYS3I
    And all the fields can be translated from there (yey, no more string translation shit)
    http://screencast.com/t/ViCS5EXvVPK

    Only thing you have to do now is to target those different pages and get the content from them. This can be done with this code-
    <?php $nr = icl_object_id( 177, true ); the_field('acf_field_name', $nr); ?>

    …where 177- is the page number of your custom page and acf_field_name your field name (duh).

    Quite simple to the client, easy code-wise.

    Let me know if there are questions

  • Hi Elliot,

    Legacy shortcode works [nggallery id=#] but the new NextGen Gallery doesn’t work in flexible/repeater wysiwyg editor.

    The new NextGen tag is like this <img alt="" src="http://domain.com.au/nextgen-attach_to_post/preview/id--3262" />.

  • I’m also running WP 3.9.1 and ACF 4.3.8 and am having mixed results with the WYSIWYG editor. On one page that I have it set it doesn’t work, but on all the others it does.

    The main difference between the various pages is that the one where the WYSIWYG editor doesn’t display has an ACF Google Map field included. If I remove the Google Map field and reload the page editor, the WYSIWYG editor then displays properly.

    When I inspect the page, I get the following error:
    TypeError: google.load is not a function
    http://anvilcentre.com/wp-content/plugins/advanced-custom-fields/js/input.min.js?ver=4.3.8
    Line 1

  • p.s. We are using the WYSIWYG inside the Flexible Content Field. Perhaps that will help with troubleshooting.


    @elliot

  • My wysiwyg is gone as well after updating. Why did you remove this feature?

  • …take it back, I’ve lost the wysiwyg editor again, and only have html, this is starting to be a pain.

  • Seems like after updating to 4.3.8 I now see the wysiwyg toolbar
    BUT no icon for adding links 🙁

    Anyone know how to add the link icon to the toolbar ?

    thanks

  • I have yet to test out the latest update, due to not wanting to break anything further, but from the looks of it, the latest version of ACF should have resolved the issue.

    Since I really needed a fix, the day I posted on this thread, I decided to use TinyMCE Advanced ( via http://wordpress.org/plugins/tinymce-advanced/ ) as a work around to the issue stated above.

    TinyMCE brings back the WYSIWYG options that are removed.

    ================================================================
    Download Latest Version: ACF 4.3.8 http://downloads.wordpress.org/plugin/advanced-custom-fields.zip
    ================================================================
    ACF Change Log as of 05.07.2014

    4.3.8
    Validation: Fixed disabled button issue in WP 3.9
    4.3.7
    WYSIWYG field: Fixed missing tinyMCE buttons in WP 3.9
    ================================================================

  • Well well. Glad so many found this useful, and that you have sites that works now 🙂

    My wysiwyg editor is still down, both the standard, and the minimal that comes with ACF – It is down on both post, pages and CPTs.

    If I deactivae ACF everything is good. If I activate again, the wysiwyg-bar disappears again 🙁

    Any suggestion on how to fix this?

    Thanks

  • Hi Elliot,

    Same problem here, and probably in many websites with computer/Internet related content – windows paths, windows registry keys, latex markup, some regular experessions, code snippets with escaping sequences are destroyed if someone uses ACF WYSIWYG to store them.

    Not to mention ASCII arts! :-))

    Solution mentioned by figureone seems fine for me also.

    Any plans for fix in near future?

    Thanks in advance
    Marek

  • Hi Elliot, just checking in to see if you have an update on this issue.

    As a refresher, the current version of ACF will delete backslashes in any wysiwyg field upon saving. This issue exists because the ACF codebase has an extra call to stripslashes_deep() to deal with old PHP versions running magic quotes.

    In my case, this destroys LaTeX markup in those fields, because every LaTeX variable starts with a backslash. Others have chimed in saying that their regular expressions get mangled.

    Your proposed solution seems fine to me. More details on it in your comment here:
    http://support.advancedcustomfields.com/forums/topic/regression-backslashes-stripped-in-wysiwyg/#post-4335

    Thanks!

  • I answer to myself. As often, it was a really simple and stupid detail : when I check post_type in the beginning of my code, I haven’t added my custom post type where I display my ACF WYSIWYG.

    My problem is resolved just adding my post type in the following line :

      // On vérifie qu'on est sur un article ou une page
  if( ! in_array( $typenow, array( 'post', 'page', 'custom_poste_type' ) ) )

  • It looks like the Google Maps issue was a conflict with All In One Event Calendar, so I was able to deactivate that plugin & make the changes I needed to (not really a solution, but a quick fix), but I am still not able to load the WYSIWYG.

    With the All in One Calendar deactivated, there are no console errors.

  • This doesn’t seem to work for ACF WYSIWYG’s – is there another solution?

  • Sorry, seems to be same problem http://support.advancedcustomfields.com/forums/topic/acf-wysiwyg-formidable-form/

    Fix from this thread is still working.

  • I’m not using the TinyMCE Advanced Plugin. I did an experiment with a clean WP Install that was on version 3.83. Installed ACF, Wysiwyg display HTML button. Updated to 3.9 HTML button disappeared

Viewing 25 results - 926 through 950 (of 1,299 total)
1 2 3 … 37 38 39 … 50 51 52