Child Theme Configurator

説明

Child Theme Configurator は、一般的な問題のテーマを分析したり、子テーマを作成したり、カスタマイズのオプションを超えて編集、修正することができる使いやすいユーティリティです。子テーマのスタイルシートを直接カスタマイズできるようにしたい場合に WordPressユーザー向けに設計された Child Theme Configurator を使用すると、CSS属性を簡単に特定して上書きすることができます。アナライザはレンダリングされたテーマをスキャンし、自動的に子テーマを設定します。最適なパフォーマンスを得るために、テーマとフォントのスタイルシートを正しくエンキューし、ベンダー固有の構文を処理します。親テーマをそのままにしながら、子テーマのルック
& フィールを無制限に制御できます。子テーマの作成方法の詳細

子テーマを管理する

Child Theme Configurator は、スタイルシートを解析してインデックスを作成するため、すべての CSS メディアクエリー、セレクタ、プロパティ、値をすぐに利用することができます。次に、子テーマにコミットする前に、カスタマイズした内容がどのように表示されるかを表示します。最後に、編集した内容を保存するので、編集内容を失うリスクなしに、子テーマでスタイルをカスタマイズできます。

既存の親テーマからいくつでも子テーマを作成することができます。Child Theme Configurator では、インストールされているテーマ (既存の子テーマも含む) から選択し、その結果を テーマディレクトリに保存できます。

準備ができたら、子テーマを有効化するだけで、WordPress サイトにカスタムスタイルが自動的に適用されます。

なぜ、子テーマを作成し、Child Theme Configurator でスタイルをカスタマイズするのか ?

  1. カスタマイザーを使用して変更することはできません。

  2. 子テーマを使用しない限り、アップデートすると、テンプレートやスタイルシートに加えた変更が失われます。

  3. Child Theme Configuratorは、使用しているテーマに基づいて、子テーマの正しい設定方法を自動的に判断します。

  4. テーマが使用している正確なスタイルセレクタを見つけ出し、素早くプロパティを変更することができます。

  5. 管理画面からテーマテンプレートの検索、コピー、編集が可能です。

  6. その他:

    • カスタマイズを失うことなくテーマを更新
    • スマートテーマアナライザーが適切な設定を判断
    • ほとんどの親テーマに共通する子テーマの問題を解決
    • 既存のウィジェット、メニュー、カスタマイザー設定を子テーマにコピー
    • 子テーマでウェブフォントを使用
    • スタイルシートを @import の代わりに エンキュー (リンク)
    • テーマ CSS をすばやく見つけて編集します。
    • レスポンシブデザインに対応した @media クエリーのカスタマイズ
    • スペクトルカラーピッカーで16進数、RGBA (透明)、名前付きカラーを選択可能
    • フォールバックスタイルの追加 (プロパティごとに複数の値)
    • 開発工数の短縮
    • マルチサイト対応
    • カスタマイザーで修正できないようにする
    • Zip アーカイブで子テーマのエクスポート
    • 親テーマの正確なセレクタを特定し上書き
    • 他の要素を変更することなく、特定の色、背景、フォントスタイルなどを変更
    • クロスブラウザーおよびベンダープレフィックス付きプロパティとCSSグラデーションの自動生成
    • カスタムスタイルをコミットする前にプレビュー
    • WP Filesystem API を使用 – 削除できないファイルを作成しない

Child Theme Configurator PRO

Child Theme Configurator の CSS カスタマイズ機能を、サイトにインストールされているあらゆる WordPress プラグインに適用します。Child Theme Configurator PRO はプラグインをスキャンし、そのスタイルシートをカスタマイズすることができます。PRO でスタイルのカスタマイズをより迅速かつ容易にするために、さらに多くの機能が追加されました。

さらに詳しく http://www.childthemeplugin.com/child-theme-configurator-pro

個別のプラグインでウィジェットコンテンツを無制限に作成可能

IntelliWidget は、カスタムページメニュー、特集記事、スライダー、その他の動的コンテンツ機能を組み合わせて、ページごとまたはサイト全体で表示することができ、複数のプラグインの作業を行う多機能なウィジェットマネージャーです。

さらに詳しく https://www.lilaeamedia.com/plugins/intelliwidget

Hook Highlighter

Hook Highlighter は、サイトのフロントページで有効化すると、WordPress の内部プログラムフローを管理者が把握できるようにします。

現在のページに対して、アクションフック、フィルターフック、プログラムファイル、バックトレース情報をインラインで表示します。

さらに詳しく https://www.lilaeamedia.com/product/hook-highlighter

クエリー/セレクタータブ

There are two ways to identify and customize baseline (parent) styles. Child Theme Configurator lets you search styles by CSS selector and by property. If you wish to customize a specific CSS selector (e.g., h1), use the “Query/Selector” tab. If you have a specific CSS value you wish to customize site-wide (e.g., the color of the type), use the “Property/Value” tab.

The Query/Selector tab lets you find specific CSS selectors and edit them. First, find the query that contains the CSS selector you wish to edit by typing in the Query autoselect box. Select by clicking with the mouse or by pressing the “Enter” or “Tab” keys. CSS selectors are in the base query by default.
Next, find the CSS selector by typing in the “Selector” autoselect box. Select by clicking with the mouse or by pressing the “Enter” or “Tab” keys.

This will load all of the properties for that CSS selector with the Original values on the left and the child theme values inputs on the right. Any existing child theme values will be automatically populated. There is also a Sample preview that displays the combination of Parent and Child overrides. Note that the border and background-image get special treatment.

