WordPress / WordPress/php-toolkit
Blueprints steps: Translate site options into PHP-serialized strings when appropriate
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 61
- Forks
- 21
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 7
Description
Blueprints allow one to set options as the site is being created. I attempted to do so, but I couldn't find out how to update options that must be serialized, such as arrays.
I tried passing serialized data, then directly an array, but that did not seem to work. Do you have any suggestions on how to accomplish this?
Thank you!
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files or tests. Start by tracing how Blueprints accepts site options, then reproduce the behavior with serialized data and with an array; done means options that require serialization are translated correctly during site creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100