Jump to content

team_wolfje

+Premium Members
  • Posts

    87
  • Joined

  • Last visited

Everything posted by team_wolfje

  1. The session hijack control checks you IP address at the beginning of the session. Then the IP address is validated every time a new page is displayed. If there is a mismatch in the IP address, you will get the message stated above. Since I am not familiar with the AOL browser it seems that indeed your IP address was changed. Can someone check out if this really is the case? If so, I can program another session hijacking method, based on other things, but the IP check was recommended to me. Thanks, Jan Paul Team_Wolfje AOL uses a "floating ip address". This should be fixed right now in our shop. Can someone with the AOL browser please check this for me? Thanks, Jan Paul Team_Wolfje
  2. The session hijack control checks you IP address at the beginning of the session. Then the IP address is validated every time a new page is displayed. If there is a mismatch in the IP address, you will get the message stated above. Since I am not familiar with the AOL browser it seems that indeed your IP address was changed. Can someone check out if this really is the case? If so, I can program another session hijacking method, based on other things, but the IP check was recommended to me. Thanks, Jan Paul Team_Wolfje
  3. Any news about the status of the "Social find" . I really like the concept.
  4. We've been fiddling with this copy idea for a long time now. Another coin with the same tracking number, a hard-plastic copy, a copy with one side the front of the coin and the back side a "not for robbing copy" text, a non-colored copy etc. For a supplier a copy-coin is a logistic nightmare and also people want to make coins for the lowest possible price. The costs of such a copy-coin however is a lot lower than the normal coin, because the trackingnumber etc is a one-time fee, but still it is a large increase on their budget. It is almost the same as the TB: two coins and one as a copy. Making a copy is a nice idea, but make is an exact same coin or make is a copy that is immediately recognized as a copy. A laminated paper with a color copy of the coin will do nicely as a copy. I still like the idea of a copy-coin, but like Marky's idea of a theft-device for geocoins the most .
  5. That's correct. At this very moment they are airborn and on the way to us. As soon as they arrive, an update will be given in this post. And there are still coins left at the shop mentioned above.
  6. Well, maybe next year we can make it a global event: events on the same day in various countries under one name? Worldwide Geocoinfest 2008 ? Since I found out about Geocoins, my travel budget cut down to almost nothing...
  7. Bert, from your fellow cachers from the Netherlands: Congrats ! Time for a career change? Will this design be used for the Geocoinfest only? Or is there a Geocoinfest Geocoin coming?
  8. Since yahoo states: And I used the link in the first post. Anyway, my vote goes to #3 (I wonder why... )
  9. Just wanted to let everybody know that I just got the message that the coins will be shipped to us second week of november. Anybody who has trouble ordering (lucky for us just a minor number of the purchases went not a 100%), please email us at info at geocoins dot nl.
  10. And the sample of the LE Silver editon. 25 of this coin will be randomly mixed with the 5 and 10 coin sets.
  11. The coin sample of the Dutch 2006 is in. There are still some left at Geocoins.nl.
  12. The artwork of the Durch 2006 is in. There are still some left at Geocoins.nl.
  13. Not all European shops use European minters. Anyway: Fazanten: thanks for the nice looking coin. Offcourse I ordered mine.
  14. Hi Bob, We'll look into that. Sorry for the inconviniance. And no, you did not buy a canal boat, but the whole canal (and delivery is instant, just turn open your water tap). Direct link to geocoins.nl in English
  15. Why would they frown on this? Maybe TPTB wonder why people are using offline databases and programs . As stated before from the geocaching website: I understand the load on the PQ servers though, and also think you should keep the number of PQ as low as possible. I understand the reticking-thingy to let people only get the PQ if they really use it. But please keep in mind that people are actually using the PQ's to get the cache hunts into their PDS/GPS/Laptop and use them offline on their cache hunts or to plan them. Expanding the XML file will allow people who use the PQ functionality to automate the PQ retick process. They are in fact using the PQ actively as it was ment to be.
  16. PQ's are made for automatic processing. The filename is not the place for storing this information. An XML tag should be the correct place for it: Header PQ: <name>New Caches</name> <desc>Geocache file generated by Groundspeak</desc> <author>Groundspeak</author> <email>contact@Groundspeak.com</email> <time>2006-09-27T03:57:05.7800628-07:00</time> <keywords>cache, geocache, Groundspeak</keywords> Should be expanded with: <expires>2006-10-14T00:00:00.7800628-07:00</expires> <id>fd9bba82-63d2-4a07-a1da-e55375037992</id>
  17. Also, the LongID of the PQ should be in the XML file to make the process fully automatic.
  18. The whole reason behind the PQ is to have them processed automatically. An XML file is not for displaying information, but for processing it. Whether the email which contains the PQ is for human eyes or not read at all is another issue all together. Allmost nobody I speak about this is reading the PQ email. The program I use gets them from the email account, and process them. Because of mailbox limitations, I delete the PQ email after processing it. However, since there are some people out there that read those emails, keep the expiry text in the email. Displaying the age of the PQ in the PQ page is a step in the right direction, however I for one almost never come to the PQ pages, other than (in my case) GSAK notifies me that a PQ has more than 500 items in it. Then I go to the PQ page and change my PQs accordingly. I would strongly suggest to put the expiry date of the PQ into the XML files. That way you can have the programs which process those PQs handle the expiration of the PQ and can generated messages, reports etc.
  19. The coins have been shipped an should arrive within 5-7 (workdays. Thanks everyone who ordered this one. They turned out real nice.
  20. The coins arrived in The Netherlands too . Thanks, they look very good!
  21. We're proud to announce the "Poffertjes Geocoin". This coin is made for the 2nd IRC Poffertjes Event on June 18 2006. The coin has a special shape of a Dutch "Poffertjespan", with small pancakes with butter and powder sugar. A real "poffertjespan" (the 3D effect of the coins wll allmost be the same): The front is 3D, the backside is 2D. Text and pictures are imitation hard enamel. - Size: 38mm - Thickness: 3mm - Cutouts: yes - Special shape: yes Trackable on geocaching.com with a PC prefix and it's own icon (a "poffertje"): The coins will be shipped after the event on June 18. The following coins are made: - 250: Regular Edition, sand brushed Black Nickel; - 150: Limited Edition, Antique Silver; - 100: Event Edition, Antique Copper, only available for those who will attend the event. (The actual numbers of event coins can chance with the number of teams attending the event itself). Although the copper version can be bought in the shop, orders without the "will collect at the event" shipping option will be cancelled and the amount payed refunded. This edition is only for those who will attend the event. If there are coins left after the events, they will be sold then. You can combine different coins into one order in the shop. Ordering site: Geocoins.nl.
  22. I get the following error on trying to log geocoin. http://www.geocaching.com/track/details.aspx?id=490396 I happens to all of these Team Myth Geocoins. Error: Server Error in '/' Application. Value cannot be null. Parameter name: Argument 'Array' is Nothing. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.ArgumentNullException: Value cannot be null. Parameter name: Argument 'Array' is Nothing. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [ArgumentNullException: Value cannot be null. Parameter name: Argument 'Array' is Nothing.] Microsoft.VisualBasic.Information.UBound(Array Array, Int32 Rank) +130 Geocaching.UI.LogBookPanel.ShowLogOptions() +107 Geocaching.UI.LogBookPanel.ShowNewLogInfo() +226 Geocaching.UI.LogBookPanel.DisplayNewLogInfo() +332 Geocaching.UI.LogBookPanel.Page_Load(Object sender, EventArgs e) +2290 System.Web.UI.Control.OnLoad(EventArgs e) +67 System.Web.UI.Control.LoadRecursive() +35 System.Web.UI.Control.LoadRecursive() +98 System.Web.UI.Control.LoadRecursive() +98 System.Web.UI.Page.ProcessRequestMain() +772 Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
  23. Very nice coin . Are there still any left? I would like to have this coin
  24. I have send you an email with the address of Team_Wolfje
×
×
  • Create New...