725 posts WordPress Ninja
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has been a beta tester for an Envato feature
  • Has collected 10+ items on Envato Market
+8 more
TylerQuinn says

Is anyone else becoming annoyed with this?

When I first started making items I was making the download packages so that the user would have to unzip and read the documentation and either zip the plugin contents themselves or FTP the plugin to their site.

Obviously this was not ideal so I started packaging the documentation inside the plugin and linking to it from the plugin admin page. This has been working great until these new prefixes came along. Users are uploading the long name zips to their sites creating horrible directory structures such as:

site.com/wp-content/plugins/codecanyon-543758423-this-is-the-items-title-now/

Granted as long as you use correct wordpress hooks for your directories it should not matter but it looks like crap and is confusing some of the buyers when they go to install plugins. I get about 10-20 more tickets a week now of people asking what to do with the file they downloaded from CodeCanyon where they would usually just assume to upload it to WordPress.

I think there needs to finally be a required packaging method kind of like WordPress themes on TF. For instance if the long file names are causing the confusion add a message to the download page that users should unzip first and read the install instructions. Or make it like TF where you use the WordPress plugin bundle format as a requirement when uploading and state on the download page that WordPress plugins are ready to upload from the WordPress admin panel.

Either way clarification in this area for buyers would cut down on a lot of unneeded support tickets for WordPress plugins.

3310 posts
  • Provided great contribution to our forums
  • Nominated Community Superstar of the month
  • Helps us moderate the forums
  • Has been part of the Envato Community for over 5 years
+18 more
dtbaker Moderator says

I always zip up my plugin folder and put that inside the main download zip file.

To install the plugin, users unzip the download file to their desktop. They will see a README file and the plugin.zip file. The README file explains the user has to upload the plugin.zip file to their wordpress.

If they try to upload the main download file to wordpress it will simply not work. By having the two zip files like this you can control the plugin folder name.

Having the documentation within the wordpress interface itself is a great idea. All authors should do this.

Hope that helps!

Dave

725 posts WordPress Ninja
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has been a beta tester for an Envato feature
  • Has collected 10+ items on Envato Market
+8 more
TylerQuinn says

This is what I was doing before the prefixes were added and users complained. :( I guess its the lesser of two evils.

Let me ask this, if the user uploads the zip like this and the files are extracted are they left on the server? Then there would be a hosted copy of the .zip file containing the plugin inside that folder.

Helpful Information

  • Please read our community guidelines. Self promotion and discussion of piracy is not allowed.
  • Open a support ticket if you would like specific help with your account, deposits or purchases.
  • Item Support by authors is optional and may vary. Please see the Support tab on each item page.

Most of all, enjoy your time here. Thank you for being a valued Envato community member.

Post Reply

Format your entry with some basic HTML. Read the Full Details, or here is a refresher:

<strong></strong> to make things bold
<em></em> to emphasize
<ul><li> or <ol><li> to make lists
<h3> or <h4> to make headings
<pre></pre> for code blocks
<code></code> for a few words of code
<a></a> for links
<img> to paste in an image (it'll need to be hosted somewhere else though)
<blockquote></blockquote> to quote somebody

:grin: :shocked: :cry: Complete List of Smiley Codes

by
by
by
by
by
by