No, can not place it in the configure.php file found in the includes file.
Google gives multiple methods of incorporating the verification code. One is by including in the header which is the mthod you described above. Another is by creating a uniquely named file (they tell you what to name it) and placing the file in the root folder. That file is to also contain specific information stated by google. I think there is one or more other options, but I forget.
Now all that said the root folder may not be the public_html folder depending on how all things are setup on theserver forthe site(s) in question. For example if there is a sub folder off of public_html named site1 and it is in that folder that all of the ZC files applicable to site1 are stored, then the root of site1 is actually the public_html/site1 folder. Yes, the root is where index.php is at so there is no change there either.
It is important though that you not mix the directions from google, pick one method and go straight through with it.
I wanted to point out that if you do decide to change to a different template, your google incorporated code will not automatically transfer with it installed the way applied. It is also why everyone else was pushing for the code to be properly incorporated into the store's root so that the chosen template wouldn't matter related to the google code.
The discussion of the configure.php file was to help you understand the pieces and parts that are in ZC as earlier in this thread you stated you didn't know where the public_html folder was on your server or maybe it was that you couldn't find it or something similar. I at no time said that the code could be installed in the configure.php file.



Reply With Quote
