70 comments found.
HI, Its been 2 hours we have renewed our support and we are not getting the access to the support forum. I’ve tried refreshing the page nothing happens.
Contact me though profile contact form with purchase ID, and I will check it out. But, I run manual check for all purchase ID’s for this plugin, and there is no change in any of them for support status. It is possible that Envato API takes longer to note the change on Envato side.
Hey Milan,
thanks for the update. What’s the safest way to apply this? Should we just replace the plugin folder with the new one?
Yes, that will be OK, and there is nothing special you need to do after that. I have updated my website via FTP and it is in testing for few days, works OK. Make sure to set new API access (if you have not done that already), because old, legacy API is now completely removed from the plugin.
Attention script users: the script doesn’t protect your content. Enter /feed at the end of your forum URL and you will see the full list of topic and even replies from “protected” forums.
Thanks for reporting, I will add option in next version to disable feeds.
Hi Milan,
looks like there is a problem with the API authentication. No one can post comments or open new topics on our support forum.
Is this something you know about? Envato API seems to be operational.
I can’t see any issue, plugin works on my website correctly, and no one else reported any issues.
OK, thanks. I’ll try to investigate the problem on my end. The plugin actually works, but clients can’t post on existing topics or create new one. They get “Error: Your topic/reply cannot be created at this time.”
Also my bbpress-nverify error log is full of messages like this:
[2017-05-04 12:25:34] : http_request_failed – new api : https://api.envato.com/v3/market/catalog/item?id=10482415&site=themeforest [debug trace] : require, require_once, apply_filters, WP_Hook->apply_filters, bbp_template_include, apply_filters, WP_Hook->apply_filters, bbp_template_include_theme_compat, BBP_Shortcodes->display_topic, bbp_get_template_part, apply_filters, WP_Hook->apply_filters, sbv_bbpress->bbp_get_template_part, sbv_bbpress->protect, sbv_bbpress->check, sbv_forum_list_required_items, sbv_api_loader->item, smart_envato_api_build->item, smart_envato_api_build->api, smart_envato_api_build->_data, smart_envato_api_build->run, smart_envato_api_build->_fetch, smart_envato_api_build->_load [error message] : cURL error 28: Operation timed out after 29022 milliseconds with 765 out of 14149 bytes received
But the API is operational and wasn’t down for the last few days.
Mhm… I just saw those are all old messages.
This type of message shows that API was down (30 seconds timeout) 2 weeks ago.
And ‘Error: Your topic/reply cannot be created at this time.’ has nothing to do with my plugin, my plugin is preventing forms to be displayed, and this error is related to bbPress problem on save of the topic. I am not sure what this is, but it is not related to my plugin.
OK, Thanks. I’ll try to investigate more on my end.
Great work 
GL
Hello,
I have started using it and definitely loving it. Can you please also block replies created by users for non-logged in users?
Non logged users can’t access forums/topics protected by the plugin, and they can’t reply in such topics. I don’t understand what you need to block?
I am actually talking about replies thread, like this one: https://ipanelthemes.com/kb/support/users/edavies/replies/
I get it. This goes to the features request list.
It is either problems with Envato API or you have set the personal token wrong (wrong permissions).
Hi GDragoN,
Great plugin, Is this plugin compatible with the latest WordPress and bbPress versions?
Thanks
Yes it is.
Is that plugin compatible with the latest changes in the Support policy? I mean if it will detect the support expiration or not.
Yes it is, it has options to control the support expiration.
Hello, just purchased. you did a great job. can you add little bit more functionality? if you add register option with envato api token and automaitcally validate purchase code (look at this plugin for register functionality: http://codecanyon.net/item/wp-envato-login/12323888) for customer purchased item so it will be more hassle free and easy to use for customer (although it’s already easy to use). what you think?
I plan to do that, but it would require major changes and rewrites to the plugin and I currently don’t have that much time to do all that.
Also, there are limitations to the way Envato API OAuth works that makes creating plugin for it complicated to the end user, and Envato is yet to create proper OAuth authentication for plugin type apps like other websites like Twitter or Dropbox have.
Hey Milan,
could you please advise what would be the best way to upgrade to the latest version? Would it be OK if I just upload the new files overwriting the old ones via FTP?
Nothing special needed, remove old plugin files, and upload new files, plugin settings are not affected with the update. Once it is done, revisit plugin settings and check out new options for Support check.
OK. Thanks a lot!
Hello,
Just purchased your plugin and will be setting it up shortly. Do you have any information on the function/method call I asked previously?
2. If I manage to get the purchase code per users, then can you suggest me some sort of function or method call for your plugin to register those purchase codes for mentioned user? I am not really asking you to tell me anything about the older plugin I am using. I am just asking if you have any sort of predefined methods/class/function which can be used to attach purchase code for specified user programmatically.
I hope to release new version in the next 3-4 days.
Very well. In the meanwhile, a hint for which file should I look into to get some understanding of the related functionality?
Bdw, the older plugin has purchase code/user_id pair stored in a separate table. So I think it should be easy for me to write a plugin for import. Once it is done, I will be happy to share it with you 
The change is not in a single file, it requires few changes, and I can’t tell you what to change right now, I don’t know it myself yet.
Very well. I will wait for the release then.
Hello,
Any news on the release yet?
It is out for few days already.
Thank you. Please let me know what function/method do I need to call in order to programmatically assign a purchase code to a user. I read the developers doc, but couldn’t find anything.
Also thank you for the added action hooks.
Function is in documentation (developers guide) and it is: sbv_add_purchase_code_to_user. But be aware, this is slow function, because it needs to validate each purchase code through Envato API to get needed data.
Yes I understand. What I will do is create an ajax interface to import purchase codes from the previous plugin. Once done, I will share it with you too.
Thanks!
Hi, this is just in regards to the comment made before this one, from @iPanelThemes. Just wanted to say that I actually use his referenced theme for my own support forum, along with your plugin to handle Envato licenses, and so far, never had any issues or problems with using either of them together.
Thanks for the comment. I had no issues with any theme so far.
Hello,
First of all thank you for developing this plugin. From the screenshots it looks really great. Before I buy this, I do have a few questions:
1. I use a theme I have developed for my support forum: https://github.com/swashata/ipt-knowledgebase-theme-wp It has many custom bbpress templates. Will your plugin override the ones managed by theme?
2. I have been using this item for a long time and I do have a lot of customers with their purchase code. I am thinking about making an import script. Any help with that would be very useful.
Hi,
1. Plugin is not replacing bbPress templates, it adds own templates (you can override them in the theme to customize them), and intercepting bbPress templates loading only.
2. Plugin is using format that is not simple, because of the different plugin features and possibilities to configure individual forums, track code support… So, it is not simply to copy data, it has to be proper object format for different things. I have no idea how that other plugin kept data for users and forums settings.
Milan
Hello,
1. Could you please give an example as to where plugin’s templates are used? I guess I can manage to modify my theme to match with your plugin.
2. If I manage to get the purchase code per users, then can you suggest me some sort of function or method call for your plugin to register those purchase codes for mentioned user? I am not really asking you to tell me anything about the older plugin I am using. I am just asking if you have any sort of predefined methods/class/function which can be used to attach purchase code for specified user programmatically.
1. Templates are used for everything displayed to user. Documentation lists all template files and what they are used for. You can copy any of them into theme folder (like other bbPress templates) and customize them (while keeping PHP code that is required to connect with plugin).
2. There is no such function right now, but it will be added in next plugin version (next week).
Milan
That is great. I am a little occupied with releasing another version of our plugin. After that I will continue work on the knowledgebase theme and also integration of your plugin into it.
Hi,
love the latest additions … plugin is getting better and better with each update. Dealing with the new support policy now, I was wondering if another feature would be possible: Exclude users (maybe via user ID in a simple textbook or as metadata to the user directly) from the valid support package requirement. That way, one can keep the forum accessible for users that bought an item prior to the new support policy getting introduced (before 09/01/2015), while all users that bought after that day do need a valid support package. Basically, grandfathering in existing users.
Tekanewa
I think an even easier way would be to simply provide a checkbox in the plugin settings, which (if activated) will prompt the plugin to fist check if the purchase date is prior to the date the new support policy took effect (09/01/2015), and if so, simply ignore the “support valid” date and only check the license key. That way, there is no need to manually “mark” users and all users that purchased before that date will still be able to access the forums, which is something I would really like to offer to my users.
Tekanewa
Thanks, both suggestions are good. Tekanawa’s suggestion for date check is easy to implement, and that will be added very soon (late next week). If needed, I can work later on the user exclusions.
Please, let me know if support check is done correctly, this needs more testing, and any information is useful.
Milan
That sounds great!
I tested the support check yesterday with another user in my forum that has an expired support, and it seems to work correctly. The only thing that ALWAYS returns a wrong status on my end is the API availability check, but you already stated in the plugin settings that this is still experimental.
Tekanewa
Testing that will be a problem, unless I catch another long downtime period for API.
I understand and I deactivated that feature for the time being.
Tekanewa
Hi, first of all thanks for creating this plugin, just purchased and now testing it before using, encountered an issue about support status check;
- checked “Use support status for each item to limit support access” option.
- checked to Protect : Forum – Topic – New Topic Form – New Reply Form
- registered as a new user, entered a purchase code to unlock a forum created before
- that purchase code’s support period is over in 1 march 2016
- however that user can still create a new topic in that forum or write a reply.
what is wrong in this scenario?
Thanks for reporting this. I will need to recheck things, and late you know once I get some more information.
This works for me. Check out the user profile page in bbPress, purchase code is listed there, and support expiration is also included.
I plan to release 3.2 version in a few days with some improvements to the support expiration.
I have finally found what the problem is, and it will be fixed in 3.2 soon.
Hi again, thanks for the update, looking forward to it.
I also have a few more feature requests;
1- an option to show the first topic only even if the forum is protected and even if the user is not logged in. That would be really good for SEO, as google would index thousands of topic pages with meaningful first topic’s content.
2-) an option to “show all protected forums to the customers” (a customer : is a user with at least one valid purchase code). So a customer can see the topics and replies of all protected forums, however, can only create a new topic or reply to a current topic in a forum if only he/she has a valid support period for that forum. This would be very useful; some topics are useful to other forum users as well.
if you add these features as well, we are willing to purchase a new extended licence of the plugin just to support you.
Thanks.
Hi,
Problem with both requests is that there is a limit to what it can be done considering bbPress templates system.
1. Plugin replaces whole template (no other way), and you want to show lead topic, so that requires to mix original and protection template. That can’t be done, considering that most themes with bbPress support have own versions of templates and they are not universal in that regard. In theory, you can override template my plugin adds and modify it to display the topic lead, before the protection notice.
2. This is hard to achieve considering that again we need to work with bbPress templates that can be very different from theme to theme, and on top of everything it requires new forum loop to filter forums by user and protection status.
I will not be able to add these features, but they can be achieved with custom coding to fit the specific theme.
Milan
ok, i see, thanks for the tips. do you have an estimated release time for the update 3.2
In about 2 days.
great, thanks.
Hi GDragoN, we’ve been seeing a lot of 403 errors from customers recently – does this have to do something with the new API changes?
Log shows this
[2016-03-17 10:22:37] : request_error - [new api]
[request url] : https://api.envato.com/v1/market/private/user/verify-purchase:PURCHASECODEHERE.json
[debug trace] : do_action, call_user_func_array, sbv_ajax_loader->verify_purchase, sbv_api_loader->verify_purchase, smart_envato_api_build->verify_purchase, smart_envato_api_build->api, smart_envato_api_build->_data, smart_envato_api_build->run, smart_envato_api_build->_fetch, smart_envato_api_build->_load
[error message] : 403: Forbidden
Many users are reporting API errors, and it is problem on Envato side, so until they fix it, there is nothing to do.
Sure, thanks for the quick response!
Hi,
Report: If you’re trying to open your own profile page, then you’re getting error – http://screencast-o-matic.com/watch/cDnubX1Qlw – Other profiles available for browsing without problems.
Regards, Igor
If your plugin is set correctly, this can happen only if the Envato API call fails for some reason. Same code is run regardless of the user you are viewing, because that code should display link to Envato user account set in plugin settings.
Try to clear cache in plugin Tools panel and try again. I will add handling for this in next version, but I believe it is API error.
Milan
Hi Milan,
Many thanks for reply. Yes, it happens on localhost without Envato key. I really appreciate your work. Amazing plugin.
Thanks again.
Regards, Igor
That’s it then. I will add extra check for this, just in case to avoid the display of warning.
Hi, this sounds like a great plugin, however i wonder if validating user purchases can be done better. Instead of validating each item in its related forum with purchase code, how about getting an api key from the user when the user is signing up and then check user’s purchases via get /buyer/list-purchases or get buyer/purchases method of the new api. If that’s possible it would automate the whole purchase validation per item/forum process. Such as when user bought a support extension or a new item, he/she wouldn’t have to look for purchase codes anymore since future purchases can always be validated with just the api key. What do you think of that?
Right now Envato OAuth implementation lacks some features to make this properly to work across every website where plugin is installed. I have contacted Envato about that when new API was made public, and 6 months later, they did nothing to change the way OAuth works with Envato API.
I can make plugin use OAuth, but that will make installation of the plugin complicated and prone to problems because each plugin user needs to make own Envato app, and not just get the token.
Hi,
1 – Does it work with new Envato API?
2 – Does it handle somehow a support period of item?
Regards, Igor
1. Yes. You can switch to new API if it is not already set. 2. Yes. There are options to enforce the support for support expiration.
