Gergely Daróczi

It still does not show any events for me, although I have updated the “GCE feeds”, created and set my own API key and set all calendars to be public. One thing I can think of: I’m using calendars of a user with Google Apps with custom domain, so the feed looks like: “[email protected]”

Any ideas how to show the events again?

I am using this feature to translate the field names to Hungarian, e.g.:

<div class="gce-list-event gce-tooltip-event">Meetup: [event-title]</div>
<div><span>Id?pont:</span> [start-date] [start-time] - [if-multi-day] [end-date] [/if-multi-day] [end-time]</div>
[if-location]<div><span>Helyszín:</span> [location]</div>[/if-location]
[if-description]<div> [description]</div>[/if-description]
<div>[link newwindow="true"]További részletek...[/link]</div>

Public page: https://r-projekt.hu/esemenyek

But I’d be happy with a po file that I could translate if that’s easier for the plugin authors.

Hi Peter, sure, thanks for your kind help.

Awesome, thank you very much, @nerdaryan. One comment you might consider: maybe disabling (and adding a tooltip to) the buttons instead of hiding them would be a more elegant solution. And it would get some more active users IMHO.

Yup, working fine after refreshing permalinks, thank you very much for your prompt and kind support.

I see the “Stream Feeds Key” and the RSS and JSON feed, but clicking on the links return “Apologies, but the page you requested could not be found. Perhaps searching will help.” (404). Any ideas? I am using the most recent version of WordPress (3.9) and the plugin (1.4.3).

Awesome, thank you very much for your kind and prompt support.

Great, looking forward to see the landing page and the new dev version. Keep up the good work!

I would be happy to test the development version, if a rather clean and just starting site would be also useful for you.

I would also love to translate the plugin’s strings to Hungarian language. @christophv, did you find any workarounds? @nerdaryan, can we help you somehow? Please keep up the good work, AnsPress is an extremely cool plugin.

Hi Guillaume,

thank you for fast answer and precious support, I will be able to check your plugin in the afternoon.
I wrote a short message on the forum you posted, I hope a public documentation will be available soon!

Best regards,
Gergely

Hi Guillaume,

I have just seen that you implemented tha linkedin API on your really great plugin. That sounds really great, thank you!

I had done some testing, but unfortunatelly I could not manage to make your plugin work with the API, which is definitely a user error made by me.

I signed up for an API key and set it in the plugin’s option menu, but private fields are not shown, also not fetched and the example script you posted on the description page shows only the fileds on my homepage.

I have tested the ‘linkedin_api_test.php’ also in your lib directory, also ‘linkedin_api_profile.php’ but I get a php error:

require_once(): Failed opening required ‘/home/***/public_html/wp-content/plugins/linkedin-sc/lib/linkedin_profile/linkedin_3.0.1.class.php’ (include_path=’.:/usr/share/php:/usr/share/pear’) in /home/***/public_html/wp-content/plugins/linkedin-sc/lib/linkedin_profile/linkedin_api_profile.php on line 18

which seems to me that the plugin requires linkedin_3.0.1.class.php which cannot be found in the plugin directory. Do I miss something?

Best regards,
Gergely

I see, thank you very much for fast aswer!

Regards,
gergely

Hi Guillaume,

thanks for fast answer. I am afraid of I could not manage to do the modifications unfortunately.
A simpler method could be parsing public (or public with link) profiles on https://resume.linkedinlabs.com/, after a user had authenticated linkedinlabs to fetch these fields by Api and also setting in a variable the url to his/her ResumeBuilder profile.
Coding that option would be a lot less work than fetching the fields via Api, I will see if I manage to code it.

Best regards,
Gergely

Dear Guillaume,

I would be very happy to see the following fields also:
* languages,
* skills and
* publications.
The first two would be more important.
As I was reading about the issue, I see, that the solution could be a bit complicated, as these fields are not part of the public profile (as I see). That means: to get the values, you/we must use the linkedb Api, which requires a sophisticated authentication and Api code on every WordPress portal.
I might be wrong.

Best regards,
Gergely