Looks interesting, but a couple of PHP issues

Hi KTS915,

Firstly thanks for your kind words. Regarding the PHP issues you have identified, these are non critical in that they just show if a setting hasn’t been set yet. However I have just released a new version of the plugin, version 3.4, which will resolve this specific issue. So thanks for bringing this up, I am always keen to improve things.

Yes you have identified a very annoying aspect of working with LinkedIn API’s which is that the token automatically expires after 60 days. Unfortunately as a developer there is no solution around this because LinkedIn uses OAuth 2.0 which requires user authentication. I guess one way around this would be to provide the plugin with your username and password and for the plugin to imitate the authentication process but I am not sure how to do this and I am sure LinkedIn would hate to know this was occurring. This approach isn’t great from a security point of view as well.

To make this process a little less lame what I have done is setup a dashboard warning message so you should receive a warning within 7 days of the token expiring. So this way you can ensure all posts will continue to be sent to LinkedIn. All you need to do is press the authentication button on the plugin settings and it should reset itself. I definitely feel the pain though because I have a couple of customers who are using my plugin and I need to login to their site every 60 days to reauthenticate! I would much rather just set it and forget it.

Thanks for the fix. I also love the idea of a warning message seven days before the token is set to expire, so I tried to set this up.

Unfortunately, I keep getting the message: “The redirect_uri does not match the registered value”

I have triple-checked everything. The only mismatch I can see is that your plugin tells me to use a URL starting with http for the oAuth 2.0 Redirect URL, whereas my site is all on https. But even after changing that in LinkedIn’s Authorized Redirect URLs box, I still get the same message.

Hi KTS915,

I am not sure about this, I haven’t heard this issue before from any other users. What I suspect is that perhaps your query plugin or something else is putting something at the end of the URL.

The URL should be like: https://yoursite.com/wp-admin/admin.php?page=wp_linkedin_auto_publish

There shouldn’t be any query strings at the end of the URL like: https://yoursite.com/wp-admin/admin.php?page=wp_linkedin_auto_publish?myparameter=value

If you are still experiencing the issue please provide me your login details so I can check this out. In the plugin settings you will find my email address. Thanks,

What I suspect is that perhaps your query plugin or something else is putting something at the end of the URL.

I’m sorry, but I’m not sure I understand this. There’s nothing being appended to the URL.

And what “query plugin” are you referring to? Do you mean Query Monitor? If so, I think you completely misunderstand what it does. But you should use it as you develop stuff. See https://www.ads-software.com/plugins/query-monitor/

provide me your login details so I can check this out.

Again, I’m sorry, but that’s actually against the forum rules. See https://codex.www.ads-software.com/Forum_Welcome#The_Bad_Stuff

Ok…

You have to understand that for developers to diagnose issues we sometimes need to login and see issues for ourselves. In this situation you have raised an issue that hasn’t been raised by any current users of the plugin which suggests there’s something unique about your environment. This could be a plugin, a theme, a server environment that is making the issue occur. I didn’t ask for your login details to be shared on the forum but rather to be emailed to me so it’s more secure.

If you want my help this is how I am going to help you, if you don’t want to send me your details I won’t help you as I can’t replicate the issue on my testing environment. The query monitor plugin, and I am very aware of its functionality thank you, can append query strings to the URL and if you entered this query string data into LinkedIn this could perhaps cause an issue.

Please remember this plugin is free and you are getting my time for free.

I do realize that the plugin is free, and I have never asked for your time. I would never be so presumptuous.

I simply reported the latest issue that I found. (And, just to augment that report, I can say that Query Monitor is not activated on the live site.) If you re-read my message, you will see that it’s just a report, with no questions asked anywhere.

The reason for such a report is just to alert you and anyone else who might currently or in future experience the same problem. If you had been able to describe how you might go about attempting to diagnose the cause, that would have been a bonus. (That would actually be much more use to me anyway, since I would be able to use that skill in future.)
But I did not expect you to provide with an outline of such steps; I assume you have other commitments just like the rest of us.

In any event, as I explained in my opening comment, I already have a plugin that can publish posts to LinkedIn, so it’s not necessary for me to get your plugin working in order for me to achieve what I want. But leaving my latest report does explain why I’ll be returning to the other plugin and not using this one.

How do you suppose I fix the problem if I can’t replicate it?

Just giving me your problem isn’t all that helpful if you don’t give me the opportunity to try and fix it.

I don’t necessarily expect you to fix it. As you said, the plugin’s free, and I don’t expect every plugin to work on every site. Sometimes that’s just life.

If you are interested in trying to fix it, then, as I said, I’d expect that you would set out what you would look at so that I can follow those steps myself. While I’m not a developer, I’m not a WP newbie either, and this is how almost every other developer I’ve come across has wanted to address an issue.

If you’re not comfortable with that, that’s up to you.

This is now marked as resolved.