Jump to content

Sandbag

Members
  • Content count

    100
  • Joined

  • Last visited

2 Followers

Profile Information

Recent Profile Visitors

4,509 profile views
  1. It is inserting information into the database whilst people are browsing, so yes, more SQL instructions are being executed. I very much don't one new command will cause a stain on the database, and users won't notice the effect. Putting the Leapfrog table into a new database is not possible without changing the code (because it uses the osCommerce database connection code which points to the original database).
  2. PatForde: Please can you enter the following URL in your browser: http://www.yourdomain.com/catalog/admin/le...amp;lastclick=1 (obviously putting in the correct path to the leapfrog_feed.php file for your site) and then view the source code of the html page. What do you get?
  3. I don't think there will be a problem as the code is seperate. Performance will be slower because more data is being inserted into the database, but that performance drop probably won't be noticeable.
  4. Can you check that the file /catalog/admin/includes/functions/leapfrog.php is present. That is where the function lf_getclicks is located.
  5. Hi. Yes you are right and I was wrong in my previous post. The time is stored in unix time (seconds since Jan 1, 1970) not mysql date format as I previously mentioned. You could write a little PHP script to convert the seconds into a more readable format if you wish.
  6. The date is stored in mySQL date time format (YYYY-MM-DD HH:MM:SS). However the date is not displayed in the Leapfrog GUI as things happen in realtime.
  7. Ok. There should be space for that. I'll have a go in the coming weeks.
  8. The code if footer.php should actually go at the very bottom of the file, not in the middle as you have it. But I guess it's working for you so leave it if you want. With regards to the question above, this is a feature I want to include sometime in the future. It's not too difficult, but screen real estate is the problem. At the moment there is not much space to add the information. If I can figure that out...
  9. This is the XML data that is sent to the Leapfrog GUI. If you right click on the page and view source you will see it laid out all pretty. So you are also gettting LDF001. Hmm. Can you confirm that you put the lf_update_tracking code in catalog/includes/footer.php and not catalog/admin/includes/footer.php. In that XML you pasted, it seems to be tracking your admin clicks. This should not happen.
  10. Please can you try typing the following into your browser's address bar: http://www.yourdomain.com/catalog/admin/leapfrog_feed.php?action=newclicks&lastclick=1 Does the page load? If you go to view source, do you see some XML?
  11. Open: flex/com/flowstack/business/Services.xml You will see a line that says: url="leapfrog_feed.php" Replace this with whatever you want to call the app. Obviously you need to rename leapfrog_feed.php as well. Once done, the flex app must be recompiled.
  12. I think someone else is experiencing this problem also, but I'm afraid I still don't have an answer. Out of interest, if you close the error message dialog box does it continue to work after a while, or do you have to refresh the entire page? In the next version I will add code to recover after this error. It would still be helpful to know why it is happening though. This is a tough error to fix though, because I do not experience it on my server.
  13. No rows means that there is a problem inserting data. Please confirm that you have added the lf_update_tracking() code to footer.php.
  14. This means that tracking data is not being recorded in the database. Please look in the 'leapfrog' table in your database and check that rows are present.
  15. In the admin menu you will see the Leapfrog menu. You can access Leapfrog by clicking on the HEADER of this menu. When the menu EXPANDS, you will see another Leapfrog link below. This one links to a NON SSL version of Leapfrog. Please can you try using this link to run Leapfrog and see if you still get the error. You will know you are on the correct page because the URL in the address bar will be http:// not https://. Thanks.
×