- This topic has 4 replies, 3 voices, and was last updated 4 years, 3 months ago by
cjwebdesigntt.
-
AuthorPosts
-
-
January 24, 2017 at 4:11 pm #7748
-
August 21, 2017 at 5:56 pm #8361
cjwebdesignttMemberI have the same issue. There is no documentation on what file you need to create for the widget to be displayed on the front end.
-
October 1, 2017 at 8:21 am #8401
cjwebdesignttMemberwow it’s been a month, no response. Can anyone point us to where the documentation for displaying the widgets html and css on the frontend?
-
October 2, 2017 at 2:13 am #8403
hughcMemberhttps://piklist.com/learn/section/widgets/ ?
Basically each widget can consist of either one or two files – if you do not define the form file, then the widget will have no options, it will just execute the single file you provide.
Please note that widgets currently break the Customizer in more recent versions of WordPress. @sbruner this seems to be one of the nastiest bugs in the current codebase. Given the way WP are pushing the customizer as a one-stop-shop for configuration, it is a deal-breaker for some, and makes me shy away from using widgets in production code.
-
October 15, 2017 at 11:02 am #8414
cjwebdesignttMemberI read that document hughc and I have the two files, I have the form where I have my configuration options. The issue comes with showing content on the frontend based on those configuration options. See screenshot from tomhodg. I have since given up on piklist implementation and documentation always seems to be lacklustre and did it the WordPress way.
-
-
AuthorPosts
- You must be logged in to reply to this topic.