DobsonDev

Hi Colin,

Sorry for the late reply (really late as a matter of fact). As far as I can tell reading through my code, the call is only stored to a WordPress transient if the cache_id attribute is set. So if you just don’t set that then I think it will make the call every time without caching the data. Obviously this will be slower but then you won’t have to update the cache_id constantly.

The other thing I think you can do is set cache_id="NULL" and that will have the same effect as leaving it out of the shortcode all together.

In the future I might add an explicit attribute for the shortcode that tells the user that nothing is being cached, but for now just leaving out the cache_id or setting it equal to cache_id="NULL" should do the trick.

Again really sorry for the late reply – for some reason I’m not subscribed to my own support forum but I’ll change that right now.

This issue might be happening because your second markdown script is causing an error for Parsedown (PHP markdown script I use in the plugin) and therefore it’s not appearing.

I know GitHub has some specific syntax for their markdown that other engines don’t use so it’s possible that is causing an error for Parsedown and therefore it’s not displaying.

If you send me the shortcode that isn’t working I can test it out and see if I can find out more. You can either reply here or email it to me at alex@dobsondev.com.

I emailed back and forth with Jacob and we figured out the problem but I thought that I would include it here in case anyone searches.

The problem occurred because cURL was unable to verify the certificate provided by the server. This can be solved in two different ways:

1. Use curl with CURLOPT_SSL_VERIFYPEER => false which allows curl to make insecure connections, that is curl does not verify the certificate.

2. Add the root CA (the CA signing the server certificate) to etc/ssl/certs/ca-certificates.crt

I will do an update later today that allows for an option to allow insecure connections if the user needs to do that. The default cURL calls in both the GitHub Readme and GitHub File Contents shortcodes will still be secure.

If you do need to use insecure connection then use the following syntax (this is an example using Font Awesome): [embedGitHubReadme owner=”FortAwesome” repo=”Font-Awesome” insecure=“true”]

What other plugins do you have enabled on your site? I tested the embeds you provided on my own testing site and they all worked – so either the theme or another one of the plugins is conflicting with mine.

Do you know if any of the other shortcodes provided with my plugin work? Also do you know if for some reason CURL is disabled on your server?

If you want to weed out the problem yourself the first step would probably be to deactivate all plugins except for mine, see if that works, then activate the other plugins one by one. You should be able to narrow down what’s causing the problem from there.

If you have any kind of error log and can give me a copy of that I might be able to help more as well.

EDIT: the code should be

div.dobdev-twitch-container {float: left; width:70%; padding-right: 5px; }
div.dobdev-twitch-chat-container {float: right; width: 30%; }

Unfortunately not right now. The PDF viewer uses the default built-in viewer that comes with most browsers, but mobile browsers do not include this feature so it will not display.

Hi klmnweb,

Unfortunately the shortcode is not meant to take in “auto” as a parameter the way it is now. However, if you leave the height blank, it will default to 100% which is pretty much the same as auto. You can also explicitly put 100% if you would rather as well.

Try that and let me know if that works for you.

dobsondev.com/portfolio/dobsondev-shortcodes/