![Invision power board 1.3.1 final](https://kumkoniak.com/78.jpg)
I'm not sure though if g_language would effect anything since I really only care about the English aspect. And that leaves g_email to match with ibf_members email. The password I believe is g_hashedpassword which can match up with ibf_members legacy_password. Then g_username instead look at ibf_members name field. In parts of G2 where it would normally check for g_id it would instead look at ibf_members at id.
![invision power board 1.3.1 final invision power board 1.3.1 final](http://architektonika.ru/uploads/gallery/main/kirill_gud/sp_a0253_1_1183576619.jpg)
Since all it is matching a userid that part should be comptable with IPB database since it also has its own id. Permission for albums are obtained from g2_PermissionMap which matches the g_userid with the g2_user table and g_id of that member. I'm sort of going on logic and theory based on php and mySQL programming for the most part right now.įrom what I can tell in the mySQL table there are at least two tables which will need to be cross-referenced if I am understanding things. Let me know if I'm going about this in the wrong direction and if there is an easier method, please. Most of it should involve just rewriting or basically pointing items to look at a different table instead of where it would normally look. However an integration like this I believe is more possible with how G2 has been rewritten. My understanding of G2 and the newer version of IPB 2.0.3 are still newer than most veterans. Those are the main steps at goals of this project that I will try to undertake to the best of my ability. Then the next step would be to create a layout/skin that would seemingly integrate G2 with IPB similar to how their own gallery system is integrated. Once there has been a bridge created and tested. This would result in multiple installations as well as testing of each feature to not only test G2 functionality but that alterations haven't affected G2 or IPB in some unforseen method.ģ. Test the bridge, usergroups and membergroups to make sure no errors. Then in the instances in G2 where it would normally call upon the g2 tables to instead point towards the IPB member tables.Ģ.
![invision power board 1.3.1 final invision power board 1.3.1 final](https://ae01.alicdn.com/kf/HTB1GqMmPVXXXXcIXFXXq6xXFXXXf/Doublepow-High-Capacity-Li-Ion-USB-Rechargeable-9V-Batteries-650mAh-battery-1-pcs.jpg)
This is probably best done by just utilizing IPB's member registration for the creation of members. Create a bridge between G2 member database and IPB member database. So we're basically going to have to start from scratch.ġ. So none of the old bridging for the member database work anymore.
![invision power board 1.3.1 final invision power board 1.3.1 final](https://ipbmafia.ru/uploads/monthly_11_2012/thumb-c6d0ea3f9019afb60dbe6082130eadba-index.png)
Since then Gallery has been completely re-written with G2 and Invision Power Board rewrote their board with version 2.0.3. The original project for integration was a bridged version during G1 and IPB 1.3 here:
![Invision power board 1.3.1 final](https://kumkoniak.com/78.jpg)