mymichael2

Update:

This may or may not lean toward a solution, but it’s a bit more info: Another company (with a different software system) was able to process their cards in sandbox mode, but when they went live using PayPal they received the same CVV2 mismatch error. After a LOT of digging they discovered that PayPal wasn’t accepting the four-digit expiry date from their system. When they switched it to two digits (ie. 21 for 2021), processing went through without a glitch.

We send through the four-digit expiry date with Jigoshop. Is it possible to switch that to two digits to see if it solves our problem also?

The catalog name has remained the same, and I don’t allow anyone FTP access. It hasn’t occurred again (yet) … I’ll keep watching it … lol … obviously. In the meantime if you have any ideas, toss them my way. Thanks! ??

Follow-Up: A little more than a week after I applied my .htaccess fix the problem returned. It was immediately after an update. And although I didn’t expect my .htaccess file to be overwritten, it apparently was. The code was missing and the remaining file was identical to the backup I had created at the time of the edit.

I re-entered the code (shown below), saved the change, and the fix took again. Should anyone using this fix run into the same problem, just apply the fix once more. I don’t know if there is a developer-driven way to fix this, but it would be awesome if it could be introduced in a future update.

The fix:

Add these lines to your .htaccess file:

LimitRequestBody 99999999999
SubstituteMaxLineLength 10M

(Note: This seems to work with SiteGround installations. I have no idea if it works with other servers.)

I am also with Siteground, and the same solution fixed my problem … Love Elementor.

Hello, I tried this fix, as I don’t prefer to have my menu at the bottom of the image on the front page. However, I didn’t like the effect, and I deleted the snippet from my child-theme style sheet.

However, when it was deleted the menu did not revert to its original location. I am wondering if there is something more I need to do.

———————

This problem self-resolved after about 30-minutes. Everything reverted to original settings.

• This reply was modified 7 years, 4 months ago by mymichael2. Reason: Problem Self-Resolved

Side-Note: I have placed these customized navigation menus in strategic locations throughout my site because of the “WP Custom Widget Area” plugin. The menus are found within the content of standard (non-BuddyPress) pages and posts, yet they link these pages and posts with everything BuddyPress … So awesome.

Well, you’re good!

It turns out that the plugin I’m using to generate dynamic links for BuddyPress members is altering the class ID (BuddyPress Direct Links) … Once I discovered that (by looking at the generated page’s source code), I was able to input the correct ID and “boom” my CSS took and the dropdown menu appeared beautifully.

Thanks for an incredible plugin!

It appears that this plugin is no longer supported. I would mark the topic resolved, but it is NOT resolved.

I’m getting ready to rate this plugin. I want to rate it high because it is SO valuable to blogs that aggregate feeds. However, if it doesn’t work I must rate it accordingly.

Any response Julian? I would love to get this working.

Update:

I just ran the plugin again (three times), and although it still did not detect duplicate posts on any of the attempts (item 1), it only gave the error message (item 2) twice.

Hello Robert … Thank you so much for something so simple! lol … Amazing how technical I can be, and how I can so quickly and stubbornly overlook the obvious.

Thanks again,
Michael

I will head that direction. Thank you for your help. This appears to be solved as far as it can be here.

I did revert to the Twenty Twelve theme and everything worked. Alas, I need the site as I’ve constructed it, so I need to somehow get it to work for me. However, I may have found a clue … I discovered what is triggering the problem:

I installed the plugin, “CKEditor for WordPress” and tried to create a new page … It worked: I was able to use the visual editor …

However … On every page where I clicked on the HTML tab, wrote anything in HTML, and saved the page, the Visual tab, the Screen Options tab, and the Help tabs were immediately and irreversibly disabled.

So I decided to use the “Source” button in “CKEditor” … And it worked. I could write in HTML, do anything I wanted there, and switch back to Visual AS LONG AS I never used the HTML tab. Moreover, by using the Source button none of the other tabs became disabled.

So, the problem isn’t exactly solved, but I have found a workaround.

I did try reinstalling WordPress a couple of times, without any change.