Carrie Dils

David,
That’s awesome — thank you!!

Carrie

Heya! Just updating this thread to note that shortcodes are enabled in widgets by default as of WordPress 4.8.0.

Hey there, I double-checked and the menu is published. I’ll ping you over in FB.

Thank you!

Thanks for your response!

I’ve double-checked both the API key and the account email and both are correct. I tried the read-write API key just in case as well as the “owner” email on the account (versus the account login email). None of those various combos did the trick.

If I echo the $url value set around line 288 of your plugin, I can see that data is being returned (https://business.untappd.com/api/v1/menus/3762?full=true), so something between that and the account validation is failing (my guess).

Any troubleshooting suggestions to see what’s failing?

Thank you,
Carrie

Thrilled to hear it! Thanks for the feedback!

Hey Ben,

Confirmed on both accounts, but looks like the culprit was a conflict in the environment I was testing on.

Thanks for the update!

Cheers,
Carrie

• This reply was modified 8 years, 1 month ago by Carrie Dils.

You’re awesome (and speedy!). ??

I left a note on the gist.

Doh! Sorry for the wrong info.

Hi Elena,

You would need to make changes to that CSS file you put in your uploads folder, otherwise the styles are identical to what’s in the original plugin.

If you describe what sort of style you like, I can make some suggested changes.

Cheers,
Carrie

Thanks for following up, Hardeep.

I disconnected bit.ly and confirmed that your plugin is sending the URL correctly (https:// in my case). Twitter’s link shortening service has picked up where bit.ly left off and still wants to add that https:// protocol to links. Not sure why, but it’s not an issue coming from Revive Old Post.

Cheers,
Carrie

Hey Ionut! I didn’t know I’d get the man himself on the forums. ??

My site settings are https://. It may be something going on in my bit.ly account then.

Thanks for the info!

Thank you, Adam!

Hey there,

Yeah, the plugin is working correctly as you noticed. The issue is that the CSS in WooCommerce has greater specificity than what you have in your stylesheet.

For the button, your CSS selector is .button and WooCommerce’s is .woocommerce a.button.

Just make your selector more specific than Woo’s. For instance, try:

.content a.button

Cheers,
Carrie

Hey Justin,
That dingleberry + sign snuck in on me on a code merge. Many apologies and the 1.0.3 release fixes it.

Cheers,
Carrie

Thank you for the good word. ??