Leaderboard

This functionality is a part of the core "System Notifications" module. From this what I can see, notifications status is disabled by default in the module settings, so you won't see any warnings. After changing status to show notifications, I see warning while trying to edit the same page from two different browsers ?

This module (github) does with site/assets/files what Ryan's DatabaseBackups module does with the database: Backup site/assets Download ZIP archive Upload ZIP archive Restore site/assets Motivation: This module can be the missing part for projects with content backup responsibility on the client's side: The client will be able to download DB and assets/files snapshots through the backend without filesystem access, thus backing up all content themselves. Release state alpha – do not use in production environments. Credits for the nice UI go to @ryan – I reused most of it and some other code from the DatabaseBackups module.

Thank you for your answers @BitPoet and @7Studio. I was using the core module System Notifications for a long time and didn't knew, that this feature came from this module. I stopped using it, because it didn't look nice with AdminThemeUIkit (the badge) and AdminThemeUIkit offers grouped notifications. I have tried the Page Edit Soft Lock module and this one looks good. ?

This is provided by Page Edit Soft Lock. Sure you have it installed?

It tells PW that there is more than one OR-group in the selector string. It's all about specifying what has to match in order for the whole selector string to match - remember that for every OR-group only one selector in the group has to match. So previously you were doing this... // Templates $selector = "(template=home|basic-page|product-category, status!=hidden), (template=news-item|product-page)"; // Fields $selector .= ", (title|headline|lead|body%=$q), (content_matrix.columns.body%=$q, content_matrix.columns.count>0)"; ...which we can represent as this... // Templates $selector = "(template selector 1), (template selector 2)"; // Fields $selector .= ", (field selector 1), (field selector 2)"; ...and it is the same thing as... // Templates $selector = "foo=(template selector 1), foo=(template selector 2)"; // Fields $selector .= ", foo=(field selector 1), foo=(field selector 2)"; ...which is saying "find any pages that match template selector 1 OR template selector 2 OR field selector 1 OR field selector 2". So this will match a lot of pages that you don't actually want to match. Whereas this... // Templates $selector = "foo=(template selector 1), foo=(template selector 2)"; // Fields $selector .= ", bar=(field selector 1), bar=(field selector 2)"; ...is saying "find any pages that match (template selector 1 OR template selector 2) AND (field selector 1 OR field selector 2)".

I've stopped wondering about things like that. There are thousands of rules for mod_security, and 99% of those only make sense for wordpress sites.

Looking forward to the alpha version of Padloper

For small websites, I have used top-level pages as pages, and use child pages as content rows. For larger ones I use the normal pages as pages that can have child pages, and make a Settings page that holds sitewide settings, with theme children, and layouts as children of the theme. I can assign a design row or php code snippet to a page, template, or make it sitewide. You can see some details on my forum post.

Just a brief update today. I’m going to give it another week before bumping the core version, as I don’t think there’s enough changes yet to warrant a version bump. For whatever reason, several of my clients have needed integration with Stripe (payments) over the last few weeks. I’d not worked with it before the last month or so, but now all of the sudden am working with it a lot, because that's what my clients have asked for. I’ve found myself working on four different Stripe integrations on existing PW sites, both Stripe Elements and Stripe Checkout. None of these are for sites that have an actual “store” where they would need a cart, but rather just “pay for your reservation”, “buy this book”, “buy this song”, and “make a donation of $10”, “make a recurring donation”, type things. After doing a few of these, I thought it would make a lot of sense to have this built into FormBuilder, which would save us time on this stuff. So this week I built Stripe support into FormBuilder (using the Stripe Elements API). It’s already fully functional, so I will be releasing a new version of FormBuilder with this capability quite soon. To add a Stripe payment input to your form you just add a new field of type “Stripe payment for FormBuilder”, and then it asks you for some info about it (like amount to charge) and then your form works as a payment processor. Stripe has a clever way of making this all work, so that the user never leaves your site, but your site (and FormBuilder) never sees credit card numbers or anything like that, so it’s secure and you don’t have to consider things like PCI compliance. I've also got some other unrelated updates for FormBuilder that I'll be covering soon as well. Have a great weekend!

There is a module in Ruby called Deface which is widely used in an ecommerce system called Spree: https://github.com/spree/deface It's been around for a while. "Deface is a library that allows you to customize HTML (ERB, Haml and Slim) views in a Rails application without editing the underlying view." MarkupRegions essentially works in a similar way. It's a bit of a shift in thinking but it's quite nice if you set things up the right way. I'm experimenting with a site profile that takes this approach extensively. How have you used MarkupRegions in creative ways?

