kongondo

I had a stab at this over the weekend (during my free time, ahem). I'm finalising it now. Hope to post alpha(-ish) version tonight. I'll start a separate thread.

I'm looking forward to seeing it in alpha! ?. Most of it (especially the backend) is already planned (going through several iterations) and all that is remaining is the relevant code.

There is one actually, sort of. Look at the 'images' field in a multilingual setup. As you are aware, for truly (I use this word reservedly) multilingual fields, each language has to have its own column. That makes it easy to search the columns in the language you want. However, in your case, since you want only one column to have multilingual features, you have two choices ( + a 3rd not very good one): Go the route of images fields. In a multilingual setup, the description column of an image field holds each languages' value, saved as JSON. E.g. {"0":"We're gonna need a bigger terminal.","1012":"Wir brauchen einen größeren Terminal.","1013":"Me tarvitsemme isomman päätteen."}. The index of the values are the language ID. In this case, 0= English, 1012=German and 1013=Finnish.The trade off here is searching in one language is limited. Change your database design pattern. No need to cram things in if they don't fit ?. Let your subject be its own multilingual field and let your other single value data live in their own non-multilingual field. Nothing wrong with that. I mention this 3rd option hesitantly. Stick with one field as your are doing but for your data (subject) column create a lookup table for other languages. I am no DB guru but the little I know tells me this 3rd option is not a good design at all.

I'm not really getting what the question is, although I haven't looked at your code in full. Are you sure about this? What do you mean by multi-language fields? Maybe install the multi-lingual site profile and see how things work? For instance, the field images works fine as a multi-language field and it is a multi-value field. I think I'm just not getting the question. if you Fieldtype is meant to store multiple values for the same page (meaning multiple rows in its database table for the same field on the same page) , then this code is not correct: In that case, you'll need to extend FieldtypeMulti. However, I may have misunderstood what you mean by multiple values. For instance, if you meant multiple database columns on a single db row, that's something different.

I'll have a look, cheers! Btw, for some reason I still thought Tracy does not support debugging in a modal?! I only noticed the setting yesterday when we were trying to help @JoshoB with the asmSelect problem! How this could have helped me recently, with VPS (lots of modal interaction)! I feel foolish ?. Thanks for Tracy again, @adrian!

Hooray! Any tip how to set this up for a linux box? Ta!

How helpful of them ? ?.

Excellent! It would be good to know what changed exactly...to help the next guy and all that ?.

In dev JS console.

We're trying to install Tracy but getting hit with 500 errors, so Tracy bar not loading. It could be nginx related, we think. Thoughts, anyone? Ta!

As we await @JoshoB's response, I can report that asm is not working site-wide, not even in /setup/template/ (list of fields in template in Basics Tab). I'm baffled by this one.

I'd say it's time for a fresh pair of eyes to have a look. If you could grant one of us a temporary access if possible...??

A couple more things: Does asm work on other page fields? Does asm work on other templates? Does switching to another inputfield (e.g. autocomplete) work? What about switching back to asm? Clearing cache? I'm out of ideas save for having a quick look at it if that's possible.

What Admin Theme are you using?

Hmm, that's strange. Does JavaScript work OK in other pages? E.g. CKEditor working fine?

I would have placed my bet on JavaScript as well. A couple of things to consider: Check for JavaScript errors and missing JavaScript files Did the page reference field settings change? (just fishing with this one :-)) TracyDebugger: install and debug with this great tool Any errors if config->debug is true?

Yes. This is how I've been doing it in my modules. Typing \ProcessWire\...every time is a pain I want to avoid ?.

A PHP oddity, I'm guessing ?.

Isn't this (and similar) superfluous? You are already in the ProcessWire namespace.

Not wanting to go OT here, if this is the case, I'm wondering if this is better off as a separate/standalone module (so, new topic ?) from what is described in the first post of this thread? Edit: Hmm..Or maybe what you describe falls within the remit of what the module in this thread is about? I think am just confusing myself now. Anyway, let me know...

Seems pretty straightforward especially if capturing flow of conversation is not important. If that is a requirement, maybe Comments module (or borrowing from it) would cut it? Just wondering out loud...

Not exactly the same, but check out Cobalt2 theme.

So, how's everyone? Version Control I finally started using VSC inbuilt version control, yipee! Thanks to @bernhard for the nudge. I got here after struggling to get a decent SourceTree replacement for Linux. Side Bar I've been wanting to move the side bar to the right but never got round to it. Today, I finally did it...and I like it! Any right side bar people here ??

Working fine here on PHP 7.2. However, I'd still do what @dragan suggested. Upgrades have a tendency to go awry :-). Also note that despite your best efforts to test locally, things may not always work as they should in your remote install. Often times it is because your host changed a setting in the server during the upgrade and worse, didn't even tell you about it! You'd be left in the dark blaming PHP 7 or some other module or ProcessWire only to realise a couple of emails later that actually, none of these were to blame ? and the culprit was a seemingly unrelated server setting. Hopefully, this doesn't happen to you...I'm not scaremongering; just thought you should be aware ?.

Update: Menu Builder Version 0.2.5. Just a quick maintenance update. Changelog Fixed a minor bug where we had to check if a variable was an array first before "counting" it. Removed a leftover debugging statement from the code (an echo of all things! Not even a bd()!!) ?.