TransPlace
03-15-2016, 06:05 AM
Hello,
I create a large web application and would like to integrate it with the forum vBulletin v5.2.0 patch level 1. What I care about:
Create a session on the forum in an external application (running on the same domain, the path to the directory points to another vhost), preferably using my server OAuth2.
Login to user account aside from logging mechanism forum. At the forum accounts are imported from an external database and therefore you user not know his account password and the session is created at the time of logging in an external system. (point 1).
Since the extension API, and more specifically `Api_User :: login` does not fulfill its role for the reason that if you try to log on incorrect data code extension will not even perform because of caught exception.
I also tried to create my own extension APIs in order not to interfere with the current flow but nothing out of it. Someone once remarked that such a modification could have to be really helpful but nothing more ...
// vB_Api::callNamed
if (!is_callable(array ($this, $method)))
{
// If the method does not exist, an extension might define it
return;
}
Can someone please help me on this?
What more, PHP hooks on which you are currently working on also will be great place to make this changes.
Another question is how I can (if I can) connect statsd stats to VBulletin? As I saw you are still using log4php which is not maintained since 2012, any chance for Monolog or other "today's" solution?
I create a large web application and would like to integrate it with the forum vBulletin v5.2.0 patch level 1. What I care about:
Create a session on the forum in an external application (running on the same domain, the path to the directory points to another vhost), preferably using my server OAuth2.
Login to user account aside from logging mechanism forum. At the forum accounts are imported from an external database and therefore you user not know his account password and the session is created at the time of logging in an external system. (point 1).
Since the extension API, and more specifically `Api_User :: login` does not fulfill its role for the reason that if you try to log on incorrect data code extension will not even perform because of caught exception.
I also tried to create my own extension APIs in order not to interfere with the current flow but nothing out of it. Someone once remarked that such a modification could have to be really helpful but nothing more ...
// vB_Api::callNamed
if (!is_callable(array ($this, $method)))
{
// If the method does not exist, an extension might define it
return;
}
Can someone please help me on this?
What more, PHP hooks on which you are currently working on also will be great place to make this changes.
Another question is how I can (if I can) connect statsd stats to VBulletin? As I saw you are still using log4php which is not maintained since 2012, any chance for Monolog or other "today's" solution?