Mapping

Beakdown Of A Typical EssenceOne Membership Site !

index.php----calls---- m0 Module Class Router

        m0------calls----m1,m2,m3,m4,m5,m6,m7,m8,m9 add more

                Module Class Page Routers v=views, c=controllers

                m1---static module--------calls v1,c1 page parts for home about login join

                m2---members module---calls v2,c2 page parts for profile wall settings aboutme

                m3---groups module------calls v3,c3 page parts for list create delete update wall

                m4---albums module------calls v4,c4 page parts for list create delete update wall

                m5---friends module------calls v5,c5 page parts for list add delete accept view

                m6---messenger module--calls v6,c6 page parts for inbox conversation delete

                m7---apps module---------calls v7,c7 page parts for list create delete update api

add more--------------------------------------------------------------------------------------------------

                m10---admin module-------calls v10,c10 page parts for users wall moderation block info

Each Module Class Page Router below stacks and stages all needed pages by views and controllers needed for each page and builds them upon conditional request.

• c2/user_check.php-----------------scripts session redirect before header view
• v2/header.php
• v2/horizontal_menu.php
• c2/left_user_profile.php-----------scripts user profile data
• v2/left_user_view.php
• c2/users_content_wall.php--------scripts users wall page content
• v2/users_content_view.php
• c5/right_friends_list.php----------scripts adding the m5/friends module parts
• v5/right_friends_view.php--------view for m5 friends module list
• v2/footer.php

Mixing Module Parts Easily.

c2/user_check.php-----------------scripts session redirect before header view

v2/header.php

v2/horizontal_menu.php

c2/left_user_profile.php-----------scripts user profile data

v2/left_user_view.php

c4/albums_content_list.php--------scripts albums list data

v2/albums_content_view.php

c3/right_groups_list.php----------scripts adding the m3/groups module data

v3/right_groups_view.php--------view for m3 groups module list

v2/footer.php

We take the above a step even more alphanumerically by naming the template page-parts and controllers also within the Module Class Page Routers and by stacking the controllers above each view where they are needed for auto inclusion of data dynamically.

a=header,b=horizontal menus,c=left menu, d=the page content,e=right menu and f=footer.

c2/user_check.php-----------------scripts session redirect before header view

v2/a1.php

v2/b1.php

c2/c1.php-----------scripts user profile data

v2/c1.php

c4/dalbums.php--------scripts albums list data

v2/dalbums.php

c3/e1.php----------scripts adding the m3/groups module data

v3/e1.php--------view for m3 groups module list

v2/f1.php

When using our .htaccess (deny to all) now we only pass the module mock name and mock page name without giving out our protected file names. So index.php/albums/list/ using .htaccess or index.php?mod=albums&page=list if you wish not to change using the .htaccess as only deny to all makes no difference. Only when passing the users credentials use sessions, hashes and salts. The idea is to mask the users ID by using a md-5 or comparable hash for the users NAME or ID bef0re passing it in the browser. index.php?mod=friends&page=viewfriend&fid=xj84eedsalkm77vbg8e3lp0bx61mn7fz then re convert it at the scripts just before retrieving the data. Page names can also be parsed this way.