Forum Replies Created

Viewing 15 replies - 31 through 45 (of 45 total)
  • Plugin Author maksbd19

    (@maksbd19)

    Thank your for your review.

    Plugin Author maksbd19

    (@maksbd19)

    To modify the the default view of the gallery you need to copy the ‘templates/profile/gallery.php’ and ‘templates/profile/video.php’ files in your active themes directory’s ‘ultimate-member/templates/profile’ folder.

    For now I wouldn’t recommend you to change the attribute as when you upload an image it would dynamically inject the image preview code in the gallery. I will modify the core to allow users to change it shortly.

    I’m submitting a patch for now that would allow you to change the default photo viewer plugin. Please update the plugin.

    I’d love to hear more more bugs and enhancement suggestions.

    Thanks for your feedback.

    I just had this problem and the following is my solution. Hope this might help someone in future 🙂

    $product = new WC_Product($product_id);
    
    if($product->product_type){
    	// as the product has a type that means the product exists !!!
    }

    Plugin Author maksbd19

    (@maksbd19)

    @garethjohnvaughan I don’t see any SHASIGN in the return url of your shop. are you sure that you are doing it right?

    Plugin Author maksbd19

    (@maksbd19)

    since there is no more inquiries, i’m marking this topic as resolved.

    Plugin Author maksbd19

    (@maksbd19)

    Thank you for using my plugin.

    I need you to do a thing for me. You need to paste the following code in the empty space before the line 567, before the the code – if( strtolower($shasignxy) == strtolower($SHASIGN) ){

    the code to be pasted-

    var_dump($_GET);
        		var_dump($x);
        		var_dump($_GET);
        		var_dump(strtolower($shasignxy));
        		var_dump(strtolower($SHASIGN));

    This code is to find out where is the real problem occuring. This is the place where the plugin verifies the transaction. Check that both the $_GET and $x arrays contain the same elements (key value pairs). Then check the $shasignxy and $SHASIGN are the same. If the last two are not same, you’ll get that error.

    You can see in the codes of some preceding lines that $x is just storing the values delivered by the Barcleys and hashing them based on the SHA-OUT code. So if the problem is arising frequently then you need to be sure that there is problem in the values which are used to generate the pass phrase.

    Now you need to try to recreate the pass phrase (shasign) by digesting the key value pairs and check if they matches in any point. You can simply comment out any key => value pair from the array $x and reload the page where you’ve seen the text ‘Transaction Verification Error’.

    Please this is a trial and error process, so that don’t become impatient. But first I will recommend you to read the instruction manuals of Barcleys to get a better understanding of the parameters and how to configure them.

    Please drop a comment what you’ve got after trying this. Since I can’t see the actual error, this is the best I can do for you.

    Thanks again.

    Plugin Author maksbd19

    (@maksbd19)

    Ok, I think you are getting this error because of the version of your WordPress installation. Is the version of your WordPress is less than 3.5? I’m really sorry that I didn’t update the minimum requirement version.

    Plugin Author maksbd19

    (@maksbd19)

    OK the transaction verification error is defined to show only then when the feedback digest doesn’t match with the generated one inside your website. Inside the payment gateway settings page please look at the options of AAVCHECK and CVCCHECK parameters. These are the culprits which was causing me to have this error while I was working. Though I kept those options if someone find that relevant. What you can do is to ask your bank’s customer service to tell about these parameter, or you can simply check those check boxes to set their default value as NO. This made the error to be resolved to me. Hopefully they will do so in your cases.

    Thanks for using my plugin.

    Plugin Author maksbd19

    (@maksbd19)

    Hello there, this header problem is because if installer doesn’t find the index.php or plugin-name.php file inside the zip file. What you can do is to download the zip file and then unzip it. You may find the plugin is nested inside multiple folder, this is causing the problem. Now you need to find the woocommerce-epdq folder and upload it via ftp. Or you can simply zip that folder and install is via the plugin installer of WordPress. Thanks for your feedback.

    Plugin Author maksbd19

    (@maksbd19)

    Thanks a lot for your review and comment.

    But I do not understand what you meant by the “Manual Order”. Can you please tell something more about this?

    Thanks again.

    Plugin Author maksbd19

    (@maksbd19)

    As there are no new updates regarding your problem, I’m going to mark it as resolved.

    Plugin Author maksbd19

    (@maksbd19)

    Sorry for the late reply. I was able to recreate this problem with my copy after I making some mistake in the SHA-OUT parameters in the plugin configuration page. This is crucial that you know what the parameters are and what must be their values. Though your transaction is verified in the Barclay, they send some information back so that woocommerce can understand the status of the payment. If there is any misconfiguration with the SHA-OUT parameters then the returned value will not pass the verification in your site. So that the “Transaction verification error” will show up.

    For more clarity, Barclay return a key value paired url encoded data and a hash code digesting those data as well. If the hash generated by digesting in your end doesn’t match with the returned one, woocommerce will assume that there is an error with the verification of the transaction. So that you need to go thorough with those parameters.

    There is bit confusion about the AAVCHECK and CVCCHECK parameters of Barclay. While I was developing this plugin they caused me a nightmare so that you should check them carefully.

    Thanks a lot for using this plugin.

    Plugin Author maksbd19

    (@maksbd19)

    First of all sorry for late reply. I wasn’t nearby of my pc a couple of days. Anyway I tried to make a trial purchase and it worked fine. It showed new order reference number, total amount and other informations. look at this Image.

    And not to say Barclay pretty hard job both for developers and users to understand their configuration and I will say that they have done a very good job to provide a secure online transaction to their users.

    For errors you should read the advanced epdq integration guide. In that file there are a list of errors and what is their meaning. Again to see what error just occurred you need to go to the back office and look for error codes.

    Thanks for using the plugin.

    I’ve just uploaded a plugin which will add a barclay epdq payment gateway in woocommerce. I look forward to the response of people.

    http://wordpress.org/plugins/woocommerce-epdq-payment-gateway/

    maksbd19

    (@maksbd19)

    I had a similar problem but recently I’ve solved it.

    My problem was-

    1) variations wasn’t showing up in the post editor.
    2) variations weren’t showing in the product’s front end page.

    For (1) I just followed the steps explained above

    For (2) there is a required field titled “Regular price” in the variation edit fields. When I set some value in there then those variations, in which i set the values, are started showing up in the product page.

Viewing 15 replies - 31 through 45 (of 45 total)