How Did You Hear About Us? Referrals Mod [Support Thread]

[MyGreyGoose]

Gogolf, Tatiana, & others, I just wanted to report back in that I was able to get it working. My problem was that everything seemed fine except that the data was not getting posted to the db. The only thing I did to get it to work is to start over from scratch and repaste the code from the mod into my files.

At one point, I had made the same mistake you are discussing that I had a create_account.php in includes\modules\custom\ but I had pasted the mod code into includes\modules\. After I fixed that mistake, it still wasn't working (I think). Then I did my "do-over" and it worked. Sooo... my original mistake MAY have been a reason it wasn't working, but I really can't pinpoint why it was not working before and now is. I'm just thanking my lucky stars it's working. I'm pulling for you guys too... I know how frustrating it is.

[MyGreyGoose]

Lina, it should be showing up in the create_account page.... 2 thoughts: 1) did you paste the mod code into the tpl_modules_create_account.php file in your includes\templates\your_template\templates folder? 2) I can't remember if there is an admin setting to turn on the feature (I don't think so), but I remember there are a few different places across admin for this mod's settings (if I recall correctly).

[tatiana77]

LankeeYankee - Works, thanks!

MyGreyGoose/Gogolf/Stellarweb - It's working for me, thankfully!

Please see my last post...


Tat

[hllight]

[FONT=Tahoma][FONT=Arial]I moved the create_account.php to the folder as suggested and that did not correct my problem. [/FONT][/FONT]
[FONT=Tahoma][FONT=Arial][/FONT][/FONT]
[FONT=Tahoma][FONT=Arial]The displayed error message: [/FONT][/FONT]
[FONT=Tahoma][FONT=Arial](Parse error: syntax error, unexpected T_CASE in /home/aaadi3/public_html/admin/orders.php on line 195) [/FONT][/FONT]
[FONT=Tahoma][FONT=Arial]is a syntax error detected during php parsing. Such a syntax error must be corrected before a program can run. A syntax error could be wrong or missing punctuation, unrecognizable operators or statements, etc. The resulting code cannot execute. This contribution does not seem to be in a bug free condition.[/FONT][/FONT]
[FONT=Tahoma][FONT=Arial][FONT=Tahoma][FONT=Arial]Is the author of the code available to assist in debugging?[/FONT][/FONT][/FONT][/FONT]
[FONT=Tahoma][FONT=Arial]I use the applezen template and this contribution is not easy to uninstall. Any suggestions?[/FONT][/FONT]

[gogolf]

(Parse error: syntax error, unexpected T_CASE in /home/aaadi3/public_html/admin/orders.php on line 195)

I got the same error when I was looking at my admin/orders however not being a "expert" with this mod I looked at the version of orders.php that comes with the new 1.3.7, that version is June 25, 2007 and the version that came with mod is December 28, 2006. If you you a file compare program you will see the differences in the two versions.

I'm guessing the error message we saw is a syntax as stated. I have not explored it, maybe something like a forgotten "}" bracket, but then again I'm the few who has problems with this mod.

I'm trying to see what effect having the original orders.php file has with this mod so I loaded the later version (that came with 1.3.7) back on my server to see which way it goes .... "hook or slice".

[hllight]

Thanks for the response! I gathered from your message that you have a procedure for removing the mod. Since I cannot get this issue resolved I want to remove it but I don't know how. Any suggestions?

[gogolf]

I'm sure there is a posting on the procedure for replacing the changes you have made to your store. You'll the constant warning with any modification you read on the forum, such as back up, back up back up.

Look at the mod's folder and files. Make a note of them and their structure.
Locate the files in your store's server files. Delete those files.

Take your last saved store (folder and files) and upload those matching files.
If you have not modified any of those files, such as you have a new clean install, simply take the files out of the Zen packet of files.

Hopefully you made a back up of your database before you installed the mod.
Upload the back up copy of the database that you have before the mod was installed.

Thanks for the response! I gathered from your message that you have a procedure for removing the mod. Since I cannot get this issue resolved I want to remove it but I don't know how. Any suggestions?

[Robbyn7]

Glad to hear some of you have gotten this mod to partially work by adding a custom directory. I tried this, deleted the create_account.php from includes/modules. Added it instead to includes/modules/custom but no go for me. I received an error message after doing this so I added it back.

[gogolf]

I get confused with all the problems the few of us can have with this mod.
Which was yours, the sql patch or the referral not showing up in the admin/customers ?

Glad to hear some of you have gotten this mod to
partially work by adding a custom directory. I tried this, deleted the create_account.php from includes/modules. Added it instead to includes/modules/custom but no go for me. I received an error message after doing this so I added it back.

[hllight]

(Parse error: syntax error, unexpected T_CASE in /home/aaadi3/public_html/admin/orders.php on line 195)

I got the same error when I was looking at my admin/orders however not being a "expert" with this mod I looked at the version of orders.php that comes with the new 1.3.7, that version is June 25, 2007 and the version that came with mod is December 28, 2006. If you you a file compare program you will see the differences in the two versions.

I'm guessing the error message we saw is a syntax as stated. I have not explored it, maybe something like a forgotten "}" bracket, but then again I'm the few who has problems with this mod.

I'm trying to see what effect having the original orders.php file has with this mod so I loaded the later version (that came with 1.3.7) back on my server to see which way it goes .... "hook or slice".

After reading this message again, you didn't say how you fixed it. Did you use the files from the December version? If so which files?