Leaderboard

@RIVO, I'm as surprised as you that you still keep coming back to ProcessWire. It really sound that this is not the tool you are looking for. That said, I will try to explain why PW is not as "usable" as others by listing some points. Flexibility (first and last point on the list)----- PW as a very well defined kind of user: coders (and willing to learn non coders) that look for extreme flexibility. The fact there there aren't many built in features makes it possible that (with some work, but not a lot) things will be exactly as you want them to be. It can seem a bit scary at first, but if you actually try to use the API you will understand how intuitive it is and how easy it is to come up with several ways of quickly building the features that you mentioned. Anyway, I can't say I agree with PW lacking those many basic features. Let's go through them one by one: There is a module for basic contact forms http://modules.processwire.com/modules/form-template-processor/. If this is too basic there's always Ryan's excellent form builder http://modules.processwire.com/modules/form-builder/ Really?? TinyMCE is exactly the same as in Wordpress and many other CMSs and there are plenty of instructions around the forum to extend it with buttons and plugins. If you prefer CKEditor (as I do) and are not able to install it, just ask in the forums, and I'm sure we will figure out what's happening. What do you mean? A frontend gallery? There are plenty javascript plugins for galleries. The advantage is that PW let's you easily use any of them. Here's is a tutorial on how to implement one of those (flexslider) http://wiki.processwire.com/index.php/Simple_Gallery_System. Please read http://processwire.com/api/multi-language-support/multi-language-urls/ Again, flexibility, flexibility, flexibility... PW will never touch your frontend code (plugins might do it, but not the CMS itself), you'll have to build the page yourself (use dreamweaver or an html template if needed), and in my opinion PW is by far the easiest and most flexible tool for doing it. Welcome to the forum

First of all, I'm a big fan of PW's current admin UI and also aware of other possible admin themes, but I'm also very happy about the discussion in that thread @kongondo linked above.. and thus also the opinions expressed here Common argument here and elsewhere seems to be that PW allows you to swap the default admin theme to something else, but I don't think that people saying this are really getting it. There's a very special position deserved for default theme. It's an entry point, first impressions are based on it, and it also plays an important role when defining PW's external image, ie. what kind of message it wants to send. I've evaluated a few CMS products myself and I must admit that for me first impressions are very important. I'm the kind of guy who first looks for screenshots and then reads the specs. That's just how my mind works and saying that it's "wrong" is, in my humble opinion, more than a bit arrogant. Current default admin theme is very usable and I myself like it's simplicity a lot, but that two-column layout @Philipp presented in aforementioned thread was simply jaw-dropping. Just because PW is a flexible framework for building awesome custom stuff doesn't mean that it can't be pretty and sexy out-of-the-box, especially if that's what many (otherwise very capable) web designers / developers are looking for. There are a lot of CMS products around that all claim to be flexible, extensible and usable. It's simply not an easy market to crack and thus I don't think that we should skip over any steps that can make PW's road less rocky.

