LinkedIn Company Page error

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #131179
    Brad
    Participant

      I get the following error when auto posting to a LinkedIn Company page (not a personal page):

      [2014-02-03 12:56:52] – [Error] [LinkedIn – AIS] – -=ERROR=- Array ( [postID] => [isPosted] => 0 [pDate] => 2014-02-03 20:56:47 [Error] => ) | PostID: 8112 – Post Title Here

      The LinkedIn Page URL field in the Nextscripts plugin has this (along with email and password of the parent account):
      https://www.linkedin.com/company/43699

      and the LinkedIn Group ID has this: 43699

      The account has been authorized with LinkedIn and the Nextscripts plugin.

      #173620
      DK
      Participant

        Any luck with a resolution?

        I’m getting a similar error…

        #176272
        maarlok

          Yes, i have the same problem on Linkedin post.

          #177992
          NextScripts.com
          Participant

            What is your API version? This was fixed in the 2.14.8

            #178311
            maarlok
            Participant

              Linkedin connection now works correctly! Thank you!

              #179225
              NextScripts.com
              Participant

                Recent LinkedIn API connection problems like empty error message, “Auth Error – Error”, and broken account confirmation have been fixed in the latest version of the plugin – 3.3.2. Please update plugin on your site.

                #406814
                Elaia
                Participant

                  Hi,
                  I updated to last 3.4.16 (with pro version) and Linkedin publishing to company pages is broken. Test button works, but impossible to auto publish or manually publish a post.

                  #406904
                  NextScripts.com
                  Participant

                    Why exactly it’s impossible to auto publish? Are you getting any errors? Please check your Log/History tab and let me know what do you have there.

                    #406921
                    Elaia
                    Participant

                      Here is the test followed by the post sending :

                      [2015-04-08 09:49:36] – [Error] [LinkedIn – Linkedin] – -=ERROR=- Array ( [postID] => [isPosted] => 0 [pDate] => 2015-04-08 07:49:28 [Error] => ) | PostID: 409 – The Title

                      [2015-04-08 09:47:55] – [Test] [LinkedIn – Linkedin] – OK – TEST Message Posted

                      #407155
                      Chris
                      Participant

                        I’m having the same issue on 3.4.16.

                        [2015-04-09 10:33:07] – [Error] [LinkedIn – LinkedIn] – -=ERROR=- Array ( [postID] => [isPosted] => 0 [pDate] => 2015-04-09 10:33:02 [Error] => ) | PostID: 700 – Lord Lloyd Webber backs WiSpire
                        [2015-04-09 10:29:13] – [Error] [LinkedIn – LinkedIn] – -=ERROR=- Array ( [postID] => [isPosted] => 0 [pDate] => 2015-04-09 10:29:07 [Error] => ) | PostID: 700 – Lord Lloyd Webber backs WiSpire
                        [2015-04-09 10:28:27] – [Test] [LinkedIn – LinkedIn] – OK – TEST Message Posted

                        #407217
                        Ryan
                        Participant

                          Same issue.

                          Plugin Version: 3.4.16 (API Version: 2.16.3 [ID:10360]) [Pro – Multiple Accounts Edition]

                          [2015-04-09 09:01:20] – [Error] [LinkedIn – LinkedIn] – -=ERROR=- Array ( [postID] => [isPosted] => 0 [pDate] => 2015-04-09 13:01:16 [Error] => WP_Error Object ( [errors:WP_Error:private] => Array ( [http_request_failed] => Array ( [0] => Empty reply from server ) ) [error_data:WP_Error:private] => Array ( ) ) – ERROR )

                          This problem appears to of started after this:
                          [2015-04-07 15:54:01] – [SYSTEM NOTICE] [A] – –==## API UPDATED SUCCESSFULLY ##==–

                        Viewing 11 posts - 1 through 11 (of 11 total)
                        • You must be logged in to reply to this topic.