Skip to content

Bug fix: Removed string "px !important;" from $font_size which should have only number seeing its usage - #434

Open
hikarine3 wants to merge 1 commit into
aramk:masterfrom
hikarine3:master
Open

Bug fix: Removed string "px !important;" from $font_size which should have only number seeing its usage#434
hikarine3 wants to merge 1 commit into
aramk:masterfrom
hikarine3:master

Conversation

@hikarine3

Copy link
Copy Markdown

removed ". 'px !important;'" because its value is used as number and it is yielding warning like

Notice: A non well formed numeric value encountered in /var/www/web/app/plugins/crayon-syntax-highlighter/crayon_formatter.class.php on line 118

Line 118: $toolbar_height = $font_size * 1.5 . 'px !important;';

So "$font_size" should not have the string 'px !important;' but it should have only number

And this string is added in different lines, so removing string from $font_size should be O.K.

    removed ". 'px !important;'" because its value is used as number and it is yeilding warning like

    Notice: A non well formed numeric value encountered in /var/www/web/app/plugins/crayon-syntax-highlighter/crayon_formatter.class.php on line 118

    And this string is added in different lines, so removing should be O.K.
@hikarine3 hikarine3 changed the title Bug fix: Bug fix: Remove string "px !important;" from $font_size which should have only number seeing its usage Apr 15, 2018
@hikarine3 hikarine3 changed the title Bug fix: Remove string "px !important;" from $font_size which should have only number seeing its usage Bug fix: Removed string "px !important;" from $font_size which should have only number seeing its usage Apr 15, 2018
@eclectic-coding

Copy link
Copy Markdown

I was having the same issue and your fix works. Hopefully, this will get merged into the code.

@xavier-bs

Copy link
Copy Markdown

I think it would be better to change on lines 118 & 119 $font_size by $_font_size because $font-size is used on line 121.

@johnalarcon

Copy link
Copy Markdown

This PR isn't a valid fix. As @xavier-bs noted, the fix should be made at lines 118 & 119.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants