Interference with other plugins or themes notes on two things
Viewing 1 Posts - 1 through 1 (of 1 total)
Author | Posts |
---|---|
March 24, 2015 at 2:18 am 39830 | |
Nayem | Right now, there are two main interference type problems we have with the latest Dokan. The first is a bug in the code which can prevent other plugins from getting info from the developer's web site. For instance, when we have a plugin update, we provide 'info' on the new update including a changelog and description of the update. The Dokan bug prevents this info from our plugin from being displayed to the user--the Dokan bug essentially destroys update info from other plugins. The fix is simple. Edit the file 'dokan/classes/update.php' At the end of the function named 'check_info' around line 199 the code says: return false; It should say: return $false; Adding the dollar sign changes the return value to the first function argument (called $false) which contains other plugin info rather than the boolean false which destroys that info. This is a problem with all Dokan plugin versions we have seen, reported, and has not been fixed by WeDevs, but really needs to be fixed by them. Until then, make the above fix in your copy. The next problem is a theme interaction issue we have while using Kadence Virtue Premium Theme and may not be a problem for other themes. The problem manifests in the product edit of the seller's dashboard. Specifically, the tabs do not work and all edit items are in one long list. To fix this problem we edit the file 'dokan/includes/theme-functions.php' In the function 'dokan_edit_product_url' around line 704 in Dokan 2.0 there is a line of code that says: return trailingslashit( get_permalink( $product_id ) ). 'edit/'; That line causes the problem and can be commented out by adding two slashes to the beginning of the line as follows: //return trailingslashit( get_permalink( $product_id ) ). 'edit/'; This fixes the problem and then the tabs sort and organize the product data as intended. Similarly, this is a problem in all Dokan plugin versions we have seen. We do not know why this line of code remains in Dokan, but if you have a similar problem, try commenting out that line and see if it fixes the problem for you. |
March 24, 2015 at 4:57 pm 39892 | |
Nayem | Hello Brenda, Thank you very much for your solution. I believe your solution will help our customers. |
Viewing 1 Posts - 1 through 1 (of 1 total)