Leaderboard

Hi Kathleen! Welcome to the forums. For the blogposts pages content, you need to import the database from the server. But for the assets (files folder inside templates/assets/) there's a technique to get them using hooks like Ryan shows on his post: https://processwire.com/blog/posts/pw-3.0.137/

v0.1.10 released. Now that new core ways of setting field widths in template context have been introduced it seems that users are sometimes setting a field width using a core input and then saving the Edit Template form. Although it's not necessary to save the Edit Template form after adjusting a field width using a core input (those settings are AJAX-saved), it's not unlikely that users will do this and in these circumstances the old width stored in the Template Field Widths inputfield was overwriting the new width. So from v0.1.10 onward the widths entered into the Template Field Widths inputfield are only saved if Edit Template is saved with the Template Field Widths inputfield in a open state. And it's recommended to use the default "Collapsed" config option for Template Field Widths if you think you might also use core inputs for setting field widths.

? @justb3a Good luck on your (new) way and many, many thanks for all your contributions !! ? ❤️ ?

hi, as you might noticed I'm no longer active in the field of PHP and ProcessWire. I tried to continue supporting my modules and wireshell but it turned out that it just doesn't work well if you don't work with it yourself anymore. I would be very happy if someone would be interested in taking over and developing this further. Just write me a message. ? ?

Awesome, works great!

I am noting that you can only use or the other - you can't combine exclude and include. So the AND/OR is within each option, not between. I think it's the typical AND/OR issue when you're using the (!) NOT operator - you need to switch from OR to AND. So, the selector for exclude is: roles!=1021, roles!=38 And the one for include is: roles=1021|38 Anyway, I have committed a new version with this functionality - please test and let me know how it goes.

Hi @Robin S - happy to add this. Just playing around with it now and I guess the main issue is that when "including" we need to go with "OR" when matching users to roles, but I think we still want "AND" with "excluded (restricted) roles". Because you want to be able to include different admin roles but not require the users to have all these roles. But if you want to exclude/restrict like the current behavior, then you want to exclude all users with any of the selected rules. Does that seem like the correct behavior to you?

Thanks. I've already used your tutorial on building custom admin pages and found it really helpful. Rockfinder2 + RockTabulator are new to me, but it looks like they'll do what I want.

@Sevarf2 thanks for giving it a try. I'll try to reproduce your error in the next days, maybe I can find a solution. sorry for your troubles.

Yes, there is a way. Just go to permissions -> add new permission. Then under "Install predefined system permissions" choose "page-edit-created" and maybe even "page-edit-trash-created" if you would like that users can trash their own created pages. After saving, add those permissions to the role/s you want to restrict. I did not checked if this is working in the Frontend editor or Fredi, it is working in the ProcessWire admin.

This should be pinned! It's Awesome! ?

Hi everyone, Sorry for the silence on this thread. This module is now generously being managed and updated by @wbmnfktr - I have updated the modules directory entry to point to his fork. I am sure he will be able to better support and improve this module than I can.

Thanks @teppo – have reviewed and merged in with some minor UI/textual adjustments to the config. Tested it too, works great! ?

Sorry @Mike Rockett – got caught up with other stuff (surprise) and forgot about this ? I've just sent a merge request for WireCache support. It's an alternative to existing MarkupCache cache method, configurable via module settings. I've also made cache TTL (expire time) configurable: https://gitlab.com/rockettpw/seo/markup-sitemap/merge_requests/1. Let me know what you think ?

After a little tweaking, I was able to get the access token back from Instagram. Using the post by @AndZyk as a starting point, I removed the following line from the module code: 'scope' => 'public_content' Instagram returned the access token successfully.

Hmm Strange get still {"error_type": "OAuthException", "code": 400, "error_message": "Only response type \"code\" and \"token\" is allowed"} OKAY IT WORKS. There was a empty space on the end from URL Thanks a lot

And here we go again… 0.6.1 is out now: Everyone is going green, only AdminThemeBoss was somehow missing the trend… So this new version fixes this glaring oversight ? New «Smooth Green» color scheme ? Fixed: Small issues with asmSelect entries Fixed: Mobile view with AOS ? Get Release Notifications ProcessWire Modules Repository Gitlab & Issues

Hallo everyone ? I have just release AdminThemeBoss 0.6.0: Introducing, a refined, more colorfull and streamlined expirience: Added: more colors ? Added: improved notifications ? Added: improved dropdows ⬇️ Added: improved integration with third party modules like ProDrafts, AOS and ASM… ? Under the hood improvements on how settings are saved and applied Fixed: Some minor bugs ??

You can use this to resize via mouse (using jQuery UI Resizable which seems to be present in the PW admin). I haven't checked fieldsets, I've updated the code, it's working fine with fieldsets too.

You can hook into ProcessPageEdit::buildForm and modify its arguments. You can add readonly attribute to all text fields (disabled works too), remove submit buttons and disable uploads. wire()->addHook('ProcessPageEdit::buildForm', function (HookEvent $e) { $editorRoles = ['senior', 'marketing', 'office-management']; foreach ($editorRoles as $role) { if (wire()->user->hasRole($role)) return; } // set all text fields readonly $form = $e->arguments(0); foreach ($form->find("type%=text") as $ta) { $ta->attr('readonly', true); } // remove submit buttons foreach ($form->find("type%=submit") as $button) { $form->remove($button); } // disable uploads foreach ($form->find("name%=image|file") as $uploadable) { $uploadable->noUpload = true; } }); But removing submit buttons leaves dropdown items behind which I think is added with JS, so you may need use JS to remove it. (I'm using AdminThemeUIKit, other themes might be different) [].forEach.call(document.querySelectorAll('.pw-button-dropdown'), dd => dd.parentNode.removeChild(dd)); I'm not sure about other fields, though.

One thing I'm going to be working on soon is adapting Trellis to ProcessWire. If any of you saw my video on adapting Sage for ProcessWire, Trellis is a project by the same group of people (Roots) which allows for you to setup an excellent development + staging + production environment using Ansible (and Vagrant for the development environment). Because of the similarities between WordPress and ProcessWire (well, in terms of the server stack required and the fact that they are both CMSes), a lot can be borrowed from their setup in terms of approach and techniques. They use WP-CLI for some things, but Wireshell can be swapped out for that nicely from what I've researched. I'm really excited to see how it turns out because this has been a huge missing piece to my workflow. This approach would replace things like Capistrano and any other deployment methods, assuming you use a dedicated VM for a site. I highly recommend checking out Trellis to see how it's done. It's thought out very well.