Leaderboard

Hi all, this is my first post here so i must tell that ProcessWire is the best CMF i know. Good work Ryan and others. After 14 days with PW i made two sites and alpha version of czech localization package. After hard time translating PW backend i found that i need one more tool. Tool which can find json files used on specific page. We speak about it on IRC with Soma and he made awesome new module for me TextDomainHelper.module https://gist.github.com/4520324 This module gives new posibility to Chrome PHP Debug module. In js output i can find all used strings and where are stored. Without this tool its much more dificult to translate PW! Example output: textdomain:/srv/http/pw_dev_translate/wire/templates-admin/default.php Text:Admin This module needs to have LanguageTranslator::getTranslation hookable. Ryan, can you make it hookable please?

HI Aaron Funilly enough, we have been talking about categories. As you noted, processwire does not have a native category or tag system, and the reason is that it is easy to build one using pages and the page field. This is incredibly rough: Create a template without a file - call it category for neatness! Dont add any fields to it. Create a page using this template - call it Categories (for fun) and make it published and hidden Now, create a couple of children to this new page with the same template - call them category 1 and 2. They should be published and visible. Now, create a new Page field - call it Category. Once you have created and saved it, edit it and under details Select a single, and then in the input tab, select PageListSelect and change the Parent of selectable page to your Categories page That field can now be added to articles and will save a category name with the page. You can then use that to filter results in your template files. You can use the same system to create nested categories, tags or whatever. You also have the option to allow people to create new categories from the field. That is very rough, sorry, but is a basic way to get you started. As for permissions, I haven't done a lot with those yet, but you can create user groups and restrict them to various functions. I am sure some better answers will appear shortly! Joss

Is there any other way to use Joomla? Note: this jab at Joomla is my personal opinion

We have many users that have come over from EE, just like we have many users that have come over from WordPress, Drupal, MODx and Joomla, among other platforms. These users are enthusiastic about ProcessWire and like to share their enthusiasm with friends. Please don't confuse the title of this thread as being something the project is trying to pursue, because it's not. I'm assuming the OP is a current/former EE user that is enthusiastic about PW and wants to share that. We are not actively trying to benefit from changes at EllisLab or trying to pursue EE users. If I were an EE user, I would want what's best for the company behind it and would stick with it. When those changes were announced, I went to the #eecms hashtag to see what all the fuss was about. There were other projects being opportunistic about it (the Perch one was actually kind of cute). We were silent on it. Just because there were current/former EE users talking about ProcessWire does not mean that ProcessWire is trying to pursue EE. EE has nothing to do with any "cause" here. I changed the theme shown on the homepage because users here thought it would be better if it showed exactly what you see when you install, until we get the rotation up. We have several sets that are going to go in there (rotating) and the one that was there previously is one of them. Now that the default admin theme is in there, there have still been folks that say "that looks like EE". I designed that admin theme and can say for certain it takes no inspiration from EE. I really don't know if the other admin theme that was in there takes inspiration from EE or not. But looking through screenshots, it seems like there are similarities and differences. I'm not convinced anyone was trying to copy the look of EE. Design trends and interfaces for similar tasks are bound to bear some resemblances to each other. People need to step out their front door. There is one thing I can be certain of though, and that's that I'm glad people might say "that looks like EE" and not "that looks like Joomla". I was glad to see this. It came along at the right time. If I was an EE user, this would make me a lot less concerned about the changes in support plans. Glad to hear PW and others are being looked at. We are thrilled to welcome any EE users. Still, if folks are happy with everything about EE from the software side (even if a little angry about EllisLab changes in the short term), they shouldn't abandon it. CMSs aren't religions, and it's okay to use more than one. It is curious to me that Blocks gets mentioned despite not even being out. Blocks appears to be built as a platform specifically targeted towards EE users, and that's probably why. The model behind that one is ultimately a paid model. EE itself is inexpensive in the grand scheme of things. Blocks apparently takes that further by just making the core free instead (a little bit of a trap). But the end result is the same: you'll be spending significant amounts of money on either, because both are built around a paid model. They are there for the money. And that's perfectly fine so long as the user understands that. But with EE, at least you are getting an experienced platform, history and track record. My opinion is that EE users looking for a change should look outward (beyond the money model) not inward. One you have your "a ha" moment with ProcessWire, you'd lose all interest in EE or anything like it. But EE users have to be willing to let go of learned complexity, baggage and preconceptions about CMSs in their mind. And not everyone is ready for that. If an EE user either isn't ready or doesn't find what they are looking for by looking outward, then they should instead look beyond the short term angry EE chatter. EllisLab is making long term decisions for the benefit of the company and the software, and it's actually a good reason for those folks that really like it, to stick with it. Individual developers are not going to be the ones paying these $20k yearly support fees, so it shouldn't be an issue. It's the big enterprise clients that will pay those fees, and they'll think it's a great deal relative to their old CMS monsters. What's good for EllisLab will ultimately be good for the people that want to implement and use their software. This is confusing quantity with quality. If quantity is the measurement, then EE isn't there yet either. If it was, I don't think EllisLab would be changing their business model. For better or worse, the EE ecosystem is also built around a money model. That ecosystem rises and falls with a business rather than the product. PW has always been about quality and has never been about quantity. I started this project as the only user for many years. When I put it out there, I intended to keep it going for the long term regardless of how many users we had. We don't get paid here. We do the work because we love it. They may be huge now, but Drupal and Joomla will really have to fight hard to be relevant in the future. They carry a lot of legacy ideas and methodology, and they kind of have to. They can only lose market share from here, so it seems like they are pursuing defensive growth strategies. When a Drupal, Joomla or WordPress developer gets a taste of ProcessWire--and really gets it--they are changed. I think that ProcessWire and systems like it will make it difficult for the likes of Drupal and Joomla to stay relevant in the long term. I'm sure EllisLab sees this too. But EE users should at least feel good that EllisLab is pursuing a growth strategy that seems geared towards growth rather than maintenance. WordPress is not great software either, but we can all learn something from the way they've grown and likely will continue to. I wouldn't trade our ecosystem or software with any of theirs. And for those that measure by quantity, we'll get there too, but we won't be counting. People from EE are totally welcome here. I'm glad you've joined the discussion. But want to be clear we are not hoping to achieve anything in that regard. If our strategy were to pursue users from other CMSs, we wouldn't be pursuing EE -- it only represents a tiny sliver of the CMS pie. We only want to gain users based purely on the quality of our software and community, and the good reputation that accompanies it. This is an open community and we don't control what gets posted. The only reason you see EE mentioned here is because of EE users that are now using ProcessWire. I appreciate their enthusiasm. While I have positive feelings for EllisLab and EE, it is not on the radar here as having anything to do with our project, goals or strategy.

TimeFormat for ProcessWire v1.0.3 This is a tiny ProcessWire Modules used for formatting times as 'X seconds ago', 'minutes ago'. It goes up to decades. Important note: this module uses 'soft limit' for units. That means that it will show '8 days ago' for 8 days, but '1 week ago' for 9 days, for instance. This will be configurable in one of the later releases. Usage It's very simple. Load module, pass the timestamp to `format` function. Bam, done. <?php $time_format = $modules->get('ToolsTimeFormat'); $posted = $time_format->ago($page->created); Links GitHub modules.processwire.com Notes v1.0.2 & v1.0.3 - bugfixing and module rename

Haha, I didn't notice that Pete is such handsome looking fellow before Joss threw that twins comment

Okay, so I was beaten to the post by the twins above! The rewrite rules have to be different, but you are messed up by the php version anyway - in fact, I am not many recent releases of CMSs will run on that - some are insisting on 5.3 minimum now. I would strongly suggest you change web hosts, to be honest. That doesn't sound like a main stream hosting company to me - I am not even sure if Zeus is even being developed any more. I know it got bought a few years back and their old support site seems to have been last updated in 2010. Joss

i think the idea is great but the implementation is not very intuitive. did you try to make the other way around? i mean, what is inside something is processed, and what is outside doesn't. brackets would be good candidates, just like in php.

@Joss - I still use Dreamweaver (I'm on Creative Cloud, so it's the latest edition) to edit code and there's no reason not to use something else, it's just that for localhost the file tree is useful to me @Antti & Matthew - exactly. Perhaps what we need to push on the site is the fact that you can implement any theme you like - one you'vebuilt, one you've bought or one you got from a dodgy guy down the pub. That would certainly compliment and expand upon the message of ProcessWire not making any assumptions about markup, and to the less techy folks actually capping it off clearly with something like this would probably help: "ProcessWire doesn't make any assumptions about your markup. This means that you can start from scratch and build your own theme or implement any theme you like from a template site". Something like that but written with more thought by Joss

Well, all cache related settings are done through the admin UI at the moment, but maybe Ryan has a better opinion on this. I'm fine with both options. I've also updated the MarkupCache module to support the CacheName "PageSelector" format. MarkupCache.module

