starfiredev

I spent a good bit of today working with it and I have some updated code. I changed the method a bit to instead pull the results from the session cookie. While it does store it in the array $formdata successfully, it doesn’t seem to write to the user_meta at all.

‘add_action( ‘wpcf7_before_send_mail’, ‘vbg_user_onboard’ );
function vbg_user_onboard(){

if(!isset($_COOKIE[‘cf7msm_posted_data’])) {
//
} else{
$current_user = wp_get_current_user();
$user_id = $current_user->ID;
$cookie_data = $_COOKIE[‘cf7msm_posted_data’];
$cookie_data = stripslashes($cookie_data);
$formdata = (array) json_decode($cookie_data);

//parse user data
$user_email = $formdata[‘user-email’];
$user_filed_before = $formdata[‘past-claim’];
}
}
‘
This is a very stripped down version for example purposes. I have about 20 or so variables that get passed through the form. It doesn’t exceed the 4kb cookie limit.

I also had some more statements to make sure it only submitted on the final form but I needed to strip things down for testing.

If there’s any help you can still offer it would be appreciated.

• This reply was modified 4 years, 10 months ago by starfiredev.

That did it! Thank you so much!

My apoligies, I was more concerned about getting the data to work first and then make it look nice.

I’ve cleaned up the code a bit. It doesn’t throw any errors but it does list Manufacturer as blank on the PDF:

add_action( 'wpo_wcpdf_before_item_meta', 'wpo_wcpdf_add_meta', 10, 3 );
function wpo_wcpdf_add_meta ($template_type, $item, $order) {
    // check if product exists first
    if (empty($item['product'])) return;
    
    $document = wcpdf_get_document( $template_type, $order, $item );
    //print_r($order);
    if ($template_type == 'invoice') {        
        $order_id = $order->get_meta('id');
        print_r($order_id);
        ?>      
        <h3>Frame Info</h3>
        <ul>
            <?php
                $frameManufacturer = $order->get_meta('_frame_manufacturer');
                ?>
                <li>Manufacturer: <?php echo($frameManufacturer)?></li>';
            ?>
        </ul>
        <?php
        }
    }

I should also mention the data I’m trying to retrieve is in the item line’s meta data. When I printed the entire order array I did see my variables so there must be a way to display them.

• This reply was modified 4 years, 11 months ago by starfiredev.

Is there any way to actually fix this? I can’t seem to find any specific cases regarding the PDFJs library not displaying certain pages for one reason or another.

I also tested it in other browsers as some people had issues with chrome specifically. Still missing pages. If you don’t know how to fix this then please direct me to a resource that can help me.

I heard back from the client and they are still having issues placing orders through the backend.

We’ll have the client test an order shortly.

Done. Please let me know once you’re finished.

You should have a link sent to your email now. The user should have enough privileges to manage our Woocommerce backend.

I don’t believe we are however I’m not certain. I’ve just sent you screenshots of our settings for the Manual Payment Gateway plugin if that helps.

That’s correct, yes. The option was enabled for this transaction as well as many others. We did try it without and it still didn’t work.

I have sent you the screenshot from the Authorize.net backend for our test transaction. As you can see no data was brought over from our site to Authorize. Other successful transactions have all the data filled in.

I have sent you an email with the details along with a screenshot. I’ll re-post the body text:

“Per your response last week here is the screenshot of the AVS error we receive when trying to make a backend payment. This happens with all names and addresses when using this method, not just the one we personally tested. The normal ordering process is still fine on the front end. We have had no other issues with processing orders with Authorize.net either.

We even tried disabling the request for the billing address in the plugin settings but we still received the same error.”