Chris Falkenstein

Thanks for the replies. I was considering how it would be to add filters to the categories. What about assigning those filter values when inputting the product? For example, I'm inputting a t-shirt on the edit screen, what's the experience for inputting the available colors? How does the edit screen for the product know to show the appropriate filter? The edit screen would have to determine what category they chose and display the appropriate filters so the user can select from a value or add a value to that filter group. Hmmmm...

Hello, Let's assume I'm organizing products. I'm looking to setup categories and filters so visitors can efficiently find products. The visitor will drill down/navigate through categories then be presented with additional taxonomies to further filter the results. I see Amazon doing this. Categories are pretty straight forward. In PW I'll create a page for each category. I'll then assign one or many of those categories/pages to the product using the page reference field. Filters aren't coming to me so easily though. How do I allow the user to assign filters from a predefined list based on the type of product their inputting? The products will be vastly different so they won't share the same attributes. Random clarification: When looking for a beer mug you won't filter based on fabric. Consider the attached, taken from this projects wireframes. Those filters (style, frame materials, etc.) are relevant to the type of product listed on the page. How would you folks recommend setting up the back-end (within PW) for this type of structure. I think what's getting me is how do I allow the client to grow the site - to allow him to setup his own filters based on new product categories. Any insight would be greatly appreciated.

Oh hell. I could of sworn I tried that. Upon getting your confirmation I tried again and it worked. I probably had some character out of place. Thanks. So the take-a-way is: You can use Markdown in your field descriptions. Great!

Hello. I'd like to include a link in my field description. See attached, highlighted in yellow, so we're all clear on what a field description is. I'd be nice to offer a link to a Markdown guide (in this case). Is this possible to use HTML to create a link in the description. I'm not looking for any hacky ways here. I was hoping it was something I could just do or option that I could tick. Thanks.

Got it. Thanks. Didn't realize I had to install it (was thinkin all core modules where installed already).

I don't see Markdown as an option. Is the Markdown module still included in the core set of modules?

Thanks for the quick reply.

Hello. Do the fields created with the textareas pro field all need to be grouped together or can I organize them among non-textareas fields? Guessing that non possible but want to confirm.

Thanks. That was certainly it.

Hello, I get the following error message when I try to publish my page. "Session: Warning (requiredIf): dependency field 'feature_image' is not present in this form. (ProcessPageEdit)" Any insight? Thanks

Hi. To answer your question, It varies. I could have two. I could have ten or more. I don't want to be limited by the concern that my buttons are going to take up too much real estate.

The new matrix field lists out the action buttons (e.g. add text, add quote, etc.). The buttons quickly run out of real estate. It's not very scalable. I would like to suggest that we have one action button, maybe just 'add' which upon clicking reveals all the available repeater items (e.g. text item, quote item, etc.). Consider the animated gif shown at the address below (taken from a page builder plugin for one of my other favorite CMS). https://github.com/TimOetting/kirby-builder Thoughts?

Thanks for the reply. After you suggested it I tried it. It doesn't hide the button, but it does throw a permissions error notification for the client's role when they try to add a "magic" block. So it's half of a solution. Ultimately I'd like the "magic" add button to be hidden from the client and, although the client can see the magic block in place, they cannot remove it.

Is it possible to hide available templates that i use in my PageTable from my clients? Let me explain... I'm setting up a PageTable to allow my client to select blocks of content to build out their web pages (see attached pic). In order for me to really give them the flexibility they need I added a new template called Magic. the magic template only holds one field - it's a drop down menu that allows them to cast spells (functions) such as 'Render staff list'. This allows the client to build pages such as... Header Image Text Magic - render staff list Header Text ... I would prefer that the client did not have access to the Magic block. Is it possible to hide the Magic template/button from my clients? Perhaps with permissions? I can see using the Hanna Code module as workaround, but i'm curious just the same. Any insight would be appreciated.

for one reason or another the 'minimalist' cke skin does not work with pw. i feel this isn't a foul on pw's end. this is a foul on the skin's author's end. i was able to make the 'minimalist' skin work by stripping down it's 'skin.js' file to something less complex. for example the original 'skin.js' file looks like this... /* Copyright (c) 2003-2015, CKSource - Frederico Knabben. All rights reserved. For licensing, see LICENSE.md or http://ckeditor.com/license */ CKEDITOR.skin.name="minimalist";CKEDITOR.skin.ua_editor="ie,iequirks,ie7,ie8,gecko";CKEDITOR.skin.ua_dialog="ie,iequirks,ie7,ie8"; CKEDITOR.skin.chameleon=function(){var b=function(){return function(b,e){for(var a=b.match(/[^#]./g),c=0;3>c;c++){var f=a,h=c,d;d=parseInt(a[c],16);d=("0"+(0>e?0|d*(1+e):0|d+(255-d)*e).toString(16)).slice(-2);f[h]=d}return"#"+a.join("")}}(),c=function(){var b=new CKEDITOR.template("background:#{to};background-image:-webkit-gradient(linear,lefttop,leftbottom,from({from}),to({to}));background-image:-moz-linear-gradient(top,{from},{to});background-image:-webkit-linear-gradient(top,{from},{to});background-image:-o-linear-gradient(top,{from},{to});background-image:-ms-linear-gradient(top,{from},{to});background-image:linear-gradient(top,{from},{to});filter:progid:DXImageTransform.Microsoft.gradient(gradientType=0,startColorstr='{from}',endColorstr='{to}');");return function(c, a){return b.output({from:c,to:a})}}(),f={editor:new CKEDITOR.template("{id}.cke_chrome [border-color:{defaultBorder};] {id} .cke_top [ {defaultGradient}border-bottom-color:{defaultBorder};] {id} .cke_bottom [{defaultGradient}border-top-color:{defaultBorder};] {id} .cke_resizer [border-right-color:{ckeResizer}] {id} .cke_dialog_title [{defaultGradient}border-bottom-color:{defaultBorder};] {id} .cke_dialog_footer [{defaultGradient}outline-color:{defaultBorder};border-top-color:{defaultBorder};] {id} .cke_dialog_tab [{lightGradient}border-color:{defaultBorder};] {id} .cke_dialog_tab:hover [{mediumGradient}] {id} .cke_dialog_contents [border-top-color:{defaultBorder};] {id} .cke_dialog_tab_selected, {id} .cke_dialog_tab_selected:hover [background:{dialogTabSelected};border-bottom-color:{dialogTabSelectedBorder};] {id} .cke_dialog_body [background:{dialogBody};border-color:{defaultBorder};] {id} .cke_toolgroup [{lightGradient}border-color:{defaultBorder};] {id} a.cke_button_off:hover, {id} a.cke_button_off:focus, {id} a.cke_button_off:active [{mediumGradient}] {id} .cke_button_on [{ckeButtonOn}] {id} .cke_toolbar_separator [background-color: {ckeToolbarSeparator};] {id} .cke_combo_button [border-color:{defaultBorder};{lightGradient}] {id} a.cke_combo_button:hover, {id} a.cke_combo_button:focus, {id} .cke_combo_on a.cke_combo_button [border-color:{defaultBorder};{mediumGradient}] {id} .cke_path_item [color:{elementsPathColor};] {id} a.cke_path_item:hover, {id} a.cke_path_item:focus, {id} a.cke_path_item:active [background-color:{elementsPathBg};] {id}.cke_panel [border-color:{defaultBorder};] "), panel:new CKEDITOR.template(".cke_panel_grouptitle [{lightGradient}border-color:{defaultBorder};] .cke_menubutton_icon [background-color:{menubuttonIcon};] .cke_menubutton:hover .cke_menubutton_icon, .cke_menubutton:focus .cke_menubutton_icon, .cke_menubutton:active .cke_menubutton_icon [background-color:{menubuttonIconHover};] .cke_menuseparator [background-color:{menubuttonIcon};] a:hover.cke_colorbox, a:focus.cke_colorbox, a:active.cke_colorbox [border-color:{defaultBorder};] a:hover.cke_colorauto, a:hover.cke_colormore, a:focus.cke_colorauto, a:focus.cke_colormore, a:active.cke_colorauto, a:active.cke_colormore [background-color:{ckeColorauto};border-color:{defaultBorder};] ")}; return function(g,e){var a=g.uiColor,a={id:"."+g.id,defaultBorder:b(a,-0.1),defaultGradient:c(b(a,0.9),a),lightGradient:c(b(a,1),b(a,0.7)),mediumGradient:c(b(a,0.8),b(a,0.5)),ckeButtonOn:c(b(a,0.6),b(a,0.7)),ckeResizer:b(a,-0.4),ckeToolbarSeparator:b(a,0.5),ckeColorauto:b(a,0.8),dialogBody:b(a,0.7),dialogTabSelected:c("#FFFFFF","#FFFFFF"),dialogTabSelectedBorder:"#FFF",elementsPathColor:b(a,-0.6),elementsPathBg:a,menubuttonIcon:b(a,0.5),menubuttonIconHover:b(a,0.3)};return f[e].output(a).replace(/\[/g, "{").replace(/\]/g,"}")}}(); i stripped it down to this... it worked. how well i'm not sure, but it did render the skin enough for me to realize that I can not fake the redactor wysiwyg. this all exposes the fact that i really want the redactor wysiwyg editor and it's not going to happen for my current client.

