• 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

ed:
better to have a subdomain

there an asset sync from stg to production.


alex:
when posting photos - unless it's at full size,
it becomes shrinked

when posting audio clips - player controls
get jumbled - player ruben installed
!!importannt



recipes plugin - receipes doesn't show 
under all posts - not big issue.

theme is based off of uncode-


golive:
- converts from wprs.rosettastone.com to rosettastone.com/

golive changes wprs to www in the domain
why doesnt it happen to christoph.

Christoph - fix ruben code? if too much work, fresh install uncode theme

- Permission to update plugins in prod and stg.(ed)

- pixels need to be installed

- WP is bad in embedding ig posts (going to ig and getting embded code)

- blog is using new logo that hasnt been approved


floating device must stay present




livechat
ec



the themes are checked into source control ..  The typical workflow is to enable the plugin to staging, use a script to commit it to git and push to production...
basically you get a shell on stgwprs1 and run

deploy@stgwprs1:/usr/local/scripts/wordpress$ ./sync-helper.sh

wordpress installation in stg live under a git repository,
so when installing plugins, code becomes dirty and needs to be
added and committed - then in production, pull changes?