Kimball31

Thank you @wpmudevsupport15. I understand.

Is there a suggestion box for future development ideas? I would like to formally suggest adding Item ID and Product Name to the PayPal configuration panel, and passed in with the Paypay order details. It seems to me a lot of your clients could benefit from more detail in the Paypal transaction.

Hi Adam, thanks for getting back to me.

I’ve come up with another solution. I’m going to add a hidden tracking code to the form. Then the mu-plugin can get the code and add it to the $request as a SKU, that Forminator sends PayPal. Paypal uses SKU as an Item ID on invoice.

Can you tell me how to I add the SKU to the $request Forminator sends PayPal? I tried updating $request in the the mu-plugin to set the sku. But this did not work. It did not show up in PayPal.

$request['purchase_units'][0]['sku'] = $tracking_code; 

MS Copilot says to pass in SKU this way:

{
  "intent": "CAPTURE",
  "purchase_units": [
    {
      "reference_id": "PUHF",
      "description": "Sporting Goods",
      "amount": {
        "currency_code": "USD",
        "value": "220.00"
      },
      "items": [
        {
          "name": "Tennis Racket",
          "unit_amount": {
            "currency_code": "USD",
            "value": "150.00"
          },
          "quantity": "1",
          "sku": "sku01",  // This is where you set the Item ID
          "category": "PHYSICAL_GOODS"
        },
        {
          "name": "Tennis Balls",
          "unit_amount": {
            "currency_code": "USD",
            "value": "10.00"
          },
          "quantity": "7",
          "sku": "sku02",  // This is where you set the Item ID
          "category": "PHYSICAL_GOODS"
        }
      ]
    }
  ]
}

• From WordFence:
• Plugin Name:?Annual Archive
• Current Plugin Version: 1.6.0
• Details:?To protect your site from this vulnerability, the safest option is to deactivate and completely remove “Annual Archive” until a patched version is available.?Get more information.
• Repository URL:?https://www.ads-software.com/plugins/anual-archive
• Vulnerability Information:?
  • https://www.wordfence.com/threat-intel/vulnerabilities/id/20199c88-1800-4d18-a0ee-0219be77b429?source=plugin
  • https://patchstack.com/database/vulnerability/anual-archive/wordpress-annual-archive-plugin-1-6-0-cross-site-scripting-xss-vulnerability
• Vulnerability Severity: 6.4/10.0 (Medium)

I found your forminator_get_form_name() function, so it’s pretty easy to go from form_id to form_name.

$form_name = forminator_get_form_name($form_id);

A caching issue got in the way of my testing. This mu-plugin is working now.

It converts the url path of the form to a Paypal payment description.

https://github.com/Kimball31/Forminator-PayPal-Order-Description-From-URL/blob/main/forminator-paypal-description-from-url.php

I’m hoping to use the form name as the description, something like this:

$body->purchase_units[0]->description = $form_name

I did some testing with your forminator-paypal-description.php plugin, but unfortunately $parsed_args does not include the form name, or anything string I can use to identify the form. So that approach does not work for me.

I found another plugin https://gist.github.com/wpmudev-sls/b8ff5a66d81b44a58e5c1b1ebbfa48f5 that offers access to the to current_url, which is close enough. But when I set $request['purchase_units'][0]['description'] = $current_url it does not show up in PayPal. Is $request['purchase_units'][0]['description'] still the correct property name? Perhaps PayPal changed the spec? The description is not coming through.

My plugin is on Github: https://github.com/Kimball31/Forminator-PayPal-Order-Description-From-URL/blob/main/forminator-paypal-description-from-url.php. Do you see anything wrong with it? Even though it generates and sets the description, the description does not show up in Paypal.

I answered my first question. I found “{form_id}”. It’s not a listed data field in the Email Notifications settings, but it works. So this “see all entries” link works in the email notification email.

<p><a >See All {form_name} Entries</a></p>

Now I would just love to find a way to obfuscate the id or link, and make it public for the email recipient.

Thanks @slingshotdesign, that works for me! I just had to modify the quotes in your code from ’ to '. As below, added to functions.php file.

function bsos_gutenberg_categories_fix($args) {
// FIX MISSING CATEGORIES AND TAGS in Event Manager edit mode. 
    $args['show_in_rest'] = true;
    return $args;
}

add_filter('em_ct_categories','bsos_gutenberg_categories_fix');
add_filter('em_ct_tags','bsos_gutenberg_categories_fix');

You can override the figcaption ‘position’ in your style. Change the position from ‘absolute’ to ‘relative’ to get the caption below the image, instead of on top of it. You will also change the font color and remove the background tinting. Here the css I use to do it:

figure.wp-block-gallery.has-nested-images figure.wp-block-image figcaption {
    font-size: 18px;
    font-weight: bold;
    background: none;
    position: relative;
    color: #000;
    line-height: 1.2em;
    margin-top: 0.2em;
}

Thank you Vladimir.
I look forward to using it sometime soon.

If you leave “line cost” empty, you get the “non-numeric value” error.

The work around we found was to make sure all “line cost” had a value. We use 0, and that worked.

The warning is visible only in the browser console on Chrome. I assume this is something relatively new. Down the road these cookies will be required to have a SameSite attribute.

You can see them on your site as well if you want to dig deeper: https://jetpack.com/

• This reply was modified 4 years, 8 months ago by Kimball31.

Yes, I see the warnings in the console. They are not causing any trouble yet, but I thought you might want to know.

Chrome Version 80.0.3987.132 (Official Build) (64-bit)

Maybe. I’m not sure what it was displaying, but certainly not displaying the page content.

I found a work around that seems to work. Go into each Widget that uses this plugin, and force it to save. What I did was just toggle the “show title” button in the widget on and off so the Save button becomes active, then save the widget.

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

We had trouble after the latest update as well. The solution we found was open each widget, and Save it. Make a small change in the settings (I changed “show title”) so the Save button is activated, then click Save.