cpedesign

Thanks. I tried the inline form and it seems to be working, so I’m going to give up on this plugin and mark this as resolved.

Thank you for your help!

@constantcontact – nothing new. Got distracted by other problems. Thanks for checking in on this.

I haven’t set up any Mashery integration. We’re using shared web hosting from Yahoo Small Business / Aabaco.

I’m leaning towards trying another plugin or the inline form. What would be the next steps in problem solving this plugin?

@constantcontact – the debugging log is activated. This is the message it shows:

[2019-01-12 22:13:25] API.INFO: mashery.not.authorized.inactive: The Mashery account associated with this request is not active, or an invalid API key was used. [“Extra information”,[“[object] (stdClass: {\”error_key\”:\”mashery.not.authorized.inactive\”,\”error_message\”:\”The Mashery account associated with this request is not active, or an invalid API key was used.\”})”]] []

@constantcontact – ignore my above question – just realized the answer’s in the error message (wp-content/ctct-logs/constant-contact-errors.log). Will try making the file and report back.

@constantcontact – where should I manually create the file and folder and what should I name them? I’m assuming they go in the the constant-contact-forms folder in wp-content/plugins/

I just double checked and the logging functionality is turned on in the settings page. I am comfortable using FTP.

Unfortunately, I can’t turn on the logging functionality. I get an error message (We are not able to write to the /swwp/wp-content/ctct-logs/constant-contact-errors.log file.).

I’m 98% sure it’s the web host’s permissions. They don’t allow certain file types like hidden files to be saved (learned this the hard way with an issue with .htaccess).

It worked! Thank you.

Thank you! I’ll try it.

I’m the entire team in this case. Comfortable is too strong a word, but I’ve edited a little PHP in the past, with a lot of coaching. I do know how to work with a child theme – I usually stick to editing the CSS.

I just had this problem and I solved it with custom CSS.

My problem:
Quotes displayed in a page using the short code had an extra dash and line space – but quotes displayed by the widget had the author and source formatted correctly, without an extra line space or em dash.

My diagnosis / solution:
I used Firefox’s inspector tool (you can use Chrome’s developer’s tools too) to figure out that this was caused by styling in my theme (Make) overriding the styling for the Quotes Collection plug-in. The plug-in uses the blockquote and cite tags to format the quotes and my theme added a line space and em dash to all cite tags within a blockquote.

Here are the theme styles that caused the problem.

blockquote cite {
	display: block;
}

blockquote cite:before {
	content: "\2014";
}

This is the custom CSS that solved my problem (your millage may vary, depending on your theme):

blockquote.quotescollection-quote cite {
	display: inline;
}

blockquote.quotescollection-quote cite::before {
	content: " ";
}