2
Thanks to both of you. It was not obvious to me from the code doc that db->query() behaved that way; just that it had some security features over queryF().
That said, I would like to stay secure within the framework of xoops. I'm passing a URL to a template so that, when clicked on, it uses a GET to pass a parameter. Since this is a link, there's no form, therefore to populate the URL I use:
$url = "http://www.site.com/modules/mod/mod_signup.php?id=".$myrow['id'];
Obviously that's passing a GET. How do I get around that? I'm not at all proficient in cookies, but if that's the only way, so be it.
That said, I would like to stay secure within the framework of xoops. I'm passing a URL to a template so that, when clicked on, it uses a GET to pass a parameter. Since this is a link, there's no form, therefore to populate the URL I use:
$url = "http://www.site.com/modules/mod/mod_signup.php?id=".$myrow['id'];
Obviously that's passing a GET. How do I get around that? I'm not at all proficient in cookies, but if that's the only way, so be it.
3
I've run into a dead end for a module I'm developing and could use another pair of eyes (or a few pair) to help me find what must be an obvious answer.
The code is as follows:
The two echo lines produce the following output:
If I copy the sql statement straight into phpMyAdmin, the insert works without a problem and that's where my frustration lies. Obviously the statement is ok, so where else can the error be? I was hoping that using $xoopsDB->error and errno would provide some insight, but I must be calling them incorrectly.
The code is as follows:
$sql = "INSERT INTO ".$xoopsDB->prefix('draft_order')." (draftid, roundnumber, picknumber, userid) VALUES ($draftid, $round, $claimedpick, $uid)";
if ( !$result = $xoopsDB->query($sql) )
{
// redirect_header(XOOPS_URL.'/',1,_MD_ERROROCCURED);
echo "Error: $sql<br>";
echo $xoopsDB->error." : ".$xoopsDB->errno;
exit();
}
The two echo lines produce the following output:
Error: INSERT INTO mockxoops_draft_order (draftid, roundnumber, picknumber, userid) VALUES (3, 1, 1, 1)
:
If I copy the sql statement straight into phpMyAdmin, the insert works without a problem and that's where my frustration lies. Obviously the statement is ok, so where else can the error be? I was hoping that using $xoopsDB->error and errno would provide some insight, but I must be calling them incorrectly.
5
I think this thread will get you using the same database, at least. I'm not sure about the different themes part.
6
I'm going to use all of you as a sounding board for building the base of this. That way, anything that I miss is caught early.
Two screens: user and admin
ADMIN
PayPal account: ______________
Text to display for thanking user: _________________
Subscription option 1 name: _______________
Subscription option 1 description: _______________
Subscription option 1 price: ______________
Length of subscription option 1: number units (days, months, etc.)
Which group will the member be promoted to: {Drop-down with groups}
<Loop last five lines to create multiple options>
USER
(some configurable text thanking the user for choosing to subscribe)
{Drop-down box box with subscription options}
Check box for auto-renew
The databases that will support this module will be:
MEMBERS
uid - integer; foreign key to XOOPS uid
subscription_type - integer; foreign key to subscriptions DB
start_date - timestamp of this subscription being approved
expiry_date - timestamp of when this subscription will end
auto_renew - integer; 0 for no, 1 for yes
SUBSCRIPTIONS
subscription_type - integer; autoincrement
subscription_name - varchar(80); name of subscription
subscription_description - text
subscription_length_number - integer
subscription_length_units - choice of days, weeks, months, years
ACCOUNTS
vendor - choice of PayPal, NoChex, etc.
account - varchar (80)
password - encrypted password field
That's where I am right now. All comments, suggestions, and criticisms are welcome.
One question I had while doing this post: where do I store the "thank you" text? Is it worth another table just for that or am I missing a more obvious answer, like a simple text file?
Two screens: user and admin
ADMIN
PayPal account: ______________
Text to display for thanking user: _________________
Subscription option 1 name: _______________
Subscription option 1 description: _______________
Subscription option 1 price: ______________
Length of subscription option 1: number units (days, months, etc.)
Which group will the member be promoted to: {Drop-down with groups}
<Loop last five lines to create multiple options>
USER
(some configurable text thanking the user for choosing to subscribe)
{Drop-down box box with subscription options}
Check box for auto-renew
The databases that will support this module will be:
MEMBERS
uid - integer; foreign key to XOOPS uid
subscription_type - integer; foreign key to subscriptions DB
start_date - timestamp of this subscription being approved
expiry_date - timestamp of when this subscription will end
auto_renew - integer; 0 for no, 1 for yes
SUBSCRIPTIONS
subscription_type - integer; autoincrement
subscription_name - varchar(80); name of subscription
subscription_description - text
subscription_length_number - integer
subscription_length_units - choice of days, weeks, months, years
ACCOUNTS
vendor - choice of PayPal, NoChex, etc.
account - varchar (80)
password - encrypted password field
That's where I am right now. All comments, suggestions, and criticisms are welcome.
One question I had while doing this post: where do I store the "thank you" text? Is it worth another table just for that or am I missing a more obvious answer, like a simple text file?
7
gniknalu,
I think (and I emphasize think) all they've done on the front page is use the PayPal functions that you can find here or here. That's just a simple system you can build into any webpage.
What we're discussing here is an installable module that will perform many of the functions listed by above. I'm trying to create that module now.
I think (and I emphasize think) all they've done on the front page is use the PayPal functions that you can find here or here. That's just a simple system you can build into any webpage.
What we're discussing here is an installable module that will perform many of the functions listed by above. I'm trying to create that module now.
8
Quote:
I would certainly hope not, unless you're talking one or two.
This is my biggest "free-time" priority, so it's just a matter of how much of that free time pops up. I don't think the actual PayPal piece will be all that difficult, it will be more putting the module together that will give me a headache.
tom wrote:
I look forward to seeing and testing any progress you make.
Although it is impossible to state a date are we talking months?
Tim
I would certainly hope not, unless you're talking one or two.
This is my biggest "free-time" priority, so it's just a matter of how much of that free time pops up. I don't think the actual PayPal piece will be all that difficult, it will be more putting the module together that will give me a headache.
9
After some discussion at fantasyasylum.com, we've decided to contribute our time to this project instead of paying Draven to develop it and then struggling with the decision whether to release it to the community or not. XOOPS has done a lot for fantasyasylum.com and it's now time to pay the community back.
I am willing to do the development of this module, but as it will be my first actual module (as opposed to hacks I've done in the past), it's going to take me just a smidge of time to get off the ground. That said, this project will be seen to completion because this module is something we desperately need.
The first version of this module will be quite simple: it will accept PayPal payments and change the user's group. After that is working and clean, I will work on the rest of the suggestions mentioned here.
If anyone has any additional thoughts or suggestions for a mod dev newbie, please let me know. Any suggestions on how to incorporate Draven's idea of a general membership module with vendor-specific submodules (modules are bad enough, but submodules?!?) would be appreciated. I'm sure there will be plenty of beta testers available when I'm ready :)
Don
I am willing to do the development of this module, but as it will be my first actual module (as opposed to hacks I've done in the past), it's going to take me just a smidge of time to get off the ground. That said, this project will be seen to completion because this module is something we desperately need.
The first version of this module will be quite simple: it will accept PayPal payments and change the user's group. After that is working and clean, I will work on the rest of the suggestions mentioned here.
If anyone has any additional thoughts or suggestions for a mod dev newbie, please let me know. Any suggestions on how to incorporate Draven's idea of a general membership module with vendor-specific submodules (modules are bad enough, but submodules?!?) would be appreciated. I'm sure there will be plenty of beta testers available when I'm ready :)
Don
10
On a slightly related note (because it involves forums and userinfo.php), the password-protected forums do not show up on the View Account page and there does not seem to be a place in userinfo.php to change that behavior. Am I missing something or will it require digging deeper into the code to find where to change this?
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|