Leaderboard

Hey, after having Lightwire Skin more or less ready for some months now I finally created a little module to make the installation easier. I hope you like it. Please report issues directly on Github: https://github.com/NicoKnoll/LightWire-Skin A cleaner and nicer CKEditor Skin using fontawesome:

The "PW ! WP" idea is clever, but not exactly my cup of tea. Also, regarding this design in particular I feel that the logo might be too much. Even if it makes it clear that this is a PW shirt, at the same time it feels a bit like having to explain a joke; it's not nearly as funny anymore. Apart from that, it's great to see (more or less) official apparel, and I sincerely wish you sell a bunch of these! A bit off-topic, but if there was a shirt available with nothing but the "ProcessWire" logo text, or the "P" symbol, I'd get one instantly. Of course I could just get a shirt like that myself, and I believe some of us have already done so, but if the proceedings would (even partially) support Ryan / ProcessWire, that'd be even better

Hello folks. I'm not 100% sure this is the right place to be posting this but, well, here goes. With both Michael van Laar and Ryan's permission, I have followed up on the idea I posted in this thread for a simple PW merchandise design and made it available on both the European and US version of SpreadShirt. Let me know if you like it. I will split proceeds 50:50 with Ryan if anyone buys any of these. Here it is in the US SpreadShirt site. Here it is in the European SpreadShirt site. Edit: I have now setup a specific spreadshirt shop for these products... PW Geeks I've ordered one of these myself from the European store and the T-Shirt quality is good but I would recommend you double check the description of whatever colour you choose in the swatch picker as it isn't clear - I ended up with metallic silver for the word "process" instead of the grey I thought I was picking. Not a pretty result.

Don't even consider getting into this business – or any business at all, for that matter – unless you're going to have water-tight contracts. If you suspect you can't handle that part, have someone else do it for you If you sell software products, you need to be very clear about a) what exactly it is that you're selling, b) what are your responsibilities as a service provider, and c) what are the client's responsibilities. Defining the limits of your liability in the case that something goes wrong is important, especially since the awkward truth is that in the long run something will go wrong, no matter how good or careful or lucky you think you are. Other than that, this post you linked to seems quite opinionated. While such text can often be great for provoking thoughts and discussion, this one is also very naively written. The author seems somewhat prone to oversimplifying things, and many of her "reasons" are easy to debunk or question. Not every situation is the same, not every need is the same, and not all clients are the same. Just saying.

Since a while I notice a problem close to yours. It happens just in case of superuser. Adding some custom fields to the user template results in inability to change the values via Admin->Access->Users as loggedin Superuser (id=41). It works with ProcessProfile. After changing values of a specific field one time in Profile it becomes possible via Admin->Access->Users too. Editing other profiles works all the time. Couldn't find the cause. Edit: 5.07.15 Allowance to edit user fields of the current user is based on the cofiguration in Module settings of ProcessProfile. If you have unchecked a field, you can't edit this field. This is default for custom fields. Change the settings in the module to give edit permission for these fields.

Steve, you should make a t-shirt for Textile. Somehow it fits

Just thought I'd add that there's an LDAP login module (on mobile so can't find the link right now) that I've been using just fine for authentication with Windows 2008 and 2012 servers from an external Apache server with no issues whatsoever (well unless one can't talk to the other due to network issues but you could sunc your username and password with PWs users every login and just let PW handle the login if it can't see the LDAP server for whatever reason).

Glad to hear you like ProcessWire, and hope to be of help here. Also: welcome to the forum! Check out this post by Tom Reno. Apparently they're using Shibboleth, and he even mentioned the idea of turning this into a configurable module. You could always drop him a note and check if he's got any plans regarding this; I'm sure there are others who'd benefit from that kind of module too This depends a lot on how you want to manage your site. Above you mentioned per-user page-specific permissions, which is one approach you could definitely take; there are many examples of something similar floating around the forum, it's surprisingly easy to build yourself, and then there's the Page Edit Per User module by Ryan. On the other hand, if you're interested in a solution that's slightly less "fine-grained" but easier to manage, Ryan's Dynamic Roles module is also worth checking out. I haven't used it that much myself, so won't go into detail on it's inner workings; from what I can tell, it's used on many large-scale sites already. We've been using the UserGroups module for all of our "per-page view/edit" needs, and we're quite happy with it; might be partly because we've been heavily involved in the creation of this module, of course. UserGroups adds a new concept of "user groups", and lets you assign view or edit permissions for each given page to one or more of these groups, which in turn can contain any number of users. Permissions are inherited, so you don't have to specify permissions for each page individually. Wanted to answer this part separately, since the answer (to me) is quite obvious: absolutely not! On the other hand, a few modules here and there are not a problem, and most of the modules you'll find in the Modules Directory are of great quality. While you can't (and shouldn't, even if you could) build a ProcessWire site just by using installing a bunch of modules, you should feel safe to make use of those that do fit your needs. We're not like [insert the name of a very popular blogging platform here], and the answer to every need isn't "there's a plugin for that". With ProcessWire you'll most likely be doing much more hand-crafting, but for many popular needs there's also a handy module – and if there isn't, just ask and often you'll be surprised at how fast the community can answer with a full-fledged solution.