The “Order” field contains the original sequence of the CSS selector in the parent theme stylesheet. You can change the CSS selector order sequence by entering a lower or higher number in the “Order” field. You can also force style overrides (so called “!important” flag) by checking the “!” box next to each input. Please use judiciously.

Click “Save” to update the child theme stylesheet and save your changes to the WordPress admin.

Adding Raw CSS

If you wish to add additional properties to a given CSS selector, first load the selector using the Query/Selector tab. Then find the property you wish to override by typing in the New Property autoselect box. Select by clicking with the mouse or by pressing the “Enter” or “Tab” keys. This will add a new input row to the selector inputs.

If you wish to add completely new CSS selectors, or even new @media queries, you can enter free-form CSS in the “Raw CSS” textarea. Be aware that your syntax must be correct (i.e., balanced curly braces, etc.) for the parser to load the new custom styles. You will know it is invalid because a red “X” will appear next to the save button.

If you prefer to use shorthand syntax for properties and values instead of the inputs provided by Child Theme Configurator, you can enter them here as well. The parser will convert your input into normalized CSS code automatically.

プロパティ/値タブ

The Property/Value tab lets you find specific values for a given property and then edit that value for individual CSS selectors that use that property/value combination. First, find the property you wish to override by typing in the Property autoselect box. Select by clicking with the mouse or by pressing the “Enter” or “Tab” keys.

This will load all of the unique values that exist for that property in the parent theme stylesheet with a Sample preview for that value. If there are values that exist in the child theme stylesheet that do not exist in the parent stylesheet, they will be displayed as well.

For each unique value, click the “Selectors” link to view a list of CSS selectors that use that property/value combination, grouped by query with a Sample preview of the value and inputs for the child theme value. Any existing child theme values will be automatically populated.

Click “Save” to update the child theme stylesheet and save your changes to the WordPress admin.

If you want to edit all of the properties for the CSS selector you can click the “Edit” link and the CSS selector will automatically load in the Query/Selector Tab.

Web フォントタブ

You can add additional stylesheets and web fonts by typing @import rules into the textarea on the Web Fonts tab. Important: do not import the parent theme stylesheet here. Use the “Parent stylesheet handling” option from the Parent/Child tab.

ファイルタブ

親テンプレート

You can copy PHP template files from the parent theme by checking the boxes. Click “Copy Selected to Child Theme” and the templates will be added to the child theme’s directory.

CAUTION: If your child theme is active, the child theme’s version of the file will be used instead of the parent immediately after it is copied. The functions.php file is generated separately and cannot be copied here.

子テーマファイル

Templates copied from the parent are listed here. These can be edited using the Theme Editor in the Appearance Menu. Remove child theme images by checking the boxes and clicking “Delete Selected.”

子テーマ画像

Theme images reside under the images directory in your child theme and are meant for stylesheet use only. Use the media gallery for content images. You can upload new images using the image upload form.

子テーマスクリーンショット

You can upload a custom screenshot for the child theme here. The theme screenshot should be a 4:3 ratio (eg., 880px x 660px) JPG, PNG or GIF. It will be renamed “screenshot”.

Zip アーカイブで子テーマのエクスポート

You can download your child theme for use on another WordPress site by clicking “Export”.

プレビューと有効化

IMPORTANT: Test child themes before activating!

Some themes (particularly commercial themes) do not correctly load parent template files or automatically load child theme stylesheets or php files.

In the worst cases they will break your website when you activate the child theme.

  1. Navigate to Appearance > Themes in the WordPress Admin. You will now see the new Child Theme as one of the installed Themes.
  2. Click “Live Preview” (theme customizer) below the new Child Theme to see it in action.
  3. When you are ready to take the Child Theme live, click “Activate.”

MULTISITE USERS: You must Network Enable your child theme before you can use Live Preview. Go to “Themes” in the Network Admin.

警告

  • Arbitrary comments are not supported. Providing a high level of flexibility for previewing and modifying custom styles requires a sophisticated parsing system. Maintaining comments that are bound to any particular element in the stylesheet is prohibitively expensive compared to the value it would add. Although we are working to include this as an option in the future, currently all comments are stripped from the child theme stylesheet code.
  • No @keyframes or @font-face rules. Child Theme Configurator only supports @media and @import. If you need other @rules, put them in a separate stylesheet and import them into the Child Theme stylesheet.
  • Only two-color gradients. Child Theme Configurator is powerful, but we have simplified the gradient interface. You can use any gradient you want as long as it has two colors and no intermediate stops.
  • CSS properties are auto-discovered. Child Theme Configurator loads the properties that exist in the Parent stylesheet. You can always add new properties using the “Raw CSS” text area.
  • Legacy gradient syntax is not supported. Child Theme Configurator does not support the MS filter gradient or legacy webkit gradient. These will continue to work if they are used in the parent theme, but will not be written to the child theme stylesheet. If there is a demand, we may add it in a future release, but most users should have upgraded by now.

ドキュメンテーション

http://www.childthemeplugin.com/ を見る

Serbo-Croatian translation courtesy of Borisa Djuraskovic borisad@webhostinghub.com http://www.webhostinghub.com

Copyright: (C) 2014-2018 Lilaea Media

スクリーンショット

  • Parent/Child tab
  • Parent/Child tab with parent theme menu open
  • Query/Selector tab
  • Property/Value tab
  • Web Fonts tab
  • Parent CSS tab
  • Files tab

インストール

  1. To install from the Plugins repository:

    • In the WordPress Admin, go to “Plugins > Add New.”
    • Type “child theme” in the “Search” box and click “Search Plugins.”
    • Locate “Child Theme Configurator” in the list and click “Install Now.”
  2. To install manually:

    • Download the Child Theme Configurator from https://wordpress.org/plugins/child-theme-configurator
    • In the WordPress Admin, go to “Plugins > Add New.”
    • Click the “Upload” link at the top of the page.
    • Browse for the zip file, select and click “Install.”
  3. In the WordPress Admin, go to “Plugins > Installed Plugins.” Locate “Child Theme Configurator” in the list and click “Activate.”

  4. Navigate to Tools > Child Themes (multisite users go to Network Admin > Themes > Child Themes).

親/子タブ: 子テーマを作成するための10の簡単な手順

  1. アクションを選択:

    • 新しい子テーマを作成する – インストールされたテーマを親として使用し、カスタマイズ可能な新しい子テーマをインストールします。
    • 既存の子テーマを設定する – 以前にインストールした子テーマを設定して、コンフィギュレータで使用するか、現在の設定を変更します。
    • 既存の子テーマを複製する – 既存の子テーマの完全なコピーを、メニュー、ウィジェットおよびその他のカスタマイザ設定を含む新しいディレクトリに作成します。この操作では、親テーマの設定をコピーするオプション (以下の手順8) は無効になっています。
    • 既存の子テーマをリセット (これにより、コンフィグレータで行った作業はすべて破棄されます) – 子テーマのスタイルシートと関数ファイルを初期設定または最後にリセットする前の状態に戻します。
  2. 新しい子テーマを作成する場合は、親テーマを選択します。設定、複製、またはリセットする場合は、子テーマを選択してください。

  3. 子テーマを分析 – 「分析」をクリックして、スタイルシートの依存関係やその他の潜在的な問題を判断します。

  4. 新しい子テーマを作成する場合は、新しいテーマディレクトリに名前を付けます。それ以外の場合は、ディレクトリが正しいかどうかを確認します。- これは子テーマの名前ではありません。以下のステップ7で、名前、説明などをカスタマイズすることができます。

  5. 新しいスタイルを保存する場所を選択:

    • Primary Stylesheet (style.css) – Save new custom styles directly to the Child Theme primary stylesheet, replacing the existing values. The primary stylesheet will load in the order set by the theme.
    • Separate Stylesheet – Save new custom styles to a separate stylesheet and use any existing child theme styles as a baseline. Select this option if you want to preserve the original child theme styles instead of overwriting them. This option also allows you to customize stylesheets that load after the primary stylesheet.
  6. 親テーマのスタイルシート処理を選択:

    • Use the WordPress style queue. – Let the Configurator determine the appropriate actions and dependencies and update the functions file automatically.
    • 子テーマのスタイルシートで @import を使用する。 – WordPress スタイルキューを使用して親スタイルシートをロードできない場合にのみ、このオプションを使用します。@import の使用はおすすめしません。
    • 親スタイルシート処理を追加しないでください。このテーマがすでに親テーマスタイルシートを処理している場合、または親テーマのstyle.cssファイルがその外観に使用されていない場合は、このオプションを選択します。
  7. 子テーマの名前、説明、作成者、バージョンなどをカスタマイズ: (クリックしてフォームを切り替え)

  8. 親テーマのメニュー、ウィジェット、その他のカスタマイザー設定を子テーマにコピーする: – 注意: すでに設定されている子テーマのオプションが上書きされます。

  9. ボタンをクリックしてコンフィグレータを実行します。

  10. IMPORTANT: Always test child themes with Live Preview (theme customizer) before activating!

FAQ

自分のテーマに加えた変更を子テーマに移すにはどうすればよいですか ?

Follow these steps: http://www.childthemeplugin.com/how-to-use/#child_from_modified_parent

When I run the analyzer I get “Constants Already Defined” notice in PHP Debug Output

This is a misconfiguration created by the Bluehost auto-installer. http://www.childthemeplugin.com/child-theme-faqs/#constants” class=”scroll-to”>How to fix.

Is there a tutorial?

ページの右上にある[ヘルプ]タブに動画があります。以下のサイトでも見られます URL: http://www.childthemeplugin.com/tutorial-videos

If the parent theme changes (e.g., upgrade), do I have to update the child theme?

No. This is the point of using child themes. Changes to the parent theme are automatically inherited by the child theme.

A child theme is not a “copy” of the parent theme. It is a special feature of WordPress that let’s you override specific styles and functions leaving the rest of the theme intact. Quality themes should identify any deprecated functions or styles in the upgrade notes so that child theme users can make adjustments accordingly.

If I uninstall Child Theme Configurator are child themes affected?

No. Child Theme Configurator is designed to work independently of themes and plugins. Just remember that if you re-install, you must rebuild the configuration data using the Parent/Child tab.

コメントを追加するにはどうすればいいですか?

Arbitrary comments are not supported. Providing a high level of flexibility for previewing and modifying custom styles requires sophisticated parsing and data structures. Maintaining comments that are bound to any particular element in the stylesheet is prohibitively expensive compared to the value it would add. Although we are working to include this as an option in the future, currently all comments are stripped from the child theme stylesheet code.

Does it work with Multisite?

Yes. Go to “Network Admin > Themes > Child Themes.” Child themes must be “Network enabled” to preview and activate for Network sites.

Does it work with plugins?

Child Theme Configurator PRO brings the CSS editing power of Child Theme Configurator to any WordPress Plugin installed on your website by scanning your plugins and creating custom CSS in your Child Themes. Learn more at http://www.childthemeplugin.com/child-theme-configurator-pro

Why doesn’t this work with my [insert vendor here] theme?

Some themes (particularly commercial themes) do not correctly load parent template files or automatically load child theme stylesheets or php files.

This is unfortunate, because in the best case they effectively prohibit the webmaster from adding any customizations (other than those made through the admin theme options) that will survive past an upgrade. In the worst case they will break your website when you activate the child theme.

Contact the vendor directly to ask for this core functionality. It is our opinion that ALL themes (especially commercial ones) must pass the Theme Unit Tests outlined by WordPress.org and ALWAYS TEST CHILD THEMES BEFORE ACTIVATING (See “Preview and Activate”).

Will this slow down my site?

Child Theme Configurator is designed to add the minimum amount of additional overhead possible and can actually improve performance. For example:

  • Child Theme Configurator creates or updates files that are already being read by the system. On the front-end, there are no database calls so WordPress can run independent of the plugin. In fact, you can remove Child Theme Configurator when you are finished setting up your child themes.
  • Custom styles are applied to a stylesheet file that can be cached by the browser and/or cached and minimized by a performance caching plugin. Because the editor creates mostly “overrides” to existing styles, the file is typically smaller than other stylesheets.
  • The code that drives the editor interface only loads when the tool is being used from the WordPress Admin, including Javascript and CSS. This means that it will not get in the way of other admin pages.
  • The biggest performance hit occurs when you generate the Child Theme files from the Parent/Child tab, but this is a one-time event and only occurs from the WordPress Admin.

HELP! I changed a file and now I am unable to access my website or login to wp-admin to fix it!

To back out of a broken child theme you have to manually rename the offending theme directory name (via FTP, SSH or your web host control panel file manager) so that WordPress can’t find it. WordPress will then throw an error and revert back to the default theme (currently twenty-fifteen).

The child theme is in your themes folder, usually

[wordpress]/wp-content/themes/[child-theme]

To prevent this in the future, always test child themes with Live Preview (theme customizer) before activating.

Why are my menus displaying incorrectly when I activate new child themes?

…or…

Why is my custom header missing when I activate new child themes?

…or…

Why does my custom background go back to the default when I activate new child themes?

…or…

Why do my theme options disappear when I activate new child themes?

These options are specific to each theme and are saved separately in the database. When you create new child themes, their options are blank.

Many of these options can be copied over to the child theme by checking “Copy Parent Theme Menus, Widgets and other Options” when you generate the child theme files on the Parent/Child tab.

If you want to set different options you can either apply them after you activate the child theme using the theme customizer, or by using the “Live Preview” under Appearance > Themes.

Every theme handles options in its own way. Most often, they will create a set of options and store them in the WordPress database. Some options are specific to the active theme (or child theme), and some are specific to the parent theme only (meaning the child theme CANNOT customize them). You will have to find out from the theme author which are which.

Where is Child Theme Configurator in the Admin?

For most users Child Theme Configurator can be found under “Tools > Child Themes.”

WordPress Multisite (Network) users go to “Network Admin > Themes > Child Themes.”

NOTE: Only users with “install_themes” capability will have access to Child Theme Configurator.

Click the “Help” tab at the top right for a quick reference.

Web フォントを追加するにはどうすればいいですか?

The easiest method is to paste the @import code provided by Google, Font Squirrel or any other Web Font site into the Web Fonts tab. The fonts will then be available to use as a value of the font-family property. Be sure you understand the license for any embedded fonts.

You can also create a secondary stylesheet that contains @font-face rules and import it using the Web Fonts tab.

Why doesn’t the Parent Theme have any styles when I “View Parent CSS”?

Check the appropriate additional stylesheets under “Parse additional stylesheets” on the Parent/Child tab and load the Child Theme again. CTC tries to identify these files by fetching a page from the parent theme, but you may need to set them manually.

Where are the styles? The configurator doesn’t show anything!

All of the styles are loaded dynamically. You must start typing in the text boxes to select styles to edit.
“Base” is the query group that contains styles that are not associated with any particular “At-rule.”

Start by clicking the “Query/Selector” tab and typing “base” in the first box. You can then start typing in the second box to retrieve the style selectors to edit.

Why do the preview tabs return “Stylesheet could not be displayed”?

You have to load a child theme from the Parent/Child tab for the preview to display. This can also happen when your WP_CONTENT_URL is different than $bloginfo(‘site_url’). Ajax cannot make cross-domain requests by default. Check that your Settings > General > “WordPress Address (URL)” value is correct. (Often caused by missing “www” in the domain.)

Can I edit the Child Theme stylesheet manually offline or by using the Editor or do I have to use the Configurator?

You can make any manual customizations you wish to the stylesheet. Just make sure you import the revised stylesheet using the Parent/Child panel or the Configurator will overwrite your customizations the next time you use it. Just follow the steps as usual but select the “Use Existing Child Theme” radio button as the “Child Theme” option. The Configurator will automatically update its internal data from the new stylesheet.

Where are the child theme .php files?

