adrian

That profile is pretty old now. Why not try this instead: http://modules.processwire.com/modules/process-blog/

Sorry for the quick follow up. The latest version now supports non-contiguous and partial line selections, so now you can do this: Note the partial line selections in this example:

This is a minor change, but I am actually really excited by it The Console panel now supports running just the selected code. I often find myself using the Console panel to test variations of code to see which is faster / more efficient. The time and memory usage is displayed after each request, but it's often a bit of a pain to keep commenting out some of the code, testing it, and then uncommenting that and commenting out the other, etc. Now you can have multiple functional bits of code and just run one at a time. You can see in these examples that I am selecting different chunks of code to be run and I can clearly see which one uses more time and memory.

Page Protector doesn't require access to the admin to work. It's easy to create your own logout link (https://processwire.com/talk/topic/684-client-logout-page/). Page Protector lets you style the login page however you want

Of course: $page->of(false); $page->phone->country = '1'; $page->phone->area_code = '123'; $page->phone->number = '4567890'; $page->phone->extension = '987'; $page->save('phone');

Hi everyone, Relatively major new version just released: 1) New run on init, ready, finished option in Console panel I am not sure how popular this will be, but it lets you inject code from the Console panel into the PW process at init, ready, or finished. This lets you test hooks and other code that you would normally add to the init.php, ready.php, or finished.php files without having to edit files, and also without affecting anyone else viewing or working on the site. This screenshot should give you the idea: As you can see, I have added a hook to change the page title on saveReady. The way it currently works is that you: enter your code click Run to "register" the code for the next page request select "init", "ready", or "finished" as the place to have it injected In this example, you would then save the current page and the hook would be injected into init() and the page title will change If you don't switch back to "off" when you are done testing, it will expire in 5 minutes. The Console panel icon will also change to a red color to provide a visual indicator that you have an injection running on each page request. Please give me feedback on this feature - if you guys are annoyed by having those options visible and you never plan on using this, I'll make it an option that can be turned off completely. 2) Make User Switcher available without setting to "DEVELOPMENT" mode When I initially built the User Switcher I was a little paranoid about the possible security implications so went a little overboard by making it only available when hardcoded to DEVELOPMENT mode. But in reality this didn't make any difference and just made it more difficult to use, so now you'll find it easier to use - it's such a great feature! If you haven't used it, give it a go! 3) Options to hide debug bar from Form Builder iframe Having the debug bar in a Form Builder iframe can be useful, but also a visual annoyance so now you can disable if you want. 4) Hide User Bar from Form Builder iframe This is automatic as there is no reason for the User Bar to appear in a Form Builder iframe and it is confusing for users and ugly. 5) Restricted panels now works with "tracy-restricted-panels" role as well as permission (needed due to recent PW core change) Due to a recent change in the PW core, it is no longer possible to edit the permissions for the superuser role, so I have now added support for assigning a "tracy-restricted-panels" role to a user. The "Restricted Panels" defined will then be applied to users with this role. The permission option will continue to work for other non-superusers. 6) ACE editor update 7) Other bug fixes / tweaks

@Robin S - I don't want to hijack @horst's thread here much more, but I think we are basically in agreement. My desire for custom permissions for superusers wouldn't be needed if we could assign some currently superuser only permissions to other roles. I think basically there is a level of control here that is currently missing and there are different ways of tackling it - the problem is that the one option we had (adding permissions to the superuser role) is now gone. I guess the workaround is to change these custom "permissions" to "roles". So for ALIF, horst could require a user has the "alif-user-account-switcher" role.

@horst - this is the issue that led to that change: https://github.com/processwire/processwire-issues/issues/371 I actually don't like the result - I think it's a reasonable scenario to add additional permissions to the superuser role and do an actual check for these. I use the same technique in Tracy, which I guess is also broken now.

Just an FYI, that a recent change to the core might make this impossible to do via the admin: https://github.com/processwire/processwire/commit/7943aa1064204db5415d661312037f1dd4199249

I just tested like this (clicked on the "Child Tab" link in the console results) and it works fine so long as I am not already on the page that is linked to.

Latest available on Github (and what you'll get if you upgrade), but not actually the latest, necessarily. I am actually confused by the changelog in AOS - the dates for 1.6.71 a 1.6.7.2 are out of order - but again, this really is an unusual situation. Anyway, I really wouldn't worry too much about any of this - it was really just meant as an example of things to look out for - I don't really think anything needs changing.

Not sure it's quite right, but what about "Upgrade to:" as the label? Or some other way to highlight it as what you'll be upgrading to, rather than it being the latest available?

Maybe the "Latest" tag isn't needed? Perhaps all that is relevant is the "Installed" tag. The issue with AOS is a mistaken version number 1.6.71 (I think @tpr intended 1.6.7.1). The more likely scenario is what you described where you might have a version that is newer, but not published yet - that can happen relatively often.

You're right, it was Tracy (not ModuleSettingsImportExport) that was the problem - I knew I had fixed that issue recently, but forgot in which module Again, sorry for the hassle with this!

I don't remember how it was before, but is this what you are expecting in this scenario? I actually think it probably is the right way to go, but just wanting to make sure you had seen this issue with AOS.

@flydev - are you running the latest version of ModuleSetttingsImportExport? There was a bug that caused this in older version - sorry about that!

Have you tried without the trailing comma?

Hey @Macrura - it might be worth describing how you are defining the matches and if it's the custom PHP code option, then post that. I have used this module without any problems, but I haven't pushed it with complex matching.

This forum is just an IPBoard forum - no PW code or use of this module. Good thought though

I haven't tested, but youtube.be should work: https://github.com/ryancramerdesign/TextformatterVideoEmbed/blob/7c8e4ddce22dc4970c17d0f63ce3d53679e7e3a8/TextformatterVideoEmbed.module#L163 Here's it working as expected: https://regex101.com/r/aEcLl2/1

Hi @mel47 - thanks for raising the issue here, but let's continue it in the FormBuilder thread where we will get more of Ryan's input

Here's the code block: https://github.com/processwire/processwire/blob/57b297fd1d828961b20ef29782012f75957d6886/wire/modules/Process/ProcessModule/ProcessModule.module#L309-L327 In case you don't know, it is called when you do a Modules > Refresh

Looks like this should be fixed now: https://github.com/processwire/processwire/commit/337e59663ba17af1083bd91edbb9a3a051da8994

Hi @rick - maybe take a look at ProcessAdminActions which uses tabs. See how I add the wireTabs class to an InputfieldWrapper https://github.com/adrianbj/ProcessAdminActions/blob/f85e537f72fdfce299cf0c2c22366a290049f664/ProcessAdminActions.module#L337-L340

Great looking site, but clicking the images doesn't work for me: