We'll create fresh WordPress site with WTG Portal Manager Beta installed. You have 20 minutes to test the plugin after that site we'll be deleted.
Manage related content for a product or service in one place then offer it to visitors…in one place.
The job of this plugin is to pull related content of all types (even a WP menu) into one area for both visitors and administrators.
Everyone should have a better experience finding, updating, adding and removing information for the portals topic. That is goal number one. The
portal manager should streamline the creation of portals and guide the user to ensure no elements of the portal are missed. That is goal two.
What do you imaging the third goal should be in a plugin of this nature, let know in the plugins forum?
Translators needed to help localize WTG Portal Manager.
These donators have giving their permission to add their site to this list so that plugin authors can
request their support for their own project. Please do not request donations but instead visit their site,
show interest and tell them about your own plugin – you may get lucky.
These contributors helped to localize WTG Tasks Manager by translating my endless dialog text.
These contributers typed some PHP or HTML or CSS or JavaScript or Ajax for WTG Tasks Manager. Bunch of geeks really!
These contributors created graphics for the plugin and are good with Photoshop. The “fake celebrity pics” creators no doubt!
These contributors published videos on YouTube or another video streaming website. Please take interest in any ads that may appear while watching them!
Explanation of versioning used by myself Ryan Bayne. The versioning scheme I use is called “Semantic Versioning 2.0.0” and more
information about it can be found at http://semver.org/
These are the rules followed to increase the WTG Portal Manager plugin version number. Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
Browse the changes log and decide if you need any recent changes. There is nothing wrong with skipping versions if changes do not
help you – look for security related changes or new features that could really benefit you. If you do not see any you may want
to avoid updating. If you decide to apply the new version – do so after you have backedup your entire WordPress installation
(files and data). Files only or data only is not a suitable backup. Every WordPress installation is different and creates a different
environment for WTG Task Manager – possibly an environment that triggers faults with the new version of this software. This is common
in software development and it is why we need to make preparations that allow reversal of major changes to our website.