Mtt
Mtt

@manton If I have a plugin removed from the directory, how will that work for people currently using it?

|
Embed
Progress spinner
manton
manton

@Mtt It won’t affect existing installs of the plug-in, but no one will be able to install it again. I’ve been wondering if we need an “archived” state for plug-ins to make this less fragile.

|
Embed
Progress spinner
Mtt
Mtt

@manton In this particular case, I think the existing setup will work fine. I basically want to pull a couple plugins and incorporate them within the theme. But without breaking existing installs.

|
Embed
Progress spinner
manton
manton

@Mtt Got it, thanks. That sounds okay to me too.

|
Embed
Progress spinner
Mtt
Mtt

@manton I'd like to remove these plugins from the directory but keep them working for existing users. Is this something you do on your end or a place where I can initiate/request it?

  • Tiny Theme Add-On: Browser Color
  • Tiny Theme Add-On: Add Fathom Analytics
  • Tiny Theme Add-On: Adaptive Photo Layout

Thanks!

|
Embed
Progress spinner
manton
manton

@Mtt I need to do that on my side for now. How would you feel if these are moved into an "archived" section, so they are hidden from normal browsing but could be referenced later if needed?

|
Embed
Progress spinner
Mtt
Mtt

@manton I’m fully on board with that.

|
Embed
Progress spinner
manton
manton

@Mtt Okay, I've archived those! They won't show up when browsing or via search, and they can't be installed, but the old links and upgrades will still work. I'm working on a developer dashboard so this is easier to manage later.

|
Embed
Progress spinner
Mtt
Mtt

@manton Perfect. Thanks! And I like the idea of the dashboard as well.

|
Embed
Progress spinner