Daca selectez

imi scoate output

    font-weight: 600italic;

in loc de

    font-weight: 600;
    font-style: italic;

Daca incerc sa fortez o iconita cu content:"\F0d5" de exemplu, dupa refresh "" o sa dispara si o sa lase numai F0d5.

N-am testat mai multe cazuri, dar in asta nu merge

fixul la om este in customify/class-pixcustomify.php
linia 639 inlocuita cu asta
if ( $load_all_weights && isset( $value['variants'] ) && ! empty( $value['variants'] ) ){

Defaulturile nu prea functioneaza initial

Daca dai reset to defaults vor functiona

Dar in schimb crapa previewul cam asa:

Am intalnit la Patch ca functia de callback sa anuleze comportamentul default al regulei, adica sa nu mai scoata css-ul. De exemplu"

array(
                            'property' => 'color',
                            'selector' =>
                                'h1 a,
                                .site-title a,
                                h2 a,
                                h3 a,
                                .entry-card.format-quote .entry-content a:hover,
                                .bypostauthor .comment__author-name:before,
                                .site-footer a:hover, .test',
                             'callback_filter' => 'patch_color_contrast'
                        ),

Scoate doar callback-ul nu si regulile de CSS - e intentionat asta?

Scenariu: sunt pe pagina de Journal si intru un Customizer. Modific niste font-uri pe pagina de Journal.
Apoi navighez pe un single post si intru sa modific niste font-uri pentru Single Post (in sectiunea Main Content). Cand deschid un field de font, apare eroarea in consola.

VM18460 font_selector_preview.js?ver=4.7:100 
Uncaught TypeError: Cannot read property 'noah_font_typeline_cb' of null(…)

https://cloudup.com/ckD-fQj8YHU

LE: alt scenariu mai simplu
https://cloudup.com/c4FqNyX1v6P

maybe an option for this

Am mai avut o problema asemanatoare, cand faceam modificari in text field-urile din customizer si nu imi triggeruia butonul de Save (#22).

Acum am incercat sa adaug codul de Google Analytics in Custom Javascript — Footer si cu toate ca initial butonul de "Save and publish" a fost activ, nu mi-a salvat toate modificarile facute:

@andreilupu cand ai ocazia, investighezi daca putem gasi o solutie care sa ofere o mai buna consistenta procesului de Saving?

Dupa ce modific un font si dupa ce inchid modalul, font-name nu se modifica:

^ in exemplu asta, la dreapta de Heading 1 trebuia sa fie Arvo in loc de Arca Majora.

2d623bb

Rosa (Help Scout) #2

Your rosa theme is broke by newest customfy update 2.71 works 3 breaks all most all of the CSS user additions to the theme

Pile (Freshdesk)
Listable

Parse error: syntax error, unexpected '&&' (T_BOOLEAN_AND), expecting ')' in /home4/techstep/public_html/gemmahenderson.com/wp-content/plugins/customify/features/customizer/controls/class-Pix_Customize_Font_Control.php on line 431

So I can't access the Customizer.

cc @pixelgrade/heroes cred ca ar ajuta un mesaj canned si marcate ticketele cu tag-ul customify-1-3-0 ca sa putem reveni la ei dupa.

Use //ajax.googleapis.com/ajax/libs/webfont/1/webfont.js as URL not //ajax.googleapis.com/ajax/libs/webfont/1.5.3/webfont.js

This decision is made based on the latest customizer changes in WordPress 4.7

Theme mod should help users save options per theme and allow them to switch between themes easily

Sometimes we need to make some fields dependent to each other. For example, when a checkbox is on another field should be visible or hidden.

Really need this for pixelgrade/timber#23

From here pixelgrade/noah#168

This happens because the default typography value isn't properly serialized.

this is a small issue for pixelgrade/timber#62

And also maybe try to translate some languages in wordpress.org / glotpress CC @raduconst

Daca modifici slider-ul si dai save o sa mearga, insa daca modifici valoarea si dai ctrl+s (pentru ca butonul de save este inca inactiv) nu va salva valoarea.

De exemplu:

"There’s also a dedicated post that walks through the process of migrating existing custom CSS options in themes and plugins to the core functionality – be sure to follow those steps if your plugin or theme does custom CSS" — via 4.7
https://make.wordpress.org/core/2016/11/26/extending-the-custom-css-editor/

Hey, nice works guys.
Does the license of it allow us to includes Customify into our theme that available for sale on TF or our own theme shop?

Regards.

O solutie sa afisam un field in functie de valoarea unui select/checkbox.

Am facut un research si am gasit plugin-ul asta care s-ar putea sa ne ajute ca punct de start: https://github.com/znbailey/jQuery-Dependent-Fields

Imi place sintaxa si cred ca putem incepe prin a scrie config-ul intr-un fisier separat in functie de tema:
$('#navigation-trigger-text').dependsOn('#navigation-trigger-format', 'text');

Ce ziceti @andreilupu @vladolaru ?

La prima incarcare a unui site neoptimizat (deci nu pe demo) o sa observi ca se schimba stilurile de la cele din tema (css) in cele din customify si switch-ul se produce cam intr-o secunda-ish.

Se poate vedea pe dev:
http://dev.code711.com/demos/rosa/

like this pixelgrade/timber#58

Tabs will be used as anchor points for sections (see #40):

Scrolling interaction recording

Visual clues for better options organizations:

Sections field markup:
'html' => '<span class="separator section">&#x1f4dd; ' . esc_html__( 'Section', 'txt' ) . '</span>',

Sub sections markup:
'html' => '<span class="separator sub-section">&#x1f4dd; ' . esc_html__( 'Sub section', 'txt' ) . '</span>',

It would be nice if we can bring together in one "extended" field the following typography related options:

font-family / font-weight / font-subset
font-size / line-height
letter-spacing / text-transform

This way we can reuse them more consistently.

I created an example and how this field configuration might look like:

// Example of an Extended Typography field
'extended_typography_example' => array(
    'type'        => 'font',
    'label'       => esc_html__( 'Item Title Font', 'noah' ),
    'desc'        => esc_html__( '', 'noah' ),
    'selector'    => '.c-card h2',

    // Set the defaults
    'default'   => array(
        'font-family' => 'Arca Majora',
        'font-weight' => '700',
        'font-subset' => 'latin-ext,cyrillic',
        'font-size'   => 24,
        'line-height' => 1.5,
        'letter-spacing' => 1,
        'text-transform' => 'none'
    ),

    // Sub Fields Configuration (optional)
    'fields'    => array(
        'font-family'   => array(
            'recommended' => $recommended_headings_fonts,   // List of recommended fonts defined by theme 
        ),
        'font-weight'   => array(
            'load_all_weights' => true,                     // False by default (used for Body fonts)
        ),
        'font-size'     => array(                           // Set custom values for a range slider
            'min'          => 8,
            'max'          => 20,
            'step'         => 1,
            'unit'         => 'px',
        ),
        'line-height'    => array(0, 2, 0.1, ''),           // Short-hand version
        'letter-spacing' => array(-5, 20, 1, 'em'),
        'text-transform'     => false                           // Disable sub-field (False by default) 
    )
),

https://cl.ly/3R133v0I0k46

CSS Editor din Customizer devine inoperabil daca activezi WooTheme Helper

Am reusit sa identific asta pe Timber 1.6.6 cu WP 4.7 si Customify 1.3.1;

@andreilupu nu a functionat solutia cu "shift+refresh", predau stafeta la @cristianfrumusanu sa dea o parere

In WP 4.7 au adaugat ei un editor de CSS iar al nostru pare sa nu mai functioneze.
Cred ca trebuie verificata versiunea WP si dezactivat by default al nostru daca e > 4.7

Nu stiu daca stiai, sau nu, dar e bine sa mentionez faptul ca daca scrii in Custom JS (footer sau header) iti va pune foarte multe spatii in fata si iti obstructioneaza putin asa logica si claritatea citirii codului (bad UI/UX).

Testat cu Customify pe ROSA si BORDER (Appearance — Customize — Theme Options — Custom JavaScript)

https://make.wordpress.org/core/2015/07/16/new-customizer-media-controls-in-4-3-and-4-2/

The issue is this line of code:

Un preview fain si destept la fonturi in customizer: