-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting: Limited connection established #327
Comments
Someone said something about too many post types. How do I check this? |
@anton-roos a couple questions/comments for you:
Let me know if neither of those two questions/issues apply in your case and we can continue to triage your issue... thanks! |
Hello There, I was very happy to see your plugin, but after 3 hours testing ... still doesn't work. Same issue "authentication failed."
I don't know where to look now. Settings are very simple, but ... I'm missing something or ...? Please help me out. Plugin would be a great gift ... if we get it work. p.s. The installation instructions are very poor. Already thought about a Youtube movie? Looking forward to your reply. Thanks in advance. Kind regards, Webagent05 |
@Webagent05 we released version 1.4 earlier today with updated instructions and information about setting up external connections. If you're not on 1.4, then please update and let me know if you're still unable to properly setup the external connections... thanks! |
@jeffpaul I still have the same message. I made an application password. Websites are running on the same server, https, ... no special settings, no cache plugins enabled. What's next we can do, to find out the issue? Kind regards, Webagent05 ps. Running on PHP7.2 |
How many custom post types do you have?
…On Sat, Mar 9, 2019, 23:06 Webagent05 ***@***.***> wrote:
@jeffpaul <https://github.com/jeffpaul> I still have the same message.
I made an application password.
Used the username + application password.
Websites are running on the same server, https, ... no special settings,
no cache plugins enabled.
What's next we can do, to find out the issue?
Kind regards,
Webagent05
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#327 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCI38L0moYSx5A9ugBTylCSE9Wq0aa0ks5vVAY1gaJpZM4a0STM>
.
|
@jeffpaul got it solved. After update connection is working. But now I'm checking the canonical function. I can't find the canonical url in my source code. Looked around and found some information between the posts here. Checked the source code and seems to me compatibility is integrated, ... but seems not to work ... not showing canonical link. Kind regards, Webeagent05 p.s. I like the idea of the plugin, would love to contribute with features. ;) |
@Webagent05 I see from #346 that you were able to get things setup, so I'm not sure if you're still having issues with the Yoast. I'm checking with our team member who's most familiar with that part of the codebase and will get back to you with any details. |
@Webagent05 you can use |
@anton-roos any updates on your setup testing? |
@anton-roos here are some updated instructions for setting up External Connections, please give them a try and see if that helps resolve your issues: https://github.com/10up/distributor/tree/fix/readme-instructions#setup-external-connections-using-application-passwords. Thanks! |
Correction on comment... Hi all, what I noticed when add a rule to htaccess ... when wordpress update runs. The rule dissapears. So evey update of WP need to add "authenticaion rule" again. Maybe need to check the htaccess (not config file) file. |
@Webagent05 are those changes related to Distributor or something else? |
Wordpress core .... update also updates rewrite engine rules. Application password plugin. RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization}] Everytime wordpress core update this rule dissapears in htaccess, .... Sorry not wordpress config as mentioned in my earlier comment. |
@jeffpaul I am still struggling, even after updating to 1.4 |
@anton-roos the most current version of Distributor is 1.4.1, please ensure you're using that on all your sites. Also, can you confirm that you followed the External Connections steps here: https://github.com/10up/distributor/tree/fix/readme-instructions#setup-external-connections-using-application-passwords ? |
I got it to work by deleting all information from the database (External Connections) etc. Then following the steps EXACTLY like on the link thank you. @jeffpaul it did give me an error at first but came right after a while. |
@anton-roos do you happen to recall what the error message was and when/where it appeared? |
@anton-roos I'm going to close this issue as resolved, but please do let me know if you're running into any further issues so we can try to help... thanks! |
@jeffpaul I am still getting Could not pull content from connection due to error. I am not sure why this is, what else can I do to try and find the problem? |
@anton-roos on the site that you're viewing the Pull Content screen, if you go to the External Connections screen, what do you see as the Title / URL / Status / Date information for the site you're trying to pull content from? Also, what version of WordPress and Distributor are you using on those sites? |
@anton-roos will you please confirm the details from my prior question so I can continue to try and help troubleshoot for you? |
1 similar comment
@anton-roos will you please confirm the details from my prior question so I can continue to try and help troubleshoot for you? |
Hi @jeffpaul I will try recreate it again tomorrow and if possible post a few screenshots. |
@anton-roos any results from your testing? |
I'm closing this due to lack of response and assuming connections are working correctly, but please re-open with additional details if things are not functioning as expected... thanks! |
I am using the WordPress.com rest API and I still get this error.
Authentication failed. Push distribution unavailable. Pull distribution limited to basic content, i.e. title and content body.
The text was updated successfully, but these errors were encountered: