Macrura

the menu css would be in the frontend code you are writing, or using; the module is there to generate the markup you require for the menu. What framework are you using for your site? Many frameworks have navigation css built in (such as bootstrap)

are you caching a plain array or a Pagearray Have you checked the database to see what is cached there in the caches table and what the expiration date is? have you tried clearing the cache using $cache->delete(...)..

as an update to this topic, after discovering the awesome power of Selectize.js, i have been able to implement really good tagging on the image fields which works much better than the technique discussed earlier in this topic. 1) place the selectize files somewhere in your templates folder http://selectize.github.io/selectize.js/ (i have placed them in a 'plugins' folder) 2) make the files load on page edit, from your AdminCustomFiles settings: ProcessPageEdit plugins/selectize/dist/css/selectize.legacy.css ProcessPageEdit plugins/selectize/dist/js/standalone/selectize.min.js 3) in your ProcessPageEdit.js file, init the plugin: /** * Selectize * ============================================ * init selectize tagging on field called images * */ $(function(){ $(".Inputfield_images input[name^='tags_images_']").each(function() { $(this).selectize({ delimiter: ' ', persist: false, plugins: ['remove_button','drag_drop'], options: [ {value: 'tag1', text: 'tag1 - use this for blah'}, {value: 'tag2', text: 'tag2 - this will do blah'}, {value: 'tag3', text: 'tag3 - a super special tag!!'}, ], create: function(input) { return { value: input, text: input } } }); }); }); Now you have a really good tagging interface: Notice how you can also add explanatory info right into the tag, but keep the tag value whatever you want; there are a lot of other options you can implement, check out the selectize docs. this is really now one feature that i believe should be included in the core or at least made into a module... first an inputfield/fieldtype single/multi select based on selectize which can improve selections when you have a lot of additional data to show about the individual select options; second would be to enable selectize.js on any image tag field and be able to define the option value/labels based globally or based on current template...

sure enough, it works like you said! no more 'sent by'...! good point though about wiremail - i currently use horst's wiremail module and am extensively using the functions for attachments and probably more; i wonder if when i get to the stage of switching that site over to mailgun, if i'll need to use the SMTP connection option, instead of API..

replying to the OP - use a data- attribute on the select using jQuery you read that data attribute for the selected item and then show it... see more here: https://processwire.com/talk/topic/419-extending-inputfields/?p=76861

right i just checked and i do have all of the spf and dkim records correctly done but i think you are saying that i should not use the mg subdomain and change that to the normal domain so i don't get those sent by things.. i wonder if you can have both mailgun and mandrill txt records

ok thanks - i followed their recommendation of the mg subdomain but i guess i need to now add all of the sending domains and dkim records for those domains, at least that's how it is with Mandrill...

@Pierre-Luc thanks for this module, everything seems to be working well and i greatly appreciate all the time you put into it; Mailgun is great, and i can see myself using it a lot in the future for transactional emails in processwire. My only issues are probably more about adjusting from Mandrill to Mailgun, i do like the Mandrill interface in terms of seeing the outbound activity list, sender, status, subject, view content etc; it's a bit more user friendly; also, this may be how i have it configured but the from address on mailgun shows a "sent by " and then a long email address like person@mg.domain.com ; i know i'm going to get some complaints from clients if that is something that can't be changed, and they may just prefer paying the $10/month mailchimp minimum plan to carry on with Mandrill..

you would have 2 options i think (besides the runtime sort field as described above), one is to sort the Pagearray after , using ->sort(field1|field2) or you could store the sortdate as a hidden field on the page using a module to write that field everytime the page is saved

been playing with Selectize.js for complex single selects; in combination with a module that lets you take various fields from the page you are selecting and put those into a json array as a data-data attribute... the selected option: open with search: sort of a supercharged chosen select .. might be worth having selectize.js into an alternate to chosen select, and bundled with the ability to define the array for json data att

oh yeah, cool, for some reason i thought i fixed it, but i will take care of it and update - many thanks for reporting this!

