guillaumev

Can you send me, by email, a copy of the shortcodes you’re using (the content of your CV page) ?

Hi Dan,

I just released a new version of the plugin which improves the support of the LinkedIn API. Please try it out and let me know…

Hi,

Thanks for the message on the LinkedIn forum. I wrote a quick tutorial here: https://www.viguierjust.com/en/2011/02/07/using-linkedin-sc-with-linkedin-api/

Best regards,

Guillaume.

Hi Gergely,

It was not a user error :-). It was my bad, an error in my last commit. I updated the plugin to version 1.1.1 and it should now work.

Let me know if you still encounter problems.

Also, if you don’t mind, I’m trying to push LinkedIn to add a documentation concerning the Javascript API. If you can help me by adding a message saying you’re waiting for the same functionality here: https://developer.linkedin.com/thread/2306?start=15&tstart=0 I would greatly appreciate it.

Best regards,

Guillaume.

I just posted an issue in Chromium: https://code.google.com/p/chromium/issues/detail?id=71174

All right so this code:

set:function(e,a,s){
e=typeof e=='object'?e:tid(e); var o=e.style.opacity||TINY.style.val(e,'opacity'),
d=a>o*100?1:-1; e.style.opacity=o; clearInterval(e.ai); e.ai=setInterval(function(){TINY.alpha.tw(e,a,d,s)},20)
},
tw:function(e,a,d,s){
var y = e.style.opacity;
if (typeof y == 'string') {
y = e.style.opacity.replace(',', '.');
}
var o=Math.round(parseFloat(y)*100);
if(o==a){clearInterval(e.ai)}else{var n=o+Math.ceil(Math.abs(a-o)/s)*d; e.style.opacity=n/100; e.style.filter='alpha(opacity='+n+')'}
}

seems to work everywhere (I haven’t tested on Opera though).

Just to give more details, the chromium version I used was running on Ubuntu Linux, while the Chrome browser I used was running on Windows XP. So I believe the difference I saw between Chrome and Chromium was either due to:
– a difference in the source code between Chrome and Chromium
– the OS difference (one on Linux, one on Windows)

I’ll inform the Chromium project about that, maybe they’ll have an explanation…

Hi,

Very interesting ! To be honest, I had tested on Chromium, not on Chrome, because I believed that the source codes were the same, but now I did some more tests and I have some interesting results:

– on IE, yes, my code doesn’t work (sorry, my bad, I had not tested on IE)
– on Chrome, without my modification or with my modification, it works either way
– on Chromium, it only works with my modification

I’ll look a little bit further and will keep you updated

Hi Gergely,

That’s what I was afraid of: this information is not on the public profile. Developing such a functionality will require quite a lot more work and, for now, I don’t have enough free time to do it.

However, if you’re interested in writing some code to do it, please feel free to do so and send me your modifications, I will happily send your changes to the repository.

Best regards,

Guillaume

Hi,

Thanks for your comment. Can you provide me with the detailed list of the extra fields you need to be added ?

Best regards,

Guillaume.

Hi,

Do you have allow_url_fopen enabled ? https://www.php.net/manual/en/filesystem.configuration.php#ini.allow-url-fopen

Hi Olivier,

In the end, someone else requested this feature on my blog, so I wrote a new version of the plugin (v 1.0.5) which now supports full URLs. You can now use [linkedinsc profile=”https://uk.linkedin.com/pub/first-last/7/d88/21″ lang=”en”].

Done. See release 1.0.4.

Thanks a lot.

Hi,

Your code seems all fine to me. I’ve added the modification to the svn. Can you check and make sure that it works for you with the code in the svn, and if so, I will do a 1.0.4 release ?

Thank you.

Thanks a lot for the help ! I released the fix (see version 1.0.3)

Ok, I think I have it right now. However, before doing a new release, could you test it as well using the version that’s on the svn repository (https://plugins.svn.www.ads-software.com/linkedin-sc/trunk/) ?

If you give me your green light, I’ll do a new release.

Thanks.