Prosper202 1.8.3 upgrade problem

by Tumhi
56 replies
Hey Everyone


Today i upgrade Prosper202 to 1.8.3 ..so now my all landing pages not working..
i mean.. landing pages open fine but all button unclickable,,
i can't click on any submit button..i check every landing page but same problem..
if i remove "Inbound Javascript Landing Page Code" in the landing pages then my landing page working fine and all button work.. but then i can't track my landing page without put " Inbound Javascript Landing Page Code "


by mistake i didn't make backup my old prosper202..
so if there is any way i can downgrade my prosper202 so please tell me...
or help me slove this problem...

thank you
#problem #prosper202 #upgrade
  • Profile picture of the author aharrold
    Damn, I just checked mine too and none of the buttons can be clicked! Thanks for pointing this out before I wasted a bunch of money.
    {{ DiscussionBoard.errors[9149566].message }}
    • Profile picture of the author eternalwarrior
      Originally Posted by aharrold View Post

      Thanks for pointing this out before I wasted a bunch of money.
      Money? Prosper202 1.8.3 is free to download!
      {{ DiscussionBoard.errors[9149569].message }}
      • Profile picture of the author aharrold
        Originally Posted by eternalwarrior View Post

        Money? Prosper202 1.8.3 is free to download!
        By sending traffic to a LP that is not functioning....
        {{ DiscussionBoard.errors[9149579].message }}
    • Profile picture of the author Tumhi
      so any one know how to fix it..... anyone have idea?????
      {{ DiscussionBoard.errors[9149664].message }}
  • Profile picture of the author altoro80
    mine are ok but i cannot track conversions
    {{ DiscussionBoard.errors[9150675].message }}
    • Profile picture of the author crams
      This is one of many reasons i don't like using 202, hosted solutions you don't half to worry about updating anything. you might need to just start a clean slate install or try renewing Landing Page Code and Outbound Redirect Link.
      {{ DiscussionBoard.errors[9150748].message }}
  • Profile picture of the author aharrold
    Same here!!! I might just bone up and buy CPVLab
    {{ DiscussionBoard.errors[9150722].message }}
  • Profile picture of the author Droopy Dawg
    Glad I held off upgrading. I'll wait til they figure it out before I upgrade mine.
    Signature


    {{ DiscussionBoard.errors[9150745].message }}
    • Profile picture of the author Dele
      Originally Posted by Droopy Dawg View Post

      Glad I held off upgrading. I'll wait til they figure it out before I upgrade mine.

      In the same boat with you.
      Glad i held on a little longer too. Will allow some time for these issues to be sorted out before i upgrade.
      Signature

      What Others Are Saying About This Top MLM Company | Get Brand New, Brand Name Products For Pennies @ New Penny Auctions | Play Online Game At Eager Zebra Games | The source through which i smile to the Bank daily with $$$ => Top Home Based Businesses

      {{ DiscussionBoard.errors[9151756].message }}
  • Profile picture of the author Tumhi
    i think this bug in this file...

    http://Domain.com/tracking202/static/landing.php
    {{ DiscussionBoard.errors[9151564].message }}
  • Profile picture of the author Tumhi
    i think this bug in this file...

    http://Domain.com/tracking202/static/landing.php
    {{ DiscussionBoard.errors[9151565].message }}
  • Profile picture of the author altoro80
    I just upgraded to 1.8.3.2 and working just fine now
    {{ DiscussionBoard.errors[9152215].message }}
    • Profile picture of the author Tumhi
      Originally Posted by altoro80 View Post

      I just upgraded to 1.8.3.2 and working just fine now
      i try to find 1.8.3.2 and 1.8.2 version..

      but i can't find them.. anyone have link these version ...??:rolleyes:
      {{ DiscussionBoard.errors[9152535].message }}
      • Profile picture of the author altoro80
        Originally Posted by Tumhi View Post

        i try to find 1.8.3.2 and 1.8.2 version..

        but i can't find them.. anyone have link these version ...??:rolleyes:
        Go into your prosper and you will see the "out of date please upgrade" link
        {{ DiscussionBoard.errors[9152553].message }}
      • Profile picture of the author crams
        Originally Posted by Tumhi View Post

        i try to find 1.8.3.2 and 1.8.2 version..

        but i can't find them.. anyone have link these version ...??:rolleyes:
        direct download the new one.
        prosper.tracking202.com/apps/download/latest/
        {{ DiscussionBoard.errors[9152565].message }}
  • Profile picture of the author aharrold
    I updated, but it seems to still not allow the buttons to be clicked.
    {{ DiscussionBoard.errors[9152636].message }}
  • Profile picture of the author Tumhi
    still same problem after updated to 1.8.3.2 ...
    {{ DiscussionBoard.errors[9153103].message }}
  • Profile picture of the author carlajoyce
    A temporary solution I found is to copy the file -> http://Domain.com/tracking202/static/landing.php from the old version (1.7.2) - overwrite latest version with that old file and use the 2 line script code for your landing page.
    i.e.
    <script language="JavaScript" type="text/javascript"> cbr202=Math.random()*10000000000000000;document.wr ite('<scr'+'ipt language="JavaScript" src="http://qtlio.com/tracking202/static/landing.php?lpip=XXX&202cb='+cbr202+'" type="text/javascript"></scr' + 'ipt>'); </script>

    Change 'lpip=XXX' to XXX is your unique tracking code.

    Hope that helps a bit - resolved my issues with the backgrounds not working on my landing pages -> Free 100+ Page eBook Reveals How to Make Money Online
    Signature
    Ready To Make Passive Income (Affiliate Cash) - Click Here

    Carla Joyce - Full Time Internet Marketer & Mentor.

    {{ DiscussionBoard.errors[9153728].message }}
    • Profile picture of the author Tumhi
      Originally Posted by carlajoyce View Post

      A temporary solution I found is to copy the file -> http://Domain.com/tracking202/static/landing.php from the old version (1.7.2) - overwrite latest version with that old file and use the 2 line script code for your landing page.
      i.e.
      <script language="JavaScript" type="text/javascript"> cbr202=Math.random()*10000000000000000;document.wr ite('<scr'+'ipt language="JavaScript" src="http://qtlio.com/tracking202/static/landing.php?lpip=XXX&202cb='+cbr202+'" type="text/javascript"></scr' + 'ipt>'); </script>

      i try this but not help me..
      i replace landing.php with 1.7.2 version.. and use old code..
      landing page working fine but i can't show in p202.. when anyone see the landing page i can't track .
      {{ DiscussionBoard.errors[9153969].message }}
  • Profile picture of the author rumbenieks
    Hey guys. I am head developer of Prosper202 1.8. I will try to answer all of your questions.

    Landin page JS bug is fixed (on version 1.8.3.3, released yesterday). You can use 1-Click upgrade or direct download link on Prosper202 website.

    You can use built-in messaging system in Prosper202, to report bugs and other issues you have with your installation.

    P.S. Prosper202 website will soon launch, with new user interface, as well with change logs for each P202 release, so you can stay on track, what is fixed and what is coming on next release.
    {{ DiscussionBoard.errors[9154229].message }}
    • Profile picture of the author Tumhi
      Originally Posted by rumbenieks View Post

      Hey guys. I am head developer of Prosper202 1.8. I will try to answer all of your questions.

      Landin page JS bug is fixed (on version 1.8.3.3, released yesterday). You can use 1-Click upgrade or direct download link on Prosper202 website.

      You can use built-in messaging system in Prosper202, to report bugs and other issues you have with your installation.

      P.S. Prosper202 website will soon launch, with new user interface, as well with change logs for each P202 release, so you can stay on track, what is fixed and what is coming on next release.


      i just update p202 1.8.3.3 . and now its working fine.. thank you,,
      p202 is good tracker..
      {{ DiscussionBoard.errors[9154464].message }}
  • Profile picture of the author aharrold
    Everything is good other than the GEO IP showing the wrong locations.
    {{ DiscussionBoard.errors[9157436].message }}
    • Profile picture of the author rumbenieks
      For everyone else, who has some issues or bugs with your P202 install, please report them with build-in messaging system on P202 right bottom corner.

      There we will be able to give you better support, then here on Warrior Forum.

      Originally Posted by aharrold View Post

      Everything is good other than the GEO IP showing the wrong locations.
      {{ DiscussionBoard.errors[9159507].message }}
      • Profile picture of the author overseer
        I'm having problem in upgrading my Prosper202.

        I've followed all of the instructions (except the delete all the files part, because I retained the folders for my landing pages.)

        After I'm done, I went to check out my URL, and then it mentioned something this:

        Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING

        Help!
        Signature

        {{ DiscussionBoard.errors[9159618].message }}
        • Profile picture of the author altoro80
          Originally Posted by overseer View Post

          I'm having problem in upgrading my Prosper202.

          I've followed all of the instructions (except the delete all the files part, because I retained the folders for my landing pages.)

          After I'm done, I went to check out my URL, and then it mentioned something this:

          Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING

          Help!
          Try "one click update" in firefox or explorer, i getting that error on Chrome i went into firefox use the one click update and it worked
          {{ DiscussionBoard.errors[9159747].message }}
          • Profile picture of the author rumbenieks
            Glad it worked well for you.

            Originally Posted by altoro80 View Post

            Try "one click update" in firefox or explorer, i getting that error on Chrome i went into firefox use the one click update and it worked
            {{ DiscussionBoard.errors[9159781].message }}
      • Profile picture of the author imgllc
        Hello,

        I keep getting the following error regardless of a upgrade or fresh install on version 1.8.3.3:
        Fatal error: Call to undefined function mysqli_report() in /home/imgllcsi/public_html/90/202-config/connect.php on line 23.

        I am currently using 1.7.2 with no issues.

        Any help with this would be appreciated.
        {{ DiscussionBoard.errors[9163367].message }}
        • Profile picture of the author rumbenieks
          Its seems that MySQLi extension is not enabled on your server. P202 1.8 use MySQLi instead of old MySQL. Make sure its enabled, before installing or upgrading to version 1.8.

          Originally Posted by imgllc View Post

          Hello,

          I keep getting the following error regardless of a upgrade or fresh install on version 1.8.3.3:
          Fatal error: Call to undefined function mysqli_report() in /home/imgllcsi/public_html/90/202-config/connect.php on line 23.

          I am currently using 1.7.2 with no issues.

          Any help with this would be appreciated.
          {{ DiscussionBoard.errors[9163786].message }}
          • Profile picture of the author imgllc
            Thanks for the help. That is exactly the problem.

            I did find a bug though:
            Under the visitor tab when I click (Download to excel) no data shows up
            on the excel spreadsheet.
            This is needed due to not all affiliate networks pass all the characters in the subid code.
            {{ DiscussionBoard.errors[9167172].message }}
            • Profile picture of the author rumbenieks
              This will be fixed in next release.

              Please, report bugs in built-in messaging system on Prosper202 1.8 or in Prosper202 forum.

              This thread is not for support!

              Originally Posted by imgllc View Post

              Thanks for the help. That is exactly the problem.

              I did find a bug though:
              Under the visitor tab when I click (Download to excel) no data shows up
              on the excel spreadsheet.
              This is needed due to not all affiliate networks pass all the characters in the subid code.
              {{ DiscussionBoard.errors[9167800].message }}
              • Profile picture of the author JohnTK
                Trying to install new version of Prosper202 1.8.3.3 Requirements are PHP 5.5 or greater, MySQL 5.5 or greater and The mod_rewrite Apache module. Need to upgrade from PHP 5.4 to 5.5. Hostgator tells me "Before we proceed we wish to inform you that EAccelerator ioncube sourceGuardian and dxcache and Guard loader will be disabled. If this is ok please reply back to this ticket."
                Anyone know why this is necessary and what are the possible ramifications?
                {{ DiscussionBoard.errors[9173228].message }}
                • Profile picture of the author rumbenieks
                  Sorry, information on P202 website is incorrect. We will change requirements on new Prosper202 website, its coming soon coming soon.

                  The requirements is:

                  PHP 5.3 or greater
                  MySQL 5.1 or greater

                  Originally Posted by JohnTK View Post

                  Trying to install new version of Prosper202 1.8.3.3 Requirements are PHP 5.5 or greater, MySQL 5.5 or greater and The mod_rewrite Apache module. Need to upgrade from PHP 5.4 to 5.5. Hostgator tells me "Before we proceed we wish to inform you that EAccelerator ioncube sourceGuardian and dxcache and Guard loader will be disabled. If this is ok please reply back to this ticket."
                  Anyone know why this is necessary and what are the possible ramifications?
                  {{ DiscussionBoard.errors[9175442].message }}
                  • Profile picture of the author mployee8
                    I'm having a totally different issue. For some reason after I install Prosper and go to my domain I get a blank page. I placed a php script containing phpinfo(). No problems there. I have been looking for a solution for days, help!!

                    I am hosting prosper on a VPS running CentOS 6.5. I have also installed zpanel.
                    {{ DiscussionBoard.errors[9177377].message }}
                  • Profile picture of the author JohnTK
                    Wound up having to setup with an htaccess record so I could keep everything else intact.
                    Wish I would have known sooner, had to jump through a lot of hoops. For some reason it did not recognize my DNS server for my domain and had to create an A record. Seems to be working now.
                    {{ DiscussionBoard.errors[9198628].message }}
                    • Originally Posted by JohnTK View Post

                      Wound up having to setup with an htaccess record so I could keep everything else intact.
                      Wish I would have known sooner, had to jump through a lot of hoops. For some reason it did not recognize my DNS server for my domain and had to create an A record. Seems to be working now.
                      Sorry to hear you had to jump through so many hoops to get things working. Based on other user's experiences, hostgator a difficult host to get Prosper202 working on.

                      Because of this, we don't recommend hosting Prosper202 with them. Eventually we'd like to be able to work with them to make the installation less error prone since they seem to be a popular host.
                      {{ DiscussionBoard.errors[9199146].message }}
                      • Hi, when I uploaded the upgrade I got the following error:

                        Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in /home2/root/public_html/tracking202/202-config/functions-tracking202.php on line 3

                        What is going wrong?
                        {{ DiscussionBoard.errors[9200955].message }}
                        • Originally Posted by doesnotmeetstandards View Post

                          Hi, when I uploaded the upgrade I got the following error:

                          Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or '(' in /home2/root/public_html/tracking202/202-config/functions-tracking202.php on line 3

                          What is going wrong?
                          You are probably on hostgator?

                          Make sure you have php 5.3 or higher and turn on short tags
                          {{ DiscussionBoard.errors[9201093].message }}
                          • Profile picture of the author BzzApp
                            Originally Posted by Nana Gilbert-Baffoe View Post

                            You are probably on hostgator?

                            Make sure you have php 5.3 or higher and turn on short tags

                            Thanks, I had the same error. Resolved it by adding to a .htaccess file
                            Code:
                            # Use PHP 5.3 for Prosper 202
                            AddHandler application/x-httpd-php55 .php
                            Signature
                            BzZApps Cash in on Native iOS & Android Apps, Web Apps and more...
                            {{ DiscussionBoard.errors[9201267].message }}
                          • Originally Posted by Nana Gilbert-Baffoe View Post

                            You are probably on hostgator?

                            Make sure you have php 5.3 or higher and turn on short tags
                            Yes, it's hostgator.
                            I have (tried to) changed the settings and it worked, thanks
                            {{ DiscussionBoard.errors[9202729].message }}
  • Profile picture of the author overseer
    I can't see the messaging system you mentioned.
    Signature

    {{ DiscussionBoard.errors[9159624].message }}
    • Profile picture of the author rumbenieks
      Then thats the problem. To successfully upgrade from P202 1.7.2 to 1.8.3.3 you need to delete all files and replace with the files in downloaded .zip file from Prosper202 website.

      Database will be upgraded on Upgrade process.

      New messaging system is available from version 1.8.

      Originally Posted by overseer View Post

      I'm having problem in upgrading my Prosper202.

      I've followed all of the instructions (except the delete all the files part, because I retained the folders for my landing pages.)

      After I'm done, I went to check out my URL, and then it mentioned something this:

      Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING

      Help!
      {{ DiscussionBoard.errors[9159628].message }}
  • Profile picture of the author Stephen Carter
    i noticed that the global postback conversion script gpb.php in 1.8.3.1 was completely wrong and has since been updated in 1.8.3.3

    however, it's still way more complex than it's predecessor in 1.7.2 and i'm curious as to why that is. it doesn't need to be an efficient script because it's a conversion script. however, it does a lot of table joins to look up "c values" and the like which seems weird to me and out of place.

    basically, the script no longer does what the global pixel conversion script gpx.php does and that seems suspect to me.
    {{ DiscussionBoard.errors[9181486].message }}
    • Profile picture of the author rumbenieks
      If you have some questions, need support with you Prosper202 or have some recommendations, please use built-in messaging at bottom right corner in your installation.

      Originally Posted by Stephen Carter View Post

      i noticed that the global postback conversion script gpb.php in 1.8.3.1 was completely wrong and has since been updated in 1.8.3.3

      however, it's still way more complex than it's predecessor in 1.7.2 and i'm curious as to why that is. it doesn't need to be an efficient script because it's a conversion script. however, it does a lot of table joins to look up "c values" and the like which seems weird to me and out of place.

      basically, the script no longer does what the global pixel conversion script gpx.php does and that seems suspect to me.
      {{ DiscussionBoard.errors[9182553].message }}
  • Profile picture of the author Stephen Carter
    i don't need support. i'm just pointing out for the benefit of others who might find that they sometimes have problems getting their conversions to properly register that the global postback conversion script as of 1.8.3.3 now contains the content of the universal pixel script which is crazy.

    you actually have the script conditionally outputting HTML for pixels - and then it tacks on headers after that! if gpb.php is still the global postback script it should never generate HTML.

    i personally won't install the new Prosper until the front end scripts look sensible.
    {{ DiscussionBoard.errors[9183106].message }}
    • Profile picture of the author rumbenieks
      Does the Global Post Back doesn't work for you?

      The reason it outputs pixels, is only because to fire 3-party tracking pixels on global postback. Probably thats not the best solution there with 3-party pixels (by rendering HTML directly on the same page), but it do the job. We will improve it in next releases.

      It will work no mater what, as far subid or sid variables are provided in postback.

      About headers, that will be sorted out.


      Originally Posted by Stephen Carter View Post

      i don't need support. i'm just pointing out for the benefit of others who might find that they sometimes have problems getting their conversions to properly register that the global postback conversion script as of 1.8.3.3 now contains the content of the universal pixel script which is crazy.

      you actually have the script conditionally outputting HTML for pixels - and then it tacks on headers after that! if gpb.php is still the global postback script it should never generate HTML.

      i personally won't install the new Prosper until the front end scripts look sensible.
      {{ DiscussionBoard.errors[9183721].message }}
    • Originally Posted by Stephen Carter View Post

      i don't need support. i'm just pointing out for the benefit of others who might find that they sometimes have problems getting their conversions to properly register that the global postback conversion script as of 1.8.3.3 now contains the content of the universal pixel script which is crazy.

      you actually have the script conditionally outputting HTML for pixels - and then it tacks on headers after that! if gpb.php is still the global postback script it should never generate HTML.

      i personally won't install the new Prosper until the front end scripts look sensible.
      Hi Stephen,

      Thanks for your feedback on this, we'll get the header issue addressed. As for your other concerns, we recently made a decision to add much of the functionality of the universal smart pixel to the global postback pixel. This was based of our user's actions and observations of the problems they were having, misusing our pixel types.

      The major functionality of the new gpb.php is the ability to piggy back post backs and also use tokens in the post back urls, we posted about this new feature here a while ago.

      Our Universal Smart Pixels just got smarter

      So for example, you can fire a postback and pass on the values of c1-c4 to that post back. This is a very powerful feature for mobile advertisers doing s2s calls and needing to send additional data back to the ad network for conversion tracking.

      Since you are the author of one of the most advanced p202 ebooks on the market, I wouldn't expect you to mix up the different pixels but a lot of our users are not as advanced as you. So the ability to conditionally output the other pixels was left in there. It has zero to minimal effect on the performance of the script.

      Finally (for everyone else) just want to add that, Prosper202 1.8.3 was a very BIG update. A lot of new features were added with the specific purpose of making our users more profitable and efficient. We tested extensively on our environment before launching, but we can't account for everyone's hosting environment. Some of you have had issues, but the majority of users have been fine.

      We push out updates quickly, and have addressed everything mentioned above so far. We are on a weekly release schedule and are about to launch our 3rd update since launching about 2 weeks ago, this one with brand new features.

      Also please note that there are only 2 of us working on Prosper202, we are not a huge team. So once again, we ask that if you have support issues or bug reports etc please don't post them in this forum, at least if you want me or Oskars to be able to help you quickly.

      We've added a very cool in app help and messaging system. It's the blue box with the question mark at the bottom right. Click it when you want to talk to us, your messages come directly to us via email and phone notifications (Long way of saying if you use the built-in system we see every message almost instantly)

      Prosper202 1.7.2 is almost 2.5 years old with bugs and issues that have been completely fixed and addressed in 1.8.3. For some people just the act of upgrading without using any of the new features, will pay off instantly in performance enhancements and productivity gains.
      {{ DiscussionBoard.errors[9183744].message }}
  • Profile picture of the author Stephen Carter
    i'm sorry Nana, i love that you are making Prosper free again and that you are building out more functionality, but i have to be blunt and point out that what you are saying here makes little sense to me.

    in the context of the pixel it makes sense, the universal pixel business i have no problem with.

    but for postback URLs the story is different. those are server to server transmissions that traditionally involve no serving of HTML to a browser page. when some third party uses the postback URL to let Prosper (or any other tracking application) know that a conversion has happened the most you can expect them to do is look at the header of the response that Prosper sends back to see whether the transmission was received OK. they don't expect you to return HTML to them that they will then do something with. at least, that's my understanding of how the universe works. no one is doing any more than it says on the contract

    i mean, if you think about it you'll realize that postback conversions may well be batch processed in a lot of cases. there's no reason for them to be done on the fly where a browser might be included in the loop.

    now if you are saying that networks WILL actually take the HTML you send back, pick through it to find the URLs that appear in image pixels, and then perform more server to server requests to "fulfill" your intent, then i would be wrong and it would work the way you are suggesting it will.

    but i think unless the industry doesn't work the way i think it does, pixels in the output of a global postback URL response are never going to fire anything the way you are hoping they will.

    if the industry WAS going to work that way it would be a whole lot more efficient to set up some kind of JSON data structure in which you sent back the URLs you wanted them to fire. that would be an organized way that everyone could agree on about what should happen with a postback URL.

    but you know what? it's just occurred to me. if you want all those extra pixels to fire, why not just have Prosper do it in gpb.php? server to server. then you wouldn't have to rely on the party at the other end to do it (which i don't think they are going to do anyway).

    that's how you should do it.
    {{ DiscussionBoard.errors[9184796].message }}
    • Profile picture of the author tzahico
      I actually find the 'HTML' feature of GPB.PHP very useful.
      Previously I used to test postbacks by creating a 'dummy' traffic source with a URL that recorded all requests to it. Now however I can just enter the real traffic source postback address and GPB.PHP will display whether the postback was sent or not, and whether the transmission was successful.

      The only technical issue that I've faced so far with Prosper v1.8.3.3 is the fact that IE cookies which are written by landing.php are not fetched by the LP redirect link, go.php... leading to low LP CR and S/U-rate statistics that affect just IE users. However, I found a solution to that problem by sending the cookie content in the URL structure of go.php (i.e. go.php?pci=3444).

      Now everything works perfectly. Thank you Nana for a great piece of software!
      {{ DiscussionBoard.errors[9185207].message }}
    • Profile picture of the author HighTechTorres
      Originally Posted by Stephen Carter View Post

      i'm sorry Nana, i love that you are making Prosper free again and that you are building out more functionality, but i have to be blunt and point out that what you are saying here makes little sense to me.

      in the context of the pixel it makes sense, the universal pixel business i have no problem with.

      but for postback URLs the story is different. those are server to server transmissions that traditionally involve no serving of HTML to a browser page. when some third party uses the postback URL to let Prosper (or any other tracking application) know that a conversion has happened the most you can expect them to do is look at the header of the response that Prosper sends back to see whether the transmission was received OK. they don't expect you to return HTML to them that they will then do something with. at least, that's my understanding of how the universe works. no one is doing any more than it says on the contract

      i mean, if you think about it you'll realize that postback conversions may well be batch processed in a lot of cases. there's no reason for them to be done on the fly where a browser might be included in the loop.

      now if you are saying that networks WILL actually take the HTML you send back, pick through it to find the URLs that appear in image pixels, and then perform more server to server requests to "fulfill" your intent, then i would be wrong and it would work the way you are suggesting it will.

      but i think unless the industry doesn't work the way i think it does, pixels in the output of a global postback URL response are never going to fire anything the way you are hoping they will.

      if the industry WAS going to work that way it would be a whole lot more efficient to set up some kind of JSON data structure in which you sent back the URLs you wanted them to fire. that would be an organized way that everyone could agree on about what should happen with a postback URL.

      but you know what? it's just occurred to me. if you want all those extra pixels to fire, why not just have Prosper do it in gpb.php? server to server. then you wouldn't have to rely on the party at the other end to do it (which i don't think they are going to do anyway).

      that's how you should do it.
      Hi Stephen!

      Did you have to update your guild because of this latest update?
      Is there anything different?
      {{ DiscussionBoard.errors[9491266].message }}
  • Profile picture of the author Stephen Carter
    there is one instance in which the current gpb.php script looks like it actually does the correct thing. it's the case where the snoopy class is used to fetch the pixel remotely. that's the type of server to server transmission that makes sense in this situation. i didn't even notice that bit of code because i was transfixed on the other problems. so that would be pixel type 4 according to the script. but for the other cases where HTML is output directly, that's not likely to work.
    {{ DiscussionBoard.errors[9186152].message }}
    • Originally Posted by Stephen Carter View Post

      there is one instance in which the current gpb.php script looks like it actually does the correct thing. it's the case where the snoopy class is used to fetch the pixel remotely. that's the type of server to server transmission that makes sense in this situation. i didn't even notice that bit of code because i was transfixed on the other problems. so that would be pixel type 4 according to the script. but for the other cases where HTML is output directly, that's not likely to work.
      Hi Stephen

      You are correct that a postback can never trigger an image, javascript, or iframe pixel. It's not technically possible.

      As you were wondering in an earlier post, Prosper202 actually recreates the 3rd party pixel (js, image or iframe) and fires it (under the right circumstances) otherwise the code just acts like a normal postback system.

      We just made it multipurpose, so we are not as crazy as you may think. But we are crazy enough to shake things up

      PS: Hurry up and install 1.8.x and get used to it, so you can have the first Prosper 1.8.x guide on the market. A lot has changed for the better and there's more to come!
      {{ DiscussionBoard.errors[9187597].message }}
  • Quick note: Prosper202 1.8.4 is available as of today.

    If you are on 1.8.3 and have the correct write permissions set, you can use the 1-click upgrade button for a wordpress style upgrade experience.
    {{ DiscussionBoard.errors[9204005].message }}
  • Profile picture of the author Farian
    Today I updated my good old Prosper 1.72 to the new 1.8.4
    I would never do any updates if I wouldn't need to move to the new server.
    Well, first thing I stumbled upon was that it is not as easy to install it as it states in instructions. There are some things that are lacking and it costed me few hours to figure everything out. I've found on the net that I'm not alone who sees the same errors, so this info below will help others:

    During the installation (clean Centos 6.5 x64, under Virtualmin)

    1. if you get this error:
    Call to undefined function mysqli_report() in /home/found/public_html/202-config/connect.php on line 23

    Solution: (yum or apt-get depending on your OS)
    yum install php-mysql
    Add this to php.ini:
    extension=msqli.so

    Then run the command: service httpd restart

    2. Then if you get the error with the abracadabra with this piece of text in the end:
    02-config/functions-tracking202.php on line 4325

    Solution:
    go to php.ini and uncomment these lines:

    short_open_tag
    Default Value: On
    Development Value: On
    Production Value: On

    Then run the command: service httpd restart

    Now everything starts to work as it described by developers.

    The first issue after installation is awful font, which is especially awful 'Clear type' switched off in browser. Now I must search where and how to change it.
    The second and the biggest issue: sudden spamming me with all kinds of advertisement! On my own site! It's the most annoying thing and the first challenge is to clean the installation from it.

    ...perhaps I will come back to 1.7.2 finally. I didn't start to use this new Prosper yet, I guess new surprising findings are awaiting ahead.
    {{ DiscussionBoard.errors[9467590].message }}

Trending Topics