kongondo

Yes Bad idea, IMHO. I've never heard anything good come out of letting clients dabble in the HTML. Not sure if PageTable Extended can help in your case. I don't think there's any module that will allow you to repeat fields 'unevenly', i.e. in repeater 1, let's repeat title and headline but in repeater 2, let's only body field, etc. Maybe you can use repeaters with some showIf? or inject your own JavaScript and markup to toggle visibility of fields as per need? E.g. tick a box for use this field...will display the field for editing....Just thinking out loud here. It might seem like the easy way out, but honestly, will you remember what these mean when you need to edit something in the future? What if you add or remove a field, do you head back to the template file to rename it? I'd be more descriptive in my naming. Just my 2p. Edit: Btw, ProFields will give you both Table and Repeater Matrix. Take your pick! Also..what Robin said! Inputfield Dependencies! Edit2: I didn't know repeater matrix allows different types of fields in one repeater!

Hi @dst81, Welcome to ProcessWire and the forums. I don't have a direct answer to your queries. I have found some topics though, that may be of interest to you. Deployment Docker Git Quote from ryan

Thanks @adrian. I'll have a look. I currently have up to PHP 7.0. It seems I'll need an app that enables me to easily switch versions. I've tried several in the past but none of them worked well so I settled for UwAMP which does have its issues to.

@adam1002. Welcome to the forums. It seems your intention was to reply to some specific post but things went awry and you created a new thread instead? If you can point us to the original thread you were posting to, we'd be happy to merge this answer to that thread .

I haven't looked at this in detail. As you await better responses than mine , why don't you just do what the error is instructing you to? Save the whole page. If that works, then work on fine tuning so that if new page, save whole page, else, save affected field only. Instead of... Save the whole page.. $page->save();

I can't find this 'add new image'. Could you please post a screenshot? Thanks.

I've sent a couple of you the latest VPS to beta test please before the official release. Thanks!

Hi @Sebastian. What's the difference between your local and remote servers? I have also not tried Blog on PHP 7. I'm hoping to move Blog fully to PW3.x sometime soon (maybe early 2018). Maybe then I can test on PHP7.

I can confirm this (PW 3.0.84). Must be a bug. To get around this, like you said previously, just choose the one under Multiple Page Selection (sortable). It will still work with your Single Page field.

Interesting idea. I'll have think. Maybe we can include and option in blog to specify the image field to use, including Media Manager field and similar.

Hi @quickjeff. I'm not sure I follow. What sort of collaboration between the two modules are you after?

I use PicPick. Open your select menu and then use the keyboard shortcut for tasking a screen grab (region, whole screen, etc)

Unless it was changed recently, AsmSelect and PageAutocomplete are configured to return 50 results. Could that be the reason why some results not showing up?

Glad you like the module. I'll have a look when I update the module to support ProcessWire 3 only. Meanwhile, you could try saving the settings directly via their respective pages. Some live in the comments page, etc. Gotta run, so can't provide more info, sorry.

We have been patient and we have been accommodating with this thread. However, it has now reached a point whereby this thread is no longer constructive and therefore it has been closed.

For now, a simple else for the !is_string() check in sleepValue() will get rid of it. It will mean, though, zeroes saved to DB for any blank values. if(!is_string($languageValue)) $sleepValue[$dataname] = number_format($languageValue, $precision, '.', ''); else $sleepValue[$dataname] = NULL;// or '' or 0

Aren't they all staying open? Will investigate.

@thmsnhl. Glad you got it sorted.

I need my head to be examined! I was looking at the wrong setting. What we've always had is the limitFields setting. That limits selectable columns. We also currently have disallowColumns, for columns that should not be selectable/displayed. For the columns to display by default we need to set the properties columns and defaultColumns. These two have been missing from VPS. I have added these to the latest version (5) that I am working on. The former is done programmatically. The latter is what you'll see as a setting in a VPS field. I hope to release this tomorrow to a limited number of users for beta testing. @Macrura, I will also add a setting to allow/disallow other users from seeing the columns filter when using the Lister. This means that they will only be able to work with the columns you've set if you wish. I think this was part of your request, no? I can't recall if this is the normal behaviour in Lister Pro. If it is not, please let me know. Bookmarks are not the only way, as per my explanation above. defaultColumns will sort this out. Sounds like a good idea. I'll have to study this first. It will certainly not make it into the current version of VPS (5). Something else I'll have to study, in this case since I've never used Bookmarks before . If you can get VPS5 by tomorrow, defaultColumns should be able to partly solve your issue I think.

My bad! That's what happens when you type just before dashing out the door . As @adrian shows above, it should be InputfieldMarkup. There's a couple of examples in the Blog module link I posted above. Note that since the method is static in the blog case, we use this instead: $m = new InputfieldMarkup; $m->label = __('Blog fully installed'); // blah blah $form->add($m); Guilty as charged sir! Ditto - the rushing out the door . Corrected the links, ta.

You add non-form stuff to forms using MarkupInputfield...for instance... edit typo: InputfieldMarkup

If using the old style, what you need is the method getModuleConfigInputfields(). I think it used to be a static method so no $this, etc, but that could have changed at some point I. Here's how we do it in the Blog module (static method). For that specific case we jump through a couple of hoops but it need not be that complicated in normal use. You can also look at other examples to get the gist of it (e.g. Tracy, [non-static method] and some core modules. Invariably, these will be Process modules, e.g ProcessPageSearch.). Your module will have to implement the ConfigurableModule interface. The Module interface is a good read.. In the links above, see also the code for retrieving saved values. Here are some old links on this topic: Possibly related Edit: see next post if you already know above; my bad; just re-read your post.

@Robin S. Excellent solution! I think it is worth mentioning in the other thread that the solution does work (and cross-reference it with this GIF)...to help those who come across that thread. Ta.

I have never tried it in a repeater but I do have my doubts. I'll test and let you know. Edit: I've just tested...and, we'll what do you know, it works! Well, mostly . I'll just need to sort out an issue similar to this one in VPS (a solution exists [scroll down a couple of posts]; just needs to be implemented). Otherwise, at the moment, the selections are affecting each other (selects have identical IDs since they are just being, er, repeated). No ETA for now though, but definitely on the cards. Thanks for your interest.

Thanks. I'll test this soon.