bluecomet

Sorry, I tried it and it prevented saving of the form in the form editor and submitting of the form in the front end. I’ve stopped using the auto-fill for now.

Found that stripe key fields do not update unless the publishable key is filled in. So I filled it in with some text for now to disable stripe and entered blank into the secret key. I think it does it.

They sent me a patch. It’s basically the following:

In line 605 of

/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ngglegacy/admin/album.php

Replace:

‘show_option_none’ => esc_html_e(‘Not linked’, ‘nggallery’),

with

‘show_option_none’ => esc_html(__(‘Not linked’, ‘nggallery’)),

I too had the CodeCanyon version of Responsive Google Maps by Mark Advertising that kept bugging me with an update to Imbaa’s version (see the Mark’s post here )

After renaming the folder to prevent conflict with this plugin, I found that it had retained all my markers. What I did was I first renamed the folder, and then reactivated the plugin (without deactivating first).

e.g. I renamed responsive-google-maps to responsive-google-maps-mark

Then went into plugin admin and clicked Activate. I had version 1.1.3. of Mark Advertising’s Responsive Google Maps with WordPress 4.3.3

Update: Update notification came back, so back to square one.

I deactivated Contact Form 7, deleted the plugin and data, reinstalled and recreated the form and everything was working again. Happened on two websites on the same host.

I also tested using the demo form that came with it so it was not a mismatched field name.

Previous to this Contact Form 7 had a message that said “Contact Form 7 3.8.1 requires WordPress 3.7 or higher” when our install of WordPress was on 3.6.1. So I updated WordPress but the problem remained until I reinstalled Contact Form 7.

All is good now.

Still wrapping my head around what price groups are. Could not find documentation on it. Great plugin.

I dug into WordPress code some more and reproduced what it was doing on my own test file outside of WordPress as follows:

< ? php

/* This line below will cause cropImage to fail */
Imagick::queryFormats( ‘JPG’);

$img = new Imagick(‘leonids.jpg’);
$img->writeImage(‘testresult16.jpg’);
$img->cropImage(150,150,0,0);
$img->writeImage(‘testresult16-crop.jpg’);

? >

WordPress does a queryFormats call which causes cropImage to fail. Either with just a blank screen, or internal server error or a memory error if the file is large. Leaving it out will work, even on large images. ImageMagick 6.4.8 2011-02-03 Q16

Waiting to hear back from Hostpapa.