Macrura

I think checkboxes are sometimes confusing to users and replacing them with an on/off switch can go a long way to making it more obvious. For example, a Yes/No button is more obvious/clear than the assumption that "if this is checked it means yes, and if this is not checked it means no"; For example i'm using this library (incorporated and initialized on some checkbox inputs): https://github.com/olance/jQuery-switchButton Here is my initialized checkbox in PW admin: This still doesn't solve the conundrum of where you want to have it checked by default... the checkbox reversed module is a clever way to solve that...other than js to set the checked attrib..

I can see one possible advantage to not extending WireMail – the ability to ad-hoc switch mailing system when you send an api email. For example, some of the emails in one list i'm sending to are being bounced due to the Mailgun server ip address; i can't switch to another wiremail email since Mailgun is extending Wiremail and then wiremail is using Mailgun... if i understand this correctly. With this module, i could just instantiate it and send using it, and avoid any conflicts with WireMail (?)

module admin page field edit links

it may have something to do with output formatting being off; not sure, i haven't worked with language yet. But it would be good to know how to explain to get this to work for multilanguage sites.

Right! my memory must be going... forgot about that...

You may be running into the multilanguage issue that was brought up here: also, are you using the correct inputfield type (e.g. multiple vs single)?

I assume you know that ASM Select supports linking to the page already in the core, so unless you need the additional features of this, that might already be a solution.

'<div class="item">' + '<span style="display:block;font-size:14px;font-weight:bold;">' + escape(item.title) + ' ' + escape(item.sum) + '</span>' + '</div>' also if you want a link you would add a line like this: ' <a class="pw-modal pw-modal-medium" href="' + escape(item.edit_href) + '">Edit <i class="fa fa-edit"></i></a></div>' +

on the CONTRA side: - i personally wouldn't care much about database bloat - how many records? - speed may not be an issue, depends on how you are using the records, and if you have caching on the front end - vendor lock in - you can easily write a script to export the records into CSV files and import to a new database; the data might change a lot over time, and what if you want to add fields to data types etc. on the 3RD way: you can leave the data in MySQL and access it in ProcessWire but, you can't really edit it that easily unless you start writing custom modules/interfaces and doing SQL queries..

you may be running into some filecompiler issue, or you have 2 copies of formbuilder somehow in your directory - check to make sure there is only 1 copy of it; you can force the filecompiler to recompile any file by opening it and adding a line at the end, and saving the file; This kind of thing seems to happens a lot when doing upgrades, some modules need to be recompiled for some reason..

Or use SettingsFactory for your settings page if it can support the fields you need.

One idea would be to clone the core inputfieldPage module and then make the renderReady method hookable. Also we need to ask @ryan if it will be possible to make renderReady hookable like render, or if there is some issue with that; once renderReady is hookable, then this module would be able to use that hook to add the required assets; If you use inputfieldSelectize, you can just make your own edit links on the items, and not need this module.

If you use Foxy.io, you can have it post the transaction data back to a URL on your site where you can process that data.

there is, but it requires using admin custom files and AdminOnSteroids... see here: the js goes in the ProcessPageEdit.js, which goes inside the /templates/AdminCustomFiles/ folder (change the fieldnames to match your fields) and the css goes ProcessPageEdit.css, same folder

@noelboss I used form template processwire way back before Formbuilder was released, and it worked fine; You can also very easily setup a service page to accept the form's post data and process it any way you want. It's very simple to do this; you can also get some ideas for how to build this: https://processwire.com/talk/topic/3779-use-csrf-in-your-own-forms/ https://processwire.com/talk/topic/2089-create-simple-forms-using-api/ https://processwire.com/talk/topic/14206-contact-form-tutorial/

I would recommend to try the form template processor, it should still work. Formbuilder is also a solid choice. Easy to create forms, and pages from the forms, and also add your own scripts and styles to forms, hook into form process and do advanced things.

i was having trouble getting this – i had these as attributes underline__type=radios underline__options=None|Top|Bottom|Both underline__description=Please select your border options. but not working, so i tried this: underline underline__type=radios underline__options=None|Top|Bottom|Both underline__description=Please select your border options. and it works; i don't think this is clear from the instructions – would be great if there were more working examples to copy/paste, in the cheatsheet

I built a simple cart system using JS + Local Storage; works perfectly and the cart contents last a long time; This is for visitors to collect swatch samples and then be able to request those samples in a form; there is no ecommerce in this case, but once you have the cart, it shouldn't be hard to use that data to interact with a 3rd party payment system.

for the most part, the hidden field option i think is best, but does take some logic and page saving; If you do want to have them be virtual, then you can do a hook wire()->addHookProperty('Page(template=product)::rating', function($event) { $product = $event->object; $event->return = $product->points / $product->votes; }); but you will be limited to in-memory selection, since the property is not in the database

i'm not following 100%; the module assumes you will want the settings everywhere (front/back). I don't see $this->wire('page') anywhere in the module, can you provide more details? By the way, the flowchart for the (non-process) module is like this: (1) find all admin pages using ProcessSettingsFactory (2) process each settings page and store the settings (these 2 procedures run in the buildFactory() method which runs on init(); and this module is autoload). This procedure might be able to be more optimized, but does ensure that any changes you make to your files (like adding inputfields) are reflected. Maybe checking the last mod date; or maybe a settings lock field on the process that prevents the file from being further processed and wirecache the array from the file;

Yes: http://modules.processwire.com/modules/connect-page-fields/

Hi @adrian - thanks for testing this - hoping to submit to modules directory soon. In terms of the process page, i think it is better to not install any, because it may cause more confusion, since the name of the process page is important in the setup.. LMK if you have any ideas about that, or do you think it should install a starter settings page, but as an option?

@Pixrael - thanks for working on that - it reminds me a little bit of the WordPress Page Builder (the old Visual Composer) which basically did the same thing, providing a visual/graphical interface that manipulated the shortcodes in the textarea.

thanks, that's very good to know, might try and revisit the app with them now that you have enlightened me!

is that a 'native' thing, i don't know much about ionic.. They started building it in Cordova/PhoneGap, but AFAIK that is not native..