15 April, 2010

What is new in JSPT 2.2?

Better Performance and API Polishing

<div>
    The JSPT 2.2 is more better in performance then previous versions of
    JSPT due to Auto-loading and cache concept. It is also better in API.
    Two API's have been triggered onBeforeProfiletypeChange and
    onAfterProfiletypeChange. More triggers are planned, and these will be
    added before beta release.
</div>

Parameter changes into Settings

The global parameters of JSPT are replaced with Settings. You can set the different values over there. No need to go on Control Panel and click on Parameter. By just one click you can quickly move to Settings. It also helps in preserving configuration over component updates.

Profile Field Control

Control over Profile fields is added. Now admin can set the following properties of each Profile Fields.
  • Allow :- Through this admin can set that the profile field is allowed to the profile type or not. By default allowed to All.
  • Required :- Profile field is required for selected profile type. By default required for All.
  • Visible :- Through this you can set the visibility of field for profile type. Let Field1 is not set for Profile1. Then this field will not be visible on profile of Profile1's user. By default Visible for All
  • Editable After Registration :- Through this you can set the field will be editable after registration or not for selected profile type. If not selected for profile type then it will not be visible when editing profile.
  • Editable During Registration :- Through this you can set the field will be editable during registration or not for selected profile type. If not selected for profile type then it will not be visible when filling profile fields at the time of Registration, but can be editable after registration. By default editable for All.
Please Note - For working correctly you need to set to yes all properties of Profile Field in JomSocial. For e.g. publish,required,visible and registration should be set to yes.
<h3 style="color: #135cae; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 15.800000190734863px;">
Invisible Profile Type</h3>

<div>
    The Feature for Invisible Profile Type is added. In invisible profile
    type the Profile Type will be published but not visible to user in
    frontend. The admin can change profile type of any user to invisible
    profile type from backend.
</div>

<h3 style="color: #135cae; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 15.800000190734863px;">
Friend Support in ACL Rule</h3>

<div>
    Friend Support in Acl Rule has been implemented. At the time of
    creating ACL Rule you can select that Yes if you want to apply that
    rule to your friend ( of blocked Profile Type ), otherwise select No.
</div>

<h3 style="color: #135cae; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 15.800000190734863px;">
Guest Profile Type</h3>

<div>
    Now the guest user can also work like the general profile type member.
    You have to select the Guest Profile Type from Setting screen of JSPT,
    otherwise default profile type will be assigned to him. You can limit
    guest user to create ACL Rule for selected Guest profile type.
</div>

<h3 style="color: #135cae; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 15.800000190734863px;">
Application Control</h3>

<div>
    Now applications can be viewed according to Owner, Visitor and Both.
</div>

<ul style="color: #333333; font-family: Tahoma, Helvetica, Arial, sans-serif; font-size: 12px; line-height: 15.800000190734863px;"><li>Owner :- This will display applications according to Profile Owner.
Only those display applications will be visible which are added and allowed
to profile owner.</li>

    <li>Visitor :- This will block the display application of profile
    visitor. In other words visitor will be able to view only those
    applications which is allowed to him(visitor), when visiting other
    user's profile.</li>

    <li>Both :- This will block the the display applications of both users
    Profile Owner and Profile Visitor.</li>
</ul><h3 style="color: #135cae; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 15.800000190734863px;">
Sync Up</h3>

<div>
    If any user's profile-type information does not exists than the user
    have to synced up. Sync-up is here since JSPT 2.0, we have improved the
    performance of this functionality. Now during Sync-Up all the
    properties of users are synced up according to Default Profile Type.
    e.g.
</div>

<ul style="color: #333333; font-family: Tahoma, Helvetica, Arial, sans-serif; font-size: 12px; line-height: 15.800000190734863px;"><li>Privacy set according to default profile type</li>

    <li>Template</li>

    <li>Avatar :- If user's avatar is custom then it will not be changed.
    etc.</li>
</ul><h3 style="color: #135cae; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 15.800000190734863px;">
Link to Profiletypes ( No need to select Profile Type )</h3>

<div>
    Now you can create the direct link to register as selected Profile
    Type. this can be done by creating a menu link. Select the Profile Type
    at the time of creating Menu Link. If user clicks on it the attached
    profile type will be selected and he/she will be redirected to the
    registration page (No more Select Profiletype page)
</div>

<h3 style="color: #135cae; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 15.800000190734863px;">
Restrict upload Avatar in Registration</h3>

<div>
    By creating ACL Rule for Can't change avatar you can not only restrict
    user to Change avatar after registration, also you can restrict them to
    upload avatar at the time of Registration. This is possible in JSPT
    2.2.
</div>

<h3 style="color: #135cae; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 15.800000190734863px;">
Tips and Tricks</h3>

<ul style="color: #333333; font-family: Tahoma, Helvetica, Arial, sans-serif; font-size: 12px; line-height: 15.800000190734863px;"><li>Profile Type Avatar at the time of registration are resize able. You
have to change the value of two constant defined in Joomla -&gt; components
-&gt; com_xipt -&gt; defines.xipt.php

        <ul><li>REG_PROFILETYPE_AVATAR_HEIGHT</li>

            <li>REG_PROFILETYPE_AVATAR_WIDTH</li>
        </ul></li>

    <li>To set the number of user which must be synced up in one request to
    server, set the value of constant in above same file

        <ul><li>SYNCUP_USER_LIMIT</li>
        </ul></li>
</ul><h3 style="color: #135cae; font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 15.800000190734863px;">
Note:-</h3>

<ul style="color: #333333; font-family: Tahoma, Helvetica, Arial, sans-serif; font-size: 12px; line-height: 15.800000190734863px;"><li>Be aware,<span style="text-decoration: underline"><strong> don't
use JSPT 2.2 Beta on your live site without
testing.</strong></span> It has significant changes, which can break
functionality of your site.</li>

    <li>This version is tested at our end, but please test before using at
    live site.</li>

    <li>You can download JSPT 2.2 at <a class="doclink" href="http://test.joomlaxi.com/index.php?option=com_docman&amp;task=doc_download&amp;gid=28&amp;Itemid=99" style="color: #1b57b1; text-decoration: none;">JSPT 2.2 Beta</a>
    </li>
</ul></div>
blog comments powered by Disqus