idleberg

when you compare an embed code produced by the mixcloud website with the one create by the mixcloud embed plugin, you will notice that the former uses url encoding (%2F for a slash) and the latter does not (/ for a slash). what i did first was increasing the tolerance of ographr to accept both, but i’m not sure why it stopped working after the update to mixcloud embed 1.5. for some reason, mixcloud embed now places the player twice into my page, first in the head of the page (!) and a second time in the top of my post (even though it should’ve been in third place on my test page!) you should probably contact the author of that plugin instead.

hm, it works for me (and didn’t before). could you give me an example for a shortcode you’re using?

edit: i just upgraded from mixcloud embed 1.4 to 1.5 – now it’s no longer working. there are a couple of other things that broke since the upgrade, in my case the player is positioned at the wrong place.

the maker of mixcloud embed should probably be more strict about the syntax, but it was easy to add a little tolerance to my plugin. as i’m working on the next major version right now, you’ll have to use this private built for the moment.

https://dl.dropbox.com/u/353649/meta-ographr-0.7.12.zip

please let me know if it gives you any troubles.

i take it you mentioned xcache because of this. i was pretty clueless about it and kind of glad that the problem could be traced down to xcache. i’m not familiar with that at all and have no possibility to test it on my own servers. maybe you can do a little investigation yourself to rule out there’s xcache involved.

no idea. i have some ideas that require a lots of changes and i haven’t had the time for any of that lately. hopefully before the summer holidays, but i can’t make any promises.

at the moment, this is not possible, but there will be some per-post options in the next major version. what you can do is fool the plugin by adding a string to the ographr_urls custom field.

example:

a:1:{i:0;s:34:"https://thisis.my/path/to/image.jpg";}

note that the 34 indicates the number of characters used in the url, replace it accordingly!

that’s coming from the facebook comments plugin, check its settings

ah sorry, you will have to update your settings! clicking ‘save’ might be enough, otherwise pick a different language first and then go back to your preference.

turns out facebook requires “he_IL” and not “iw_IL” as specified in this list. i’ve released an update fixing that, thanks for reporting!

take a look at this. it’s probably the same problem with hebrew, try and choose ‘hebrew’ rather than ‘hebrew (israel)’

this plugin cannot create screenshots of your plugin <- should’ve been “of your website” of course ??

the only thing that troubles me, facebook is get the description from the opengraph tags since that one’s empty – the site is using a fallback and analyses your site. i still think that there’s some plugin (or the theme) interfering with ographr. do you use any plugins that create a custom excerpt?

that could be due to facebook’s cache, here’s how you can enforce a refresh. otherwise the cached link should expire after a week or two.

1. try disabling your other plugins one by one to see if any of them interferes with retrieving the excerpt of a blog post

2. try using the default theme for the same reasons as above

hopefully we can narrow down the source of the problem

this plugin cannot create screenshots of your plugin. %screenshot% is meant to show a themes’ generic screenshot. otherwise you only have the option to post an url to a screenshot you made. sorry.