[wp-meta] [Making WordPress.org] #627: When parsing WordPress with non standard paths the inline code doesn't work

[Making WordPress.org]

#627: When parsing WordPress with non standard paths the inline code doesn't work
----------------------+-------------------------------------
  Reporter:  atimmer  |      Owner:
      Type:  defect   |     Status:  new
  Priority:  low      |  Component:  developer.wordpress.org
Resolution:           |   Keywords:  needs-testing
----------------------+-------------------------------------

Comment (by coffee2code):

 Yes, in order to parse a file for source code it needs to be able to
 access the file.

 The option 'wp_parser_root_import_dir' should contain the path to the root
 directory of the WP source that was parsed. This option is set by the
 parser.

 If that option is not set or has no value, then the path to the actively
 running WP site is used.

 In the event you want to adjust the behavior above, you could:

 * Manually configure the path in the 'wp_parser_root_import_dir' option.
 (Or delete it if the path to the parsed files is different or isn't
 accessible to the site).
 * Filter the option (via 'pre_option_wp_parser_root_import_dir') and
 configure a different path
 * Pre-parse the source code for all functions and methods after the
 initial parsing (storing the values in '_wp-parser_source_code' meta for
 each) so that no runtime parsing ever takes place (and thus the parsed
 source doesn't need to be accessible or present).

 (I present the above not as an explanation to you @atimmer since I know
 you know it; just documenting it for someone who may be looking into this
 later.)

 Is there some different handling you'd like to see happen?

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/627#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org