renobird

Alright people, we need 16 more willing contributors, and a dev (Ryan? *wink*). Not convinced? Go take 3 minutes and try the redactor demos.

+1 Adam, same thing happened to me.

20 contributors at $20 each. I'm good for 2 spots.

Looks like there are a few other CMS's (including perch) using Redactor WYSIWYG editor. I'm jealous seeing the other kids playing with a toy that I want and don't have. This came up before in another topic, and it sounds like there are possibly some licensing issues. Thought I'd start a topic specifically to discuss this—incase there is any possibility of adding it to Processwire. I don't have enough knowledge about the licensing, or the skills to turn this into a module—but I make a great cheerleader! Wait... that didn't sound right.

Thanks Jasper, Gremlins I guess. All seems well now.

I think commercial modules are appropriate and should be encouraged. I suspect there are a large number of us that utilize Processwire (and other open source products) to make a living. I think collectively we are fortunate (and spoiled) by the myriad of software available at no cost. Processwire has made a massive impact on my productivity and ability to deliver complex products. If Ryan can develop some commercial modules that allow him to spend more time developing PW (and make a profit on all the work he's put into this truly amazing system), I am happy to support that effort — and if there's a place to donate to the cause directly, I'll be glad to do that as well.

Maruchan, MarcC, Marco, Robin Masters? Directus looks pretty cool, but as soon they started talking about tables and using SQLPro/PHPMyAdmin I lost interest. diogo, ROFL!!! Well played.

Hi Jasper, Just installed this module (running 2.2.9) and I get this warning: Warning: preg_match() [function.preg-match]: Compilation failed: unrecognized character after (?< at offset 6 in /x/xxxx/xxxx/xxxxx/wire/modules/Fieldtype/FieldtypeDatetime.module on line 175 Does this hook into the FieldtypeDatetime.module somehow? I'm not sure what was going on there. I uninstalled/reinstalled both modules and the warning is gone.

I feel like I broke something in that install just by looking at the screenshot.

Hi Marc, That works for this particular case (and is exactly what I did as a workaround), but it becomes a bit cluttered if I have to do that for each pairing. I have a couple other cases that would need different pairings. Thanks for the quick response.

This probably needs to be in the "Wishlist & Roadmap" forum, but I'll post it here in case anyone has another solution. I need to be able to select more than one label field when creating a page field. In this particular case, I need to show the user's name, as well as the university ID#. See screenshot for clarification.

Thanks Marc! I think that would do it. I'll report back on what I come up with.

Well—not surprisingly—that's a bit over my head.

You both have it exactly right. I'll take a a look the video embed module and see if I can mod it to work. Thanks

There may already be a method or module for this, but I can't seem to find either. I'm looking for a way to embed a slideshow in TinyMCE from images uploaded in PW. Any ideas?

+1 to that. Working in anything else these days feel like a chore to me.

ROFL!

I want to see the rest of WillyC's profile photo.

HAHAHA! +1 on what Soma said.

Hi Ryan, That would work perfectly!

Hi diogo, Yes, manual grouping is what I was proposing. My idea would be that when you create a new field you can manually add it to a group.

Hi Steve, You can sort them by type if you click on the header of the type column. I use that quite a bit actually. To clarify a bit more: I would say the majority of my fields are "generic" and can be reused in a variety of contexts. But, there are still a lot that are specific to certain *kinds* of templates. For example, the calendar template has a lot of fields, most of which can be reused in other forms, so it would be nice to create a grouping of fields called "forms" for things that are only going to be used in forms. Maybe I'm just being *too* organized here.

Maybe I need to just get used to having a massive (and kind of messy) list of fields that I just filter. It just seems to take a bit more work (to me at least) than being able to quickly identify fields of a certain *type*. In my mind I see it working much like the modules listing. I don't think it's a issue on most sites—but for this "beast" I'm working on there just seems to be a need for a lot of fields—even when reusing as much as possible.

Hi Ryan, Absolutely, I was just thinking of this as a way to help visually organize. After talking with Apeisa on IRC, I realized that prefixing field names as a way to group them is not always a good solution either. Since fields can be renamed based on context it's almost better if they have generic names for easy reuse. So ultimately I need less fields, but the fields view is becoming even more unorganized as I try to keep the names as "vanilla" as possible. Having a way to visually organize certain "groups" of fields would really help.

Thanks Ryan, I was hoping to transition to using Google Calendar as a way to manage all our calendars (and there are a lot). I tested it some today, and Google Calendar isn't going to provide all the functionality we need. However, it is well suited for some of our more specialized calendars that are essentially a list of dates — in which case this module will be perfect.