[Resolved] PHP bugs in our midst

Davidc316

It's a real drag, but there seems to be some kind of problem either with my script or with PHP, but whatever the case I dare say it's a common problem because I notice that this very forum seems to suffer the same flaw.

Basically the trouble is this sometimes when you click a form button of some sort, then sometimes the program doesn't recognise that you've registered a command and it won't register your intentions until you've clicked twice or maybe even a few times.

TWO EXAMPLES ARE AS FOLLOWS:

Example 1: One this forum- when you click "thread resolved" has anyone else noticed that sometimes it doesn't register it on first attempt? In my case I can tell you that I sometimes need to go back and click "thread resolved" several times until it registers that the thread is indeed resolved.

Example 2: One my little shopping cart program that I'm working on- when I click the "Add to cart" button it takes me to the page with my current shopping cart. HOWEVER, the cart is always empty on my first visit I always have to go back and click "add to cart" twice!

This problem is ruining PHP for me and I just wish there was something I could do about it.

Have anyone else encountered these problems, do you know what's causing them and what (if anything) can be done?

Thanks.

stolzyboy

it's not so much a PHP program problem as the coder him/herself, there has been numerous problem with the thread resolved problem, and jstarkey has been working on it, you should tell him when it doesn't work, there are only certain situations it doesn't work, like when you click to go to the last post in the forum with the arrow, and when you post a message then try to click it it won't work either, but if you click on the forum, then the thread, then go to the bottom, it will work every time

Davidc316

It's ok, I solved it. There is no PHP bug after all.

The problem was to do with my session variables not being passed from page to page.

Tell whoever is working on the "thread resolved" problem that just maybe it could be to do with the absence of one or two "session_start()" commands.

stolzyboy

no, it has nothing to do with session_start(), it has more to do with passing the threadid via query string, and making sure the addslashes it used when inputting into the database, but there, like i said, are only about two different scenarios when you can't use the resolved link

Davidc316

Ok, fair enough.

For the record, I can tell you that thread resolved doesn't work in the following situation:

If I type out a reply to a post and I am the original thread started then after I hit "Submit Reply" I taken to a screen which gives me an opportunity to read through the entire thread. If I then hit "thread resolved" that's when it doesn't work.

Not only that, but the only way that I seem to be able to get "thread resolved" to work is if I come right out of the thread (onto the main forum) and then go back into the thread again. For some reason that seems to do the trick.

Anyway, thanks for your help. Till next time!

🙂

stolzyboy

that is right, and that is one of the situations i explained that were supposed to be fixed, and were at one time, not sure what happened

jstarkey

Testing it now.

jstarkey

Argh, ok. I'll get this fixed asap.

Sorry, everyone. I can't hack vB itself so I'm trying to add these features without touching the internal code. Kinda weirds things out a bit. There are also several ways to get to the threads, like stolzy mentions newpost, that slipped through.