renobird

Here is a quick screenshot of an admin page we use to manage the initial hiring process of new employees. The module hooks into FromBuilder and pulls in entries that are associated with the page. So all the information on the left is from a FormBuilder entry, the sidebar is a little more typical and just made up of the fields assigned to the template. I'll post more about that later. We don't allow users to edit the comments, because they are part of the document trail, but they have a chance to review them in a modal before the actual submit happens. The "notify of comment" pulls in a list of people with particular roles. I'll post the code a little later, I need to put out a small fire first.

You need: Page Reference Field Parent page to hold the tags (for example: /config/tags/) Template for the tags Create the parent page /config/tags/ Create the tags template (no need to have a file, and only needs one field "title") Create a Page reference field. (called tags for this example) a. In the settings "Allow new pages to be created from this field" b. input field type: autocomplete, or whatever type works for what you are after. Assign your "tags" field to templates where you want to allow tagging.

Yep. I'll post a screenshot of a process module that has a comments sidebar when I get to the office tomorrow.

I've been keeping my eye on this since apeisa tweeted something about it a few weeks back. Looks really cool. And for some reason I like the way he sounds when he says "pinegrow". Weird? Perhaps.

I can post a working version of this tomorrow. I use page comments (with user profile images) as part of admin pages a lot.

The frontend can be coded (HTML/CSS/JS) of your choice. So "themeing" can be as easy or difficult as you make it. The admin markup can be altered to a point, but a lot of the functionality needs to have specific markup (jQuery UI). Theming the PW admin isn't difficult, but it can be very time consuming if you want to make wholesale changes. There is a lot to consider. My suggestion would be to start by copying and make small alterations to any of the core admin themes, you might find that you can alter the CSS enough to get what you are looking for without having to make a fully custom theme.

For dates I would suggest adding a date/time field to your template. Call it "post_date" for example. Have it default to today's date. That way you don't have to set it, but you can adjust it if needed. This lets you pre/post date your entries easily. Now instead of using "created" in your selector, use the name of your new date/time field "post_date".

adrianmak, So, saving to a page is just like creating a page. (a page in this case being a group of fields in the admin). If you want to view the entries in some other format, you can create a frontend view for those pages, or you can create an admin page (via Process Module) or use the Admin Custom Pages module.

No worries, thanks for the update.

Hellomoto, Take a look at some other modules. You can learn a lot by checking out the core modules too. /wire/ is your friend.

Soma, I just got around to using this module, and it's great! It makes setting all these up SO much easier. Thanks man.

Seems really fast here. I'll take a longer look later, but looks/feels really nice so far. Great work as always!

Ah, I see your class already does the same thing. So yeah, either way to get what you need. Seems easy enough to do in the template.

Could be slow if you have a lot of pages, but for a reasonable number this might work. foreach($pageArray2 as $p){ if ($pageArray1->has($p)) continue; $pageArray1->append($p); } *untested and written in the browser.

Welcome chadamas, I've been using PW since late 2011, and I don't think about CMS's anymore. I suspect you will never look back.

Good one Adrian! Thanks for sharing.

I think you can prevent them from deleting their own page by using 2 roles. Role 1 would have edit but not delete permissions and would be assigned to their main page. Role 2 would have edit and delete permissions and would be assigned to all the allowable child templates of their main page. (See this post/thread) Here's the modified version of PageEditPerUser. PageEditPerUser.module I'm not entirely this meets all your requirements — I haven't read this topic all that close to be honest.

Still seems like JS would be the easiest. JSON with paths for all the images, grab random from there.

@LostKobrakai Perfect! I would love to see that implemented.

@chuckymendoza, I have a modified version of PageEditPerUser that assumes if they have edit then they also have add children permission. I'll post it tomorrow when I get to the office. (Remind me if I forget).

@Aleksey Popov I think we've uncovered all the options.

I knew Pete had asked about this ages ago, took me a minute to find it. Check out this reply from Ryan — it's basically an example of the str_replace() idea Soma mentioned above.

@Jan Nice technique, but won't that only pull a random image for the first page view that creates the cache file? For that to work, do you need to add "of" to the cache disabling variables in the cache settings for the template? Wouldn't PageRender just serve the cache file without ever getting to the PHP in your template?

Hi horst, That's what I'm aiming for. I've only had a few minutes to work on it, so I just have the sidebar open/close now.

@nico I plan on included those changes. I've been working with it like that here, and I like it. Other notable things I've been working on this week: Fixed sidebar and header Save open/close state of sidebar (via cookie).