Using session_start() in your plugin without having it encapsulated in a function means that it will run on every single page load when your plugin is active. That means you've just broken caching for everyone because the way PHP Sessions work is they indicate the visitor using sessions is unique and should have a non-cached view of the website. This specifically breaks Varnish type caching.

Please remove this from your plugin, or put it only in the function that absolutely must have it.

----

Please make sure you've addressed ALL issues brought up in this email. When you've corrected your code, reply to this email with the updated code attached as a zip, or provide a link to the new code for us to review. If you have questions, concerns, or need clarification, please reply to this email and just ask us.

# Any redistribution of this script without the expressed written consent
# of Virtual Solutions is strictly prohibited.

Also, this clause is unenforcable by us:

"Copying any of the code
# contained within this script and claiming it as your own is also
# prohibited."

For what it's work, Copyright notices can certainly be required under the GPL (though that's worded a little abnormally for GPL code), but we cannot accept the plugin with the requirement to get permission before distribution, as that flies in the face of GPL.

It's required that all code be compatible with GPL to be included in our repository.

For more information on what types of licenses are compatible with GPL, please review the following links:

A readme.txt is needed so your plugin will display correctly in our repository, but also so we can make sure you're providing the users with all the information they need before they install your plugin. Our goal with this is to make sure everyone knows what they're installing and what they need to do before they install it. No surprises :)

This is especially important if your plugin is making calls back to your own servers. For the most part, we do not permit offloading of images or code, however in the case where you are providing a service (like Disqus or Akismet or Twitter), we permit it. The catch is you have to actually explain this to the layman in your readme, so they know where data is going.

Keep in mind, we don't want to see a readme.MD. Among other things, the formatting for markup is different, and the filetype isn't read by our system.

Please send a link so the completed plugin can be downloaded. Alternately you can reply to this and send a .zip or .rar file. As this is for a new plugin request, please reply within seven days of this email or we will reject your plugin.