Child Theme Configurator automatically adds a blank functions.php file to the child theme’s directory. You can copy parent theme template files using the Files tab. If you want to create new templates and directories you will have to create/upload them manually via FTP or SSH. Remember that a child theme will automatically inherit the parent theme’s templates unless they also exist in the child theme’s directory. Only copy templates that you intend to customize.

How do I customize a specific color/font style/background?

You can override a specific CSS value globally using the Property/Value tab. See Property/Value, above.

How do I add custom styles that aren’t in the Parent Theme?

You can add queries and selectors using the “Raw CSS” textarea on the Query/Selector tab. See Query/Selector, above.

親テーマからスタイルを削除するにはどうすればいいですか?

You shouldn’t really “remove” a style from the Parent. You can, however, set the property to “inherit,” “none,” or zero (depending on the property). This will negate the Original value. Some experimentation may be necessary.

子テーマからスタイルを削除するにはどうすればいいですか?

Delete the value from the input for the property you wish to remove. Child Theme Configurator only adds overrides for properties that contain values.

How do I set the !important flag?

We always recommend relying on good cascading design over global overrides. To that end, you have ability to change the load order of child theme custom styles by entering a value in the “Order” field. And yes, you can now set properties as important by checking the “!” box next to each input. Please use judiciously.

How do I create cross-browser gradients?

Child Theme Configurator uses a standardized syntax for gradients and only supports two-color gradients without intermediate stops. The inputs consist of origin (e.g., top, left, 135deg, etc.), start color and end color. The browser-specific syntax is generated automatically when you save these values. See Caveats, below, for more information.

How do I make my Theme responsive?

The short answer is to use a responsive Parent Theme. Some common characteristics of responsive design are:

  • Avoiding fixed width and height values. Using max- and min-height values and percentages are ways to make your designs respond to the viewer’s browser size.
  • Combining floats and clears with inline and relative positions allow the elements to adjust gracefully to their container’s width.
  • Showing and hiding content with Javascript.

For more information view “Make a Theme Responsive”:

評価

2022年8月17日
One of the most useful plugins
2022年6月8日
I've complained about this in a support thread and nothing seems to have been done. This is a big problem because you wouldn't expect a plugin doing CHILD THEMES to care about caching the style sheets. So you'll spend hours trying to figure out why your stylesheet changes are not updating......and duh.......its the CACHE from THIS PLUGIN. This is the function that does the damage. add_filter( 'style_loader_src', 'chld_thm_cfg_version', 10, 2 ); function chld_thm_cfg_version( $src, $handle ) { // only filter links for current theme if ( is_child_theme() && strstr( $src, get_stylesheet() ) && ( $ver = wp_get_theme()->Version ) ) $src = preg_replace( "/ver=(.*?)(\&|$)/", 'ver=' . $ver . "$2", $src ); return $src; } THIS IS NOT A NEEDED FEATURE!!! If anyone is needing a work around this seems to do the trick. Add to the child theme functions. I also added . "style.css" because if you are developing with a dev domain with the name of the child theme in the domain (which I often am) then this plugin also ads versions to EVERY SCRIPT instead of just the child css. Adding the extra match criteria makes this hack more likely to only effect the child css. add_filter( 'style_loader_src', 'fix_child_theme_version', 10, 2 ); function fix_child_theme_version( $src, $handle ) { // only filter links for current theme if ( is_child_theme() && strstr( $src, get_stylesheet() . "/style.css" ) && ( $ver = time() ) ) $src = preg_replace( "/ver=(.*?)(\&|$)/", 'ver=' . $ver . "$2", $src ); return $src; } I have an other solution posted in the support thread that works also.
2022年5月28日
The basic CTC must be active for the Pro version to function. Under WPv6, installing or activating the Pro version totally uninstalls the basic version, so they *can't* both be active at the same time. This is true with each of the handful of themes I've tested against. "Support" is totally unresponsive. Money wasted for the Pro upgrade is for naught.
2022年5月19日
Thanks a lot for this plugin.
2022年5月5日
This plugin works exactly as it says it does. The video tutorial is clear and well explained. Thanks so much!
263件のレビューをすべて表示

貢献者と開発者

Child Theme Configurator はオープンソースソフトウェアです。以下の人々がこのプラグインに貢献しています。

貢献者

“Child Theme Configurator” は8ロケールに翻訳されています。 翻訳者のみなさん、翻訳へのご協力ありがとうございます。

“Child Theme Configurator” をあなたの言語に翻訳しましょう。

開発に興味がありますか ?

コードを閲覧するか、SVN リポジトリをチェックするか、開発ログRSS で購読してみてください。

変更履歴

2.5.8

  • Fixed some stylesheet issues

2.5.7

  • Updated for WP 5.6

2.5.6

  • WP 5.5 update removed commonL10n – causing scripts to break – replaced with CTC getxt value.

2.5.5

  • Removed curly brace syntax from substring argument in Packer class.

2.5.4

  • Fixed case where registered styles not showing in queue during analysis.

2.5.3

  • Fixes to stylesheet. Updates to help tabs.

2.5.2

  • Logic to prevent malformed style properties
  • Minor cosmetic changes

2.5.0

  • Preview class now evaluates stylesheet hooks as they fire instead of calling them again to prevent function exists errors.
  • Tested for PHP version 7.1
  • Modified input parser to allow multi-stop background gradients.

