The reason why the HTML output seen in the browser cannot be directly mapped to the server-side source code is that it is mostly dynamically generated. In CMS systems the articles are normally even saved in a database, which makes mapping to it impossible. Though issue 5035 <http://code.google.com/p/fbug/issues/detail?id=5035>describes an approach to allow the user at least to create some mappings to his (locally stored) server-side script files.
Sebastian On Sunday, February 9, 2014 6:50:50 PM UTC+1, Jim Zubemo wrote: > > I see this was posted in 2009. It's 2014 now and I had to face the same > challenge ...sigh! :p > > Anyways, I realized we cannot see the source php file in Firebug. So I > also have a local copy of the CMS and uses Notepad++ to find string in a > directory. > > On Friday, 25 December 2009 12:39:15 UTC+5:30, redhat wrote: >> >> Hi- can Firebug tell me the name of the file where I'd find the source >> code that I am inspecting, just like it does for CSS files? For >> instance, in Wordpress themes where there are lots of php files. I'd >> be inspecting an element that doesn't show up in a php file itself, >> but WP is pulling the element from a supporting file (not sure how to >> describe this, but I hope this makes sense). >> >> FB tells me which CSS file has the styling information for that >> element, but what about the file that contains the html? >> > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/5db8bedf-3c65-45a4-8f93-f10bc6f31be0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
