dleigh

No I didn’t. I had installed Pods awhile back with a possible use scenario but never got around to using it (I guess I found another solution – don’t remember). Anyway, I was searching for this problem and found an issue in the Gutenberg git repository where Pods was mentioned as the culprit for one of the posters (as well as the CMB2 for another poster). So I remembered having installed Pods earlier and sure enough it was activated. I deactivated it and the problem stopped. As I’m not a current Pods user I didn’t pursue it further.

Also the Pods plugin and CMB2 plugins have been identified as creating this behavior as well.

Oh yeah – I’m on version 5.4.3.2 of AAM on 4.9.8 of WordPress with the SiteOrigin Vantage theme and just a few plugins (new test site). I deactivated all plugins except AAM and I still have the same problem.

This MAY help people. I had the same problem. But when I put the message between HTML tags it stayed. HOWEVER, it still didn’t display – instead it said that the message was undefined.

Bump…anybody home at Simple Calendar? We’d like to get this working. Thanks!

There WAS whitespace. I removed it, but still got exactly the same error message. Is there some more debugging I could turn on or logs I could look at or could I send you the P12 file?

Ok, just created a new one. Looks like the same error:

An error occurred: Unable to parse the p12 file. Is this a .p12 file? Is the password correct? OpenSSL error: error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag. Your settings could not be saved.

So what do I do now?

Hi,
I have exactly the same error message. If I take the url that is in the field “Private Key Url Path” and enter it as an address in my browser, my p12 file starts to download. So that means that the address is correct doesn’t it? If I open the file in notepad++, it’s a lot of encrypted text, so I assume that’s the correct p12 file.

Any ideas of what other reasons the plugin would say “unable to parse” than it simply couldn’t find the file?
Thanks!

I would also echo what @cucocreative said. If you don’t have any groups, your import will SAY it worked, but it will not have put anything anywhere. This is perhaps something the developer needs to address, as it’s confusing when starting out. So define at least 1 group and when you import you can specify that you’re importing into that group. Note, if the group is, for example, Apache, you’ll also need to define where your .htaccess file is so that in addition to updating the database, the plugin can update the .htaccess file.

Never mind – to TEST when you only have a LIVE account, you set the live account to TEST, but you set the plugin to LIVE so that it goes to the right URL. If you want to completely TEST, you must be testing against a authorize.net TEST account, not a live production account.

Just updated to 3.0.10 and it looks good (the date anyway – need to work the css to get back to what we had with the old version).

Many thanks!

That was exactly it. Thanks!!!

The white screen happened when I had the new and legacy plugins activated simultaneously. When I disabled one of them then that went away.

I got the legacy plugin installed and set up the parameters from another installation of my site that was still on the old version (pre-3 – not legacy fork). The site that was still setup on the old version still correctly gave me results. When I cloned all the parameters of a given calendar, however, the legacy fork still did not give me any results. So now I’m stuck with a non-production version of my site that works with the old GCE plugin or the production version of my site with the v3 plugin but with bad date formats.

I’d prefer to move forward, but the French date format thing really needs to get resolved.
Thanks.

For anyone else who stumbles across this searching for a solution to my original problem, it was the gettext integration feature of Transposh that was causing the problem. I don’t know why it suddenly happened (maybe my upgrade to 4.3.1 of WordPress changed the interaction with Transposh?) Anyway, disabling that feature in the settings of Transposh brought everything back to normal.

Sounds VERY promising!