2.4.x

  • Analyzer now saves all signals on successful child theme regardless of analysis results.
  • This fixes a bug in some themes where the enqueue hooks were being rewitten incorrectly after adding web fonts.
  • Fixed a serious regression bug created by version 2.4.2.
  • Added call to customizer.php to initialize theme mods prior to analyzing child theme
  • Deferred copy_theme_mods until after child theme analysis. This allows hooks in Preview to initialize custom theme mods
  • Added mpriority (max priority) to CSS object to accommodate multiple irregular stylesheet hooks
  • Restored original (pre 2.4.1) version filter hook style_loader_src to child theme stylesheets to prevent caching
  • Strip closing php tag from functions.php to prevent premature response header
  • Fixed localization issues (thanks @alexclassroom for identifying these)
  • Modified style_loader_src hook to only add timestamp under certain conditions to prevent loading delay for most requests. (thanks @anthony750)
  • Automatically add action parent RTL stylesheet when child theme does not have one.
  • Handle case where parent theme changes queue action incorrectly points to non-existent child theme stylesheet.
  • Correctly copies customizer css to child theme.
  • Fixed PHP 7.3 compatability issue (thanks @forest-skills for identifying this)

2.3.x

  • strip scripts during template scan to prevent false positives
  • check file size during template scan to prevent timeout
  • changed syntax of statement that was being flagged by WP Defender
  • Fixed bug in screenshot copy.
  • Fixed incorrect reference to errors array in UI.
  • Added ability to rename @media query
  • Added height/Width for theme images on Files Tab
  • Added test for RTL in Analyzer
  • Added test cases for WP Rocket and AutOptimize plugins in Analyzer
  • Added redirect for error condition after configurator POST
  • Clarified descriptions for certain Analyzer signal conditions
  • Set priority of child theme css hook to force load after parent
  • Remove pruned selectors from menu

2.2.x

  • Modified preview to include all registered stylesheets in queue
  • Disable Autoptimize in preview
  • Added support for General Sibling Selector (~)
  • Fixed CSS class loading FALSE for dictionaries on fresh install
  • Fixed using wrong nonce for plugin mode preview (Pro)
  • Fixed error thrown when packing negative integers (Pro)
  • Disable Pagespeed in preview
  • Fixed Preview and Analyzer for some child theme configurations by removing nonce requirement
  • Fixed header not being repaired on first pass with “Repair Header” selected
  • Fixed styles being pruned before new “Raw CSS” styles are added
  • Fix bug in parent dependencies
  • Fix bug where stylesheet dependency arrays are not being initialized
  • Add action hook to extend copy theme settings feature
  • Display non active tabs, enable upgrade/register before config data is created
  • Show raw results after Analysis to help debugging
  • Fix javascript not escaping quotes in input fields
  • Restored original ajax preview and added fallback method for cross-domain preview
  • Fix in javascript affecting Pro users
  • Cross domain Parse error
  • Showing “reconfigure” message on new install
  • Manual upgrade Pro from plugin
  • Add pre_option stylesheet and template filters to Preview class
  • Use child theme name on duplicate
  • Ability to force/unforce dependency
  • Identify and handle imported stylesheets, convert to links
  • Fixes related to testing if CTC Pro is installed

2.1.x

  • change packer class to use standard < 5.4 array syntax
  • Loading dictionaries on demand
  • Reversed key/value dictionary structure for huge memory improvement
  • Added packer class to flatten multidim arrays for huge memory improvement
  • Reduced key name lengths throughout
  • Improved data validation on inputs
  • Require minimum Pro version ( Pro users only )
  • Move html output to separate view includes
  • Move theme mod routines to own functions

2.0.x

  • Fix: preview not parsing parent styles correctly when minimized.
  • Fix: cast argument to array in sort functions.
  • Updated Child Theme Configurator language template.
  • Updated child theme preview class to use is_theme_active and other methods to eliminate conflicts with Jetpack and any other plugin that references the customize manager.
  • Updated child theme preview class to send origin headers and run customize_preview_init action along with some other actions.
  • Added logic conditions in preview class to help prevent Analyzer from failing in some cases
  • Enabled theme zip file export for any selected theme independent of theme currently loaded in Configurator
  • Fixed bugs present with servers not running Apache with SuExec
  • Fixed issue with Windows servers that do not return C: with filesystem paths
  • Automatically set priority of enqueue hook based on value from parent theme
  • Made file scan routine more efficient
  • Support for background-image as base64 data
  • Tweaked analyzer signals
  • Updated language template and de_DE files
  • Fix: case where child stylesheet link was not being added resulting in “This child theme does not load a Configurator stylesheet” notice
  • 修正: デバッグモードでの致命的なエラー
  • マイナーなバグ修正
  • New Theme Analyzer automatically checks for issues and determines correct settings
  • Step by step setup of Parent/Child settings
  • Simplified parent stylesheet handling options
  • Option to write new child theme styles to a separate stylesheet
  • Uses WordPress style dependencies to ensure correct child theme stylesheet load order
  • Automatically repairs themes that use outdated stylesheet handling methods
  • Parses parent theme files and only displays templates that can be be overridden by child themes
  • Numerous minor bug fixes