I meant another foreach loop. $csu = $pages->find("template=crms-updates, crms_status_updates=$page, sort=-crms_start_date"); if ($csu) foreach($page->crms_status_updates as $csu) { echo "<strong>{$csu->crms_start_date}</strong> |"; echo " {$csu->crms_comments} |"; // handle multiple page titles foreach($csu->crms_show_contact as $csu_page) { echo " {$csu_page->title}"; } echo nl2br("<br />"); } (ps. I recommend leaving the styling part to the CSS (and remove -es from php)

Hi Teppo. I did try getting exactly such a shirt accepted by SpreadShirt's legal department but the p as an @ logo was rejected without reason. I guess it was too similar to others - but that is speculation. I will look into running a SpreadShirt hosted shop on my one of my own domains with exactly such a design in it as I believe the rules for product acceptance in such a shop are a lot looser.

If you set the field to be multiple then you should get its values as a (PageArray), that is, using a foreach loop. Your example doesn't tell if you are using a loop or not.

Hi valan, Have you tested the module yet to see if it will work for your needs? I'm not sure I fully understand your question, but it sounds like you want to be able to set the visibility property of a particular page field to "Open when populated and not editable (locked)" but still have the edit link show? Is that correct? The issue with this and with the other limitation you asked about is the fact that PW doesn't always provide the necessary CSS/JS hooks to be as granular as I would like (strangely, it does for some of the inputfields but not others). Ryan may have fixed this in 2.6, but I haven't had a chance to look at it again. I would like to fix this at some point, if possible!

Yes you can do version control with git using processwire (I recommend gitlab in order to host the code https://gitlab.com/ ) https://processwire.com/talk/topic/7441-using-git-instead-of-ftp-in-shared-hostings/ But version controlling a database is something I do not have experience. A quick search drops this result http://programmers.stackexchange.com/questions/241109/is-backing-up-a-mysql-database-in-git-a-good-idea Maybe you can go and make a database dump and git control that file. and using git anex https://git-annex.branchable.com/ in order to keep large files.

I think the comments there say it all about the value of that post. About the the paragraph that you quoted, obviously you have to be clear about this with the client.

Gosh.. Totally missed that module configuration. Thanks!! That works like a charm!

Quick overview of some updates I'll be sending to Ryan tomorrow. New Features: Sidebar saves open/closed state. Sidebar opens/closes with arrow keys. Sidebar toggle icon moved. Search input is now a masthead overlay. It's takes the same number of clicks as before (one) since the input is focused on click. The overlay can be closed with the (x) icon, or the up arrow key. User information is now customizable to any text fields associated with the user template. So you can use fields like a first_name last_name. Custom color schemes can be set in /site/modules/AdminTheme/AdminThemeReno/styles/. These files survive PW updates, so you can easily create custom variations on the theme without having to reinstall it after an update. (Thanks Pete!) Top navigation items are now hookable, so you can add additional single or nested items. Top navigation has quicklinks to ProcessWire resources for Superusers. (forums, docs, github, cheat sheet, etc..) There are other tweaks and fixes here and there, but these are all I can think of right now... Changes to masthead and top navigation Superuser Quicklinks User Information Search Overlay

Could this line be the problem? Notice you are checking statusHidden twice rather than statusUnpublished: if ($galleries_page->is(Page::statusHidden) || $galleries_page->is(Page::statusHidden)) {