Thread:RedReaper83/@comment-4962005-20120428162026/@comment-4962005-20120501165332

i think i've rewritten this post about 5 times. :P Anyway, I don't think javascript will work. It would be VERY messy. And like I mentioned, PHP is out of the question unless its something wikia supports already.

Here's what I was going to write so you can judge for yourself on the use of javascript. Sorry if it's too hard to understand or overly easy to understand... but I'm not 100% sure how much you guys know about web development. Anyway, we could still try to do what I mention below if you guys want, but this may not be the best option. If we can find a way to do it with only wiki keywords and no or at least few GET requests, that would be 100 times better (and cause me a few less grey hairs :P).

Sorry, I'm about to speak geek for a minute, but it might help me work this out. For example, when you click a submit button on a web site after filling out a form, it sends a GET request to another website. That's what we want... because a GET request sends parameters to that next site. Then its just a matter of parsing the GET request in the URL. For example, when you go to a page and it says something like this in the URL /page?id=3&name=Sarah&error=1, it's telling the page that it should know that:  id  is 3,  name is Sarah, and error is 1. Generally, the page that gets the information saves it and then redirects to another site so quickly, you never see the transaction happen.

The only problem with what I mentioned above, is that we'd have to ensure all links to the card tables and pages first went to the database sending a get request stating which page it needed to redirect to. i.e. mainDatabase?page=RareCards. Then we would have to parse all of the strings in the database (unpleasant and slow) to find the data that goes to RareCards. The URL to the Rare Cards page would look something like this (I'm not using actual values): /RareCards?card1=Alligator&price1=475&atk1=2000&def1=3700&max1=4000/5000&card2=Child&price2=475&atk2=2000&def2=3700&max2=4000/5000&&card3=Tiger_Shark&price3=475&atk3=2000&def3=3700&max3=4000/5000...... etc until all of the card's information is on that url. A VERY VERY long URL. Then if someone wanted to get to the individual card page, they would have to click on the link in the table, which would send the card name to the database, which would then do the same thing as above to the card page.