thanks, but i already tried that. and i just tried it again for good measure. it all seems simple, but it's simply not working. let me try the office 2013 skin just because that did work for Mike. hold please... well well well. the office2013 skin works without a hitch. the minimalist skin says it's a port of another theme. perhaps it depends on that theme's files? i don't see any mention of that in the docs.

thanks for the replies. i know i applied all manor of paths and name/path combinations within the 2+ hours toying with this. Mike, can you provide the exact config parameters that worked in your case when applying the 'office 2013' skin? AND, besides placing the folders/files in the proper location (path below), are there any other items that need attention? /site/modules/InputfieldCKEditor/skins/

thanks for the reply, but that post is referring to the lightwire module which is indeed a skin and i got that to work, but i'm interested in knowing if it's possible to simply download any of the skins found on the ckeditor website - found here - and get those to work with PW. is this lightwire module doing something special to be compatible with PW? i already fussed with that global config file (found at the location below) when i couldn't get things working with using the admin panel's 'custom config option'. /site/modules/InputfieldCKEditor/config.js

thanks. i tried lightwire and it's a good alternative, but are these modules the only alternative to the default ckeditor skin? does a ckeditor skin have to be built as a module in pw or is there a way to take what ckeditor offers (on their website) and use it within pw?

How do you set a new skin for the CKEditor? I downloaded the 'Minimalist' skin from the CKEditor site. I created a folder called 'skins' (e.g. /site/modules/InputfieldCKEditor/skins ). I then placed the new skin folder, minimalist, in the skins folder (e.g. /site/modules/InputfieldCKEditor/skins/minimalist ). Finally i navigated to the 'Custom Config Options' for my field and proceeded to input a number of iterations of what i thought could be the correct syntax based on it wanting json and what the CKEditor docs instruct. See attached screen shot. So after 2 hours trying I figured It was time to ask you good folks. Yes. I read this post. It didn't help. It all seems very simple to do, but it is simply not working.

thanks 'LostKobrakai'. i'll give it a gander.

yup. building out the cms for the client really does eat up a lot of time when you're loading pages, saving, saving again, navigating to another admin page, etc. tasks become redundant but i suppose that's the drawback of a GUI. this script based setup is very interesting. i do wish the process was a bit simpler for us primarily-front-end developers though. OOP? scary. i've seen some cms using yaml to setup fields. that looks more friendly. see here for statamic's method to get an idea. who wants to build a module that would allow us to import a yaml file to translate into new fields? question: where do you run these scripts? so i code up one of these php files to create a bunch of fields. where do i put this file (in the structure of pw) and run it?

thanks for the quick reply. your confirmation led me to a discovery... it turns out that if you create a PageTable field and assign only one (1) template you get a 'add new' button (as shown in the attached pic above). it does NOT use the label from that template. but when you assign two (2) or more templates the system will use the template labels to lable the buttons. i feel it should use the template label for the button even if one template is assigned. i posted this on the wish list here.

it turns out that if you create a PageTable field and assign only one (1) template you get a 'add new' button. it does NOT use the label from that template. but when you assign two (2) or more templates the system will use the template labels to lable the buttons. i feel it should use the template label for the button even if one template is assigned. this topic came up in the general support area, here.

Is it possible to change the label of the 'Add New' button that appears with the PageTable field? Please see attached. I see folks have different labels for these buttons. How is this achieved? Furthermore i see that some developers have multiple 'Add New' buttons with their PageTable implementation - as if setting up a feature very similar to a 'Matrix' found in Craft CMS - where each block of content gets its own 'Add New' button. How is this achieved? Is this only possible with the PageTable Extended module? I'm not really interested in styling the Admin page to mimic the frontend. I just want to custom-label those buttons and find out more about the multiple button setup. Please advise.