Opened 10 years ago
Closed 10 years ago
#627 closed defect (bug) (wontfix)
When parsing WordPress with non standard paths the inline code doesn't work
Reported by: | atimmer | Owned by: | |
---|---|---|---|
Milestone: | Priority: | low | |
Component: | Developer Hub | Keywords: | |
Cc: |
Description
If you parse WordPress from a non standard path (like in a subfolder such as wp) the inline code won't work.
The reason for this is because the parser only saves the start and ending lines and the file path. In this case the file path doesn't exist.
This should never be an issue on the live version of devhub, but still something that is worth noting.
Change History (2)
Note: See
TracTickets for help on using
tickets.
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:
(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?