I think this would be much clearer if the support definition was available first.
If the definition of support is very clear then it will certainly cut down on majority of support abuse, and I really don’t think we will get buyers abusing the system (asking for feature requests, customisations, incompatibilities between themes and plugins, etc..).
So if someone pays for extra support and then starts complaining that they need a new feature, too bad, it will be clearly defined they are not allowed to ask about this. So we will have an official ruling to fall back on.
This is good!
They all use decent caching and reverse proxies like nginx. You’re basically getting a static copy of WordPress without going through the hassle of manually making a static copy
(i.e. nginx will look for a cached html file that was automatically generated by WordPress, if it finds it, that gets sent to the client, if it doesn’t find it, it hits Apache/WordPress/PHP and generates the static cached files automatically for next time. And if there are login cookies present or certain “shopping cart” ajax calls are made, those are not cached, so you can have a fully static html cached WordPress theme but still have things like shopping cart quantity updated via ajax just fine, and you can still login to WP and make changes, it’s all rreally good ).
theodisbutler saidhttps://github.com/dtbaker/wizvato (ignore the wordpress plugin stuff in there). Theme is from materializecss, check out their website.
dtbaker saidI am seriously looking for the link to github. I want that theme!
Feel free to fork on github
Anyway, your Wizardo is nothing compared to what I’m bringing out. It’s going to take your entire army of developers to win first place against me.
Woohoo, can’t wait to see it
It looked like it is now possible to verify a purchase simply by authorizing the user with Envato
I thought so too originally, but at the moment it’s just the old API (plus search) on a new framework. The OAuth stuff does let them implement this in the future though, so it’s a big step in the right direction (see post above)
In theory, something like this wouldn’t really work from a WordPress theme or plugin, though, right? They would need to enter some sort of purchase code, license key, or something saved in there, that WordPress can use in the background.
Think of it the same way as a buyer can “login” from your theme and you can get their email address/username from the API. Hopefully they add a new similar endpoint that returns the list of purchases/codes. So in the same way we can get email address, we should be able to get purchase code. Once we can get the purchase code from the API then we can do background processing. All new features and I’m sure would be really complicated to implement but I’m hanging in there.
Ideally it would be a single button in the theme “login to verify purchase”. No keys or anything.
Okay, thanks! I still can’t get the URL the API returns to work in WordPress since the update but I’m hoping their support can shed some light on that. Still awaiting their response though
With the URl that comes back, are the parameters encoded? e.g.
?foo=1& amp ;bar=2 ? does the URL work when pasted in your local browser? what happens when enabling WP_DEBUG and echo’ing the output from wp_remote_get using the new URL? sorry don’t have time here to test the output
I’d like to introduce Wizvato – a wizard to help buyers find items.
Select a category:
Highlight which items you like, and quickly see which items you don’t like:
View more item details, add your own personal notes, and easy navigation between search results:
Here she is: http://dtbaker.github.io/wizvato/wishlist.html
(it’s not complete, I was just too excited not to share, I still need to add a “summary” showing all your highlighted items at the end)
Feel free to fork on github