Leaderboard

Hello ProcessWire community At first I like to thank and congratulate Ryan for this wonderful work and I wished that I knew Ryan a long time ago And by the way you look awesome in the overview video Ryan And now a little bet about me: My name is Faisal Halwan from Saudi Arabia. I work in web development over 14 years now, and have dealt with various content management systems and PHP scripts in general. I was always dreamed of a flexible content management system for use in almost anything or what is now called CMF or allow me to say ProcessWire Thank you Ryan, you make my dream came true Yet I couldn't find any result in for any Arabic article talking about ProcessWire I will do my best to present ProcessWire and provide support in Arabic as soon as possible. Thank you and keep up the good work

How open to some input/diversion are you, seems like building a new theme should have had a community discussion before hand. Maybe the work could even have been off loaded to a "GUI task-force" of sorts? I feel like the end result could benefit from more open brainstorming and discussion. Not to say I don't like this theme, but with all the great themes already in existence it's apparent there are a lot of great ideas floating around out there... anyway don't mind me I'm insanely picky. this is.comunitey discushion no ? there anothor page u.missed page.1:: ... i make willyC colors schemos.too ok.to poopst in here ?

I have just finished and uploaded new layout of the MSSOOnline website. http://mssoonline.org/ I used latest ProcessWire and HTMK Kickstart to develop this website for not-for-profit organization. This is another not-for-profit website I developed with ProcessWire CMS as volunteering work. I love ProcessWire so much that I keep creating website for free for charities!!! Please provide your feedback for improvement or to fix any issues.

This, or upgrade to the new TinyMCE v4? Theme is a nice improvement, though some things like the insanely small PageListActions still worry me (I've had clients complain about the size of these in my themes and I've never gone below 12px). How open to some input/diversion are you, seems like building a new theme should have had a community discussion before hand. Maybe the work could even have been off loaded to a "GUI task-force" of sorts? I feel like the end result could benefit from more open brainstorming and discussion. Not to say I don't like this theme, but with all the great themes already in existence it's apparent there are a lot of great ideas floating around out there... anyway don't mind me I'm insanely picky.

What you did earlier for table "field_body" was correct - I was trying to say don't apply the same fix blindly to all keys named "data" as they're not all the same. So, for table "field_body" change "KEY `data` ( `data` )" to "FULLTEXT KEY `data` ( `data` )" (as column "data" is of type MEDIUMTEXT in that table). But for table "field_display_specialty_footer" leave the key to what it was ("KEY `data` ( `data` , `pages_id` , `sort` )") as column "data" is not of type TEXT/BLOB there.

For those interested for now, I created a github repo along with some description how to install and use it: https://github.com/somatonic/BlocksContent Thanks

This must be one of the best ProcessWire quotes ever. Just saying.

And another small update for "lateLoad" which is useful for deferring the loading of third party html/scripts/images. https://github.com/jdart/Spex#lateload

Hi, Diegonella. Try to use this module. Put it in your site/modules folder. Your fieldtype for transaction number has to be a textarea. After you've installed the module, select InputfieldTextareaLookup for your transaction number fieldtype on it's Input tab. Now your field will display as a paragraph so user won't change it. Please, let me know if it works as I didn't test it. Cheers! InputfieldTextareaLookup.module

