XPress - A theme and bridge for bringing WordPress into XenForo [Deleted]

There's likely a second exception logged in the ACP error log. In short, XLink hasn't been able to make a connection to your WordPress installation for one of many reasons. Maybe you put the wrong URL, your WordPress installation has restricted access or resides behind a proxy?

I got the same error as many others here:

Exception: No route was found matching the URL and request method in src/addons/ThemeHouse/XPress/RemoteHandler/Traits/APICall.php at line 83

  1. ThemeHouse\XPress\RemoteHandler\Platform->callAPI() in src/addons/ThemeHouse/XPress/RemoteHandler/Platform.php at line 49
  2. ThemeHouse\XPress\RemoteHandler\Platform->syncSettingsToRemote() in src/addons/ThemeHouse/XLink/Admin/Controller/Platform.php at line 164
  3. ThemeHouse\XLink\Admin\Controller\Platform->actionSave() in src/XF/Mvc/Dispatcher.php at line 321
  4. XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 248
  5. XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 100
  6. XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 50
  7. XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2177
  8. XF\App->run() in src/XF.php at line 390
  9. XF::runApp() in admin.php at line 13

I think a got a pretty standard installation.
Disk path: /var/www/html/wp.
URL: http://myXenForoSite.som/wp/

I havent done anything other to Wordpress then installed it and added the addons.
When I use the Xpress theme Wordpress site looks weird:
197452

This is how the default Wordpress theme looks like:
197453


When I try to delete the link I got errors too:


Exception: No route was found matching the URL and request method in src/addons/ThemeHouse/XPress/RemoteHandler/Traits/APICall.php at line 83

  1. ThemeHouse\XPress\RemoteHandler\Platform->callAPI() in src/addons/ThemeHouse/XPress/RemoteHandler/Platform.php at line 178
  2. ThemeHouse\XPress\RemoteHandler\Platform->_delete() in src/addons/ThemeHouse/XLink/RemoteHandler/AbstractPlatform.php at line 100
  3. ThemeHouse\XLink\RemoteHandler\AbstractPlatform->delete() in src/addons/ThemeHouse/XLink/Admin/Controller/Platform.php at line 185
  4. ThemeHouse\XLink\Admin\Controller\Platform->actionDelete() in src/XF/Mvc/Dispatcher.php at line 321
  5. XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 248
  6. XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 100
  7. XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 50
  8. XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2177
  9. XF\App->run() in src/XF.php at line 390
  10. XF::runApp() in admin.php at line 13
Wordpress Health Check:
197454
Any ideas?
 
There's likely a second error below the first in the stack trace in the ACP error log that gives you more information.
 
I got the same error as many others here:

Exception: No route was found matching the URL and request method in src/addons/ThemeHouse/XPress/RemoteHandler/Traits/APICall.php at line 83

  1. ThemeHouse\XPress\RemoteHandler\Platform->callAPI() in src/addons/ThemeHouse/XPress/RemoteHandler/Platform.php at line 49
  2. ThemeHouse\XPress\RemoteHandler\Platform->syncSettingsToRemote() in src/addons/ThemeHouse/XLink/Admin/Controller/Platform.php at line 164
  3. ThemeHouse\XLink\Admin\Controller\Platform->actionSave() in src/XF/Mvc/Dispatcher.php at line 321
  4. XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 248
  5. XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 100
  6. XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 50
  7. XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2177
  8. XF\App->run() in src/XF.php at line 390
  9. XF::runApp() in admin.php at line 13
I think a got a pretty standard installation.
Disk path: /var/www/html/wp.
URL: http://myXenForoSite.som/wp/

I havent done anything other to Wordpress then installed it and added the addons.
When I use the Xpress theme Wordpress site looks weird:
View attachment 197452

This is how the default Wordpress theme looks like:
View attachment 197453


When I try to delete the link I got errors too:


Exception: No route was found matching the URL and request method in src/addons/ThemeHouse/XPress/RemoteHandler/Traits/APICall.php at line 83

  1. ThemeHouse\XPress\RemoteHandler\Platform->callAPI() in src/addons/ThemeHouse/XPress/RemoteHandler/Platform.php at line 178
  2. ThemeHouse\XPress\RemoteHandler\Platform->_delete() in src/addons/ThemeHouse/XLink/RemoteHandler/AbstractPlatform.php at line 100
  3. ThemeHouse\XLink\RemoteHandler\AbstractPlatform->delete() in src/addons/ThemeHouse/XLink/Admin/Controller/Platform.php at line 185
  4. ThemeHouse\XLink\Admin\Controller\Platform->actionDelete() in src/XF/Mvc/Dispatcher.php at line 321
  5. XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 248
  6. XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 100
  7. XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 50
  8. XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2177
  9. XF\App->run() in src/XF.php at line 390
  10. XF::runApp() in admin.php at line 13
Wordpress Health Check:
View attachment 197454
Any ideas?

I was getting same error so i check cloudflare.com ip (that using my site) and whitelist it in my server Firewall and in Wordfence plugin (Work perfect for me).
 
Question about the WP Toolbar Visible menu.

If you are a member in XF, an account will also be created in WP.
I do not think you need to use the WP Toolbar Show menu.
However, I can not find a menu to hide the WP Toolbar Show menu when I create an account.

Do all accounts have to manually unhide the WP toolbar after signing up?

I would like to know how to add the WP toolbar auto-disable feature to all accounts automatically when I sign up.
 
Question about the WP Toolbar Visible menu.

If you are a member in XF, an account will also be created in WP.
I do not think you need to use the WP Toolbar Show menu.
However, I can not find a menu to hide the WP Toolbar Show menu when I create an account.

Do all accounts have to manually unhide the WP toolbar after signing up?

I would like to know how to add the WP toolbar auto-disable feature to all accounts automatically when I sign up.
We solved the problem.

Wp-admin - includes -admin.php
Wp-admin - includes -admin.php

// ------------- This website is read only -
add_action ('after_setup_theme', 'no_admin_bar');

function no_admin_bar () {
if (! current_user_can ('administrator') &&! is_admin ()) {
show_admin_bar (false);
}
}
// ------------- this website is read only - so staff can log in ------------------
 
Has anyone gotten the Latest Articles widget to work? I can't get it to show on the wordpress sidebar or anywhere on the XF side.
 
There's likely a second error below the first in the stack trace in the ACP error log that gives you more information.

Yes, here:
Stack spor

#0 src/addons/ThemeHouse/XPress/RemoteHandler/Platform.php(178): ThemeHouse\XPress\RemoteHandler\Platform->callAPI('/xpress/v1/sett...', Array, 'POST')
#1 src/addons/ThemeHouse/XLink/RemoteHandler/AbstractPlatform.php(100): ThemeHouse\XPress\RemoteHandler\Platform->_delete()
#2 src/addons/ThemeHouse/XLink/Admin/Controller/Platform.php(185): ThemeHouse\XLink\RemoteHandler\AbstractPlatform->delete()
#3 src/XF/Mvc/Dispatcher.php(321): ThemeHouse\XLink\Admin\Controller\Platform->actionDelete(Object(XF\Mvc\ParameterBag))
#4 src/XF/Mvc/Dispatcher.php(248): XF\Mvc\Dispatcher->dispatchClass('ThemeHouse\\XLin...', 'Delete', Object(XF\Mvc\RouteMatch), Object(ThemeHouse\XLink\Admin\Controller\Platform), NULL)
#5 src/XF/Mvc/Dispatcher.php(100): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(ThemeHouse\XLink\Admin\Controller\Platform), NULL)
#6 src/XF/Mvc/Dispatcher.php(50): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#7 src/XF/App.php(2177): XF\Mvc\Dispatcher->run()
#8 src/XF.php(390): XF\App->run()
#9 admin.php(13): XF::runApp('XF\\Admin\\App')
#10 {main}

-------------

