Skip to content
Discussion options

You must be logged in to vote

Hi, are you using the latest release: 2.1.1? The 2.1.0 did had this issue and was fixed with 2.1.1.

Replies: 1 comment 4 replies

Comment options

You must be logged in to vote
4 replies
@Rudiberto
Comment options

@KatjaGlassConsulting
Comment options

@Rudiberto
Comment options

@KatjaGlassConsulting
Comment options

Answer selected by Rudiberto
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants