Yesterday as I was listening to a podcast (Windows Weekly, if I remember right), they were talking about how some browsers are distributed with certain plugins built in and ready to go, such as Flash. We all know how many issues Flash has, right?

So I began thinking, hold on… If any plugins in the default SnowCMS package have any vulnerabilities, an entirely new version of SnowCMS would have to be released because that installation package would need updating (I don’t want to update it without a version change…), but all existing installations would merely get the plugins update through the plugin manager, and their SnowCMS version would be different, and a fake update would need to be sent out to change it.

To me, that is quite pointless. So the idea of distributing SnowCMS with plugins is out. The plugins folder will be completely empty when you download the installation package . Plus, this allows other plugins which aren’t first party to have just as much chance to be picked as ours.

But of course! When you setup SnowCMS the very last step will mention the fact that SnowCMS, by default, comes with very little functionality, and there will likely be a list of plugins (such as link managers, page managers, stuff most people would intend to use SnowCMS for) with the most popular ones.

Just thought I would let you know

If you are wondering what’s currently going on, right now I am working on member management, which will require a new tool (the Table class, but more on that later), once the new tool and member management are done, I will start on an error log viewer (completely slipped my mind!!!). After that, work on the SnowCMS site will begin! So soon enough, SnowCMS.com will actually be powered by SnowCMS Why you may ask..? Because! Until the site is setup, I won’t know exactly how the plugin site will be setup, which is quite important to do before plugin management can be done

Till next time, cya!