1.7.x

  • Fix: regression bug in 1.7.9 causing new property menu to fail
  • Fix: use nonce when retrieving front-end html to parse default additional stylesheets
  • Refactored classes to make Child Theme Configurator more lightweight on front end
  • Fix: disable autoload on configuration data options
  • Fix: normalize media query and add to menu when added via raw css
  • Fix: Margin and Padding shorthand generated incorrectly.
  • Addressed case where parent or child theme is in subdirectory.
  • Minimized admin CSS.
  • Sanitize child theme slug
  • Remove cascade load order comments from generated CSS
  • Set admin background to prevent theme override
  • Refactored background normalization function to better follow CSS specification.
  • Check child theme exists function case-insensitive.
  • Changed chldthmcfg.init() call to fire on load instead of .ready() to prevent JS conflicts
  • Uses spectrum color picker to support transparency and named colors.
  • Refactored entire system to support fallback values for any property.
  • Fix path when duplicating child theme on first run
  • New Feature: “delete child values” button – easily revert custom styles in child theme stylesheet
  • Will not write child theme stylesheet if error detected in functions.php
  • Fixed minified JS
  • Restored multisite admin menu link under Tools by popular demand
  • Automatically Network enables new child theme on creation
  • Fix for FTP notice – now uses PHP_OS constant to detect win vs nix
  • Added duplicate child theme feature
  • added dismiss option to warnings by popular demand.
  • Changed @import tab to “Web Fonts.” @import statements are automatically converted to enqueued external links.
  • Added “Enqueue both parent and child stylesheets” option to enable child theme overrides without using @import.
  • Added checks for hard-coded link tags in header template to help resolve incorrect stylesheet load order.
  • Fix: “Enqueue child stylesheet” now passes correct value.
  • Fix: hide called before iris init
  • Fix: @import not being written on rebuild/configure
  • Fix: min height on property/value panel
  • Only prune child theme selectors on rename
  • Removed conflicting wistia javascript link
  • New Feature: Enqueue child theme stylesheet option for themes that do not load it.
  • New Feature: Child Theme and Author website, description and tag fields.
  • Fix: Redesigned UI Javascript using jQuery objects for better browser memory management.
  • Fix: Child Theme Stylesheet version is timestamped to force browser reload after changes.

1.6.x

  • Fix: Empty functions file created causing inserted markers to be output to browser.
  • Fix: check for closed PHP tag in functions file prior to inserting markers
  • Fix: undefined constant LILAEAMEDIA_URL
  • Fix: logic to determine whether to display config notice
  • Fix: incorrect path generation and validation on Windows servers
  • Added error handling and notification to prevent jQuery conflicts and out of memory conditions
  • Fix: removed max-height on property/value overlay
  • Added debug option
  • New Feature: Copy selector button for Raw CSS textarea on Query/Selector tab.
  • Fix: Menus rendering incorrectly for RTL locales
  • Fix: Border-top etc. not being written correctly to stylesheet
  • Fix: Refactored ajax semaphore logic and flow
  • New Feature: Better child theme handling for multisite. Moved interface to Themes menu and check for network enabled.
  • Fix: Restrict child theme configurator access to install_themes capability
  • Fix: Preview links to Themes admin if not network enabled to prevent ‘Cheatin, uh?’ error.
  • Fix: only users with “install_themes” capability have access to Child Theme Configurator. This resolves permission issues with both multisite and single site installs. MULTISITE USERS: The Admin HAS MOVED to Network Admin > Themes > Child Themes for better handling for multisite (network) installs.
  • Fix: Regular expression introduced in version 1.6.2 parses selectors incorrectly.
  • Fix: replaced wp_normalize_path with class method to support legacy WP versions
  • Fix: support for multiple layered background images
  • Fix: background:none being parsed into gradient origin parameter
  • Fix: support for data URIs
  • Fix: support for *= and ^= notation in selectors
  • Fix: add check if theme uses hard-wired stylesheet link and alert to use @import instead of link option
  • Fix: conflicts with using jQuery UI from CDN – using local version of 1.11.2 Widget/Menu/Selectmenu instead
  • Fix: using wp-color-picker handle instead of iris as dependency to make sure wpColorPicker() methods are loaded
  • Fix: copy parent theme widgets logic is different when child theme is active
  • New Feature: option to load parent stylesheet using wp_enqueue_style (link), @import or none.
  • Thanks to cmwwebfx and Shapeshifter3 for pushing me on this
  • New Feature: automatically-generated slug and name
  • New Feature: restore from backup and reset options
  • New Feature: backup files to “Child Theme Files” on Files Tab so they can be deleted
  • New Feature: Added new theme chooser select menu with screenshot, theme info and link to live preview.
  • Fix: Admin scripts now only load when CTC page is being viewed.
  • Fix: parent CSS preview to correctly display all parsed parent stylesheets in sequence
  • Fix: Refactored throughout for maintainability

1.5.x

  • New Feature: Load imported stylesheets into the CTC admin so web fonts can be previewed.
  • Set preview swatch to z-index -1 to prevent it from covering up the controls
  • Spread config data across multiple option records to prevent out of memory errors with large stylesheets.
  • Do not automatically select Bootstrap CSS files as additional stylesheets to (greatly) reduce overhead.
  • Add jQuery UI styles that are no longer being loaded by default in the WP admin (autoselect menus).
  • Fixed a bug in the way zero values are handled that was breaking css output in certain situations
  • Added regex filter for non-printable (e.g., null) characters in input strings
  • Fixed a bug introduced in v1.5.2(.1) that copied all of the parent styles to the child theme stylesheet. This should only be an issue for ‘background-image’ styles that reference images in the parent theme and do not have child theme overrides.
  • Rolled back changes to the javascript controller that introduced a number of type errors.
  • Tweaked preview ajax call to handle ssl.
  • Automatically set additional stylesheets to parse based on parent theme links in head.
  • Render parent CSS including additional stylesheets
  • Added copy option to Parent/Child tab to assign menu locations, sidebars/widgets, custom header, background, and other options to new Child Themes.
  • Refactored CTC to use the WP_Filesystem API.
  • Non suExec configurations will now require user credentials to add, remove or update Child Theme files.
  • Added the ability for you to make the files writable while editing and then make them read-only when you are done.
  • You can also set your credentials in wp-config.php: https://codex.wordpress.org/Editing_wp-config.php#WordPress_Upgrade_Constants