Greetings, I have had several conversations with people about this. All the time, I hear, "But Joomla has all those templates." It can be difficult to explain that the reason there are no "templates" (themes) in ProcessWire is not because something is missing. It's actually the opposite... With ProcessWire, the entire world of design possibilities is your "theme." You can go to any theme site (Themeforest, for example) or just create your own layout, and there -- you have a ProcessWire theme. If you see a WordPress theme you really like, it's simple to bring the design into ProcessWire (if you want). It is just a matter of challenging the assumption that a "theme" must be specific to the CMS. Thanks, Matthew

DateTime() takes a string argument when creating new object - it takes the very same arguments as strtotime() does. It's a natural date parser, so if you want to tell it that 'this number is a timestap', you have to prepend '@' before it. That means, that you could theoretically do this: $tf = $modules->get('ToolsTimeFormat'); echo $tf->ago('2012/12/24 18:00'); Edit: +bonus tiny english lesson 'learn' is a word you use when you gain information ('I'm learning'). When you give information, the verb is 'teaching' (e.g. "I am teaching you, you are learning from me"). Hope that helps. (as an absolute off-topic, if I ever make a mistake, you are absolutely free to correct me, so I can learn something new )

That's a good question. I would rather stick with "Markup" for this, but it doesn't generate markup for a format so it could be TextFormatter. I think Tools is too general. Everything is a "tool".

Ah, you've misunderstood. I wasn't talking about directory, but rather page domain.com/tools/ajax-dispatcher/{urlParam} and based on urlParam, you'd call different ajax code (in this case, the code being neatly wrapped as module)

There ain't themes on EE and PW because they don't generate markup => very hard to provide any kind of theming.

This is an interesting point and I think it is probably one of the main reasons they have grown*, but I would be interested in knowing how much themes have helped to the growth of these amongst professional developers - which is the market segment where things like EE and ProcessWire are probably more comfortable. I can only talk of my own experience, but although when I first started using Mambo I did go theme hunting, I quickly worked out that this was more of a burden than a help - converting someone else's theme often took more time than writing my own, and most of the themes out there seemed so loaded with functionality that I did not need that they slowed the site down. Later with Joomla, the only one I used was one with Twitter Bootstrap built in as a starting point but the rest blank. Since there is no theme system as such, in ProcessWire, it cannot take advantage of that sort of promotion in quite the same way. Though obviously if you are using it with a framework like Bootstrap, you can replace the bootstrap.min.css file to change buttons and colours. But I see that as a strength since you can use any framework or templating system or none at all as you wish, without having to work round any preconceived ideas. As I have joked before, you can even use an old copy of Dreamweaver. *Note: The other thing that has helped Drumlapress is that they are available with Factastico and other systems with many hosting providers reprinting tutorials or creating their own hints and tips peculiar to their particular set up.

There's a mistake in the foreach: You have to replace "$page" with "$item". <?php $latest_portfolio = $pages->get("/referenzen/")->children(); foreach($latest_portfolio as $item) { $thumb = $item->portfolio_image; //Note the change from $page to $item echo '<a href="' . $item->url . '"> //Note the change from $thumb to $item... or do you want to link to the image? <img src="' . $thumb->url . '" alt="' . $thumb->description . '" </a>'; } ?> Also you want to check if there's really an image before outputting the img tag, as ryan mentioned above.

