renobird

Thanks. I have a few base class process modules. When I saw that you were using a non module version, I was curious if there was a reason. Then I saw you moved away from it, so I had to ask.

Antti, Curious why you moved away from the abstract class / non module version.

Do you need this field to be shown in the admin or frontend? Are you just setting a value programatically, or does it require user input? I see now "in template".

Adrian, You are a machine! I don't know how you manage to answer things so fast. You are everywhere! Excellent job, I'm consistently impressed and how quickly and thoroughly you respond.

I missed that part about creating a JPG/PDF. pages2Pdf modules works great.

pankaspe, Welcome. You might want to look at the Repeaters field type , ProFields:Table, or ProFields: Multiplier (if it's a simple field), or there is also ProFields: PageTable that is free and part of the core, but I don't know if there is any documentation yet.

Glad you found some solutions that are close. I haven't looked into the search module lately, but if you can hook into it, then you can probably have it skip results for pages with the user template that don't have the same name or parent as the current user. I'm on mobile now, or I'd check. Don't worry, the search issue can be solved.

owzim, I can't believe this exists, and that I missed it before now! I though, "Hmm, let me see if anyone has anything out there about using YAML with ProcessWire". ….and lo and behold, I find this awesomeness. Much appreciated.

Both of those are good options. If you just need to select a few pages (1-3), the I would go with autocomplete. If you need to select more, then the multiple transfer is great.

Don't get me wrong, the last time I used any kind of tool like this was the original Dreamweaver in 1997, and I don't use any of the major frameworks. I do like Foundation though. I think it's important to evaluate new tools. Are they worth adding to your toolbox? In the case of an application like Blocs, I could see using it to build something small and quick. A lot of projects don't have the budget to hand code a fully custom design. Tools like Blocs could be a good alternative to using a pre-made template. Of course, you can also invest some time in creating snippets, setting up macros or using toolkits like emmet.io in your code editor. You can build sites pretty quickly that way. Joss mentioned a few of these above — if you haven't already, checkout bourbon, neat, bitters, refills. Those thoughtbot folks make good stuff. I agree with the idea of focusing on something and becoming an expert—but just up a few levels from the topic of tools. Specialize in web design/development. The tools you use to accomplish that are going to constantly evolve. You don't have to trade your tools for the latest shiny new fad, but you should explore things — sometimes they aren't just a fad.

Glad you found it.

It could, "easily" is relative. If you did that, it's essentially it's the same thing as autocomplete with a different UI. You could also go back to kongondo's suggestion of making some CSS changes to the asmSelect option to get something pretty similar.

I think LostKobrakai is suggesting you add that to your selector. That way your PageArray only containes pages where that field has some value. Optionally you could do: $showcases->filter("fieldname!=''");

So yeah… *hoping to flip back to the original topic* Blocs looks cool. Would be interested to hear how it goes if you build a ProcessWire powered site with it.

Soma, is that German? Looks like a Finnish word actually.

Hi kathep, I haven't tried Blocs, but it looks nice. I've been keeping my eye on Pinegrow. I think with either of those it would be pretty easy to design your static pages and then hook the HTML/CSS/JS up to ProcessWire.

The multi-lanugage issue is a good catch. Seems like Nico's module would give you complete "free" tagging with the UI you are looking for.

What Jan posted above works, but in my opinion complete free tagging is a mess. You end up with a ton of tags that are similar. You also get over tagging or no tagging at all. We setup something like this a while ago, and eventually realized it wasn't a useful method. Just my 2 cents. In the end there is no right way, and ProcessWire will let you build pretty much any solution you want.

How would you like the tagging to work? You mentioned earlier a comma list. The issue there is that the user has no way of knowing if the tags already exist, or is spelled differently, etc... So you end up with a bunch of tags that are duplicates, or users simply not tagging things because they aren't presented with the available choices. You could however create new pages (tags) based on a comma separated list and just have it skip duplicates. In that case you would need to create a module that took the contents of your comma separated list and created new pages from them on page save. (You don't have to create pages from these, but it seems easier to me to have them for search filtering purposes). I don't really see the benefit over using one of the already available options. Do you have dozens of tags for each post, or something that makes the current options inefficient?

Here is a paste that shows how the entire sidebar gets built. There's really nothing too fancy here. Pulling in specific FormBuilder entries and allowing edits that in turn update the associated page gets a little fancier, but nothing all that complicated really. There are certainly other ways to build that sidebar, but I needed to have a lot of control over the settings, and the template has a lot of other fields that are specific to another part of the process, so I can't just foreach the fields.

LostKobrakai, Forgot to mention, the reason it's all returning markup is that when I build the form, the comments get added like so: // Comments $field = $this->modules->get("InputfieldMarkup"); $field->markupText = $this->renderComments($page); $form->add($field);

Here are the 2 methods related to comments from the Process Module in the screenshot above. You can do pretty much the same thing in a template instead of a module. Sorry I don't have time to explain further, or put it into a more complete write up. Hopefully you can pick that apart and get what you need.

Felix, Looks great! I'll take a closer look later today. Congrats!

...as Peter mentioned, you can chose several options for the field type. I use checkboxes a lot myself.

Thanks. I do a lot of custom admin pages here. Looking now I have 10 Process Modules that create custom admin functions. Some are simple, some a super complex. I'll get back here soon with some code examples. Sevarf2, Most of the things I've built that use comments were built long before the new comment system.