Prosper202 Mod? (8)

c1-c4 variables must be less than 50 characters long

Is there a way to increase the number of characters to 300+?



I looked into my database and edited the 'varchar(50)' to say 'varchar(500) but the c1 still passes just the first 50 characters lol



I'm ready to give away the love letter Mr.Green wrote to me - to the one who helps me out

j/k

I didn't get my letter and my $3 damn you lorenzo

You changed the database length correctly but I am guessing the code that enters the info limits it to 50 before entering it to the database so it doesn't break it.

Look in two places. First the page you enter it look at the form and make sure maxlength is not set to 50. Then look at where the form send the info too and look for the variables that captures to form variable and make sure it is not trimming it to 50 characters.

If you are still having issues then let me know and I can see if I can look into it.

clicktrack! Thanks a ton

For others who might be interested in this, here's how you can increase the number of characters for c1-c4:

Edit the functions-tracking202.php file from trackingdomain.com/202-config/

Find this line

		//only grab the first 50 charactesr of c1
		$c1 = substr($c1, 0, 50);
		$mysql['c1'] = mysql_real_escape_string($c1);

Hi just wondering what kind of use case of C1-C4 would need the extra length. Trying to figure out if we should officially change it or maybe add some other functionality to make up for the need.

Thanks

The offer I'm testing doesn't support pixels, only s2s tracking.

For that, my traffic source requires me to store a key (300+ characters) in my database and send back the data everytime a conversion occurs.

Quite similar to how subids work in Prosper, only difference is that the random number generated in a bit longer.

Originally Posted by lifetweak

The offer I'm testing doesn't support pixels, only s2s tracking.

For that, my traffic source requires me to store a key (300+ characters) in my database and send back the data everytime a conversion occurs.

Quite similar to how subids work in Prosper, only difference is that the random number generated in a bit longer.

The funny thing is, the subid field the network has..stores only upto 255 characters ( read this ) , so some leads might not get updated with the traffic source, since the data I need to store is mostly about 200-350 characters.

Its great that we can add our pixels to Prosper 1.7! That solves the problem for me

Originally Posted by Mr Baffoe

Ok interesting, so are you doing something like this &c1=[[[some token to generate the randome key]]