I don't have much time to review these. Not sure if it helps, but here's some of my notes: Online Editors https://c9.io/ - Amazon’s Cloud 9 https://www.koding.com/ - can work on local files and sync remotely https://codeanywhere.com/ https://codenvy.io https://coder.com/ https://gitpod.io - open any github page in an online VScode editor that can create a pull request back to github. Uses Docker. Prefix any github page with https://gitpod.io# ex. https://gitpod.io#https://github.com/arunoda/learnnextjs-demo Test and Share code - Web based IDE https://codesandbox.io/ - can install VSCode extensions see https://hackernoon.com/announcing-codesandbox-v3-4febbaba1963 https://stackblitz.com/ - online VSCode Editor than can run react like CodePen https://repl.it/ https://hyperdev.com/ - like http://plnkr.co/ but better to test and share your code https://snack.expo.io/ https://codio.com/ - full dev stack testing https://glitch.com/ http://runnable.com/ http://codepen.io/ https://codepicnic.com - ex. https://codepicnic.com/posts/that-moment-when-i-showed-my-students-how-to-bring-their-code-to-life-bd686fd640be98efaae0091fa301e613 Maybe one of these would fit your needs?

Good points! Htacces changes are very rare anyhow, so that would be totally fine. I'll think of that option in the future ?

pwFoo your uploaded image is broken

Recently I have been trying to improve the user friendliness of various page select fields, including single select and checkboxes. The issue comes down to the fact that if say for example you have a single checkbox, you can explain what the effect of checking that box is. But if you are using checkboxes on a page select field, there is no way to have any extended information about the option. An example of where something like this is already in use is on the Status field - each option has the title of the option, e.g. Unpublished, and then additional info, like "Not visible on site". Currently my solution is to use a custom inputfield that extends the primary inputfield, which extends the attributes for each option, and then use javascript for handling the display. On checkboxes, adding uk-tooltip to the checkbox labels with the data-description on the option becoming the tooltip content. (see screenshot below) On single selects, i have some JS replace the field description with the info about the selected option. (see screenshot). The reason i'm posting this here is to see if there is any simpler/better way to do this, e.g. hook into the creation of the options for any page field and add the custom attributes, without having to change the inputfield type. And i thought this could be a good candidate for AOS. To better illustrate how it works, i have included some screenshots and links to the repos for the select extended and checkboxes extended. Select Extended: nothing selected Option selected, with option's description showing: https://github.com/outflux3/InputfieldSelectExtended ----- Checkboxes Extended hovering over any option shows the option's description: https://github.com/outflux3/InputfieldCheckboxesExtended

It only loads the defined .htaccess.local files. The regular .htaccess files are completly ignored. Yes, you may need to copy all locally required parts from regular to local AccessFiles. But I locally work with the pw distri htaccess file. I don‘t want to have settings included for caching or for ProCache. Also rewrites for different domain names to one final domain etc. only stays in the online file. Nothing of that is needed or explicitly must be avoided locally. Maintaining the .htaccess for online deploy exclusivly and add .htaccess.local to the .gitignore. ?

ProFields (especially Matrix Field) and ProCache.

+1 Version: DEV (3.0.130) AdminTheme: Uikit - defaults

Try commenting that line above in again and change Rewrite base to / . Another thing... reload after login attempt without error... it had this in my Brave browser a few days back. Its settings didn't allow JS, cookies and almost everything else. You could try another browser or less strict privacy settings as well. Which ProcessWire and PHP version are you using? Was it a blank intallation or a profile with modules or anything else?

I had the old one also installed and the keywords were in the templates. Now it works great thanks

There are predefined system permissions for this - you just have to install them: https://processwire.com/docs/user-access/permissions/#page-edit-created https://processwire.com/docs/user-access/permissions/#page-edit-trash-created

There are multiple pages existing in the example above, so yes it does work. I saw your post in the other thread - the problem is that you are using a single unnamed OR-group for all your selectors. Only one parenthesised selector in the OR-group has to match. So when you do... $selector = "(template=home|basic-page|product-category, status!=hidden), (template=news-item|product-page)"; ...this means that any unhidden page with the home, basic-page or product-category template and any page with the news-item or product-page template will match regardless of any other selectors you later add to the same OR-group. Have another look at the documentation for OR-groups and try giving names to the different OR-groups for template and field values.

I have not installed this module and I have the same problem. On my current installation I have only installed a few modules. So I guess it has nothing to do with other modules.

I think is an issue when the module Helper Field Links is installed with SeoMaestro Note on the left screen, each field has display issues with the field name. I could probably hide it with some CSS but wondered if you'd consider making it work out of the box.

I do it this way: $t = $this->database->query("DELETE FROM MarkupActivityLog WHERE `page_id` = $page->id");