Pass WordPress post_ids as custom metadata to Parse.ly
Open
Nobody has claimed this yet.
wp-parsely
- Dominant language
- PHP
- Stars
- 66
- Forks
- 36
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
As of now on Parse.ly we only have canonical urls to uniquely identify post and since Prod and Non-Prod environment can configure differently so its better to have post_ids also which can help us to uniquely identify posts.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the WordPress plugin's Parse.ly tracking integration and the current canonical-URL metadata path. Determine where custom metadata is assembled, then verify that post_ids are included and distinguish posts across production and non-production configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100