That Twitter link is a pretty common occurrence. Things like that happen on the web every day as I'm sure everyone knows - I've seen things like "X looks like Y, must be a rip-off" due to things like colour schemes over the years and I don't think the users get confused over minor similarities (if you're logged out of the forum software here, the skin for that has green, square buttons at the top-right, and that's in the forum software's skin, nothing to do with EE or PW so nobody has the rights to a colour or shape in my mind ). Obviously it can go too far with whole interfaces copied, hence my earlier concern - I've had an entire one of my sites cloned in the past and that was annoying to say the least. On to the rest, there's some interesting stuff there - a lot of your questions can only be answered by ryan I think, but here are my personal thoughts on some other parts: It took me a while to understand what you meant by Blocks - I thought this was something to do with EE to begin with, but a search on Google shows it's a new CMS. The title is very clever - whilst it sends shivers down my spine ("blocks" to my mind brings back visions of the web when data was very much siloed into containers and is the realm of older CMS' in my mind, though I know a lot are still around that operate this way) it's also very clever, as that's a term most non-devs are familiar and comfortable with. I'm not suggesting that's how it works, just that it has a clever, simple, catchy title Hope Apeisa doesn't mind me giving my thoughts on the the ProcessWire e-commerce module and I hope I'm not miles off with this (correct me if I'm wrong Antti), but it is marked in the modules directory as being at proof of concept stage at present. I think I'm right in saying that it's in use on a couple of sites though so it does work. Apeisa, is part of a larger dev team in the company he works for (again, correct me if I'm wrong) and the module was built to fulfil the needs of a website for one of their clients. At some point personally think it will have developers building payment and shipping modules for it and it being one of the key modules, but I think it's fair to say that it is in the early stages at the moment. But it's one of the oddities of ProcessWire that you could technically whip up a payment module in an hour or two that will work with it and be using it quite happily - there's just lots of features that dedicated e-commerce solutions have that aren't there yet because nobody's picked it up and built those extra bits into it as they haven't had the need to yet. I know personally though of one ecommerce site I've built recently where I wished I'd built it in ProcessWire and expanded upon that module rather than pour as many hours as I have done into a full-blown e-commerce solution trying to bend it to my seemingly straightforward needs There is the potential issue at present (and I think I'm getting a sense of that from your post) that it's not apparent who is behind ProcessWire. I think (personal opinion again) that this is intentional as it's ryan in the driving seat with the rest of us contributing with support and tutorials on the forums, docs on the Wiki and of course the modules. There are also rare cases someone will write some code that makes it into the core, but the rarity there is no bad thing - it's just that ryan's built the system so well and it's already incredibly powerful. If you really get stuck in with it and experience the power, it all seems so elegant and well thought out, and at the same time there's so much in there that if I didn't know better I would expect it to be the work of a larger team rather than one person. I've honestly never seen anything this complicated work with so few issues or bugs - ryan has a rare gift (and a tonne of experience). I think it's fair to say that it's a community effort as a whole, and if you spend some time on the forums you can kind of get a sense of who does what (I talk lots and use brackets far too much in every post) but maybe one of the next steps is to loosely define a "team" with "roles and responsibilities" - the thing there though is that you're stuck between trying to do that to be helpful to newcomers to show who does what, and at the same sounding a bit like a big company-driven CMS and introducing hierarchies where those in the hierarchy aren't actually coherently linked to a company. It puts people's minds at ease, but it can be a bit smoke-and-mirrors. To me, the "next level" isn't about churning out modules, even if they are quality - that will come with time and I expect we'll be well into the hundreds in 12 months' time, but why have what others have? As a bad example, Wordpress has 125 pages of plugins just to do with the word "gallery" - that's over 1,000 gallery-related plugins - how many ways of delivering an image gallery are there?! Also consider that a normal gallery wouldn't even need a module in ProcessWire, just a template, a few lines of code and you're away - it's already there in the API functionality-wise. I hope that as we see more modules written for ProcessWire that when it looks like someone is re-inventing the wheel that we can persuade people to work together and have a modules combining different options where appropriate rather than lots of modules doing almost the same thing, but I think it's inevitable that we'll get to a point somewhere along our upward curve where that's too much to manage. The beauty of ProcessWire is that the basic requirements for the majority of small and large websites are already covered out of the box. It's just things like ecommerce that need some more attention at some point. (Another irrelevant personal view - for most developers I'd wager that unless you're specifically targetting shop owners the majority of your sites aren't shops anyway, but I can see how it would be off-putting if your business revolves around e-commerce - still, there are tools out there for that so there's no rush to have a full-featured solution for it in PW). The "next level" things to me are more about: Official docs on the website - something more coherent that gathers together the Wiki, the main Tutorials etc and has use cases (with code) for every function in the Cheatsheet Probably a structured series of screencasts to highlight some of the common things you can do - focusing on specific things like image galleries etc. They're almost the same thing, but it's important to cater for people that prefer to learn by reading and people that prefer to watch tutorials being built before their eyes. The more we show people what they can do if they get stuck in, the better, but ProcessWire's key differentiators are that it makes no assumptions about your markup or the type of site you want to build - therefore it makes you get your hands dirty with a little PHP, HTML and CSS. This will turn away a lot of people I'm sure, but I'd say that if you're not willing to roll up your sleeves and get your hands dirty just a little then why are you building a website instead of hiring someone to do it for you EDIT: Adam beat me to it by almost an hour, but his answer is a concise version of my waffle

No, but I looked it up and read some info about it -- sounds like a great one. I need to check it out sometime.

Teppo, first if all, thanks for this super module! Just wondering about the login times. In my installation they show the server time (in Amsterdam). So in the UK, currently on GMT time, it shows GMT+1. Is there a way to correct this? I have set timezone to $config->timezone = 'Europe/London'; in config.php if that has anything to do with it?

Netcarver, thank you for the kind words, that makes my day. Though I think you give me way too much credit. It's the community here and the people like yourself that make it great.