Thank you for the clarification. I guess this is why it's important to leave comments. :)
On Aug 18, 3:06 am, Mike Ratcliffe <[email protected]> wrote: > The browser has no knowledge of which templates have been used to > create a file. The only thing that you can do is add comments to the > php templates. > > e.g. > Before the first HTML tag in header.php: > <!-- header.php: START --> > > After the last HTML tag: > <!-- header.php: END --> > > On Aug 18, 9:44 am, Eric Reynolds <[email protected]> > wrote: > > > Thanks Mike. Of course, by default, a Firebug user would assume that > > the coding comes from the page that's being viewed. But, with > > Wordpress, the php is mixed in with html. > > > Unfortunately, the comments, in green, don't identify the page where > > the code resides. The comments only display basic info about the > > actual code. I was wondering if Firebug could indicate something like > > "source code from header.php" or something like that so I would know > > that I have to finalize my code revisions or additions in that file. > > > I hope this makes sense. > > > Eric > > > On Aug 18, 12:00 am, Mike Ratcliffe <[email protected]> > > wrote: > > > > In the HTML tab select "Show Comments" from the tabs dropdown ... the > > > wordpress templates files include comments that identify them. > > > > On Aug 18, 2:57 am, Eric Reynolds <[email protected]> > > > wrote: > > > > > I've been using Firebug to proof changes for html pages, and it's been > > > > great. Now, I am proofing a Wordpress site, and dealing with php and > > > > CSS files. No problem with identifying the CSS. Yet I don't know how > > > > to identify where changes need to be made in viewing php files. I make > > > > corrections in Firebug, but I have to go headhunting for the code > > > > because Firebug doesn't tell me the page that I am viewing. Any help > > > > appreciated. -- You received this message because you are subscribed to the Google Groups "Firebug" 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/firebug?hl=en.
