forked from isaw/isaw.web
-
Notifications
You must be signed in to change notification settings - Fork 3
/
PROD_SNAPSHOT.txt
127 lines (99 loc) · 5.94 KB
/
PROD_SNAPSHOT.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
Moving a production snapshot to development server
==================================================
Steps to follow for testing all code for upgrade to July 2015 theme, with a snapshot of the production database.
On production server
--------------------
- Copy Data.fs to development server.
- tar/gzip blobstorage and copy to development server.
On development server
---------------------
**Jazkarta steps:**
- From ZMI, export isaw-home and home-slides to somewhere on the file system
where you can get them back later (irrelevant if you don't have an existing
database that's been customized with same, e.g. on a local dev environment).
- Change directory to /srv/isaw.web.
- Stop all supervisor processes (bin/supervisorctl stop all).
- Copy old Data.fs (var/filestorage/Data.fs) to Data.fs.old.
- Move blobstorage (var/blobstorage) to blobstorage.old.
- Move Data.fs from production to filestorage directory.
- Move blobstorage.tgz from production to var directory and untar/ungzip.
- Make sure user.group for Data.fs and blobstorage is set to plone.jazkarta.
- Run buildout (bin/buildout -N -c production.cfg).
- Start supervisor processes (bin/supervisorctl start all).
- Make sure there are no customizations in /isaw/portal_skins/custom.
- Browse to /isaw/prefs_install_products_form.
- Make sure collective.easyslider is installed.
- From the same place uninstall Dropdown Menu and collective.navigationtoggle.
- From the same place, run upgrade steps for isaw.policy and isaw.theme.
- From ZMI, remove isaw-home. Import isaw-home and home-slides from FS.
- Browse to /isaw/events/selectViewTemplate?templateId=event-listing
- Browse to /isaw/news and unblock content portlets in the container.
**ISAW steps:**
*Turn off email notifications until migration complete*
- Browse to /@@rules-controlpanel
- Check the checkbox labeled "Disable globally"
*Fix up secondary navigation*
- Browse to /people/@@manage-portlets and make the following portlet changes:
+ remove navigation portlet from right portlet slot
+ add navigation portlet to left portlet slot with the following settings:
+ title: [[leave blank]]
+ root node: "People /people"
+ include top: YES
+ only show...: NO
+ start level: 0
+ nav tree depth: 0
- Do the same for the following sections (root nodes mutatis mutandis):
+ /about
+ /library
+ /graduate-studies
+ /visiting-scholars
+ /support-isaw
*Fix up events listing*
NB: past events have speaker and affiliation information in the summary (description) field instead of in the fields designated for such content. This will be a later manual cleanup step **if** we want archived events to match new formatting.
You will probably want to create and publish (temporarily) a couple of test events in the /events folder in order to verify that the collection we set up next actually works. Recommend you set one with start date == current date and another sometime in the future.
- Browse to /events and add a Collection "Event Home" with criteria set to:
- Type: Event
- Location: absolute path, /events
- Event start date: After Today
- Review State: Published Externally
- Sort on: Event start date
- Set display on collection to Event Listing
- Use "Manage Portlets" link to add a calendar portlet to the right column (you may see two calendar portlets as a result, because it's also presently set on the parent folder)
- Set state of "Event Home" to published (submit for publication -> publish)
- Browse to /events and use "Manage Portlets" to disable the calendar portlet in the right column.
- Return to /events and use the Display menu to "Select content item as default view" and select "Event Home"
- Delete any test events you created
*Fix up people listings*
- Browse to /people/faculty and change "Display" to "People listing"
- Do the same for:
+ /people/staff
+ /people/visiting-research-scholars
+ /people/students
+ /people/research-associates/
+ each of the following subfolders under /people/alumni:
* Scholars 2013-2014
* Scholars 2012-2013
* Scholars 2011-2012
* Scholars 2010-2011
- Make sure the other subfolders under /people/alumni are set to "display" -> "folder_listing"
*Fix up blog listings*
- Browse to /news
+ Select "display" --> "Set content item as default view" and then select "ISAW News Blog" from the listing (it is a collection with the id "collector") -- may already be set
+ Select "display" --> "Item display" --> "Tiled listing"
+ Open each of the first two or three pages full of news items listed and crop the image for "tiled"
- Browse to /library/blog
+ Select "display" --> "Set content item as default view" and then select "ISAW Library Blog" from the listing (it is a collection with the id "collector") -- may already be set
+ Select "display" --> "Item display" --> "Tiled listing"
+ Open each of the first two or three pages full of news items listed and crop the image for "tiled"
*Check main navigation*
- Secondary (top bar) should be: "About ISAW", "People", "Library", "Resources & Publications", "Research", "News", [[search icon]]
- Primary (secondary bar) should be: "Graduate Studies", "Visiting Scholars", "Events", "Exhibitions"
- Footer should include contact info on the left under NYU logo, hours in the center (corrected), and "Support ISAW", "Jobs at ISAW" and "Login" on the right.
*check workflow and states for /guide and /about/employee*
- Should have placeful workflow configured to "intranet" already
*Update home page overlay text*
- Grab and style appropriate bits and pieces from news (for the second slide) and events (for the third slide), if any so that we are not out of date on the home page
*GO FULLY LIVE: Turn on email notifications now that migration is complete*
NB: This the very final step. After this, senior leadership will start getting email notifications again on item submit etc.
- Browse to /@@rules-controlpanel
- Unheck the checkbox labeled "Disable globally"