szabesz

My new blog post on setting up a Blank Proflie: http://szabesz.hu/blog/my-basic-setup-of-processwire/

First of all, thank you for the reply! Maybe it's just me who found it hard to get a proper idea what to expect. Also, while writing these words I have just realized that there is http://demo.processwire.com/ and by logging in I see that ListerPro (and ProCache) is used there, so I could have checked it out, but maybe other Pro modules could be demonstrated this way and the Store should point to the demo site.

I always clone a site form production to my local dev machine, I follow the simple workflow of syncing files AND cloning the database of the production site to my Mac. To clone the db I use this in a simple Bash script including the following: printf "Trying to drop all the tables of the Target database called $DB_TARGET_NAME \n" mysqldump -u $DB_TARGET_USER -p$DB_TARGET_PASS --add-drop-table --no-data $DB_TARGET_NAME | grep ^DROP | mysql -u $DB_TARGET_USER -p$DB_TARGET_PASS $DB_TARGET_NAME printf "Trying to download+import the database...\n" mysql -u $DB_TARGET_USER -p$DB_TARGET_PASS $DB_TARGET_NAME < <(sshpass -e ssh $SSH_ARGS "set -e; mysqldump -P 3306 -h $DB_SOURCE_SERVER -u $DB_SOURCE_USER -p$DB_SOURCE_PASS $DB_SOURCE_NAME | gzip -cf" | gzip -cd) So I drop all the tables of the target DB first, then import the production DB via SSH as seen above. I have a keyboard shortcut to launch the script, so that I can get the production db in a matter of seconds in the case of not gigantic databases. (Which I do not have currently...)

I recommend: https://processwire.com/blog/posts/introducing-tracy-debugger/#mail-interceptor-panel When Adrian is back, we should ask him to add a setting which makes it possible to always intercept emails in DEVELOPMENT mode of the module, so that we do not forget to set it.

+1 But why not the "full documentation"? I purchased ListerPro without actually knowing what I'm gonna buy, I was just wild guessing. I do like what I have but was surprised by the low number of Actions it comes with, for example. I've also been thinking about ProFields, but descriptions and proper examples of the usage of those fields are scarce, so I cannot really see if I really need them or all the features I need can be done with the built in core fields. Speaking of ProFields, they are listed here: https://processwire.com/talk/store/ But there is this one here: http://modules.processwire.com/categories/premium/ which is rather outdated as far as I can see. And there are the old video demonstrations, also rather outdated.

How about a Buy-a-Coffee too? We need options!

Oh, I was banging on open doors Again, thanks for the great module!

Sure, the module works fine, and it supports spam protection based on the time the client uses to fill it in and to submit it, which is quite useful I think. It is just this label that should be somehow eliminated if possible. Since it is a ProcessWire form API field, I do not know how to achieve it.

I don't know: https://github.com/justb3a/processwire-simplecontactform/blob/master/SimpleContactForm.module#L275

@justb3a Speaking of invisible fields, validator.w3.org/nu reports: Error: The for attribute of the label element must refer to a non-hidden form control. date'>↩↩ <label class='form__item--label' for='scf-date'>Date</ But I need to hide this field too. What is your recommended solution?

@Brian Scramlin I have not completely read this thread, but do you have ProDevTools? Considering this: "VIP Support When you purchase ProDevTools, you are purchasing full access to the VIP ProDevTools member area. This is where downloads and upgrades for products are made available, and where VIP support is provided directly by ProcessWire's lead developer, Ryan. This is particularly useful with the ProfilerPro service, and Ryan is there to help you optimize your site and resolve bottlenecks discovered with ProfilerPro. It's also useful with the API Explorer module, as it will likely open up a new world of things you can do with ProcessWire, and we'll be there to help you learn and answer questions as they come up." This offer might be the one you need now.

More recommended literature: https://processwire.com/blog/posts/processwire-2.7-is-here/#access-control-and-permissions https://processwire.com/blog/posts/processwire-core-updates-2.5.14/#multiple-templates-or-parents-for-users https://processwire.com/api/ref/#users & -access and – of course – a lot can be learnt by testing and studying these to: http://modules.processwire.com/categories/users-access/

In my case I used UIkit 3 with LESS, so I could just style easily like this: #contact-form input:extend(.uk-input) {} #contact-form .field--error--message:extend(.uk-alert-danger) {} #contact-form #wrap_Inputfield_submit:extend(.uk-width-1-1\@s) {} #contact-form .FieldtypeTextarea:extend(.uk-textarea) {} #contact-form #wrap_Inputfield_scf_message:extend(.uk-width-1-1\@s) {} more info on Extend

Have you seen this? (Sure, it is not the admin but the API, but I guess the same call is used...) https://processwire.com/api/ref/sanitizer/match/

I've filed a request: https://github.com/processwire/processwire-requests/issues/97

Here is what works with NetBeans: /* ----------------------- ProcessWire API variables ------------------------ */ // <editor-fold> /* @var $page Page */ /* @var $pages Pages */ /* @var $modules Modules */ /* @var $user User */ /* @var $users Users */ /* @var $permissions Permissions */ /* @var $roles Roles */ /* @var $input WireInput */ /* @var $sanitizer Sanitizer */ /* @var $session Session */ /* @var $log WireLog */ /* @var $cache WireCache */ /* @var $datetime WireDateTime */ /* @var $files WireFileTools */ /* @var $mail WireMail */ /* @var $config Config */ /* @var $database WireDatabasePDO */ /* @var $fields Fields */ /* @var $templates Templates */ /* @var $languages Languages */ /* @var $wire ProcessWire */ /* @var $wire \ProCache */ // </editor-fold> NetBeans seems to be picky about the way you "format the comment", hence the explicit code folding and the variables separated into their own comment lines.

Thanks for the report @Robin S! However, we are missing them, aren't we? Anyway, this module with extended features to support permission overrides per template would be a great addition to the core modules.

This is just terminology, do not meditate too much on it eg.: WordPress: custom post types, Drupal: node. Surely, there are more like these out there... Each must have its history behind it.

Something like this?

Also: Dynamic Roles Module might me of interest here. I have not used it, to tell the truth, but Ryan has updated it recently so that it is installable on PW3, that is why I guess it works too, see: https://github.com/ryancramerdesign/DynamicRoles more:

I see, thanks! Any plans on updating it? (PW3 & the above mentioned...)

@LostKobrakai Hi, is this module 3.x compatible? I'm asking this 'cos it is not stated here: https://modules.processwire.com/modules/process-access-overview/ Checking out Ryan's blog post on access control/permissions I gather that nothing has changed since ProcessWire 2.7 in this regard, so the module should be ok with PW 3 I guess, but to make sure I thought I'd ask...

@elabx Hi, FYI, Adrian is still away for more than a month, see:

I'd rather have it updated as soon as the version changes. "Manual update can be automated as well". I mean some sort of easy way to update it manually would be a better solution.

Ah, I always install it by default. Thanks for reminding me. I often trip over these naming inconsistencies. Also, regarding modules, I still find it confusing that the word "installing" is used for both getting the files of a module and also for running the actual installation process.