Font Awesome Page Label (almost stable version) Yet another PageListLabel module, why? Font Awesome is really awesome, hundreds of high quality icons, ready to use. (Don't we all know how cool icon fonts are.) I wished to use icons in conjunction with the other PageList modules out there. (Page List Better Labels, Page List Image Label & Page List Show Page Id ) I wanted the possibility to style the icons individually with CSS. Showing icons triggered bij template name, but can be overruled bij Page ID. (Trash Page, 404 Page not found etc.) I wanted a better file or folder indication in the PageList tree. Download: github modules directory

Thank you for the quick response kongondo, exactly what I was needing - works great.. Btw, kongondo, you were the one who initially got me excited about ModX after I got a handle on Wayfinder using your tutorial. The fact that you're here now is a confirmation that PW is the new game in town

Hi flyerdave, Welcome to PW and the forums. PW "template files" are nothing more than HTML interspersed with some PHP to output the dynamic content. There are various ways to convert that theme for use in PW. One way is just to copy the output HTML by viewing source in your browser. Then, you would strip that of all dynamic content and remain with the skeleton HTML. Maybe you could also do this directly from the WP theme PHP files but am not sure. It has been a while since I looked at WP themes. All I remember is that they are a nightmare! I highly doubt you will need all those 25 PHP files in PW! After this, you will have to decide how to output those dynamic content of your site. Those would either be whole pages or fields of certain pages. I would say converting the theme for use in PW should be the least of your worries. You should instead concentrate, in my humble opinion, on learning the basics of PW. In order to make best use of the system, you will have to know some very basic PHP. Have a look at the following topics in the docs: http://processwire.com/api/variables/ http://processwire.com/api/selectors/ http://processwire.com/api/templates/ This will require some work and willingness to learn on your part beyond the point and click common in other CMS. On the other side, great rewards and total freedom await you if you are willing to overcome this initial hurdle

Scaling should happen on later time, on template level I think. (Don't mess up the originals) code for your template: $images = $page->images; // assumed that the field called images if(count($images)) { foreach($images as $image) { $width = $image === $images->first ? 600 : 200; $thumb = $image->width($width); echo "<img src='{$thumb->url}' alt='{$thumb->description}' />"; } } This should work, didn't test it.

I would say: ProcessWire has more basic features then any other CMS out there that I know. ( but it's not a one two three, click, click: I have a new website ) In other CMSses you have to learn a lot of things to (maybe it doesn't look like code, but it is). But when you switch to an other CMS your Knowledge is gone. I don't want to invest in a unsure future. Who can say that the big 3 will be the big three within 3 years. If you don't want to code at all. I think it's better to not a CMS at all. There are plenty of website builders for Mac or PC.

Small world . Nice to know that the book was helpful, thanks. Well, I think I can say with utmost confidence that I'll never get you excited about another CMS . It's hard to imagine anything better than PW; I haven't found it and am not looking either . David, welcome to awesomeness! aka PW .

Hi David, See this thread and Diogo's response...it should get you on your way... http://processwire.com/talk/topic/3133-detect-first-and-last-sibling-page/

Actually, Andrew, I have just realised the above may not be what you want. The above limits how many characters you can type. If on the other hand, you are looking for something that will trim the amount of text entered to a certain number, there was some code posted here on the forums but can't find it at the moment... Here it is, by Ryan http://processwire.com/talk/topic/22-how-to-build-a-news-page/?p=51

All strings can be translated in PW. It is as easy as. $this->_("provide your english here") or __("provide your english here") instead of "provide your english here" Then If someone needs to translate your module the translatable strings are in there. The translator should go to /Setup/Languages/ Then to the language, say Dutch. There fill in the path of your module ProcessWire will detect all __('translatable strings') & $this->_('translatable strings') and present the translator with inputs. Then The translator can type in "vertaalbare tekst" go to the next, etc. translate them all. Save... Done $field->description = __("Fringilla Sollicitudin Consectetur"); or $field->description = _$this->_("Fringilla Sollicitudin Consectetur"); To make it more fancy, use the sprintf or printf printf(__("Created %d pages."), $count); example protected function buildForm1() { $f = $this->modules->get("InputfieldText"); $f->name = 'fieldTitle'; $f->label = __('Field Title'); $f->required = true; $f->description = __("The title of the page field to be created."); $f->notes = __("Use capitals, spaces etc."); $form->add($f); ..... }

TEXTAREA COUNTER http://modules.processwire.com/modules/textarea-counter/ http://processwire.com/talk/topic/2343-char-counter-for-texttextarea-fields/ Source Code: https://github.com/boundaryfunctions/TextareaCounter TextAreaCounter.module: https://gist.github.com/somatonic/4252958 TextAreaCounter.js: https://gist.github.com/somatonic/4252962

Hi, Not answering your question...just a comment/rant at Foundation CSS. <rant>I use Foundation myself and I didn't know about this. What an absurd way of creating a divider effect!! </rant>

Well, I see two in your picture, which one is Martijn and which one is Geerts?

I'm glad you will be sticking with us Here is the A-B-C: http://processwire.com/api/ http://processwire.com/talk/topic/693-small-project-walkthrough-planets/

Hey guys! I have to admit that I'm a huge fan of good design. Today P&T have released their Craft CMS 1.2 and .. woow! It looks good. I have tried that system as well but will stick to PW because it's the most powerful and flexible system in my opinion. But Craft just looks so much better. So, are there any plans to re-design the backend any time? I know the backend looks ok. And yes, it works. But design changes and for quite a lot of people, it's an important factor when it comes to choosing a CMS. (Please don't come up with some "they have no ideas about it then" kind of stuff) Why not stick to web design trends and update the backend from time to time? I'd like to see PW both, most powerful and best looking CMS Craft might really be a great inspiration, what do you think? And yes, re-designing might be some work. But finally it's part of the way you "sell" your product. Let PW be modern in the frontend as well

Have you at least compared pw's api with craft ?? Obviously you didn't check the available admin themes in the forum and on git. Yes it takes time to dig the forum to find them. Some pw users here made really great looking admin themes. And "beautiful" backend or frontend isn't the same for everybody, it's totally subjective. You are expecting to find a theme that fits your personal taste. It doesn't work that way. And especially not for PW that is designed to be functional internally (core) in the first place. The external is up to the user customizing the admin css and html to make it look anyway you want. Yes I was once one of them. Typical script kiddy and web builder wannabee hanging around in the scene. Going from one cms to the next only by the look and feel of it because of lack of judging the ratio between cms rules and functionality. Same like you would judge on how a car looks because of lack of understanding how the engine is designed that makes it run. However after trying enough different cms'es each with it's own frustrating wall of rules you have to adapt to, you stop looking at how a cms looks. You start looking for a cms without frustrating and silly rules but that adapts to you as a designer or coder on how to use it any way you want at any level of experience you already have or will develop later on. Welcome to PW unlimited

This module provides a way to rapidly generate Page fields and the required templates and pages for use as a drop down select (or any other Page field type). This module will let you create a full page field setup in literally a few seconds To use, run Page Field Select Creator from the Setup Menu Enter a Field Title, eg: Room Types Select Options - These will become the child pages that will populate the page field select options. There are two different options. Option 1. TITLE FIELD ONLY - enter one option per line, eg: Single Double Suite Option 2. MULTIPLE FIELDS - the first line is used for the field names and the first field must be 'Title'. Subsequent lines are the values for the fields, eg: Title, Number of Beds, Number of People, Kitchen Facilities Single, 1, 1, Fridge Only Double, 2, 2, Fridge Only Suite, 3, 6, Full Kitchen Choose the parent where the page tree of options will be created, eg a hidden "Options" parent page Select a "Deference in API as" option depending on your needs Choose the input field type Check whether "Allow new pages to be created from field?" should be enabled. As an example, if you entered "Room Types" as the field title, you would end up with all of the following automatically created: a fully configured page field called: room_types MULTIPLE FIELDS OPTION - 3 additional fields - number_of_beds, number_of_people, kitchen a parent template called: room_types a child template called: room_types_items (with either just a title field, or with the 3 additional fields as well) a parent page called: Room Types a series of child pages named and titled based on the per line entries in the Select Options textarea The templates are configured such that the "room_types_items" child template can only have the main "room_types" template as a parent, and vice versa. Then all you have to do is add the newly created page field to any template you want and you're ready to go! You can grab it from: Modules directory: http://modules.processwire.com/modules/process-page-field-select-creator/ Github: https://github.com/adrianbj/ProcessPageFieldSelectCreator

Thanks to Ryan, I've managed to knock my next module into usable shape. The URL Shortener adds a link shortening feature to ProcessWire, so you can host your own short URL service from a PW site now. You can create as many bins for short links as you need & the module sets up an example bin when you install it. Each bin is a PW page that uses the LinkShortenerHome template. This template allows you to set the length of the shortened links that will reside in it. Shortened links are simply child pages that automatically use the LinkShortener template. As these links are normal PW pages you can manipulate them from the admin page tree just like any other page. Anytime you create a new short-link page in any of your bins, it will automatically be named with a random string that is not already in use in that bin. You get the chance to review this short string before adding the full URL and saving the page. Once the page is saved any visit to the short link's URL will be redirected to the full URL.

I've been working on an experimental module set that adds 2-factor authentication to ProcessWire with the help of Steve Gibson's PPP one-time-pad system. This is split into two modules; a CryptoPPP library that implements the otp system and a 2-factor authentication module that uses it to add 2-factor authentication to ProcessWire. The 2-factor module adds an additional "Login Token" field to the login page into which the authenticating user will need to enter the next unused token from their one-time-pad. Pages from their pad can either be printed out in advance in a credit-card sized format (with codes being crossed out as they are used as shown here) or the required token can be sent to their registered email address so they don't need to print anything out. This second option requires a good email address be present in the user's account in order for them to be sent the token. Email Delivery To set up email delivery go to the 2-factor module's config page and choose "token delivery via email" and save the settings. Next, make sure that every user who will use the system has a valid email address set up in their account. Upon the first failed user login attempt, the required token will be emailed to the user’s email address and they should then be able to log in. Printing Pages From The Pad If you prefer to print the tokens in a handy credit-card sized format then… Go to your profile screen Expand the “PPP Initialisation Vector” field Hit the “Show Token Cards” button to open a new browser window with the next 3 useful cards Use your browser’s print option to print these out Trim them to size and store ...but make sure you print these out before you enable 2-factor authentication on your account. If you cross out your used codes, you will always know which code to use when logging back in -- and if you forget, the first login attempt will fail and the token field will then prompt you with the location of the correct code to use. Why would I ever want to use 2-factor authentication? If your site is only for you or for people you know use good passwords then you probably never will need a 2-factor authentication system. But it has been shown that many users use passwords that are, well, rubbish not very good and having a second factor can be useful in mitigating poor passwords. As the second factor in this system comes out of a one-time-pad system (meaning it will not be reused) then having the user's password leaked or guessed should not compromise their account nor will having someone spy out the token they are using to log-in as tokens are not re-used (well, not for a very long time.) Known Problems You need to hit the save button after you install the 2-factor module to get it to remember the initial settings. (I guess I'm not setting the defaults correctly at present but pressing the button will allow you to move forward for now) Uninstall of the 2-factor module leads to a lot of warnings. Attachments

Hi everyone, I made a walkthrough of a web app I built using ProcessWire for the Tenova Group mining company. They needed an intranet application to keep track of their daily plant operations. I designed and developed a ProcessWire solution that would allow registered employees at Tenova HYL to record events regularly in an event log. Storing all of the events in this manner would allow registered users to find the events they're looking for using keyword search, date filters as well as filters based on other criteria. Each event also allows the user to upload supporting files for download, such as Word documents and PDFs, as well as upload relevant images to be displayed in a modal window. A high-performing, powerful solution using the ProcessWire CMS. Read about the project here in my portfolio. See the video here: Tina Holly tinaciousdesign.com

For four years I said the exact same thing about ModX.. Then I stumbled upon an article from someone explaining why they switched to PW.. I reluctantly checked out PW, because I had already fully committed myself to ModX. Like you, I'm very glad to find PW. And also to find such good community support!

Just a little note to the translations: If you're in a class context (extending Wire), the way to translate strings is like this: $this->_('Your string to translate'); Whereas in templates, there's the following syntax to use: __('Translate me baby'); Great module

OF, I think you are confusing the Blog Profile and the Skyscrapers profile. Those images are in the latter, not the former . For instance, westin.jpg is here: /site/assets/files/4179 and marriott3.jpg at /site/assets/files/4190

thanks martin for taking your time to help me. i think i might have found the answer. seem as if sass outputs a wrong charset declaration, see here. i'll give this a try later tonight and report back. anyway, strange things happen with all this new technologies ...

Hey, no worries - I was going to be working on another new module today, but may as well get this one perfected first What exactly do you think it needs and how do you see it working? I have played around with multi languages in PW a little, but since I don't really have a need, I am still not terribly literate with it yet. Am I correct in assuming that you wouldn't really need multi-language versions of the title of the Parent page? I am thinking you'd only need them for all fields of the child pages? So, would having separate "Select Options" textarea fields for each installed language cover everything needed? It would be great if you could detail out how you think it would work best so I don't go down a confusing path! Sorry for being an ignorant English speaker PS Go grab v6 from Github - some restructuring of the form - layout and instructions, fixing of a bug if the field already existed, and more friendly error reporting in general.

hi martijn, unfortunately not. just a cut-and-paste error.

@RIVO I love to hear this: For the moment I'll stick to PW for my personal projects and learning. You won't regret learning a little PHP. Even if you leave PW, the knowledge is there, ready to use everywhere.

Wow! So many useful replies already! @ pwired - thanks for posting those links! Very useful to start with! @ Martijn Geerts - kinda true, PW has more basic features than many of orher cms (but not instantly applicable). Thanks for Font Awesome suggestion @ diogo - Thanks for your patience and suggestions. Very good tips, it will help for sure! Form Processor is good for start, Ryan's template is Awesome Your replies are very "refreshing", they reinforce my initial feeling that PW has so much potential! It looks like PW offers Great Rewarding with Little Learning. So I should do the learning. For the moment I'll stick to PW for my personal projects and learning. Well, I guess it just sounds that way. As I said, my mind doesn't really get it yet but my heart (unconscious mind) loves PW. I trust my unconscious mind! And I am very happy this forum has so many skilled and helpful guys. Thanks all for replies. I will start with A-B-C. Thanks! I'am glad I found PW and this Forum! Have a nice day!

Yes, it is possible and has been done. I am in a hurry so can't go into details but there are at least two examples in the forum. One, a bookmarking app by Jonathan and the other an Intranet app. No code examples for the above two, atm..but, yes, it can be done See also Diogo's Admin Custom Pages module. You can also do this by creating your own Process Module.

Hi Alan, Really busy here at the moment so sorry for the brief reply but, yes, the "bc" maths functions are needed for the PPP library. I thought I had the modules check for availability of those functions when it was installed (will check later) did you clone your site to your host (in which case modules will not execute the prerequisite function availability check) or did you try installing the modules directly on the host?

Go to the forum under community support and start reading topics under all 9 titles. Really all your answers are there. Will take 10 or 20 minutes. Have a look here too: http://processwire.com/talk/topic/4173-grouped-forum-posts-links-articles-tutorials-code-snippets/

Yes. But that's not the point. I'd like to see an attractive default theme. So many people decide whether to use the system or not by "looking" at it: it's a visual process. Look at Craft: Is there anything you can do with it you couldn't easily using PW? No. But see how many attention it's getting, compared to PW. It simply offers a great visual experience, and I'm 100% sure this is a reason.

Wil test tomorrow, thanks for all your effort! Did the testings this morning... simply love it. Thanks for bringing in my ideas !

Good point - v4 is now available and includes a list of available text fields that can be used instead of automatically creating new ones if appropriate.

There are already a few good admin themes to choose from. You can also customize them yourself.

Same error here, but love it! Best PW theme out there, should be improved and become default

http://processwire.com/talk/topic/4398-two-column-admin-theme-concept/ Ongoing discussion about PW backend...

I wouldn't go too fancy about this. Perhaps simply a repeater with two fields: day and hours so they can add multiple day/hours pairs. (Edit: one simple textfield would suffice in this case too, seperate days and hours with some parsable seperator (for visual seperation in the front end), each pair seperated by new lines) Another idea would be you have a repeater with four fields for each repeater item: begin_day (Select field (PageField) with the 7 given days) end_day (Select field (PageField) with the 7 given days - optional for a span of days) begin_time (integer field) end_time (integer field) format the stuff accordingly in the template so they can very flexible enter anything here Mon-Tue: 7am-8pm Wed: 10am-4pm Thu-Sat: 10am-10pm

Greetings, This is fun. But it really is a good subject to compare what life is like before and after ProcessWire. I already posted my humorous visual. But now, after using ProcessWire more in recent months, here's another way I see it... Before ProcessWire I spent too much time comparing and experimenting with CMSs and frameworks, chasing after specific capabilities. How well does this system do search? What are the templating or theming requirements? Is there a module for [fill in need]? Does it do tags? Is it easy to integrate scripts? No single system did all of these things well, so I was always trying another one, always having to be satisfied with "good enough," and always working around limitations. New projects always presented another "surprise" coding need I had not considered before, forcing me to search again for a system that can do it. After ProcessWire I can confidently handle all of these capabilities, dong them the way I need them to be done for each project, and I know the system will provide an intuitive way to handle those "surprise" coding needs that inevitably arise. I gain better and better understanding of the underlying coding principles behind these development capabilities. Thanks, Matthew

Hey all, Here's a demo of what I've built. It's become my primary bookmarking system: I didn't demonstrate it in the video, but this system works amazingly on a mobile device too. It's so easy and quick to pull up stuff I want to read when at a coffee shop or have a few minutes to kill when on the go. I found Diigo's Android App very limiting in comparison, especially since it doesn't allow you to view all of your bookmarks on the mobile app (last time I checked). I have no plans as of yet to release this, but I may in the near future if you are all really interested. There are features I still want to build out as well as a lot of code cleanup and security measures that need to be implemented. Enjoy! Jonathan

Guys, try to keep other languages than English, PHP and Klingon on translation forums. It is little bit frustrating for us who read all unread topics.