On Wed, 09 Oct 2013 01:52:44 +0300, Νίκος Αλεξόπουλος wrote:
> Is there something i can try to isolate the problem and make it work? Of course there is. That is part of the job of the developer: hard work trying dozens, maybe hundreds of different things until you isolate the problem. There are no shortcuts, no magic button you can push to immediately identify the source of the problem. If you are not willing to spend hours, maybe days or weeks, working on this problem, then you should hire a programmer who is, and stop fooling yourself that you are a professional developer. An amateur who programs for fun can just give up when a problem becomes too difficult and isn't fun any more. A professional has to keep going. Start by identifying which browsers this occurs on. You should test using at least Firefox, Internet Explorer, Safari, Chrome and Opera, for as many different versions as you can find. You should also test with less common browsers such as Konqueror, Epiphany, lynx, links and others. See if there is a pattern in which ones behave as you expect and which ones don't. You should also test with and without cookies enabled, ad-blockers, and similar. Maybe you can replicate the problem if (say) the user accepts the first cookie, then rejects it when they click Back. If this only occurs with a single version of a single browser with cookies enabled and no ad blocker, you should report it as a bug to the browser developers. Make sure you give them enough detail to replicate the problem. If it's an old version, they'll probably say Won't Fix, and you'll just have to accept that your cookie handling code won't work for some percentage of visitors. Have you checked that the server is setting the cookie values you expect? Have you checked the value of the cookie in the browser? If you don't know how to do these things, this site will teach you everything you need: https://duckduckgo.com/ Follow the links until you reach enlightenment. There are *thousands* of pages on debugging programming problems. If you find it is broken with *all* of the above browsers, then you should suspect a bug in your Python code. In that case, since other people have failed to reproduce the reported problem, you are obviously doing something different than what you are telling us you are doing. Only in this case should you come back here to ask for help with your Python code. Before you do, read this, and follow the instructions: http://www.sscce.org/ If you are not willing to do these things, then stop pretending to be a professional developer, and admit that you are only programming for fun. There is no shame in this -- not everyone is cut out to be a professional programmer, just as not everybody makes a good doctor or taxi driver or carpenter. > By whole counters project is based on cookie handling now.... If you cannot solve the cookie problem, maybe you should reconsider the decision to rely on cookies. -- Steven -- https://mail.python.org/mailman/listinfo/python-list
