Of course, having already done your own due diligence you must have a recent backup that you can easily revert to, right?
It’s very poor practice to just update a live site (with fingers crossed) to any major release (WP v4.3 or WC v2.4 for example) without testing it on a staging server first if that’s what you have done.
“Major” updates typically don’t get applied automatically so you take your chances by upgrading blind like that. Sometimes it works out and other times not so much. The most prudent route is usually test first, deploy after.
With how much time is given to authors between releases, there’s little reason for authors and buyers not to try early releases and either fix / report the issues. There’s plenty of blame on both sides. What makes the situation worse is people who upgrade unprepared / without a disaster plan.
Much has changed in the many months since I posted that quote. It’s in it’s 2nd generation now and I use it privately for client sites. It’s quite a bit more modular now (no longer a monolithic plugin) and is comprised of multiple plugins (use what you want / ignore what you don’t). It’s been very well received by the modest userbase I have cultivated after some initial education from myself.
There’s no documentation or onboarding screen / process presently (though users seem to get along fine without them). Your comment serves as a good reminder that I should finally update the demo site perhaps as early as this weekend. I’ve been using the new version for while (even works fine with WP v4.3 / WC 2.4) but have let the demo go stale. Once it is updated, I’d have no issue letting you check it out.
Just send me a message through my Envato profile page and I’ll reply to your message when it’s ready.
While i like cheap prices as a customer, i always wondered why all the themes are so extremely cheap here. I mean, for a custom build website, you would pay several thousand Euros.
That’s likely just a lack of buyer education on Envato’s part IMO. Themes and a custom built websites aren’t even close to the same thing. Since you’re not getting a custom built site when you buy a theme. Themes sold here are not “really” turn key solutions either though often touted as such and still require a fair amount of time, effort and knowledge to make anything with.
Bespoke custom sites are even more than regular custom sites. The price Envato charges is still below the industry average but should never approach the cost of a custom site due to the stark differences between themes and actual custom sites.
Why do you think you need an application for this? Applications were made before mobile devices / web browsers could handle real functionality. That’s all changed now and having an app for each OS should be a secondary concern rather than a primary one. It’s perfectly fine to do both.
Doing what you ask may be made much simpler though if you add the functionality to an existing mobile friendly site instead. Then this would cover more device platforms than just those two.
XCode can’t be used for mobile platforms don’t run iOS. Even if this were not the case, ignoring platform differences between iOS and Android would frustrate users of each platform. Each app needs to implement platform specific optional guidelines to be a quality app.
Do you already have a mobile friendly / responsive site? If not, start there and only if you think you still really need it should you create separate apps. The site and and all the apps will need to be maintained separately and doing it right can be expensive. Having one site to cover it all will be much less work / expense to begin with. You can always add on later as you grow.
If you’d rather not do any of that, you might even be fine with a service like following – http://www.happytables.com
While not a requirement, this item would seem to exhibit a total disregard (not unique to your item) for the WordPress style guide and the platform itself. Your item shouldn’t look like a non native web app that was then turned into a WP plugin just to cash in the platform’s popularity. Even if that’s the only motivation (other than say – making great software), you could stand to be more subtle about it.
Perhaps if / when you redesign, consider adopting the WP Native styles, etc (as made abundantly clear if you search even just a little bit). That would be a distinguishing characteristic (way to stand out) right there since it sadly gets often overlooked.
I’m a virtual nobody on the web but here’s an article on the matter from someone who’s more well experienced and known (in WP circles anyhow). Be sure to read the comments too!
We Should Be Using The WordPress Style Guide – https://tommcfarlin.com/wordpress-style-guide/
Awesome article but definitely not for the TL;DR crowd. Lol.
Talks about way more than just Thesis. Very detailed and interesting read. I wasn’t an active WP user back then and find the history to be quite enlightening.https://poststatus.com/thesis-automattic-and-wordpress/
I do like the bit he said about clarifying the split by saying GPL PHP instead of just GPL by itself though. Even the 100% GPL items here contain items that aren’t 100% GPL which in turn means they’re not licensed properly. It’s inaccurate at best and disingenuous at worst. So, spelling things out more would be a good thing, right?
This is Matt Mullenweg’s take on the split license approach…
There is No Such Thing as a Split License – http://ma.tt/2015/07/licenses-going-dutch/
I’d be interested to hear how various Envato buyers and authors feel about WordPress items that are licensed this way?
Do you agree / disagree with Matt? Share your opinion.
+1 @ BoldBlocks.- totally agree on this.
Here’s an example of what not to do courtesy of the “CSS Hero” WP plugin. I don’t use it but have dealt with people that have / have had it installed. It uses ridiculous tactics like this. Sadly, you won’t realize what they’ve done until you’re already a customer. It’s almost like a punishment for buying it legitimately.
However, they apparently also felt the need to go above and beyond the norm to make things more difficult than even what has been described here. When you buy the product, you also likely won’t realize that you weren’t given the full product (source code) either like with most WP plugins. They purposely do not distribute the full source code but rather just a shell. It’s a client / server based plugin product. It’s not encoded or encrypted but simply incomplete.
What this means is that you’re only given what amounts to a client to connect with their server. It needs to phone home each time you invoke it’s user interface on the front end of your site. The license verification code that would otherwise be the attack vector for someone wanting to hack the system is stored remotely just out of reach which is good for them. If they’re ever down though, you don’t have internet access, the company goes out of business, etc – you’re pretty much screwed whether your license is real or not.