Timeline for Problem with using custom shortcode with ACF WYSIWYG field
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13, 2017 at 1:22 | vote | accept | aslamdoctor | ||
| May 19, 2017 at 16:53 | answer | added | aslamdoctor | timeline score: 1 | |
| May 19, 2017 at 15:17 | comment | added | aslamdoctor | colored-list is just an example shortcode I have used for the query, actually there are lot more shortcodes I have built which are being integrated with ACF so it's better to have some solid solution and not temporary. | |
| May 19, 2017 at 15:14 | comment | added | WebElaine | Maybe use a second shortcode? If the repeating content inside [colored-list] is similar you could add the correct <p> tags that way. Then just make sure there are no line breaks between the nested shortcodes. | |
| May 19, 2017 at 15:12 | comment | added | aslamdoctor | Yes I have checked it in text mode. Infact I used same content in Standard content editor that shows data on frontend using the_content() method and there it works perfectly. I have already contacted ACF support guys and they are telling me to remove wpautop filter. But that will make the content without P tags (even the needed one) which is again not a good result. | |
| May 19, 2017 at 15:02 | comment | added | WebElaine | Have you tried viewing the wysiwyg editor in Text mode and deleting line breaks? That may remove some of them. One other option might be to make the ACF field a text field instead of wysiwyg editor. You can include HTML in an ACF text field, though if you have non-techie users this may be a pain for them. If neither solution works, I'd suggest contacting ACF directly. One similar thread: support.advancedcustomfields.com/forums/topic/… | |
| May 19, 2017 at 10:38 | history | asked | aslamdoctor | CC BY-SA 3.0 |