Add support-related links to plugin options page

[raamdev]

As mentioned in #610, it would be nice to include several support-related links at the top of the plugin options page:

I would add Knowledge Base, Support, and Blog to the Pro version, and Knowledge Base, Community Forum, and Blog to the Lite version.

[jaswrks]

@renzms This might be a good one for you to tackle, since you have already worked with this specific area of the code in ZenCache before. Would you like to give this a shot? If so, let us know so that we can assign this to you. Thanks man! :-)

[renzms]

@jaswsinc @raamdev

Sure, I'll take this one!

I would add Knowledge Base, Support, and Blog to the Pro version, and Knowledge Base, Community Forum, and Blog to the Lite version.

These should all open in new tab/window correct?

[jaswrks]

:-) Cool!

[renzms]

@raamdev

On your link for the blog I think you meant: http://zencache.com/blog/

Your link up there currently goes to: zencache/blog/

[renzms]

@raamdev @jaswsinc Tested, submitting PR

[jaswrks]

ha. It would be cool if we owned http://zencache

[jaswrks]

Better: zencache://blog

[raamdev]

@renzms I made a few tweaks (see wpsharks/comet-cache-pro@38806c7 and wpsharks/comet-cache-pro@f2da851) and I'm attaching screenshots below.

Lite version

Pro version

In the Pro version, the mailing list links are moved up to make use of the space vacated by the Pro Preview and Pro Upgrade links, which are not shown in the Pro version.

The Plugin Updater and the Stats/Charts page has also been updated:

[raamdev]

Next Lite Release Changelog:

• Enhancement: Added support-related links to the plugin options page.

[raamdev]

Next Pro Release Changelog:

• Enhancement: Added support-related links to the plugin options page.

[raamdev]

ZenCache v160222 has been released and includes changes from this GitHub Issue. See the v160222 announcement for further details.

---

This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#612).