1.4.x

  • Removed backreference in main CSS parser regex due to high memory usage.
  • Fixed uninitialized variable in files UI.
  • Feature: export child themes as zip archive
  • Added transform to list of vendor properties
  • Bug fixed: parser not loading multiple instances of same @media rulesets
  • Refactored uploader to use wp core functions for compatibility and security
  • Increased CHLD_THM_CFG_MAX_RECURSE_LOOPS to 1000 to accommodate complex parent frameworks
  • Fix: javascript bug
  • Fix: regression bug – sanitizing broke raw input selectors
  • Fix: escape quotes in text inputs. This has bugged me for a while now.
  • Fix: Escape backslash for octal content values. Thanks Laurent for reporting this.
  • Fix: Normalize colors to lowercase and short form when possible to prevent duplicate entries in the data
  • Refactored the way CTC caches updates and returns them to the UI controller to reduce memory consumption.
  • Prevent out of memory fatals when generating new child themes.
  • Changed “Scan Parent for Additional Stylesheets” to individual checkbox options for each file with a toggle to show/hide in the Parent/Child tab.
  • Added automatic update of form when Parent Theme is changed.
  • Pre-populate Parent/Child form when parent slug is passed to CTC options.
  • updated parser to match selectors containing parentheses and empty media rulesets
  • Tweaked the Files tab options and added check for DISALLOW_FILE_EDIT
  • Removed automatic @import rules for additional stylesheets that are loaded.
  • Fixed bug caused by new jQuery .css function handling of empty css values (preview swatch).
  • New Feature: Theme Files tab:
  • Copy parent templates to child themes to be edited using the Theme Editor.
  • 子テーマテンプレートを削除します。
  • 子テーマ画像をアップロードします。
  • 子テーマ画像を削除します。
  • 子テーマのスクリーンショットをアップロードします。

1.3.x

  • Fixes a bug with the way the @import data is stored that threw errors on php 5.3 and corrupted v1.3.2 @import data.
  • New Feature: option to scan parent theme for additional stylesheets. This allows CTC to be used with themes such as “Responsive” by CyberChimps.
  • New Feature: automatically copies parent theme screenshot to child.
  • Fixed unquoted regex pattern in file path security check function. Thanks to buzcuz for reporting this.
  • Updated help tab content. Added additional sanitization of source and target file paths.
  • Changed CSS preview to retrieve directly from WordPress Admin instead of remote http GET to prevent caching issues.
  • Added loading icon for CSS preview.
  • Fixed JS type error on backup toggle.
  • Improved extensibility throughout.

1.2.x

  • Replace PHP short tags with standard codes.
  • New Features: You can now rename selectors in place from the Query/Selector panel. Made stylesheet backup optional. Bugs fixed: Incorrect parsing of background position when ‘0’, fixed type error when background image url value is removed.
  • Bugs fixed: “star hack” properties no longer throwing js error. Important flag now works on borders and gradients.
  • New features: Link to Query/Selector tab from specific Property/Value selector, new property focus on adding new property. Bugs fixed: clear Query/Selector inputs when loaded selector is empty, use latest min.js script.

1.1.x

  • Added check for writability before attempting to create child theme files to avoid fatal error on servers not running suEXEC. Fixed a bug in the ctc_update_cache function that was throwing a fatal JS error when new media queries were saved via the Raw CSS input. Configurator now adds functions.php file to child theme when it does not exist.
  • Added reorder sequence and important flag functionality. Fixed bug where multiple inputs with same selector/property combo were assigned the same id. Fixed bug in the shorthand encoding routine.
  • Added tutorial video to help tabs.
  • Added call to reset_updates() before update_option() to prevent serialization errors.
  • Query/Selector panel now defaults to ‘base’
  • Fixed bug causing background-image with full urls (http://) to be parsed as gradients
  • Fixed bug causing property menu to throw error when selector has no properties
  • Fixed sort bug in shorthand parser that was returning properties in wrong order
  • Fixed bug that assumed lowercase only for theme slugs. (Thanks to timk)
  • Fixed update redirect to execute on first run
  • Small bug fix to javascript (casting number to string)
  • Fixed major bug where inputs containing ‘0’ were being ignored
  • Removed “no leading digits” requirement for theme slug
  • Change query sort function to keep parent order of queries without device width rules
  • Fixed gettext calls to use static namespace parameter
  • Auto populate child theme inputs when existing theme is selected
  • Correctly remove border when values are blanked
  • Fixed duplicate “new property” bug on Query/Selector panel
  • added timestamp to backup file
  • Added encode_shorthand function to recombine margin/padding values when all 4 sides are present
  • Corrected parsing for certain backgrounds and gradients (e.g., supports hsla color syntax)
  • Handle empty selectors
  • Ajax load for menus and updates
  • Clean up Parent/Child form UI and validation
  • Streamlined UI overall

1.0.0

  • 最初のリリース。