Title: Plugin Refactoring ?
Last modified: October 5, 2019

---

# Plugin Refactoring ?

 *  [cantoute](https://wordpress.org/support/users/cantoute/)
 * (@cantoute)
 * [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-refactoring/)
 * Juste to let you know, I’ve started to write a Cache-Control plugin that one 
   can rely on.
 * I’m managing around 100 wp behind reverse proxy.
    Some are on heavy load (100k
   + daily visitors) and I got tired of rescuing servers each time one plugin or
   an other blows all up.
 * So I’ll make it very simple (all ready > 500 lines ö) and I’ll try to make it
   smart (aka detect if settings imply reverse proxy) and cleanup any Set-Cookie/
   Pragma or Expire that could get in the way.
 * For most of it, I’m picking in this plugin the bits that have proven good (I’ve
   been using it for as long as I can remember messing with wp)
 * It needs a good refactoring… and a smarter admin (pain full to set one by one).
 * I hate writing php… and even more wordpress.
    My php is basic but I have 15years
   experience as sysadmin + dev and have switched to node
 * I’ll juste make the part that does the job – sets/fixes the headers – but I won’t
   get near making a wp-admin option page… as I said, I have no joy doing php, and
   wp-admin will just make me cry.
 * If anyone is up for doing the handy option page… I’m open to ideas and help.
   
   Other then that I’ll juste use a json to manage settings.
 * Publishing the plugin in SVN … same thing… too much for me.
 * But perhaps sharing what I’ll have could save others waisting their time on this.
 * I don’t make it sound like an exiting thing… But if one knows how to do an option
   page and an other how to publish the thing…
 * has anyone used this plugin ?
    [https://github.com/afragen/github-updater](https://github.com/afragen/github-updater)
   it could simplify the mission
    -  This topic was modified 6 years, 7 months ago by [cantoute](https://wordpress.org/support/users/cantoute/).
    -  This topic was modified 6 years, 7 months ago by [cantoute](https://wordpress.org/support/users/cantoute/).
      Reason: typo

Viewing 1 replies (of 1 total)

 *  Thread Starter [cantoute](https://wordpress.org/support/users/cantoute/)
 * (@cantoute)
 * [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-refactoring/#post-12002008)
 * This is where i have reached… still quite a bit to do but base structure is there.
   
   It doesn’t yet send the header, but this should be hapeing soon.
 * Going to use a plain php config.local.php one can edit in wp plugin editor
 * [https://github.com/cantoute/wp-cache-control/tree/dev](https://github.com/cantoute/wp-cache-control/tree/dev)
 * any comment/feedback welcome.

Viewing 1 replies (of 1 total)

The topic ‘Plugin Refactoring ?’ is closed to new replies.

 * ![](https://ps.w.org/cache-control/assets/icon-256x256.png?rev=1632145)
 * [Cache-Control](https://wordpress.org/plugins/cache-control/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/cache-control/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/cache-control/)
 * [Active Topics](https://wordpress.org/support/plugin/cache-control/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cache-control/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cache-control/reviews/)

 * 1 reply
 * 1 participant
 * Last reply from: [cantoute](https://wordpress.org/support/users/cantoute/)
 * Last activity: [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-refactoring/#post-12002008)
 * Status: not a support question