thanks - the latest version should have this already on line 93: $siblings = $this->editedPage->siblings("include=all"); are you sure you have the latest version?

this is presenting a major hassle for me, i have 2 places now where this markup appears in selects, one in admin and one on a formbuilder form, and i can't launch this site till i can fix it. any idea on how to hook and fix? been trying various things with no luck; tried hooking into FieldtypeMulti, FieldtypePage, Fieldtype, can't get the hook to fire or strip those tags EDIT: while it would still be good to have a fix for PW 2.7 branch for displaying these, i have found a solution described here: https://processwire.com/talk/topic/12045-page-select-subfield-display-issue/?p=115674

@justb3a - thanks, and i accepted the pull req and i'll up the version and add the table css tomorrow...

hey this is great and was something i was eventually going to work on also, because it would be good to have a dedicated fieldtype for key value where they are entered into fields like this. Currently i use tables for this, and here is a thread with some other info, possible use cases; one thing that might be cool would be to have another column as in Martijn's example, so there is a name (key) label and value, and in his example there is also a trick for hiding the name of the keys from non super users (so they wouldn't break the front end in case they changed an in-use variable) https://processwire.com/talk/topic/8373-use-delimited-texarea-table-or-yaml-for-settings/

cool, glad it's working out; i just added table css, from uikit to the scoped css; not sure how needed it is, but i just started using tables in my documentation and saw there was no styling; ** i'll be adding the table styles to the next update

the process admin help does not interact with the help tabs; the process module only gives you like a global page where all of the help docs are in 1 long accordion. the help tab on the page editor is rendered in the help tab module, so it does a selector to see if there are any matching help docs based on the template select and then I think it uses a hardcoded body field, so in terms of that, i would probably need to implement a setting to allow users to select which field will contain the markup... i will check it out and get back

Right, they are just body fields rendered in the accordion; you would setup the help root and then the help pages themselves, and then select which templates to show on; all markup for the help page itself would be done in the ckeditor

could you post a screenshot ? does the lightbox option work? i can test again, maybe i broke something on the last update...

do you mean the help tab, or the process page, that shows all of the help docs?

this may also be of use: https://gist.github.com/pamelafox-coursera/5359246

I didn't know it was possible. but RSS seems to support pagination; you'd need to hack the module i think though in order to support the pagination. In terms of filtered feed that sounds riskier, but you can always load the feed with a different page array, shouldn't be any issue, maybe you can explain more about why you need it - i guess you want different feeds with different titles, but want to generate them all off the same page?

update - if you need to be able to access your variables inside functions or the admin you can use $config.. in config.php, setup an empty array for siteSettings like this: $config->siteSettings = array(); then in ready.php file, array merge values from a settings table (profields table) or any other type of setting (MultiValue Textformatter, YAML settings ...), in the admin like this: // Get your settings from wherever $st = $pages->get('/settings/')->settings_table; // temporary array to merge with global $settings = array(); foreach($st as $row) { if(!$row->value) continue; if($row->disable == 1) continue; $settings[$row->setting] = $row->value; } // merge $config->siteSettings = array_merge($config->siteSettings, $settings); i'm curious if anyone sees any possible issues with this; it works now and i can access my siteSettings everywhere doing this; you can access the settings like this from templates: echo $config->siteSettings['yourKey']; or in function.. echo wire('config')>siteSettings['yourKey'];

so if i wanted to make an api variable called settings, how would i populate it with the object, say from the ready.php, or would i need to create a module? so would it then be possible to have a wire('settings')->siteTitle sort of thing?, instead of $config->siteSettings['siteTitle']

ok thanks - that's good to hear ! on some previous projects i was getting those values in the _init and just setting variables i could use in templates, but were not available in functions, modules or the admin (such as in runtime markup field). For this, I had initially tried to add items to the array directly but was running into an "indirect modification of overloaded property" error. After researching that, i solved it by using the array merge; though i am curious if there is a way to add items directly on the fly from a template file, maybe i need to use the _set ? __set( $key, $value ) Provides direct reference access to set values in the $data array