Any word from Envato staff on the scenario I presented above? I know that the terms do allow you to register on behalf of a “third party (which may include your employer or other entity)”, so clearly this is allowed. So what if you work for a big company and you create an account on their behalf. When you quit, the company should keep the account. The same principle should apply for a company of one. If I register an account on behalf of FillerSpace Inc, and then resign, the company should still own the account. If someone then buys FillerSpace Inc, the account did not transfer, it still belongs to the same company.
Technically, you could transfer your membership, even though the terms say you can’t. You are allowed to register on behalf of a third party (e.g. your employer or business). You can then sell the business that owns the account. The membership still belongs to the business, so no transfer took place, but the business belongs to the new owner.
Los Angeles, CA, USA!
jonathan01 said
Never ever ever set any folder on your server to 777
Unless it’s not connected to any network 
Thanks for your replies. If the question ever does come up, I found something that looks promising:
add_filter( 'locale', select_language );
function select_language( $locale )
{
//array of all known translations
$translations = array(
"es" => "Spanish",
"es_ES" => "Spanish (Spain)",
"es_MX" => "Spanish (Mexico)",
);
if( !isset( $translations[$locale] ) )
{
//full local isn't in array, remove country code
$locale_lang = preg_replace( "!_[A-Z]{2}$!Uis", "", $locale );
if( isset( $translations[$locale_lang] ) )
{
//language only file exists, return this
return $locale_lang;
} else {
return $locale;
}
}
return $locale;
}
That works if the person thinks to just use the language code, but the problem is what if they include the country code too, but I don’t have that specific po/mo file? Consider this:
Language directoryes.po es.mo es_MX.po es_MX.mo es_ES.po es_ES.mo
define ('WPLANG', 'es'); //Works, I get the default Spanish translations
define ('WPLANG', 'es_ES'); //Works, I get translations for Spanish spoken in Spain
define ('WPLANG', 'es_MX'); //Works, I get translations for Spanish spoken in Mexico
define ('WPLANG', 'es_CO'); //Broken, no po/mo file for Colombia, I get English
I would expect logic to check for Colombia first, and then fall back to just Spanish (es.po/es.mo)If I have po/mo files named es_MX and I set WPLANG to es_MX I see the translations. If I name the po/mo files to es and set WPLANG to es, it works too. My question is, why doesn’t WordPress fallback to es.mo when I set WPLANG to es_ES (which doesn’t have po/mo files)? I want to have a general translation for a language, and specific ones for certain countries, but I don’t want people to have to just choose es if es_ES is more appropriate. Is there any way to fall back to just the language if language_country doesn’t exist?
Themico said
Or can try your luck on CodeCanyon. Think on the idea and write a plugin (jQuery or WP), and if its become popular then you can make nice money for a long time. Of course, a lot of items on CC are not profitable (or low), but if you really come with great idea and item that make life easier for many people then you will succeed.
I have gone back and forth about going this route. I had a few ideas I wanted to build into a WordPress theme, but I wasn’t ready to build a whole theme. I considered making some of the most prominent features into plugins for sale on CodeCanyon, but the math just doesn’t add up. Most plugins on CC are $10-15, and the extended license is only 5x. So for $50-75, someone can buy an extended license for your plugin and include it in a theme that sells for $40-$55. It makes more sense to go the theme route, even if you have to learn design, or better, find a designer to make PSDs for you. It would be better to give the designer a flat rate if you can afford it, rather than a percentage of the sales. I thought about goin
At the very minimum, you have to let users change colors and customize the layout. You could do that with several preset color schemes and several versions of each template type, or you could use a full-blown options panel and page builder. The popular files tend to have the latter, and they sell 75+ themes per week. The demo should be pretty comprehensive, so users can see every variation first hand, because they won’t read the description past the first bulleted list. I would expect very few sales for your first theme (unless it has an amazing design and truly unique features) because buyers won’t trust you yet.
000000 Ninja style!
