Thanks for both your help I'm almost there now.
The  $param= $_GET['_escaped_fragment_']; worked fine, now the rest of
my php works.

One other query, however; What should the links generated by this php
file return?
If my normal code set history to something like "#meep" (which would
now be "#!meep") should the static page have that link set to "#meep"
"#!meep" "?meep" or even "?_escape_fragment_"

I assume I could use #! that googles crawler would automatically
change to "?_escape_fragment_" but wouldn't it be better to give it
directly? or would that not associate the links correctly? Of course,
if I stuck to just using ? then it would make the site browsable for
people with JavaScript turned of too.

-Thomas







On Jul 14, 10:05 am, RPB <[email protected]> wrote:
> Hi darkflame,
>
> Not sure I fully understand your second question, but you should be
> able to just use $param= $_GET['_escaped_fragment_']; and then process
> the code as normal.
> Also, the 'Fetch with googlebot' tool in Webmaster tools is very
> helpful, showing you exactly what google will actually be crawling.
>
> Cheers,
> Robwww.yournextread.com
>
> On Jul 11, 12:07 am, darkflame <[email protected]> wrote:
>
>
>
> > a) As my server doesn't support server-side java, I'll be using php to
> > generate the static/snapshot pages. How close do they have to be to
> > the proper/GWT ones? Is it good enough if the text and links are
> > exactly same....but not the images/layout?  I dont want to be accused
> > of spoofing, but replicating the layout exact will prove a lot of
> > work.
>
> > b) Is there an easy way to parse the new urls? I used to use just GET
> > in PHP to retrieve each expected key/value, but this doesnt work now
> > that _escaped_fragment_ has been added at the start.  Is there a
> > recommended method? or do I just code my own parser?

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to