Huckleberry

Connected today, and shared a post as admin. Both works.

In case others have the same problem, the solution was to deactivate “Move script to footer” option from the General tab in the plugin settings.

I’ve emailed you through your website, because I’d prefer not to disclose this information in public.

Saludos

@macmanx Ok, I’ll add a pixel and see what happens. Would be fun if it works. I’ll let you know.

@macmanx I don’t think that has to do with the problem. Above 200 the preview image becomes large. 200 and below will give a small image to the left of the post.

My problem is that the image sometimes doesn’t show.

@minova & @markzahra

My apologies. I just realized that I am using the “Speed Booster”-plugin which has an option: “Removes extra Font Awesome styles”. When this was activated, it came in conflict with the snippet you provided. I deactivated the option, and the snippet now works like a charm.

@renzms
Thank you very much

Hi @renzms, thanks for your reply.

No addon in use. I have placed the short code on this page. The first item dated 26 March is not from the external RSS-feed, but a post from the front page. So strange.

@minova & @markzahra, thank you for your replies.

I tried to inject the code in the theme functions file, and then by using a code snippet plugin. Neither worked. Google PageSpeed is still reporting that it is being loaded under “Diagnostics / Minimize Critical Requests Depth”. Check the link PageSpeed

I have also tried to scan the code in your plugin to comment out the part that loads the css-file from maxcdn.bootstrapcdn.com but I couldn’t find it, and PHP isn’t my strongest suit.

I have also used FontAwesome’s own plugin to check that it is the WP RSS Aggregator that is injecting the font-awesome.min.css file. (It reports a potential conflict when installing the FontAwesome-plugin.)

Thank you, @kraftbj , as you promised, it now sets the posts to PUBLIC.

@tmmbecker Awesome! Looking forward to hearing more. I tried to set the flag myself, but my PHP/JS-knowledge is not so good.

Thanks to you all at Automattic. Once I start getting an income from the website I will purchase your plans. At the moment it’s all pro bono.

@tmmbecker Nothing has changed with the scope (“visibility”) for shared posts. It should be still possible to share with “Public”, but Publicize keeps putting “Connections Only”:

Share on LinkedIn: Share on LinkedIn lets a member more easily share relevant information to their network and others on the LinkedIn platform. This API has the same functionality as before. See the documentation for the new format.

visibility Defines any visibility restrictions for the share. Possible values include:
CONNECTIONS– The share will be viewable by 1st-degree connections only.
PUBLIC– The share will be viewable by anyone on LinkedIn.

Am I missing something here?

@macmanx Thanks. Do you have a link to the documentation for this? I can only find the old docs.

@gemmaevans Until Jetpack 7.0 the shared posts’ visibility was “Public”. After updating they became “Connections Only”.

Thanks for looking at this.

The latter.