teppo

Looks great Marcus, I'm looking forward to trying this out! Just thinking out loud, but you could, perhaps, simplify this a bit without sacrificing any flexibility: // the sprintf way echo $flags->renderLink("Add %s to flags", "Remove %s from flags"); // the placeholder way echo $flags->renderLink("Add {flag} to flags", "Remove {flag} from flags");

Thanks Adrian! This has been on my to-do list for a while, looks like I can tick it off now. Benefits of free software -- just wait long enough and someone will solve it for you The way I've seen this implemented before was a checkbox titled "Force password change on next login", which was unchecked when a password was changed. That would slightly simplify things by removing the need to check it for existing users.. and perhaps make things a bit easier to understand if you want to use it at some point later (for some reason unchecking "password changed" sounds weird). Just saying, doesn't matter much either way. The module looks great and I look forward to using it.. on all of our sites Edit: by the way, would you mind specifying a license for this module? I'm not suspicious of your motives or anything (honestly), it's just that I try to avoid any code where licensing isn't clearly stated, and modules are no exception here

@Macrura: I've just pushed 1.0.4 to GitHub. This version drops saveReady hook in favour of ___processInput() method. This actually eliminates the need to throw any exceptions, as the module can simply use current value and continue saving the page. Hope this helps -- and hope it doesn't cause any additional issues either. I've tested it in my own environment and everything seems to work just fine, but please let me know if anything goes wrong!

Just checking: are you trying to embed actual Admin UI (the admin tool you use to manage PW content with a browser) within Phalcon's admin pages? That's the idea I'm getting from your post and if that's the case, it has very little to do with API and bootstrapping. By bootstrapping you gain access to ProcessWire's content via API, i.e. you can use wire('pages')->find('...') etc. in external code. Admin, on the other hand, is best described as an application built on top of ProcessWire's core (and thus it itself uses the API that ProcessWire provides). If you want to embed the entire admin tool into another application, you've got several options: embed entire admin tool with an iframe (not exactly a pretty method, even though individual pages in ProcessWire's admin can actually be embedded as "modal" views by using GET param 'modal', e.g. example.com/processwire/page/?modal=1) redirect users to said URL directly (if I'm reading you correctly, this is what you're doing right now) create a custom admin page to the ProcessWire site for managing content and embed that (most likely still using an iframe) create a custom application within Phalcon's admin page that bootstraps ProcessWire and uses it's API to manage content (this would probably be the cleanest solution, but I've no idea how Phalcon really works so can't really provide any additional pointers)

No, not by an URL. That'd be a huge security issue, among other problems, since by bootstrapping ProcessWire your script essentially gains superuser permissions.. Bootstrapping generally requires the sites to be on same server, so as long as that's true this isn't a problem. If they're hosted on different environments, you'll have to mock up a public API of sorts to share data, provide views that are embedded via iframes.. or use Pages Web Service to connect the sites.

@Neeks: which ProcessWire version are you using? WireMail was introduced in ProcessWire 2.4.1, which means that you still need current dev branch to run it. I'm assuming that this is the problem. Either that, or there's something wrong with your ProcessWire installation (less likely).

Anyone who has told you that you are The big lebowski? I like to create graphics that is all. I can see the resemblance.

@djr: first of all, welcome to the forum! Very interesting first post you've got there I may be the wrong person to comment on this, as I haven't had much time to think about these kind of changes (too busy building stuff on ProcessWire to spend time thinking what to change about it, I guess) but your idea made me wonder .. how could selectors work properly with such a structure (not knowing for sure that a specific field behaves same in different places sounds like a problem) and what kind of effect would it have to scalability and performance (I'd imagine this leading to tables with hundreds of thousands or millions of rows quite easily, which could become an issue considering overall speed, indexes etc.) Current database structure works quite well in both respects, so this is definitely something that would have to be considered carefully. Other than that, I'm actually not entirely sure that we're on the same page here about some of the things you've mentioned in your post: You mentioned that this way fields wouldn't "have to be global constructs", yet I see that as a good thing. Reusable fields rather than page-specific ones. I'm not entirely sure that I'd prefer to have field schema on the disk, even if it makes duplicating that schema in another installation in some ways easier. One of the key strengths about ProcessWire, in my use cases, is that I can very rapidly build new data structures with the admin tools it provides. How well would that be in line with having that structure as files on disk, I wonder? They're definitely not mutually exclusive things, but don't seem to fit that well together either (though perhaps it's just that I can't see it yet!) Anyway, interesting idea and definitely a good thought provoker

@Craig: that's a good idea and the script looks OK to me. Just some quick observations: This doesn't seem to replace index.php, which does sometimes change (though very, very rarely, so perhaps not a problem at all) Same thing with .htaccess, which could be even more problematic, since each site may have custom settings here (diff+notice?) Also, if you're hosting multiple PW sites in the same location, generally speaking I'd suggest shared wire directories. Symlinks are good for that. This is what I've done to make upgrading a larg(e/ish) amount of sites at once feasible. Anyway, great to see how others are solving this

Thanks, added

@Manfred62, I posted a new thread here: https://processwire.com/talk/topic/6850-module-inputfield-trumbowyg/. Is it OK if I add your translation to the langs directory of the module?

This is an inputfield module integrating Trumbowyg WYSIWYG editor into ProcessWire, quickly hacked together after some discussion at the Redactor thread. Trumbowyg is a light-weight alternative to more feature-rich editors, such as CKEditor or TinyMCE. Both this module and Trumbowyg itself are still in alpha state. Customisation options include only a subset of what Trumbowyg provides, more will be added in the near future. Also, link and image features as seen in other RTE modules (TinyMCE and CKEditor) are not implemented yet. The module is available at https://github.com/teppokoivula/InputfieldTrumbowyg.

@adrian: I'll take a closer look at that tab issue soon. About the link dialog, I'm not really sure -- it's probably the same thing as with image dialog, that it should be replaced. Too bad, since these super-clean dialogs are part of what makes Trumbowyg such a pleasure to use The scope of Trumbowyg seems pretty limited for the time being and for an example I haven't yet found any 3rd party plugins for it (regarding paste buttons and "pretty" code formatting). I'll take a closer look ASAP and see if there's anything available, otherwise might have to cook something up myself. In the meantime I've added some basic config options to the module. Edit: tab issue should be gone now. Forced higher z-index value to fullscreen Trumbowyg editors.

@Manfred62: https://github.com/teppokoivula/InputfieldTrumbowyg. Just for testing, though, it's far from polished (mostly just a quick fork of InputfieldCKEditor with 90% of everything stripped off). What I'm not really sure about, should this become a "finished" module, is how the images should be handled? Trumbowygs default image tool is clean and pretty, but doesn't really make sense in ProcessWire, so I'm thinking that the image plugin from other RTE's should probably be ported here or something like that..

@dazzyweb: I'd assume so too.. at least as long as you're willing to swallow their other requirements, such as the "fair use" clause accompanied by statement that they alone decide what this "fair use" consists of. I for one wouldn't, but that's just a my personal opinion. There's a whole world of difference between proprietary and free software and I know which side I prefer