(→PageLines Customize plugin vs. the Custom Code setting) |
(→PageLines Customize plugin vs. the Base Theme) |
||
| Line 16: | Line 16: | ||
If neither of those scenarios apply, it's really up to your preference on which method you choose. | If neither of those scenarios apply, it's really up to your preference on which method you choose. | ||
| + | |||
| + | If for some reason you are using both the PageLines Customize plugin and the Base Theme, any custom code entered in the PageLines Customize plugin will take priority over the same code entered in the Base Theme. | ||
==PageLines Customize plugin vs. the Custom Code setting== | ==PageLines Customize plugin vs. the Custom Code setting== | ||
The PageLines Customize plugin allows you to make any change you need to without editing the core framework. This way when the PageLines 2.0 framework gets updated, you won’t have to worry about losing any custom changes you’ve made. Many of you upgrading from PlatformPro will remember using the Base child theme to add your customization. In PageLines 2.0, you can still use the Base Theme , but you also have the option of using the PageLines Customize plugin. It acts as a child theme.
Contents |
There are two main files in the PageLines Customize plugin for editing: style.css & functions.php.
Editing the style.css file, you can apply custom CSS to your theme.
Editing the functions.php file, that you can add pretty much anything else.
Many people have asked "What's the difference between the PageLines Customize plugin and the Base Theme?" or "Why should I choose one method over the other?" Both methods contain their own style.css & functions.php files that you can edit & add your own customization. Either way you can customize your site while keeping your files intact when you apply a core update.
The advantage of the Child Theme is that you can customize PageLines 2.0 core sections without losing any edits when you update the core. The disadvantage is that you can't then install a 3rd party child theme through the store and update it, as you will lose your edits.
The advantage of the PageLines Customize Plugin is that you can update the core files and a 3rd party child theme and still keep your edits. The disadvantage is that sections folder isn't scanned in to the plugin. So any changes you make to the core sections will be lost when updating.
If neither of those scenarios apply, it's really up to your preference on which method you choose.
If for some reason you are using both the PageLines Customize plugin and the Base Theme, any custom code entered in the PageLines Customize plugin will take priority over the same code entered in the Base Theme.
You can also add custom CSS via the Custom Code tab located in the PageLines=>Settings menu. The Custom Code tab is a simple quick way to add custom styles to your current site design, however it is not necessarily considered the preferred method. Using the PageLines Customize plugin to make your CSS changes is preferred for several reasons:
Any code changes you enter into style.css via the PageLines Customize Plugin will override the Custom Code settings that contain the same changes.
For more information on CSS & how it relates to PageLines 2.0, click on CSS Customization
The PageLines Customize plugin is available for free in the PageLines Store.
From your WordPress Administration Panel:
You will now be able to edit the new style.css & functions.php. They are located in \wp-content\plugins\pagelines-customize
If you prefer to edit these files through Wordpress instead of a text editor, remember that "PageLines Customize" is a plugin, and can be accessed via:
Dashboard=>Plugins=>Editor