chimac
Forum Replies Created
-
I have been testing it everyday and since disabling that plugin it has worked perfectly. Today I enabled the plugin and it still continues to work. As a side note I suspect that there may have something happening with that plugin since for the last two weeks it seems to duplicate the image in the media library. It wasn’t a priority so I didn’t troubleshoot it. Now it is only showing one image in the image library with that other plugin, so perhaps that was the cause.
Oh I forgot to mention that I deleted my company page so that may have contributed to the issue. Since it had to post at two different places, and LinkedIn often has funny glitches perhaps this confused that other plugin. This is just wild speculation. I don’t have hard evidence.
No matter I feel confident about this solution. If it bothers me again I will disable this plugin and stop using it. Thank you!
- This reply was modified 4 months, 1 week ago by chimac.
I’m sorry I forgot to answer your questions. This is my personal site, but because of the way that LinkedIn used to work with posting plugins I setup the business/company side so that I could autopost with other plugins.
I am only using my personal WordPress account with my LinkedIn profile which also has a business aspect. I guess I should try to simplify this by seeing if I can delete the business/company part. I will look into that as well.
Thanks!
I disabled a plugin called Automatic featured images from Youtube/Vimeo since it was the only plugin that interacted with LinkedIn but I am not sure that solved it.
I looked in the permitted applications and strangely even though I had approved it, it wasn’t in the list. However after disabling that plugin I was able to connect and not have an error and the app shows as having permission as an allowed app in LinkedIn. Time will tell and I will update you if anything changes.
I just posted something and it worked perfectly with that plugin disabled.
Brian
Thank you for your response.
I will try troubleshooting at the plugin level. I will let you know if I discover anything.
Brian
Tran, you are a genius! That fixed it. I confirmed it with the WP repair URL on my own domain. I love this plugin! When I make more money I will buy your other products.
Forum: Plugins
In reply to: [WP LinkedIn Auto Publish] Suddenly can’t post to LinkedInThanks for the follow up. Yes it was resolved. I didn’t see anything in the regular WordPress markup that would cause a problem but the post wasn’t worth the effort to troubleshoot it further. Not every post is a winner.
Forum: Plugins
In reply to: [WP LinkedIn Auto Publish] Suddenly can’t post to LinkedInLooked like the issue is resolved. I looked over the code of that post and all I had was normal internal linking using the WordPress linking function in the toolbar. Done that thousands of times. Here is the next post showing the issue is resolved. Thanks for your help.
Forum: Plugins
In reply to: [WP LinkedIn Auto Publish] Suddenly can’t post to LinkedInCrazy. The new post works with an image and all. I haven’t done anything different in that post but something in the content isn’t allowing it to publish. I won’t publish without photo as well so its something in the code.
Forum: Plugins
In reply to: [WP LinkedIn Auto Publish] Suddenly can’t post to LinkedInVery interesting. I made a new post and copied the content of that post into the new one and with a different title it wouldn’t publish. I verified on LinkedIn that your plugin has permission to publish and it shows today as the registration date since I did the Connect to LinkedIn thing successfully today. Im going to try to publish a different new post. The other post had already been previously published that worked and surprised me.
Forum: Plugins
In reply to: [WP LinkedIn Auto Publish] Suddenly can’t post to LinkedInYou won’t believe what just happened. I was working with another company about a different issue about having my website validated with some text and when I randomly updated a page it published on LinkedIn! Clearly something is wrong with this post.