Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Blueprints steps: Translate site options into PHP-serialized strings when appropriate

Open
  • Is something wrong?
#35 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
backend

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.

Description

enhancement

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!

Dominant language
PHP
Stars
61
Forks
22
Avg merge
19h 34m
Merged PRs (30d)
7

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WordPress/php-toolkit

All issues in WordPress/php-toolkit

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.