Treehouse Meeting #9

Please feel free to continue the conversation by posting comments below.

Meeting Discussion included:

  • Launch of Treehouse CODE snippets
  • Discuss first major Treehouse collaboration project
  • and lots of other chit-chat…

Mentioned resources:
https://shopify.github.io/liquid/basics/introduction/
https://www.mailerlite.com/
https://www.emailtooltester.com/en/blog/email-deliverability-july-2019/
https://hail.to/whangaparaoa-school/publication/9zcblWF
https://google-webfonts-helper.herokuapp.com/fonts
https://www.treehousecommunity.co/code

Also, a quick poll:

What’s your primary website design tool?

  • Photoshop
  • Illustrator
  • XD
  • Figma
  • Affinity Designer
  • Affinity Photo
  • Templates
  • Outsourced
  • Other

0 voters

2 Likes

All of those links need cleaning, they link to a youtube url and then forward out. :slight_smile:

Thanks for spotting that James. I’ve cleaned them all now.

1 Like

Thanks @Adam.Wilson! Very good idea to do a follow-up like that here.

Do we have an Advanced URL Manager yet?

October 16th I believe is the new date for Advanced ULR Manager as they want to rehash this due to some issues in the first version.

1 Like

Hello community,

Here are the answers to some points mentioned at the meeting:

1 ) "Having to use liquid in Treepl vs BC’s {modules} syntax issue"
Treepl CMS provides toolboxes for layout and content textarea that allows you to retrieve desired component or property output just by several clicks, similar to what you have in BC.
Can you provide more details regarding issues caused by using Treepl’s component as alternatives for {module_} tags and property output “{{this[‘propName’]}}” instead of {tag_prop name} bc tags?

2 ) "Component type module_category_list issue"
@TimL
Can you provide a site where you hit an issue with the categories component that you mentioned at the meeting and describe what category specifically is broken?

3 ) "Contact CRM migration"
Either migration through “BC to Treepl” app or importing through the admin will never allow you to set passwords to that CRM contact because it is not GDPR compliant and basically not secure (only confirmed ownership of an email account allows to set a password to the account based on that email).

Both flows will allow you to migrate all contact data (except the password) including cases, orders, event subscriptions, and subscriptions to secure zones.

But in order to restore access to the site for any CRM user the flows below should be applied:

  • a user goes through restore password flow,
  • a user retrieves restore password email
  • a user follows the link and sets his new or old password and retrieves access to the account (where he can find migrated data, such as cases, orders, access to some secure zones etc).

Thus you need to find the flow that will fit you most to trigger your CRM users to go through restore password flow.
It may be an email blast to all users asking them to restore their passwords or you can go through each user in admin and click on password restoration icon for them.
It’s up to you.

3 Likes

It’s AURLM1’s big day! :smiley:

Hello @vlad.z, thanks for your reply. Regarding the use of Liquid as a requirement for Treepl which came up as some kind of a little challenge for new partners in the Treehouse meeting: I personally think that in general Treepl can be set up for regulare sites without the need to code Liquid. There are some special scenarios in which a conversion from BC without coding Liquid is difficult (e.g. if a BC site has a dedicated mobile template and you would use the request object to work around that) but that’s what the code section on the Treehouse site is good for :-).

The issues we had with the component module for category lists was more related to the scenario we use it for: We needed the categories listet by that module to be passed along as a url parameter to another page. We used the name property for that, until we found out that name only holds the child category when using multi-level categories and that we need the parent and child category if we want to filter e.g. a module output. We ended up using the url property (which in a way holds both, parent and child) but a property parent for this module would be nice.