Lately there have been lots of people that are not enjoying the default admin theme, so we've been working on making something new. Not trying to solve all issues or add every new feature we'd like, but just trying to come up with something to have as an interim replacement for the default admin theme until we can afford the time to do something broader in scope (like Phillip Reiner's great admin theme design for example). So this theme doesn't necessarily break a lot of new ground, but hopefully has some of the improvements that people are looking for. Visually, the goal here was to find a lighter, more modern look and reduce the boxes-in-boxes feel of the current admin theme. I've opted to commit it to the dev branch because it requires the latest version of ProcessWire on the dev branch, and likely will continue to with updates. Meaning, I can't distribute this one as a 3rd party theme very easily. This is because I'm making core updates related to the admin theme at the same time. So if you want to help test this new theme, you'll need to grab the dev branch of ProcessWire. The new admin theme is in /site-default/templates-admin/. That means you'll see it as the default theme if you are installing a new copy of PW. But if upgrading an existing copy, you'll continue to get the old theme. If you want the new theme, then just copy the /site-default/templates-admin/ directory to your /site/templates-admin/ directory on your existing PW install. This would be in addition to replacing your /wire/ directory with the latest one from dev, as usual for PW upgrades. The existing default admin theme also remains in place in /wire/templates-admin/. So if you want to stick with the existing/stable admin theme, then just make sure you don't have a /site/templates-admin/ dir in place (unless you are using a 3rd party admin theme). This admin theme is probably not production ready, as it's not been tested in many browsers yet. I personally haven't yet tested it in anything but Chrome and Firefox in OS X. Please let me know if you experience issues in other browsers. I fully expect things won't be pretty in IE... but they never are. To start, this comes with 3 color schemes (though we'll be adding more too): Warm: Modern (similar to processwire.com site colors): Classic (similar to existing admin theme colors): To switch to one color theme or the other, specify a GET variable of 'colors' in any URL you are accessing in the admin: /processwire/?colors=warm /processwire/?colors=modern /processwire/?colors=classic To specify a default, edit your /site/config.php and set to one of the following: $config->adminThemeColors = 'warm'; $config->adminThemeColors = 'modern'; $config->adminThemeColors = 'classic'; We'll probably make this switchable in the user profile at some point, but that comes later. This theme also comes with some new features (most of which have been copied/inspired from the work of others here, whether in other admin themes, modules or designs): It now uses Font-Awesome icons rather than jQuery UI icons. We now only use jQuery UI icons for actual jQuery UI widgets. Note that asmSelect and our file/image inputfields are built as jQuery UI widgets, but I don't think anything else is. Basically, the majority of icons in the system are now Font-Awesome icons. You can associate Font Awesome icons with templates. When associated with a template, the icons will appear in the page list, in front of the page title. To use this, edit any template and go to the Advanced tab. In the "List of fields to show in admin page list", you can type in any Font Awesome icon name (in addition to the field names you could before). For example, in the Page List screenshots above, I have my "search" template configured with the value: "icon-search title". You can associate Font Awesome icons with fields. When associated with a field, the icon will appear at the beginning of the input. For example, I associated a coffee icon with my "title" field in the screenshot below. To do this, edit the field, click on the Advanced tab, and enter the icon name in the new field provided for it. The top navigation now supports simple dropdowns. A new "user" dropdown has also been added that contains profile and logout links. The main Pages screen contains an "add new..." button, that is itself a dropdown to a list of templates that are configured adequately for us to know where they would be added. To use this, you have to configure your template "family" settings. The search box is now ajax powered, though this was introduced a couple weeks ago in the existing admin theme too. The theme is responsive too, of course. This is all kind of preliminary and open to changes. I'm trying to keep the scope of the project fairly small since I don't have much time to work on it. But just wanted something to quiet the haters a bit for a little while, so that we can take our time on the bigger admin theme project for longer term. We'd appreciate your feedback if anyone has time to help test.

So, I've been seeing some email-related topics around here and actually had quite a few struggles of my own with this very subject myself lately. Thing is that sending email should be easy, but it's not always that; especially for those who have to work on multiple, low-price (and regrettably often low-quality) platforms that may or may not provide proper mail servers.. or prefer to host their services themselves and still want to avoid setting up and maintaining a mail server. Hosting a mail server can be real pain in the ass when things don't work like they should, not to mention that most people have very little knowledge about DNS entries etc. this requires. Anyway, long story short: yesterday I started thinking that wouldn't it be sweet to have a layer of abstraction within ProcessWire for sending email? Of course one could still use PHP mail() -- there's no way and no sense in even trying to stop that -- but using a common gateway would definitely bring in some extra value. This layer I'm talking about could by default use built-in PHP mail() but also make it possible to override it, thus allowing multitude of options that PHP mail(), being bound to Sendmail / it's alternatives, can't offer without additional server-side software (such as Nullmailer.) By making sending emails hookable it could also enable all kinds of interesting tricks to be done when mail is sent -- such as writing a custom log file, sending another email to someone else, updating local content (I'd imagine that this could be useful for building newsletter platform, for an example) and so on. Since words tend to fail me at times like these, I put together a quick proof of concept of what I'm talking about here, accompanied by one example of what could be achieved by doing this: A very simple yet functional Mailer class Two commits on top here list all the changes I've made in my PW fork to make this work -- including the fact that I've altered some default modules to use $mailer->send() instead of mail() SwiftMailer module, again very simple but fully functional (though only tested with Gmail SMTP) drop-in replacement for PHP mail() So, what do you folks think of this? Please keep in mind that this is just a suggestion and I'm not saying that this is the right path to take especially considering that it would add another API variable -- it just felt like best option here and I couldn't think of cleaner way to achieve it.

Things like this confuse me... #masthead, #headline, #content, #footer { padding-right: 20px; padding-left: 20px; } Turning this off has little visual impact and seems redundant to the function that the .container serves, this kind of styling should really be handled by a class anyway. Also the markup and subsequent use of position:absolute; on items in the #masthead seems bizarre to me. If instead you wrap the top and bottom portion of the masthead separately and style them accordingly there is no need to absolute position the elements, simple floats will do. There is also then no need for the #masthead_shade element. <div id="masthead" class="masthead"> <div id="masthead_top"> <div class="container"> <!-- LOGO --> <!-- SEARCH --> </div> </div> <div id="masthead_bottom"> <div class="container"> <!-- NAV --> <!-- BREAD --> </div> </div> </div> With this setup we can create consistent height on the nav and breadcrumbs by simply setting: #masthead_bottom{ background: $masthead-secondary-bg; border-top: $masthead-secondary-border; line-height: 2.5em; } Then the elements just need to be floated. This also wouldn't prevent you from doing what you currently are with the mobile version of the masthead, though you would need to remove the float obvious (although just removing the floats and letting the elements fall in place naturally would be how I would do it). With other small tweaks the difference is minimal (though I prefer CAPS and font-weight:bold; in my nav/pageLinks generally). Oh, I also added outline:none; to the search query, can't stand they way those outlines looks. EDIT: Also the search query is to hard to see, maybe drop the transparentize value to 0.7? #ProcessPageSearchQuery { height: auto; padding: 2px 7px 1px 7px; font-size: 1em; border: 1px solid transparentize($reverse-text-color, 0.7); background: transparent; width: 100%; color: $breadcrumb-link-color; border-radius: $button-radius; outline: none; } EDIT 2 Oh and I increased the PageListItem padding, though this should maybe be handled by line-height .PageListItem { padding: 0.5em 0; }

I just wrote a very tiny grid system I call it FontZero. It's based on inline block and font-size behaviour. Not net tested in IE, but I think IE 7 and below will fail. ( due inline-block ) IE8 will do I guess. Others should play nice & Safari has problems with floating numbers for at least 2 years. Other frameworks have issues with it as well. Please report any issues for IE8+ & any other browser. Example: FZ5 is 1/5 of 100%. FZ9 is 1/9 of 100%. There's the full range from 1 till 12 You can calculate columns: Example for class .FZ11 .FZ11-2 + .FZ11-4 + FZ11-5 = full row 2 + 4 + 5 = 11, for .FZ11 we need 11 to make 100% Example: .FZ2 FZ2-1 + FZ2-1 = full row 1 + 1 = 2, so 100% ( 1/2 * 100 ) + ( 1/2 * 100 ) = 50 + 50 = 100% Advantage over most other grids The code below makes 3 column and 3 rows, no need for row markup, <ul class='FontZero'> <li class='FZ3'><img src='...'></li> <li class='FZ3'><img src='...'></li> <li class='FZ3'><img src='...'></li> <li class='FZ3'><img src='...'></li> <li class='FZ3'><img src='...'></li> <li class='FZ3'><img src='...'></li> <li class='FZ3'><img src='...'></li> <li class='FZ3'><img src='...'></li> <li class='FZ3'><img src='...'></li> </ul>

If we're talking apps i would also like to mention prepros, it does a lot http://alphapixels.com/prepros/ If we're talking apps i would also like to mention prepros, it does a lot http://alphapixels.com/prepros/

That's fine with me, though it doesn't necessarily have to be on GitHub. I think it's just as easy to post any new SCSS file(s) in here along with a screenshot of what's proposed. I think there was a bug in there when I first posted it related to this (colors switching back to main). I did fix it and think (hopefully) that was fixed in yesterday's commits.

@adamspruijt, yes please submit any feedback you'd like, that's what this thread is for. I would just request that any feedback be based on actual use/testing the theme itself rather than the screenshots, as the screenshots are fairly limited in scope relative to the theme. We may have to wait to act on some of the feedback until we approach the bigger admin-theme project in the future, but all feedback is appreciated either way. For instance, if there is a consensus that the page list actions are too small, I'll be glad to increase the default size of them. That's also a fairly simple thing to do. Chances are that the value in your session was already set to something, and the session value overrides the $config value. To resolve that, just set your session value to match the $config value, or clear out the session value by specifying an unknown color theme. /processwire/?colors=classic /processwire/?colors=poopst I'm not sure that I like the sound of that, but if you mean post a color theme file here that's great.

No need to hack anything. Check out Image Interceptor: http://modules.processwire.com/modules/textformatter-image-interceptor/ That will take care of the resizing and can also add a class to the image that can be used to trigger a call to your lightbox script.

just an idea: make CKEditor to the new default RTE?

It doesn't sound like a DB migration issue, it really sounds like a file migration issue. My best guess is either: 1) File permissions on your Hanna code modules rendered it unreadable to your web server; or 2) that you had Hanna code installed as a symlink on your source server, and the symlink didn't migrate or didn't match up on the target server. That would explain why you'd have a Hanna Code Setup menu item and DB entries, but no ability to run it. Installing through Modules manager would have fixed it since it knows to install the files into the right place with the right permissions, etc.

That sounds like an interesting idea, but that's not currently possible. When PW bootstraps, it loads several things from the database into memory, like template and field definitions, etc. When you make another database connection, you are just connecting to another database and not bootstrapping all of PW.

The grid view is primarily for sorting or seeing it all at a glance. It's not a great view for entering content. This is not meant to replace the existing list view, just provide an alternate that you can toggle when it suits your need. In my case, a client needed the ability to sort large groups of photos more easily, so I made the grid view primarily for that reason. Currently it starts out in list view but provides the little icon at the top that lets you switch to grid view. I'm not sure it'd be good to start in grid view just because you can't delete or enter description/tags... though you can upload. I've not tried it yet, but I'm also assuming that the grid view would hide any options for the Thumbnails/CropImage module as well. But if there's demand for starting out in grid view, I'm open to adding the option. It's just that the grid view is fairly targeted towards sorting rather than general management. Down the road, we may be able to add more options to the grid view too. Thanks, it looks like that could happen if there is a leftover parent template ID for a template that has been deleted. I've added a check for this so it'll appear on dev later today.

Glad you were able to get it working! The problem must have been there in the source database (can't see why it could have worked like that there though..) or then it got introduced during the export process. This answer in SO explains why MySQL didn't like the key definitions you had, but where they originally came from remains a mystery.

Just wanted to mention, I made first little update to show the select dropdown again (was set hidden with JS before) just for now. I made last minute changes and haven't really thought about it, that I just had a case where the block was lost and I couldn't reselect it. Updated readme with some additional infos. That being said, consider current state early alpha and a start to get a feeling if this would work out all well. Still many details that need to be addressed. Thanks

Welcome to PW ralberts. This is possible by default with: Language alternate fields

Coming back to this. As mentioned I'm hard thinking a brewing something since a long time, just haven't been able to pull it off yet. It's often good to wait and sometimes it just makes click, also growing with PW and it's ability can make a big difference. Yes even I am still learning, I got something I think would be a good way to build flexible content blocks, it's just not that far yet to really release it. What Ryan has proposed with iframes sound good in theory but I think would be not a good option at all. It could work but I'm not excited about it because of scalability in the admin, scrolling etc and it would be more of a mad hack with JS IMHO. But the idea with using a page field made sense to me and I was thinking a lot about how to bring the concept I have to the admin, so you can add and edit "blocks" on the page. Until now I only got a really rough proof of concept and was working on front-end only, and not at all complete so you could add blocks etc (I created them manually) After some more testing and coding: So far this is how I got it setup/working: (much like repeaters work) - you create templates for the blocks (partials kinda) - you create a template for the parent page of the blocks in the admin, where you also use family settings to restrict children template to the block templates you create Backend - the module creates a custom page field using the input ASM select multiple, you then add to templates you want to have those blocks - the module sets up a parent page in the admin branch for the page you create with this field - the module hooks into the ASM select to add a "+ Add new block", with a click you open a modal where you have the add page screen and template select. Once create you close the modal and the ASM select will have that new option added. You can sort them as usual - the module enables the editlink modal for the selected blocks (much like selected fields on template context) Front-end - the module uses Fredi and it's own script and markup you can use to render the blocks (simply: echo $blocks->render() - the partial templates are located in a subfolder /blocks where you script the output same as you would with a normal template - the blocks have a little toolbar you can move blocks up and down (saved on the fly via ajax), and a Fredi edit link that lets you open and edit the block in a modal - the idea is that you also could also output the blocks manually As said this is all still rough and slowly taking shape, and many details still need to be taken care of, but just wanted to mention. I think a alpha/beta testing is possible very soon but don't want to make it public until it's more marinated and stable. Also if somebody interested in helping out drop me a message.

Hey Ryan, I am no designer, so take my comments with a grain of salt, but I like the warm color scheme the best - it looks great! The one change I would like to see is the implementation of a sidebar rather than top tabs like the ERGO theme has, but similar to onjegolder's modification: http://processwire.com/talk/topic/1856-release-ergo-admin-template/?p=43471 I love the way the left sidebar tree is expandable for quicker access to items under setup. Of course this could also be done by making the setup menu a dropdown menu (sorry, I see you have already done this - NICE!), but I still prefer sidebars - given our modern widescreen aspect ratios it seems a better use of space. Also, and maybe this is just me, I have always found it easier to move the mouse left and right, rather than up and down - hence I have my OS dock/taskbar on the side, rather than on the bottom. Maybe we need a real UI expert to chime in Maybe a little off-topic, but I have also been wondering if maybe it is time to have a new "Tools" item in addition to "Setup" where modules can place their interfaces if it would be more appropriate.

I added a check at that place for and you might want to get the following module file and let me know if it's gone. But as said I don't understand, that when it gets that far there's should be a object. Can you tell what file or image field there is where it throws the notice, maybe I understand little more. But nothing dramatic. ChromePhpLogger.module

I'm seeing certain similarities with another thread, http://processwire.com/talk/topic/3530-most-selector-operators-throwing-errors/. Even the exception matches that thread perfectly. There's no "*=" or "%=" with page type field (just like that exception says.) It's not a bug or missing feature either, it's just that there's no need for such an operator. With page type fields "=" simply checks if page field value contains a value, not if it's equal to it What Antti pointed out above seems to be exactly what you're after; per your description you've got products with a field "categories" and pages with one category selected and you want to find any products that include that category in their "categories" fields. In this case this should do the trick: $pages->find("categories={$page->category}"); I'd even go as far as say that if it doesn't seem to work, the issue is probably something entirely different. Just to make sure, in your original post you mentioned field "categories" for products and your selector was "category=...", is it possible that something similar (ie. misspelled field name) is the actual issue here?

@Raymond: 1) As a first workaround you may install PiM too, and set $config->imageManipulatorOptions sharpening to none. That way you can leave $config->imageSizerOptions as is, while all CropImages should be handled by PiM (the automaticly created) and with the manual created you need to select none in the dropdown-list. 2) can you send me or upload an example of this black lines/dots noises? There is a BUG in GD-Lib with Alpha-Transparency in PNG. It isn't recognized by some functions.

I quickly created a PW inspired color scheme for Sublime Text with this tool http://tmtheme-editor.herokuapp.com/. You can grab it from Github https://github.com/ocorreiododiogo/ProcessWire-SublimeColorScheme Enjoy! edit: I used the beautiful "Gloom" as starting point

Are you talking about the Markup Cache module? If so, you should be able to use: $cache->removeAll();

Login screen is localized thrue default language. If you want login screen in other language than en, load your non en localization to default language. Before user is logged on, system did not know about users language setting.

Add fields to the user template. In the templates, filter options, show system templates.

Thanks Ryan for looking into this. I can confirm that it works for me in php 5.3.1.

Minor update 1.0.3 to fix delete (move to trash) page button throwing the alert when form was modified before.

Hi Marty, Have you seen the CMS Critic case story Ryan wrote a while back? That seems pretty extensive dive into this subject.

@MatthewSchenker: Thanks a lot. We were searching for a CMS/CMF that completely fits our needs for quite a long time. We used to have our own, properitary CMS but quit developing it for several reasons. Afterwards we were using the usual suspects (Typo3, Wordpress, ModX...) but never were really satisfied with each of them. I think we finally found what we were looking for and will be happy contributing stuff to the community (in fact we've already started to ). @NoDice: If it inspires you that's propably the best thing that can happen. Thanks a lot!

Now available in the modules directory: http://modules.processwire.com/modules/admin-template-columns/

Hi, Since the previous logs showed that the unpublished pages have a publish_until date set to 1970-01-01 01:00:00 which actually is a Unix timestamp 0. Could you please try something for me? Please change line 180 from: if($p->publish_until <= $currenttime) { into if($p->publish_until <= $currenttime AND $p->publish_until > 1) { This would prevent the module from unpublishing pages with the 0 (1970-01-01 01:00:00) value set in the publish until field and should resolve the issue (although it isn't a pretty solution. ) Let me know if it works. If it does, I'll push a new version to Github. /Jasper

I've updated Spex to include support for "slots" and image preloading. Check out the details below: https://github.com/jdart/Spex#slot--hasslot https://github.com/jdart/Spex#addimage I'd also like to add that there are equivalent procedural helpers available that don't require the $spex variable: https://github.com/jdart/Spex#procedural-helpers

I hope so too. But I've got a big GitHub issues list to work through, and a few more new things to polish off, so it may be awhile yet. But rather than waiting, I'd encourage folks to use the dev branch. Though I'm wondering if we might benefit from having another "beta" branch, which would be a variation of the dev branch intended more for official presentation and download links, etc.

Don't you guys get tired of so many frameworks?

it is working using ob_end_clean() that erase the output buffer and turn off output buffering ob_end_clean(); $mpdf = new mPDF(); $mpdf->WriteHTML('<p>Your first taste of creating PDF from HTML</p>'); $mpdf->Output(); exit;

Here's a proof of concept PW Admin Theme Switcher (video and write-up). It shows how versatile PW is. Since everything in the PW tree is a page, including Admin this was easy to do. I think on the roadmap PW will eventually allow switching between Admin Themes? Anyway, here's how I did it (verbosity below is intentional ). This is not a module but can easily be converted into one. Currently, I don't plan to do so since I suspect it will be overtaken by events (roadmap). Instead, I used the excellent Admin Custom Pages (ACP) module. On load, PW will first check if there is an admin template at /site/templates-admin. If there is none, it will check in /wire/templates-admin/. The file it looks for first is /site/templates-admin/default.php 1. I copied the contents of /wire/templates-admin/ to /site-templates-admin/ 2. I modified the contents of default.php as shown below in order to use it as a controller file $theme = $pages->get(1424)->theme_selector;//id of admin theme switcher page (the child page) include($config->paths->adminTemplates . "{$theme->name}/default.php"); 3. In order to use ACP in PW 2.3, you have to create a parent and child page. The child page will be rendered in the Admin. 4. I created pages under Admin as follows: Admin Theme Switcher Admin Themes (id#1424) Default Teflon Moderna, etc. 5. Admin Theme Switcher has nothing of interest. It just enables me to render its child page in PW Admin. Admin Themes has a single Page Reference Field from which only its children can be selected. This field is called theme_selector. Its reference value is the ID of whatever child page of Admin Themes is selected. 6. Default, Teflon, etc., have various fields to hold data about the themes - author, version, description, screenshot, etc. I populated these as needed. 7. In the above code (#3), 2nd line, I am telling PW where the default.php is. I am appending the name of the selected child page of Admin Themes. Hence, if the current selected page is Minimalist Blue, its PW name, minimalist-blue is included as part of the path. This means I need to create a corresponding folder at that path. 8. I grabbed all my themes in their respective folders including all their files and copied them to /site/templates-admin/. This ensured that there would be no conflict having multiple themes in /site/templates-admin/ folder. I also copied the default PW theme with all its files into a folder called default. I ended up with a structure like this: /site/templates-admin/default/ /site/templates-admin/teflon/ /site/templates-admin/moderna/ /site/templates-admin/appy/ etc. 9. Of course since the themes were now in sub-folders, paths in their respective default.php would be wrong. I needed to change this, e.g. in /sites/templates-admin/teflon/default.php, I changed the paths as follows: $config->styles->append($config->urls->adminTemplates . "teflon/styles/ui.css?v=2"); $config->scripts->append($config->urls->adminTemplates . "teflon/scripts/inputfields.js"); $config->scripts->append($config->urls->adminTemplates . "teflon/scripts/main.js?v=2"); $config->styles->append($config->urls->adminTemplates . "teflon/styles/droppy.css") <?php include($config->paths->adminTemplates . "teflon/topnav.inc"); ?> 10. Now that all is set up, there's two ways to change the current Admin theme: a. The template file of Admin Themes has a foreach that loops through its child pages (the theme pages) and outputs the meta data in a I column Grid. Each item has a radio input field to select the theme. On save, jQuery Ajax sends the single value (ID of selected theme) to a simple processor file. The processor file updates the value of the single Page Reference Field (theme_selector) using PW API. Via JSON, the processor then tells jQuery if update was successful and page is reloaded. b. Alternatively, the theme can be changed by editing the Admin Themes page, selecting a child page (theme) using the single Page Reference Field (theme_selector) and saving. PW will auto-reload the page, applying the new theme. As you can see, there is no rocket science here.....just an amazing CMS

Agreed. This is something I thought of too.. right after posting that original topic I haven't really had the need to switch mailer "on the fly" before (especially when using Swift Mailer, which has always been pretty damn effective at sending to multiple recipients / batch sending emails etc. out of the box) which is also why I considered replace best method here. This way once an alternative mailer module is installed and configured it just magically takes over and developer doesn't even need to know that anything has changed (other than the fact that suddenly Mailer has awesome super powers.) On the other hand, I could imagine that in some cases (such as when sending those newsletters..) one might definitely want to switch to another provider -- perhaps even a web service like Mailchimp or Campaign Monitor. For this reason alone it would make a lot of sense to have Mailer configurable at code level. There would still be multiple ways to approach this need and I don't think any of them would need to eliminate the ability to create those "drop-in replacement modules": // like posted above ... $postmark = $modules->get("MailerPostmark"); $mailer->provider = $postmark; $mailer->send(...); // ... or you could also init another Mailer! $myMailer = new Mailer("MailerPostmark");

Thanks Pete, sounds like we should definitely go ahead and add the octits-stream to keep the firefox happy. I will plan to add this. Thanks for your research and testing here.