How to Migrate from Platform to PageLines - Revision history

Henry at 00:41, 26 June 2012

2012-06-26T00:41:35Z

Henry at 00:41, 26 June 2012

2012-06-26T00:41:06Z

MrFent at 08:03, 29 January 2012

2012-01-29T08:03:56Z

MrFent at 08:01, 29 January 2012

2012-01-29T08:01:24Z

MrFent at 08:00, 29 January 2012

2012-01-29T08:00:53Z

MrFent at 04:01, 27 January 2012

2012-01-27T04:01:46Z

MrFent at 19:20, 26 January 2012

2012-01-26T19:20:59Z

MrFent at 15:37, 26 January 2012

2012-01-26T15:37:54Z

MrFent: Created page with "PageLines 2.0 is a major new release to the previous Platform Pro product. When upgrading from Platform Pro there are some things to consider. *'''Always back up your databas..."

2012-01-26T15:33:04Z

Created page with "PageLines 2.0 is a major new release to the previous Platform Pro product. When upgrading from Platform Pro there are some things to consider. *'''Always back up your databas..."

New page

PageLines 2.0 is a major new release to the previous Platform Pro product. When upgrading from Platform Pro there are some things to consider.

*'''Always back up your database before doing an upgrade'''
* All data will be untouched, your posts, pages and content will all remain intact in the database.
* Default option settings have changed in 2.0 so any default options set in Platform Pro will be removed in the upgrade
* Section control has changed in 2.0 to be more flexible and as a result these settings will need to be reset after the upgrade
* PageLines 2.0 has been upgraded to incorporate HTML 5 and some of the html structure has changed. Sites with heavy CSS customizations will need to make changes to their CSS after the move.
* In 2.0, there is no longer a Base child theme that handles custom code. Instead, use the [[Glossary#PageLines Customize Plugin|PageLines Customize Plugin.]] You can still use the [[How to Use the Custom Code Settings|Custom Code Settings]] to make changes to CSS as an alternate method.

@@ Line 1: / Line 1: @@
 <html>
-<div class="page-header zmt zmb"><h1>How to Upgrade from Platform to Framework</h1></div><html>
+<div class="page-header zmt zmb">
 First, check out [[Is it Safe to Upgrade?]] if you have any concerns or questions. Once you decide to "make the switch," follow these suggestions:
 # Back up your database

← Older revision		Revision as of 00:41, 26 June 2012
Line 1:		Line 1:
		+	<html>
		+	<div class="page-header zmt zmb"><h1>How to Upgrade from Platform to Framework</h1></div><html>
	First, check out [[Is it Safe to Upgrade?]] if you have any concerns or questions. Once you decide to "make the switch," follow these suggestions:		First, check out [[Is it Safe to Upgrade?]] if you have any concerns or questions. Once you decide to "make the switch," follow these suggestions:
	# Back up your database		# Back up your database

← Older revision		Revision as of 08:03, 29 January 2012
Line 1:		Line 1:
		+	First, check out [[Is it Safe to Upgrade?]] if you have any concerns or questions. Once you decide to "make the switch," follow these suggestions:
	# Back up your database		# Back up your database
	# Copy any custom CSS, functions, sections, etc into a text editor		# Copy any custom CSS, functions, sections, etc into a text editor

@@ Line 6: / Line 6: @@
 # Move all of your widgets back to the desired locations (Appearance -> Widgets)
 # Visit each tab of the PageLines menu and adjust the settings to your liking (don't forget to enter your account info too!)
-# Paste your custom CSS, functions, etc that you copied earlier back into your site. There are three ways to do this:
+# Paste your custom CSS, functions, etc that you copied earlier back into your site. <br />There are three ways to do this:
 #* [[How to Use the PageLines Customize Plugin|PageLines Customize Plugin]]
 #* [[How to Use the Base Theme|Base Theme]]
 #* [[How to Use the Custom Code Settings|Custom Code Settings]]

@@ Line 1: / Line 1: @@
-So far there have been no ‘major’ issues for people upgrading their sites to the new PageLines Framework.
+# Back up your database
-The average time to make the switch ranges from '''five minutes to a few hours depending on the level of customization that was previously applied to the website.'''
+# Copy any custom CSS, functions, sections, etc into a text editor
-That said, there are still a few things you should be aware of when upgrading. They are…
+# Move all of your widgets to the "inactive" area (Appearance -> Widgets)
+# [http://www.pagelines.com/wiki/index.php?title=How_to_Install_PageLines Follow these instructions] on how to install & activate PageLines
-'''The Good News → “Non-Destructive Upgrade”''' – Because we knew there would be some issues with upgrading the framework, we worked to make sure the upgrade was “non-destructive.” This means that if you try and upgrade and don’t like what you see, or don’t have time to fix a couple issues, you can always revert to PlatformPro. Easy.
+# Reestablish your Wordpress menus (Appearance -> Menus) and save
+# Move all of your widgets back to the desired locations (Appearance -> Widgets)
-'''CSS Changes''' – In developing the framework, it’s very difficult to prevent CSS changes from happening once in a while on upgrade. With PageLines there were a few changes to markup (e.g. using ‘section’ as opposed to ‘div’ elements in some cases…) This has caused a couple issues.
+# Visit each tab of the PageLines menu and adjust the settings to your liking (don't forget to enter your account info too!)
-Solution The minor CSS problems can be fixed easily by correcting your custom css rules to align with the new elements.
+# Paste your custom CSS, functions, etc that you copied earlier back into your site. There are three ways to do this:
+#* [[How to Use the PageLines Customize Plugin|PageLines Customize Plugin]]
-'''Section Control''' – To improve the functionality of Section Control, we had to change the way its data was stored in the DB. Therefore section control options get wiped on upgrade.
+#* [[How to Use the Base Theme|Base Theme]]
-Solution Simply set these options again and you are good to go.
+#* [[How to Use the Custom Code Settings|Custom Code Settings]]
-−
-'''Global vs. Meta Options''' – To give you more control over your pages, we moved many section options to the MetaPanel. This means that the global options are no longer relevant.
-Solution Simply setup meta options for customized sections across your site; you can also use the new default option handling system.
-−
-The PageLines Framework is a major new release to the previous PlatformPro product. When upgrading from Platform Pro there are some things to consider.
-−
-*'''Always back up your database before doing an upgrade'''
-* All data will be untouched; your posts, pages and content will all remain intact in the database.
-* Default option settings have changed in PageLines so any default options set in PlatformPro will be removed in the upgrade
-* Section control has changed in PageLines to be more flexible and as a result these settings will need to be reset after the upgrade
-* PageLines has been upgraded to incorporate HTML 5 and some of the html structure has changed. Sites with heavy CSS customizations will need to make changes to their CSS after the move.
-* In 2.0, there is no longer a Base child theme that handles custom code. Instead, use the [[Glossary#PageLines Customize Plugin|PageLines Customize Plugin.]] You can still use the [[How to Use the Custom Code Settings|Custom Code Settings]] to make changes to CSS as an alternate method.
-−
-Upgrading and Issues

← Older revision		Revision as of 19:20, 26 January 2012
Line 7:		Line 7:
	* PageLines 2.0 has been upgraded to incorporate HTML 5 and some of the html structure has changed. Sites with heavy CSS customizations will need to make changes to their CSS after the move.		* PageLines 2.0 has been upgraded to incorporate HTML 5 and some of the html structure has changed. Sites with heavy CSS customizations will need to make changes to their CSS after the move.
	* In 2.0, there is no longer a Base child theme that handles custom code. Instead, use the [[Glossary#PageLines Customize Plugin\|PageLines Customize Plugin.]] You can still use the [[How to Use the Custom Code Settings\|Custom Code Settings]] to make changes to CSS as an alternate method.		* In 2.0, there is no longer a Base child theme that handles custom code. Instead, use the [[Glossary#PageLines Customize Plugin\|PageLines Customize Plugin.]] You can still use the [[How to Use the Custom Code Settings\|Custom Code Settings]] to make changes to CSS as an alternate method.
		+
		+	Upgrading and Issues
		+
		+	Aside from a couple communication problems on our part, so far there have been no ‘major’ issues for people upgrading their sites to 2.0 (fingers crossed!).
		+	The average time to make the switch ranges from 5 minutes to a few hours depending on the level of customization that was previously applied to the website.
		+	That said, there are still a few things you should be aware of when upgrading. They are…
		+
		+	The Good News → “Non-Destructive Upgrade” – Because we knew there would be some issues with upgrading the framework, we worked to make sure the upgrade was “non-destructive.” This means that if you try and upgrade and don’t like what you see, or don’t have time to fix a couple issues, you can always revert to PlatformPro. Easy.
		+
		+	CSS Changes – In developing the framework, it’s very difficult to prevent CSS changes from happening once and a while on upgrade. With 2.0 there were a few changes to markup (e.g. using ‘section’ as opposed to ‘div’ elements in some cases…) This has caused a couple issues.
		+	Solution The minor CSS problems can be fixed easily by correcting your custom css rules to align with the new elements.
		+
		+	Section Control – To improve the functionality of Section Control, we had to change the way its data was stored in the DB. Therefore section control options get wiped on upgrade.
		+	Solution Simply set these options again and you are good to go.
		+
		+	Global vs. Meta Options – To give you more control over your pages, we moved many section options to the MetaPanel. This means that the global options are no longer relevant.
		+	Solution Simply setup meta options for customized sections across your site; a new default option handling system is coming with version 2.1.

@@ Line 1: / Line 1: @@
-PageLines 2.0 is a major new release to the previous Platform Pro product. When upgrading from Platform Pro there are some things to consider.
+The PageLines Framework is a major new release to the previous PlatformPro product. When upgrading from Platform Pro there are some things to consider.
 *'''Always back up your database before doing an upgrade'''
-* All data will be untouched, your posts, pages and content will all remain intact in the database.
+* All data will be untouched; your posts, pages and content will all remain intact in the database.
-* Default option settings have changed in 2.0 so any default options set in Platform Pro will be removed in the upgrade
+* Default option settings have changed in 2.0 so any default options set in PlatformPro will be removed in the upgrade
 * Section control has changed in 2.0 to be more flexible and as a result these settings will need to be reset after the upgrade
 * PageLines 2.0 has been upgraded to incorporate HTML 5 and some of the html structure has changed. Sites with heavy CSS customizations will need to make changes to their CSS after the move.
 * In 2.0, there is no longer a Base child theme that handles custom code. Instead, use the [[Glossary#PageLines Customize Plugin|PageLines Customize Plugin.]] You can still use the [[How to Use the Custom Code Settings|Custom Code Settings]] to make changes to CSS as an alternate method.