![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 12 years ago
Closed 12 years ago
#349 closed defect (bug) (fixed)
Verify parser will not alter custom fields during updates
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Developer Hub | Keywords: | |
| Cc: |
Description
Custom fields are needed to hold additional manually curated information, however it needs to be verified that running the parser for updates will not remove/alter the values in these fields.
If the parser will affect them, the parser needs to be changed to handle the presence of these custom fields.
Change History (2)
Note:
See TracTickets
for help on using tickets.
From what I can see in the WP-Parser code, there are checks to see if an entry already exists for a documentable element. If so, then that entry is updated, including the meta data. Custom data using other keys are not touched, so as long as you're using a different key name to WP-Parser, existing additional data should stay intact.