I am new to the FSO and frankly APIs in general. For the most part I have coded in the basic web standards, so I apologize for my lack of understanding.
The church web site is under a content management system called
Expression Engine (EE). I would consider myself pretty knowledgeable
using EE, as I have several dozen sites overall developed under that
platform. I am not sure if I want or need to use the native EE user management or not. I am currently using that to handle content management accounts and restricted areas on our site. I know that EE has built-in codes like {if logged} and so forth that would be nice to use for a previous question.
I want to build a custom log on with custom forms for FSO for a church web site. Basically the end goal is for the end-user to be able to login, contribute (online giving), manage his/her account then log off all within the look and feel of the church site. The current method I have in place is using the weblink javascript button routine but that simply opens up the FSO forms.
I understand API is the way this would be handled and something to do with XML code to grab the iCode; however that is where my experience comes to a complete stop. I have use XML in a very very limited fashion and simply do not understand the process of getting that iCode tag I need or the user data.
Searching the site, I noticed a EE module called listee but from what I have concluded is that is only use to build an EE template for which list all of the users under the FSO church account. I do not believe that is the goal.
Is there anyone here that has built this into EE web site that can help a newbie XML developer get the final results?
Thanks.