I will keep the content of this post for logging purposes, but all further information and updates will be available on the WordPress plugin page. The version that I offered for the very first beta release is no longer available. If for any reason you still wish to obtain it, please contact me directly with a short summary of your reason.
The latest version hosted on the WordPress repository can be downloaded right from here:
To install, please read this post for the plugin requirements. Then if everything sounds good, copy the extracted contents of this download to your WordPress plugins directory.
Over the next few weeks this post will be updated regularly to accommodate for general information on my WordPress plugin called Extensible Widgets. This plugin started as a collection of widgets that I developed over time and used in numerous projects. I eventually merged them into one conglomerate which is now known as the Extensible Widgets plugin. Currently I do not have extensive documentation on the plugin functionality and code-base yet, which is why I mentioned that I intend to update this post regularly. A Quick summary is that this plugin in its current state is a PHP widget class manager, as well as a collection of useful widget classes that build on each other for extended functionality. When the plugin is first activated, the widget classes included are not registered automatically, and will not appear within your WordPress widgets administration page. To activate your desired widgets you must go to the Extensible Widgets Registration page. From there you can read a short description before registering anything. This plugin also comes with an Export and Import page. You will notice this functionality is very useful in backing up your current data of all your widgets and Extensible Widgets settings. I felt this was a major necessity since while using Extensible Widgets these little pieces of data suddenly turn into major aspects in the whole of your website. I needed to give an acceptable method of retrieving, backing up, and restoring that data if something bad happens.
Version & Requirements:
This plugin is released in beta. This means that it should be functional on most and hopefully all supported platforms, and any bugs brought to my attention will hopefully be squashed in due time. This plugin requires PHP 5 and above. Sorry PHP 4, it is time to upgrade. I do not want to rewrite my entire code-base for hosting providers that do not believe a language version over 5 years old is stable enough for an upgrade. What I will also mention is that the plugin should be PHP 4 testing compatible. This means that you should be able to install it, just not activate it. The PHP 5 bootstrap should not load until the version check has passed successfully. Well, as I said before, this plugin is beta, and I am just trying to get it out there. I hope people try it out and give me any feedback and bug reports you may have. If this thing becomes more popular than I anticipate, then a better method of reporting submissions will be provided. For now, I think this post will suffice.
Changelog:
- 0.7.1 ~ 02/07/2010: Well, I am going back on the previous log in continuing to log here, but oh well. I realize that this is actually a good place to post pre-updates, or ‘current status’ kind of logs. Therefore I will post that landykos has reported more errors on a Windows server regarding a serious PHP bug and preg_match with Windows file system paths. I am in the process of sorting this one out.
- 0.7.1 ~ 02/05/2010: The plugin has been committed to the WordPress SVN repository, and all following changes will be logged there. For the time being, this will be the final log entry within this post.
- 0.7 ~ 02/03/2010: WordPress has approved this plugin, and I will be undergoing the hosting transition to the plugin repository. This will be happening at the same time as the fixes for the errors mentioned previously.
- 0.7 ~ 02/01/2010: landykos pointed out to me many errors occurring on his Windows platform running PHP 5.3. I believe I have identified most if not all of these errors, and will be trying to fix them shortly. Most of them I believe are due to path discrepancies, which may have been a little laziness on my part, I apologize. I will post a new version and update this log when I do. Thanks!
Screen Shots:
Leave a Reply