Greg Neise

Again, thank you for your expertise, time, and wonderful product.

That did it, thank you!!! I swear, I read that documentation until I was blue in the face, but didn’t pick that bit up about needing two separate shortcodes.

One last thing, the pagination controls display vertical like this:

1
2
3
…
13
Next>>

Is there a way to format that so it’s horizontal, like:

1 2 3 … 13 Next>>

Thank you! The CSS I was trying was formatted slightly differently, but didn’t work. The CSS you provided above didn’t work either, but got me closer to the solution for aligning the items to the top, which is:

.gallery-item {
text-align: left;
vertical-align: top;
}

I’m not using Gutenberg. I’m using the Avada theme (which does not use Gutenberg by default, and uses the “classic” text editor), placing the shortcode from my original post here in a <code> element, which is specifically for various code (as you suggest).

What’s interesting and frustrating is that the only part of this that’s being ignored is the <br> tags. I’ve been using Avada for years, with all kinds of code in <code> elements, and it’s always worked as expected. ˉ\_(ツ)_/ˉ

Any other ideas or guidance is greatly appreciated, and thanks again!

David, thanks again. It seems that the PDF viewer we use — which intercepts links that go directly to PDF files and forces them into the viewer is replacing the MLA gallery links completely.

I think you can mark this as resolved, and I need to figure out another way to create our archive galleries. Thank you *very* much for your time and effort.

Hi David, thank you for the reply. As a way of testing things, I took the same short code and just changed the file type, then assigned one of the images the same attachment category:

[mla_gallery size=full columns=4 attachment_category=birding-archive post_mime_type=image/jpeg post_parent=all link=file]
mla_caption=’{+title+}‘
[/mla_gallery]

That is working as expected on the site’s front end:

https://www.aba.org/test-bunny-single-post/

… not sure what to make of that.

I should add that it was working fine with Avada up until the last SG Optimizer update, about a week ago.

They completed the order(s). Information that is collected at checkout is in the database, … but not in the order, and of course, there was no payment collected.

Confirmation emails were sent, but transaction was not completed:

New Order: #6398
You’ve received the following order from :
[Order #6398] (January 22, 2019)
Product Quantity Price
ABA Tropicbird Pendant with Sterling Chain (#pendant) 1 $60.00
ABA Luggage Tag (#luggage tag) 4 $12.00
ABA Tropicbird Earrings (#earrings) 1 $40.00
Subtotal: $112.00
Shipping: Priority Mail Medium Flat Rate Box
Tax: $0.00
Total: $0.00

We have contacted some of the customers, and they thought that their order went through. This has happened 5 times (4 different people) since January 18 (none before).

###

It has now happened to one customer twice. Looking a little closer, all of the transactions with this problem have this in common:

[tender] => C
[trxtype] => A

I also notice that successful transactions have [custom] filed that looks like this:

[custom] => {“order_id”:6362,”order_key”:”wc_order_5c4119c728d07″}

… and problem transactions, like this:

[custom] => {“order_id”:6364,”order_key”:””}

And, sales that go through successfully:

[RESPMSG] => Approved

…vs problem transactions:

[RESPMSG] => Verified

Please advise.

• This reply was modified 6 years, 1 month ago by Greg Neise.

UGH.

In the PayPal Here plugin, a required field is “PayPal Email”. We use a login name that is not an email address with our PayFlow Pro account, and the PayPal Here plugin won’t recognize that as valid.

In the Accepted Payment Methods box, we should (I think) be able to choose: PayPal Payments Pro 2.0 (PayFlow), which is the only payment method we use (and, of course is your excellent gateway plugin).

I’m not sure how to make the two work together. We don’t, and can’t use just standard PayPal. We are a non-profit organization, and we have a special rate, account, etc. with Paypal.

• This reply was modified 6 years, 6 months ago by Greg Neise.

Notice from Facebook:

https://newsroom.fb.com/news/2018/04/restricting-data-access/

Invalid argument supplied for foreach() in … /wp-content/plugins/user-registration-aide/user-reg-aide-admin.php on line 323

I’m having the same issue. New install.

Figured out part of the problem: changing the “Admin Footer” options seems to break the plugin.