gep13

Perfect, thanks for the info!

Gary

Hey,

Just wanted to follow up with this as I didn’t get any response to the submission of the Compatibility Reports that I sent through.

Thanks

Gary

Hey,

That is great news, I think it would be a very useful addition.

In terms of the suggestion for using a plugin, how would that “look”. Never actually created my own plugin. Are you saying that I could create a plugin that is “activated” for each post, and then within each post, look to see if there is an embedded YouTube link. If that link is found, then add the addition meta tags to the page, so that Facebook can pick them up?

Any tips on where I could get started creating this?

Thanks

Gary

Hello,

Thank you for your time so far!

As requested, I have completed your instructions, and sent them off to you.

I suspect that what you are going to highlight is this issue:

“[0] => SSL certificate problem: self signed certificate in certificate chain”

However, I see this issue on both sites, as you will see in the reports. However, JetPack/Publicize work fine on the gep13.co.uk/blog site, but doesn’t from the aberdeendevelopers.co.uk site.

Any ideas why it would work from one, and not the other. As I mentioned, these sites are running on the same server, granted in two different virtual directories within Apache.

Thanks

Gary

This was it:

https://blog.stuart.shelton.me/archives/883

I had to do this to get JetPack activated on the Aberdeen Developers site. Didn’t have to do this on gep13.co.uk site.

Now it seems I have to do this to get Publicize to post ??

Any ideas?

Thanks

Gary

Hey,

I run these sites on my own server, and to the best of my knowledge, curl is enabled on both. I certainly haven’t switched it off. Both sites were setup in exactly the same way.

I have had to use the Core Control plugin, because i struggled to get JetPack connected originally, and after googling I found that the plugin could help.

I will try to find the blog post about it.

Thanks

Gary

Hello,

Thanks for getting back to me!

This is really starting to not make any sense to me.

I have done what you suggested, but in order to delete the accounts, I had to use the Core Control WordPress plugin to disable the cURL Transport within “External HTTP Access”. With that disabled, I was able to remove both the Twitter account, and the Facebook account.

I then added the Twitter account back in, and still with the cURL Transport disabled, I did a test blog post, and publicize successfully post to Twitter.

However, when I re-enable the cURL transport, doing another test blog post means that Publicize no longer works.

The really confusing part is that I have another blog, https://www.gep13.co.uk/blog, which is hosted on the same server, with the same plugins, and Publicize works perfectly there, without the need to touch the cURL transport. On this blog, it is enabled.

Can you think of any reason my Publicize works in one place, and not in another?

Thanks

Gary

Is that your own plugin Jeremy? Is it not available in the WordPress Gallery?

Call me paranoid, just not sure about installing that, knowing nothing about it ??

Thanks!

Gary

That would be great.

This was a nicely nice addition when I was using dlvr.it, but I have switched to using Publicize now as I prefer everything to be in one place, so would really like to see this in a future version ??

Thanks!

Gary

Hello,

The issue that I had was exactly as described here.

I didn’t have any hard drive space left of my Web Server, which meant that there was no way of extracting the contents of the zip file.

I cleared out some space, and everything started working.

Gary

Hello Jeremy,

Thanks for getting back to me!

I have just installed WP Bit.ly, and I am happy to say that this is now working as expected!

Thanks! Hope you have a great New Year!

Gary

Hello,

I use the bit.ly linker plugin, and on publishing a blog post, this link was generated by bit.ly linker:

https://gep13.me/W5xqrx

Which is what I want, however, in the tweet that was created:

Test Blog Post https://t.co/kEvD0Ats

— Gary Ewan Park (@gep13) December 28, 2012

The following URL was created:

https://wp.me/p1yU7f-qg

Which isn’t what was expeceted.

Am I doing something wrong? Is there another plugin that I should be using?

Thanks

Gary

Hello,

I have been able to resolve this issue, it was exactly as you suggested. Thank you very much for taking the time to reply!

Thanks

Gary

That is great news! Thanks for the update!

Gary

Any update?

Please let me know if there is anything that I can help with.

Gary