Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author SiteOrigin

    (@gpriday)

    Thanks so much for all the bug reports. I’ve logged all of these. Hopefully we can get them sorted out as soon as possible.

    Just out of interest, are you creating your own widgets using the Widget Bundle framework? It’s been our goal to make the whole framework as developer friendly as possible, so this is awesome. Please let us know if there’s anything else you’d like to see in the framework.

    Thread Starter Steve

    (@stevesicherman)

    Hi Greg, just a couple more:

    – the textarea field strips out all line breaks unless you enable allow_html_formatting.
    – I wasn’t able to get my own modules working outside the so-widgets-bundle/widgets directory. I tried following the instruction and used the hello-word example but I kept getting the same error (Fatal error: Class ‘SiteOrigin_Widget_xyz_Widget’ not found in …). I played around with the class name but couldn’t get it to work.

    I’m really liking working with the framework, it’s a much leaner solution than installing something like ACF or Piklist which are one of the few frameworks that offer widget support. Plus the preview support is nice.

    One suggestion I have would be for a slightly modified Select Posts screen that’s triggered from the Post field, it relies on the user already knowing the post title they’re looking for (via the autocomplete). If there was some kind of list of posts to select from that’d be a nice addition. Perhaps even making the posts selectable from the “This query returns # posts” screen.

    My other suggestion would be for field toggle support (show/hide fields based on other selections).

    Last suggestion! The ability to add a placeholder attribute on a field.

    Plugin Author SiteOrigin

    (@gpriday)

    I’ll take a better look at the allow_html_formatting issue.

    As for the fatal error, I spoke to our lead developer on the widget bundle project and he said that the hello-world example requires the latest development version of the widgets bundle. This version added the ability to use custom class names. We’ll be pushing a release with all these new features, but in the meantime, you can download it from GitHub.

    https://github.com/siteorigin/so-widgets-bundle

    I like your suggestion re: the post selector. I’ll log this as a feature in our issue tracker.

    I wanted to add some field toggling, but in the end we just went for using custom Javascript for each widget form. This gave us much finer grained control. You can see this in action in the Google Maps widget.

    Keep the suggestions coming – they’re gold ??

    Thread Starter Steve

    (@stevesicherman)

    Thanks I was able to get the widgets working in a separate directory.

    Last suggestion! A link field type that supports both external and internal links (the latter via autocomplete) would be great.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘A few post field type bugs’ is closed to new replies.