lbryio / lbryio/lbrypress

Text Color is not carried over into LBRY Post

Open
#31 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
21
Forks
7
PR merge metrics
No merged PRs in 30d

Description

**DESCRIPTION:**
Using text color in a Wordpress post does not carry over to the LBRY version.

-----

**REPRO STEPS:**
1) Log into self-hosted Wordpress site w/ LBRYPress Plugin
2) Create a new post
3) Create a Paragraph Block
4) Write text and apply non-black text color
5) Publish the post and review on LBRY

**Results**: Text color is black

**Expected:** Text color is non-black

-----

**ENVIRONMENT:**
Ubuntu 18.04.4
WordPress 5.3.3
PHP 7.2.24
LBRYPress 0.0.1
Lodestar Theme 1.0.8

-----

**IMAGES:**

![LBRYPress_0 1 1_TextColorLBRY](https://user-images.githubusercontent.com/30788194/82759929-89802080-9dad-11ea-8565-35e05a0701fb.png)

![LBRYPress_0 1 1_TextColorWordpress](https://user-images.githubusercontent.com/30788194/82759930-8be27a80-9dad-11ea-92ed-71765a48b826.png)

-----

**LBRY ADDRESS:**
bZSqrVdpxt5KJdn2eGMUzT9Jn3gEiRet7b
mail@cahlen.org

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No source file or test is named. Start by tracing how WordPress paragraph blocks are converted into the LBRY post, then compare the generated output for a non-black text color; done means the published LBRY version preserves that color.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
backend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.