Macrura

@kongondo - thanks - yes, i could also just delete and remake the field, since i can copy the code, and there is no risk of losing entered data... it would be good to fix though, as surely someone along the way is going to try and rename one of these..

@kongondo - wondering if there might be an issue with renaming fields using this fieldtype; i tried renaming an existing field but got a sql error;

how about wordLimiter? i have this in every single site.

great - i was planning a write up/tutorial on various ways to do menus on PW; historically i've done it using a lot of different ways (besides the usual generating from the page tree); for some simple sites now i use a profields table, now that it supports page selects. but i do think the menu builder is the best for larger sites; let me know if you need any help on it, i can donate time over the next 2 months.

@kongondo, Thanks for making this. i finally had time to test this out and it's very great - i'm planning to use it from now on for most projects...

can you see console errors (js)?

you could also escape double quotes, if you're not following the style guide explicitly and wish to have double quotes on the output

page name should be enforced to be unique already, but you could use this for text fields: http://modules.processwire.com/modules/fieldtype-text-unique/

how would one output an optgroup in an options field, if it is somehow possible? ran into this today...

on the last major ec project i worked on we extensively researched magento, but alas it couldn't meet the requirements matrix, whereas wp/woo was able to; However i have 2 ec sites that have been a dream with fc+pw; and have been looking closely at snipcart, and of course padloper...

here's a quick way to change the slider increment for your date timepicker, (this would go in AdminCustomFiles/ProcessPageEdit.js): if(typeof $.timepicker != 'undefined') { $(function(){ $.timepicker.custom = { stepMinute: 15, }; $.timepicker.setDefaults($.timepicker.custom); }); } if you run the latest version of timepicker addon (1.6.1) you can use selects instead of sliders: (for example if you are on current dev/stable, you copy the inputfield to site/modules and tell the system to use that one; then upgrade to the latest timepicker, and copy the new css to the datetime css; if are on devns, word is that it will include the latest version of timepicker). if(typeof $.timepicker != 'undefined') { $(function(){ $.timepicker.custom = { stepMinute: 15, controlType: 'select', oneLine: true, }; $.timepicker.setDefaults($.timepicker.custom); }); }

you can't edit the hanna code 'cached' files directly

great - thanks! Checked it and it's all working now... Also looking forward to the next version!

hey tpr - thanks and also let me thank you for this module, it looks great, and you have put a lot of work into it - it will be really handy for this project i'm working on where we need to check that links to external sites are working/correct! So i checked everything and troubleshot it to where i have narrowed down the issue to the field restriction - if that is set, then it doesn't work; setting the template restriction works... being that i don't really need to restrict by field, i'm all good, but i can further assist with this issue if you need more info. thanks again!

I'm not having any luck getting this to work... no arrow is shown; I'm on Mac, Firefox, Chrome, but no luck; templates and fields all setup.... no js errors.. Any idea what might be the cause, or how to troubleshoot? TIA

Hi steveooo - do you intend the users to nest the modals, or do you want to prevent the nesting? Are you asking for a way to make the successive modals to max out?

Perhaps this question should be posted on the Blog Module thread?

I sort of handle this situation using this: http://modules.processwire.com/modules/admin-page-field-edit-links/ but then editors do need to click on the item after it is added to fill out those additional fields; not a perfect solution, but might be the only option currently

the reason you can guess that it's not processwire is that if you look at the sourcecode, everything is ok, in terms of the paths to the assets. If you click on one of those paths, it gets redirected, which means something in the htaccess or index.php might be amiss, or something wrong with the server. So you can't connect to the folder through FTP, and replace the index.php and .htaccess files?

i would replace the .htaccess file asap. then if that didn't fix it i would replace the wire folder, and index.php also i would file a support ticket with the hosting provider

It should work

right - forgot about template cache and settings (been using WireCache lately)

I think template cache is duration based - i didn't know it would clear on save

@prestoav - you could duplicate the FieldtypeSelect module and then make some mods to support your option groups, like anything preceded with --- could be turned into a group etc..

you can use the new slider module that was recently released, it has a whole admin interface. other than that you would use PW fields to hold the various options and settings for each slide; this will be totally dependent on which slider you are using, as well as how often you think the site managers will be needing to change stuff; Here are some ways it has been accomplished on my end: 1.) Using Profields Table to hold settings for each slide; custom module populates default settings (rows) and then the values are adjustable in the 2nd col of the table 2.) Using textarea to hold the code for each slide (or Ace Extended inputfield); slide code can be edited directly; 3.) Same as #2, but allowing for use of placeholders, like Slide image, link, button text, so that that the editors can use regular fields for some of the slide settings - such as selecting an internal page to link the silde to 4.) YAML field - captions, animation settings, etc 5.) Pagetable and PW fields to hold all custom settings, Slider inputfield for some numerical settings