Release of the new version of the modLivestreet 0.3.0-rc module

Continuing our topic about the MODX and Livestreet bundle module, I present a new version of the modLivestreet module: livestreet-0.3.0-rc.transport.zip



What's new? Yes, almost everything :-) Module rewritten from scratch.

1. Significantly changed (improved) the logic of processing requests for LiveStreet.

2. Added synchronized user registration in MODX and LiveStreet. Now registering a user through the MODX admin panel, the user is automatically created in LiveStreet, and processing a request for LiveStreet to register a user, registration passes through MODX, which in turn also provides simultaneous user registration in both engines.

This feature can be disabled through the setting.



Under the cut of the work scheme (simplified) MODX in the standard version and with the modLivestreet module and a more detailed description of how synchronous registration of users in MODX and Livestreet takes place (Scheme, how registration has changed in MODX will be posted later), as well as the source code.

')

UPD: build a package on github: github.com/Fi1osof/modx-livestreet





So how does this module work?



1. The main plugin in this module is triggered by two events - onHandleRequest and onPageNotFound.

In the first case, there is a check for requests to Livestreet in principle (and initialization of Livestreet variables), as well as a check for accessing static Livestreet files and its individual modules (such as Captcha).

In the second case, another task is performed: if the MODX found the target page when processing the request, then the onPageNotFound event basically does not work, and LiveStreet will not be processed, unless the livestreet.run snippet is explicitly called in the MODX document, which performs the LiveStreet request. This approach allows us not to tie MODX only on LiveStreet. That is, we can make a completely independent site on MODX, but make a section / forum / (or a separate subdomain of forum.site.ru), define the incoming page there, register a call to the snippet [[! Livestreet.ru]]] (to provide the root site), in the settings specify the livestreet.url_perfix '/ forum /' and all. All requests for the mask /forum/.* will be executed with the LiveStreet call and we get our blog. Here you can add a verification of rights or call only a specific branch of the blog, etc.

In the case, if the document is not found and the onPageNotFound event is raised, and the URL corresponds to the Livestreet section, then the Livestreet request is already executed. There is a small disclaimer: if this is a request for registering a Livestreet user, then a snippet registration user snippet.livestreet.ajax-registration.php is called





In principle, as you can see, the plugin is not at all great for such functionality. So anyone will understand if he wants to modify it to fit his needs.



2. To execute requests for LiveStreet snippet snippet.livestreet.run is used.





He is quite small. We bluntly call LiveStreet, buffer it and return the result. Thus, it is possible to process both the content before output and the results of Ajax requests to process the execution check (this is especially important when registering users, since in the case of synchronous registration of users in MODX and LiveSteet, it is necessary to interrupt registration in case of checking the registration of the user as in MODX, so in Livestreet).



There is again a reservation. In Livestreet, the content rendering class is not quite competent. In the Ajax output mode, LS makes a stupid exit (); that breaks the work of the entire module. Therefore, in LS it is necessary to make a small manipulation:

In the components / livestreet / docs / forLiveStreet / source / engine / modules / viewer / Viewer.class.php file

in the DisplayAjax method ($ sType = 'json'), replace exit (); on return;

and in the Display method ($ sTemplate) replace

 if ($this->sResponseAjax) { $this->DisplayAjax($this->sResponseAjax); } 

on

 if ($this->sResponseAjax) { $this->DisplayAjax($this->sResponseAjax); return; } 

In principle, this will not change the independent work of Livesreet, but will give us the opportunity to process the results of Ajax requests and continue our logic.



3. Snippet livestreet.ajax-registration.

This snippet handles a Livestreet user registration request.





If synchronous registration is disabled in the settings, then the snippet is not executed, and if this is a direct request to register a user in Livestreet, then the request is sent to Livestreet and that's it.

If synchronous registration is enabled, the request is sent not to Livestreet, but to register the user in MODX (the core / components / livestreet / processors / security / user / ajaxCreate.class.php processor is called, where the extended modUserCreateProcessor class is called). The essence of calling this processor is simple - call the base processor to create a MODX user through the system processor modx / processors / security / user / create.class.php

The reason for this call is that we cannot directly call this processor, because it checks for the right to create new users, and an unauthorized user does not have this right. Therefore, in this class, we simply overwrite the verification of this right (For a hint on this technique, special thanks bezumkin ).







Well, when a user is registered in MODX, we post our plug-in livestreet_users for the OnBeforeUserFormSave event.





At the time of registration of a MODX user, after all checks (if everything is OK), a plugin is executed and an attempt is made to register a user in LiveStreet. If the attempt fails, we return LiveStreet errors and interrupt the registration of a MODX user. If everything is ok, then we finally register the user in MODX.

Thus, we achieve that users can be registered through the MODX admin area, and through FrontEnd, and there and there we will see all possible errors, and we will get user registration in MODX, and in LiveStreet. And in the future, these users, if necessary, can be linked by email (as in LS, email is a unique key).



That's all :-)

That's what I love MODX for::) We have seriously changed the work of the engine, without affecting the byte of the code of the engine itself.

But under MODX there is no social module.

But Livestreet is an excellent social application, but it does not provide such an API as MODX. They even have no admin as such.

But together these engines can give a great product! I will continue to develop this module.



UPD 2: New release released: modlivestreet-0.4.1-rc.transport.zip

New:

1. All elements and settings now have the modLivestreet prefix, because unfortunately the new module is not backward compatible with the previous version. But surely this will not be a problem for anyone. It is enough to remove the old module and put a new one and on the main page change to

2. Added check for the extension of downloaded files from the / templates /, / uploads / directories, etc., in order not to download .php, etc.

Of course, there shouldn't be such files there, but at least in / skin / config / there is such a file.



UPD 3: Security Note: modxlivestreet.ru/blog/modLivestreet_security/7.html