froger-me / wp-packages-update-server

WP Packages Update Server - Run Your Own Update Server for Plugins and Themes
GNU General Public License v3.0
141 stars 39 forks source link

{feature request] Company and contact information as taxonomy #9

Closed claytoncollie closed 5 years ago

claytoncollie commented 5 years ago

Hi there. first off, thank you so much for this plugin and that it is open source. I have been using the plugin-update-checker library on a suite of plugins and had building a plugin like this on my roadmap. I am over the moon that I have found this plugin and really appreciate your hard work. Thank you so much! I was searching for the update-plugin-checker repo on github and this plugin popped up on Google. I was yelling in my office at my coworkers how pumped I was that I found this plugin. Seriously thank you!

I am in the early stages of setting this up and went through the exercise of adding a package. Everything was very straight forward in that respect. What I could see down the road is that typing in the person's name, email, and company every time will get cumbersome, especially when a single client has 4+ licenses. I was thinking to make this data entry more efficient that each license could be associated with a taxonomy term that is the contact. And then the contact term holds the name, email, company name, etc. So really just an idea, not a 'request'.

Thanks so much again. Really appreciate your hard work!

froger-me commented 5 years ago

Hi @claytoncollie , thank you for the kind words, and the suggestion! It is definitely something that would be really useful. At the moment I am focusing on other projects in general and pure maintenance for WPPUS specifically. However, I think it is possible to create a companion plugin that pre-fills the values of the form based on a taxonomy term, in a non-disruptive manner:

This way, you'd be able to achieve what you're looking for, and keeping it contained would ensure that if, down the line, the feature is added to core, you'd just have to disable your plugin, or at worst migrate the terms to a new taxonomy.

froger-me commented 5 years ago

Closing the issue.