8 Comments


  1. This is a great resource. With the push for more functionality in the Customizer this type of solution will be a great help to people wanting to get things done quickly. I’m putting this repo on my watch list.

    Reply

  2. The customizer needs better organization if it’s going to be the go-to place for anything more than basic configuration. It will become quite easy to just shove dozens of settings and then the side panel will become very cluttered with no standard hierarchy. Right now with the Widget customizer baked in, there are a lot of setting panels if you have a lot of widget areas. I have seen quite a nice idea for a solution by the team that worked on the widgets that would solve it though.

    Reply
    1. jpelker

      “I have seen quite a nice idea for a solution by the team that worked on the widgets that would solve it though.”

      Can you point to this solution? Thanks!

      Reply

  3. The Google Fonts Dropdown has built-in caching, which creates a cache file on the user’s machine so that you don’t have to call the API so many times.

    There are three things that can be improved with this approach.

    First is the direct use of the file system for caching, which will not work in any non-single-server environment. Caching the list using the Transients API is a much better and more efficient way.

    Second is the use of fopen() and fwrite() to write to the file system, which should probably not work in a secure hosting environment for anything outside of wp-content/uploads. A good alternative is the proper use of the Filesystem API.

    Third is the direct use of cURL, which means it will by-pass any logging or debugging scripts, proxy settings, timeouts, and will also fail if cURL happens to not be installed on the server. Using the WordPress HTTP API is the preferred way for remote requests.

    Reply

    1. Thanks for your feedback Konstantin! Maybe I can get Paul Underwood to drop by and check it out.

      Reply

    2. All good points Konstantin, this was originally a proof of concept project I haven’t updated it for a long time.

      With the exposure that the project is getting I think it’s time for an update. I’ll include your points in the next update.

      Thanks
      Paul

      Reply

  4. I was wondering when something like this would be created. Sort of like a starting ground for adding things to the customizer. Last I hear, it wasn’t the easiest thing in the world to do. However, as Peter mentioned, some sort of standard or organizational concepts will need to be hammered out before everyone starts putting everything and the kitchen sink into the customizer, ruining its purpose.

    Nice work Paul.

    Reply

Leave a Reply