i also tried the same code using login form, but i have a problem.
i want auto close the thickbox after submiting complete data,,

pls help me >>

I’m using Thickbox 3.1 to show signup form. The form content comes from jquery ajax post. The jquery lib is of version 1.4.2.

I placed a “signup” link into a div area, which is a part of my other large pages, and the whole content of that div area is ajax+posted from my server.

To make thickbox can work in my above arangement, I have modified the thickbox code a little like that:

//add thickbox to href & area elements that have a class of .thickbox
function tb_init(domChunk){
$(domChunk).live(‘click’, function(){
var t = this.title || this.name || null;
var a = this.href || this.alt;
var g = this.rel || false;
tb_show(t,a,g);
this.blur();
return false;
});}

This modification is the only change against the original version. Beacause the “signup” link is placed in ajaxed content, so I Use live instead of binding the click event directly.

When I tested on my pc, the thickbox works well. I can see the signup form quickly, without feeling the content of the parent page(here, is the other large pages) get refreshed.

But after transmiting my site files into VHost, when I click the “signup” link, the signup form get presented very slowly. The large pages get refreshed evidently, because the borwser(ie6) are reloading images from server incessantly. These images are set as background images in CSS files.

I think that’s because the slow connection of network. But why the parent pages get refreshed? and why the browser reloads those images one more time? Havn’t those images been placed in local computer’s disk?

Is there one way to stop that reloadding? Because the signup form can’t get displayed sometimes due to slow connection of network.

To verified the question, you can access http://www.juliantec.info/track-the-source.html and click the second link in left grey area, that is the “signup” link mentioned above. Thinks!

it would force a refresh, and will create a logged in state provided you have set the session

Glad you find it usefull, it will depend on what sort of CMS you are using, but the traditional data flow is after submission,

1. clense the data (to stop sql injection etc)
2. check the validity of the values from the array against a database of users and there passwords etc
3. display an error message if they are not found, or set a session of logged in if they are
4. close the box, and force a page reload causing the cms to recognise the sesssion.
5. the cms would detect the logged in state, allowing access to sensitive area`s of the site

I hope that helps

Adrian

thanks
Jeff