Sorry if you don’t like the answers you’re getting. Though please don’t cross-post as your other thread about this was already enough.http://themeforest.net/forums/thread/codecanyon-extended-license-who-handle-the-support/129989
If I buy an extended license from CodeCanyon (for example ABC slider) and use on my theme, who will handle the support for ABC slider? Me or the author of ABC Slider?
Is it legal if I give the ABC Slider’s license key to buyer of my theme?
You should always be actively trying (as much as you’re able to) to provide updates to the user. By purchasing the extended license, you’re in a way also agreeing to be the “go between” / “middle man” for your buyers. You should never recommend / suggest to any buyer that they should contact the author the plugin for support. You should make updates as quickly and frequently as is practical (ideally within the same business week that the plugin author makes them available). This will mitigate support inquiries to yourself and potentially some of the unjust injuries to other party. Do your support and updates well and your buyers may feel they can rely on you for such things. Of course, there will always be a percentage that still chooses to contact the 3rd party author but that is made lesser when the theme author is responsive. Many may only seek another support route if their first choice is unsatisfactory while the rest may simply be ignorant (somewhat unavoidable) of the fact that they aren’t licensed to contact the 3rd party plugin vendor.
No, it is not permissible to give your Envato license key to anyone outside your organization. Keep it private. The key entitles the holder to support and is often the only way an author is able know to provide support. You don’t want to permit any buyer to get support / updates directly by giving away such info. They haven’t paid for the privilege and it could also be considered an abuse of the plugin author. Any extended license holder that does this should have the license invalidated IMO. However, if any buyer wants to have updates / support more directly, they can always opt to purchase their own regular license. You can actually suggest this remedy, should you be unable to appease or provide the level of service any particular buyer is after.
When will you perform? Nothing more admirable than following a dream and achieving. Good luck!
Well, apparently no one is interested and / or able to comment on this. While I find this somewhat surprising in this large community of talented professionals, I shall try to develop a solution myself then.
Stripe works great with WooCommerce if used from any given WP website itself. This post is NOT a request for a payment gateway that sends orders to Stripe. I already have that implemented. I’m using the extension available from WooThemes.com
What I’m looking for is an existing WooCommerce extension that either regularly syncs with or works in a PUSH type manner with Stripe to IMPORT / pull in new orders and create orders, customers, etc when an order was placed with Stripe outside of WooCommerce.
Why would an order ever happen outside WooCommerce? Well because sometimes orders will need to be processed using something like (card reader in person on smartphone rather than website) – http://www.innerfence.com/stripe-mobile-app-card-reader
Yes, I already suggested just using the website (responsive) as an app. It behaves much like one. However, it lacks the ability to automatically / quick read a physical / plastic card in a POS situation
Anyone know of anything like this? Thanks in advance for any useful information anyone is able / willing to provide.
Have you viewed the page source in the browser and checked to see whether the JS path is actually valid / resolves? Any errors in the console?
Regardless of whether you use “wp_enqueue_scripts” or no, if it’s a bad url then it’s not going to load. Where / in what file are you enqueuing? Are you using an hook to run the enqueue code? This is all not at all specific to VC but JS and WP.
Aside from that also have a look here for VC specifics when you’re sure of the rest – http://kb.wpbakery.com/index.php?title=Category:Visual_Composer
Well, the previous response was out of frustration of not finding results on debugging the issues after almost 12 hours, we had long known that TinyMCE 4.0 will bring issues. If you simply browse around you’ll find that there are many many people facing similar issues and all the blame will be given to the Plugin/theme authors and developers. Worst part is that TinyMCE 4.0 is not backwards compatible, several functions have simply been renamed/changed without a fallback.
I see. Venting of frustration is fine. Spreading misinformation, not so much. I felt the need to try to prevent any potential spread of misinformation here. I have no need to browse around as I’ve been directly involved in several such situations personally. However, I feel that is just the way of things. Plugin / Theme authors like us know what TinyMCE is but end users don’t typically.
Let them remain ignorant about such things, that’s one reason they pay us. That’s also why I purchase from others as I’m still ignorant of so much. There’s always someone smarter. Though if any author has procrastinated (or supposedly didn’t have the time to go) about fixing any such issues until the 3.9 RC2 / Final was out, I have little to no sympathy. That’s just bad form IMO. Good Luck!
WP 3.9 is one of the most unstable updates by WordPress so far. It has also meant death for many plugins using TinyMCE. Popular plugins such as Ultimate TinyMCE (over 2 million downloads) have declared end of life.
WooCommerce have already said they are not going to update. refer link.
, the compat3x does not work (link), The WP codex isn’t updated refer link ..I wonder why was there such haste to release it, when it was already known that upgrading TinyMCE to 4.0 would have issues and considering the impact of this on # of websites
LOL. You’re quite the drama queen aren’t you?
First off, I know change is hard. However, v3.9 isn’t as unstable as you claim. The release date was well known in advance. There were months where you could have tested more / provided more input during the betas and RCs. If you failed to get sufficiently involved then don’t blame the WP team.
Apparently, you’re unaware of the fact that Ultimate TinyMCE has only been Eol ‘ed because it’s been replaced with this (so not really dead) ...
WooCommerce is the brand rather the company. Woothemes will continue to update WooCommerce and the built in WC ShortCode will still work (no site breakage).
However, the ShortCode generator may just be MIA for a while. I know this can be fixed because it was already fixed on another plugin. It’s a TinyMCE issue rather than a WP one anyhow. If you’d done any amount of decent testing before release, you’d probably have already fixed it by now.
So, the sky is not falling and it’s really just your own stuff need fixing. They’re only dead if you decide to abandon them in their current state.