Previous GuzzleHttp\Exception\ClientException: Client error: POST http://mysite.com/wp/?xf_user=1&rest_route=%2Fxpress%2Fv1%2Fsettings resulted in a 404 Not Found response:
{"code":"rest_no_route","message":"No route was found matching the URL and request method","data":{"status":404}}
- src/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113
#0 src/vendor/guzzlehttp/guzzle/src/Middleware.php(66): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response))
#1 src/vendor/guzzlehttp/promises/src/FulfilledPromise.php(39): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response))
#2 src/vendor/guzzlehttp/promises/src/TaskQueue.php(47): GuzzleHttp\Promise\FulfilledPromise::GuzzleHttp\Promise\{closure}()
#3 src/vendor/guzzlehttp/promises/src/Promise.php(246): GuzzleHttp\Promise\TaskQueue->run(true)
#4 src/vendor/guzzlehttp/promises/src/Promise.php(223): GuzzleHttp\Promise\Promise->invokeWaitFn()
#5 src/vendor/guzzlehttp/promises/src/Promise.php(62): GuzzleHttp\Promise\Promise->waitIfPending()
#6 src/vendor/guzzlehttp/guzzle/src/Client.php(131): GuzzleHttp\Promise\Promise->wait()
#7 src/vendor/guzzlehttp/guzzle/src/Client.php(89): GuzzleHttp\Client->request('post', 'http://mysite...', Array)
#8 src/addons/ThemeHouse/Core/Http/HttpClient/20181220.php(23): GuzzleHttp\Client->__call('post', Array)
#9 src/addons/ThemeHouse/XPress/RemoteHandler/Traits/APICall.php(71): ThemeHouse\Core\Http\HttpClient->simplePost('http://mysite...', Array, Array)
#10 src/addons/ThemeHouse/XPress/RemoteHandler/Platform.php(178): ThemeHouse\XPress\RemoteHandler\Platform->callAPI('/xpress/v1/sett...', Array, 'POST')
#11 src/addons/ThemeHouse/XLink/RemoteHandler/AbstractPlatform.php(100): ThemeHouse\XPress\RemoteHandler\Platform->_delete()
#12 src/addons/ThemeHouse/XLink/Admin/Controller/Platform.php(185): ThemeHouse\XLink\RemoteHandler\AbstractPlatform->delete()
#13 src/XF/Mvc/Dispatcher.php(321): ThemeHouse\XLink\Admin\Controller\Platform->actionDelete(Object(XF\Mvc\ParameterBag))
#14 src/XF/Mvc/Dispatcher.php(248): XF\Mvc\Dispatcher->dispatchClass('ThemeHouse\\XLin...', 'Delete', Object(XF\Mvc\RouteMatch), Object(ThemeHouse\XLink\Admin\Controller\Platform), NULL)
#15 src/XF/Mvc/Dispatcher.php(100): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(ThemeHouse\XLink\Admin\Controller\Platform), NULL)
#16 src/XF/Mvc/Dispatcher.php(50): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#17 src/XF/App.php(2177): XF\Mvc\Dispatcher->run()
#18 src/XF.php(390): XF\App->run()
#19 admin.php(13): XF::runApp('XF\\Admin\\App')
#20 {main}


I was getting same error so i check cloudflare.com ip (that using my site) and whitelist it in my server Firewall and in Wordfence plugin (Work perfect for me).

I'm hosting my servers on-premises, with both wordpress and XenForo on the same webserver, so I don't see how this "XLink" issue can be related to firewall. And as far as I know I have nothing to do with coudflare? Or is it some Wordpress stuff that uses som cloud functions? Sorry for my lack of knowledge.
 
I'm hosting my servers on-premises, with both wordpress and XenForo on the same webserver, so I don't see how this "XLink" issue can be related to firewall. And as far as I know I have nothing to do with coudflare? Or is it some Wordpress stuff that uses som cloud functions? Sorry for my lack of knowledge.

XenForo interacts with WordPress via the WordPress API. If your server can't reach the WordPress API, or if the WordPress API can't identify the calls as coming from the same server, XPress will fail to interact with the API and throw the given error. If the URL you've entered in the platform settings is correct, a 404 normally means that WP failed to authenticate the call from coming from the same server, which for example happens if the call goes through a proxy such as cloudflare.

We strongly recommend to resolve that by configuring either your server or firewall in a way that lets the server make the call directly, as that'll also improve performance of the bridge, but if that should not be possible, you can bypass the verification by setting up an API password in both configurations instead, as I've outlined in this post.
 
@Finalmarco regarding your review, just wanted to say that we offer a money back guarantee. Its a bridge, simply cannot work in every environment. Perhaps you can consider that in your review. I don't find it fair to review us on a feature we never claimed to have, but I understand. And appreciate your theme review :P
 
Back
Top Bottom