Darren Doyle

Here's a workaround for having a global SCSS file (which is why I care about the aliases to begin with) that worked for me based off of the comment by...

Admittedly, there are a _lot_ of chunks that shouldn't be translated, though. Perhaps use a custom, user-settable category/categories to identify chunks that need translation. Example: user creates categories "Translatable" and...

First off, I would like to say that I do acknowledge that this is a lower-priority request compared to some of the others. Having said that, let me address some...

Of course, in MODX there are 100 ways to skin a cat. Reasons not to use the Lexicon (for me): - It's just inconsistent management of content (bad UX) -...

I think part of this back and forth gets to the differences in how we are using MODX. You don't want to put content in chunks and don't think it...

> And just because I am curious: Do you grant your Editors the rights to edit Chunks? If not: What happens if a Editor wants to change a String in...

But the words / content isn't going to be inside code. It will just be words, sentences, and paragraphs inside a chunk. If it needs to be _styled_ content (aka,...

I just corrected this bug on my own install... pretty easy fix really... On the plugin on line 95ish you are doing an intersect of the submitted language array (sorted...

What is your environment (Browser, OS, language settings, etc.)? (I'm sure that will help) I'm on a Mac here. Used Chrome to test. Set up English (en) and Spanish (es)...

I think I may have tracked this bug down... or at least gotten on the right track. After doing a lot of tracing through stuff, this is what I've found:...