Hi,
the plugin “Blog Post Linking” work correctly for admin users, but for editors and authors the specific forum linking widget in /wp-admin/post-new.php appear empty and do not create automatic topic on new post.
Maybe have i to set some permission that i don’t found yet?
Thanks
Check in your forum permissions for the permission sets being applied to the user groups for those users to make sure you have allowed them to use blog linking.
The rules are that a user must have the forum permission turned on and must be able to publish blog posts.
Something missing.. i don’t understand.
I have created a forum group called “authors”,
i have assigned new permissions called “authors permissions”, this is “standard permissions” with added:
* Can create linked blog post and forum topics
* Can break link between blog posts and forum topics
Finally in every forum i have added permission for author group with author permission.
Then i create a wordpress temp user with wordpress type “author” and i assigned forum “author” group.
The linking widget is always empty..
I didn’t say anything was missing…
Could it simply be that your users do not have this option turned on in the WP screen options at the top of the page?
Sorry, i mean probably something is missing in my configuration..
The widget is present and enabled, but empty:
Maybe there are some kind of conflict with other plugin?
The screenshot is for temp user created when i go in /wp-admin/post-new.php (https://simple-press.com/support-forum/sp5-plugin-topics/blog-post-linking-not-work-for-editor-and-author/#p106149), i am trying to fix it for users.
If i will enter in /wp-admin/post-new.php with admin user there are no problem, it work correctly.
With admin users the widget is ok:
But with author/editor user the widget appear but it is empty:
Ok, i fix it.
I deleted plugin settings and repeat same operations for create permission and groups, i deleted the user too and recreated new one.. now it work.
Thanks
I have to be honest and say I am relieved as I had no idea what might have gone wrong 🙂
So perhaps some spurious data had somehow manifested itself. Sorry about whatever it was but most glad you are back up and running.
