Leaderboard

Hi everyone, Event Mentor is now running on ProcessWire and ProCache (it previously on Hero Framework). It's also linked up with DigitalDeliveryApp to handle payments and digital downloads. Site design by monodesign. Cheers Marty

Page References Tab This little module adds a new tab, References, to the page editor. There it lists pages referencing the page that is being edited (title, path, field). There are also links to view or edit the listed pages (if they're viewable/editable). Only fields of type FieldtypePage are considered to be references and system fields are not listed at all (roles, permissions). It's nothing much, but as the subject has turned up a couple of times in the forums, I decided to give it a try. So watch out what you're asking! Screenshot Links Modules directory: http://modules.processwire.com/modules/page-references-tab/ GitHub: https://github.com/niklaka/PageReferencesTab

Hi, have done the first tests with templates and want to share this one as a starting point for a lightwight responsive layout. Could be good for small websites without the need of big frameworks. The zip contains head.inc and foot.inc like they are in ProcessWires Basic-Example-Profile, and 2 css and 2 js files. If you want try out just Backup the head.inc and foot.inc from Basic-Example-Profile and copy the files form zip file into templates folder.

Here's my first processwire site: www.a-cat.nl ported from modx, the design was already ported from wordpress to modx. HTML Kickstart is used for the basic structure. I had someone do the porting from modx. There are still a number of layout issues with it, having to do with html kickstart margins mainly, but all in all this site is pretty much as I like it. The amazing and awesome apeisa thumbnails module is used to make all the images that are used all over the place in this site, that really makes a difference in speeding up writing new articles, I used to crop the images offline, but now it is a snap. The site also uses the ProCache module, so tell me how fast it feels. Any suggestions welcome! I am sooo happy I found processwire, I come from modx evolution which was/is absolutely great. Processwire is what I hoped modx would grow into. If you want to know why I now went for processwire read the former leading german modx guy who really nailed it for me in this page where he explains why he left modx and went for processwire. With processwire I might have to learn a bit more about php, but from what I see so far processwire really delivers on speed, flexibility and simplicity..

Hey, if anyone should think about writning a on-page editing module this might be helpful: http://vitalets.github.com/x-editable/demo.html Greets, Nico

Hey, UD-Media is a german hoster. And they offer a feature-request system. So some weeks ago I posted there if they could add PW to the "1-Click-Install" stuff and today I got a mail that it will be available with the next software update they are doing. Much love to them: Go and register yourself there: udmedia.de (and support me by clicking this link before this ) They are really great and a lot cheaper then my old hoster I left two years ago. Greets, Nico

Not exactly what you're looking for but may be some help - http://maplacejs.com/

It's sure sounds like a bug. I think it's best if you filed this as an issue on GitHub. That way it definitely gets the attention it needs from Ryan. And I'm going to try and make the test suite cover at least some basic access checks as well.

ProcessWire Email Obfuscation (EMO) Download | GitHub Email Obfuscation module for email addresses with 64 base crypting. This module finds all plaintext emails and email links from the document and replaces them with span elements including configurable replace text. All the addresses are encoded to 64 base strings and stored in spans data attributes. Then on client side we decode these strings back to their original state. Install Create new 'EmailObfuscation' folder into /site/modules/ and place the content of this repository into the directory. Login to processwire and go to Modules page and click 'Check for new modules'. Find 'EmailObfuscation' and click install. You can make optional configuration changes in the module admin page. Thanks This is a ProcessWire module fork from MODX Evolution plugin emo E-Mail Obfuscation. http://modx.com/extras/package/emoemailobfuscation EDITED ON: 2013-03-03 - Added description. 2020-04-16 - Fixed GitHub links and updated description. Hello all. Just found PW few days ago and it's already looking awesome! Here comes first contribute and some questions for developing it further. There was one existing email obfuscator on reposity that didn't use any crypting for addresses so I decided to do a little test run and port the one that we currenly use with MODX Evo to ProcessWire module. I'd like to make PageAutocomplete like gonfigure option to admin so that one could select and set templates to exclude module action. It looks like autocomplete is tied to pages and since templates are not set to system as pages this is option is no go, am I right?

I wanted to give you a little preview of a new module I've been working on recently: the Form Builder module. This module lets you create simple-to-complex forms and place them in your site without any need for development. In this video we show how we can create, publish and test a simple contact form in less than 5 minutes. Then we take a quick look at a more complex form (already produced). I recommend viewing the full screen + HD 720p version so that you can see it more clearly than in this small forum embed. (note: there's no sound, so no need to adjust your volume) More about the Form Builder The Form Builder has many options for the developer to customize output and create their own themes, markup, etc. But the goal here was to build something that could enable you (or your client) to publish a form in less than 5 minutes, so that's the focus of this video. This tool is literally easy enough for your clients to create and manage their own forms. Or from a developers perspective, it takes something that used to consume hours and makes it happen in minutes. Form results save in the database and optionally can be CC'd to you by email. Result entries and be viewed, filtered by date, and even edited in the admin. You can export results to a spreadsheet as well. I'm working on the ability to export to pages, though that isn't quite ready yet. How the Form Builder will be licensed This module will be individually licensed on a per-site basis for a small license fee. It will also be available for free personal use to established forum members. Basically, I want to see if I can substitute some of my client work to focus on ProcessWire instead. And in order to do that, I need to have an income (I have a family to support). So I thought that building a special tool like this would be a way to make a go of it. A lot of you have asked to make donations to the ProcessWire project, and while we still won't be able to take donations, you will be able to support the ProcessWire project by purchasing and using the Form Builder in your own client projects. So a lot of motivation for this module came from wanting to provide something really special for all that had wanted to support ProcessWire. After a few months of work, I'm pretty happy with how this module has turned out -- it's already saved me tons of time in my client projects. So I'm thinking and hoping you guys will really like it too. I look forward to your feedback.

Captain Hook ProcessWire Hooks Cheatsheet http://somatonic.github.com/Captain-Hook/ or on processwire.com http://processwire.com/api/hooks/ I created a simple list with a live search for all hookable methods available in the core. All methods prefixed with a "___" (3 underscores) are hookable. Methods can be made hookable by simply adding those ___ to it. ------------------------- I usually don't really need this, but thought it would be good to have an official list for reference. I used Sublime Text2 for searching and dumb a file with a search for " ___" in wire core. From this list I created a html file with a php script and added some fuzzy live search, similar to the API cheatsheet. If you use Sublime Text 2 like me you can simple use Goto Anything command super+p to show a fuzzy search for files. Enter a class name you want to search for. For example "fields" or "process page edit" you will recieve a list of files found in PW. Highlight the file and typ a @ to see the symbol list quickly or select the file and super+r the get the symbol list.

http://nicenicejpg.com/ A friend of mine built this. I thought it was pretty funny. I have used placekitten.com in the past, but with a '90s rapper things just got a lot more fun.

http://www.swisscinema.org/gimage/b9b371458ab7c314f88b81c553f6ce51.jpg

Superuser always has access but it might need to have access check at least thats what the error suggests. Tick guest give view access and try again.

Seems like there should be a fix. If access is defined via home_old, and home_old has: Do you want to manage view and edit access for pages that use this template? "yes" Would seem to me that it should work. ?

Why didn't you just modify the home template fromt he beginning. I never needed to change it to another template. I think you messed up with the root with access and changing template to a custom with no access yet defined, now you don't have access to modify it again? Not sure at all what happened

Another great way to promote PW.

Hmm, just looked at one of my installs and it only shows guest — which is checked. Seems to work correctly. You are still getting? Can't save page 1: /: Selected homepage template cannot be used because it does not define access. Are you sure you are editing the template that your "Home" page is currently using? I'm only asking, because I've done that one myself.

Hi Wishbone, In your new homepage template, look under "Access" Do you want to manage view and edit access for pages that use this template? Check "yes". I think that should solve your issue.

@antknight: they don't matter - in this case. You should take a look at this post by nik where he explains pretty comprehensively how this stuff works

$news = $page->rootParent->find("template=news-item, limit=5, sort=-date"); echo "<ul>"; foreach ($news as $newsitem) { echo "<li><a href='{$newsitem->url}'>{$newsitem->rootParent->title} - {$newsitem->title}</a></li>"; echo "<span>{$newsitem->date}</span>"; } echo "</ul>"; That should be enough. There's no need for "if($page->path === '/')" either, since $page->rootParent always points to parent page closest to root except while viewing root page itself (in which case it points to current page.) Exactly what you need for a task like this

Ahh sorry, should've seen it, I was talking about page references themself showing links to the linked pages Your's is the other way round... got it.

Thanks again for making this. I have added it in the middle of the API navigation.

You must create only one language_gateway template and create the pages /en/ /de/ with it. It only needs a title field. Also you need to create a empty language_gateway.php file. Enable urlSegments on that template too if you haven't. The module will take the title to use as the urls segment, name isn't used. So urls would be: domain.com/en/about/ domain.com/de/ueber-uns/ if you get a 404 on all those urls event with domain.com/about/, does the site work without language url module? I think it would be good to have a profile with the module enabled and working for those wanting to start.

Hey Nico - great and useful module! It would be good to point out that this module requires PHP 5.3, else your whole site will WSOD. -marc

Hello. http://processwire.com/talk/topic/2263-resized-images-%E2%80%93-purge-originals/

Very well said Joss. Processwire goes beyond just another cms and thus it is going to be a very good starting point to define what processwire actually is, what it can be and do, for who and for what. Processwire can be put in a much wider perspective than a cms and that will promote it very well on a meeting and demonstrating it to new people. Look for example how Luis ported his php app office management suite to PW because of it´s flexibility, scalability and built-in user-roles. I think more examples of this kind would serve very well on the about page on the processwire webpage to show it more directly and openly. Actually it is already there under "What's unique" and "Why processwire" on the about page, but newbies can easily overlook what is actually said there. At least that's what happened to me in the beginning. After being left out from modx evo I started my journey to another cms and came across processwire two times. I didn't really see that the architecture of processwire is even more open than modx evo. If you can't imagine something it is hard to see it. It was only after hanging around on the forum, discovering to my surprise that I was not the only one coming from modx evo, going through the processwire basic website tutorial, that I had my "light bulb" experience. Long story short: put on the website of processwire that it is actually "a scalable modx evo on template variables steroids" and newbies will rush in more quickly and not miss the point. Of course I have put here just an example that does not cover processwire completely, but I think you get my idea. I think Luis ported office management suite to PW will be a good example. I'm sure there are more of them.

I recently had to prune a 800k image collection where many files were orphaned or needed to go (product no longer available) . Had the relative path in the db. Exported the records to a Filemaker DB and copied the images to the local HD. Imported the image file size and dimensions into the DB from the filesys, ran a query, moved selected records out of the tree to a new directory and synced the revised file tree back to the server deleting the orphans. How many records do you have? If your going to reprocess your images on a Mac, you could give Graphic Converter a try. It has some very nice batch operations that are easy to implement.

Another option that would bypass Pw caching, even ProCache is to send an ajax request to handle the counter. If you use jQuery, this would be something like this: //Javascript <script> $(document).ready(function() { var data = {'action' : 'handleCounter'}; var url = '<?= $page->url?>'; $.post(url, data); }); </script> //PHP if ($config->ajax && $input->post->action == 'handleCounter') { //... //put your php code in here //... exit(); //Quit since this was only a request to update the counter } To make this work you would need to disable caching for the POST "action" variable. This is done in the template settings under Cache > Cache disabling POST variables

I launched it today: http://fyp.washington.edu/ I can't even begin to explain how excited I am by this software. It feels like I accomplished more in a month than in the last ten years of professional web dev work. Finally, a CMS geared to the needs of content publishing and information modeling (i.e. taxonomy and ontology) -- not news, widgets, or journaling. Like so many others I had been struggling with the Drupal/Wordpress dichotomy. Drupal feels like hitting myself in the head with a hammer and Wordpress is insecure and inflexible. And both their inner workings seem completely opaque, no matter how often I build with them. Enter PW, CMS of my dreams. The FYP site is combined with Zurb's Foundation Framework, which I am similarly enthusiastic about. Also above all jQuery + CSS3, which seem like a never-ending treasure chest of wonders. I did the interface design and development as well as the information architecture and all of the programming. My favorite thing about the site is the way I was able to give it gears that turn with the seasons -- for each season of the year I added tag "pages" and then tailored parts of the interface to match. The homepage image, the default header, and the selection of front page slides are all determined by what time of year it is. I was able to expose almost EVERYTHING to the content stakeholders through the flexible field system. I could totally get run over by a truck tomorrow and all would be well. I LIKE THIS. Maybe some don't. But I've always been in this field in the hopes of empowering people and making room for creativity. ProcessWire works with these goals, not against them. Cheers, Jenn p.s. the slider is RoyalSlider. I dig it too.

Part of the trick is defining the target market segment. There is an industry wide problem at the moment where market segments are very poorly defined. There are two reasons for this: Firstly, the majority of marketing is done by non marketing people, and secondly this is all very new and shiny and no one is totally sure what to do with it yet. This even shows with companies like MicroGoopple - with the lack of strict market segments, they have all tended to go for scatter gun marketing in every area all at once. With ProcessWire, the issue is "Is it a CMS or not?" Well, that runs into a problem almost immediately - what on earth is a CMS? Or, more precisely, who is a CMS for? Blogger is a CMS. It is a straightforward system that allows people to manage content in a very precise and defined way. Wordpress is a CMS. It works like blogger, except you can host it locally and make it work not like blogger at all. Joomla is a CMS, except they would like to point out that it is a Framework with a CMS on top of it. Drupal is definitely a CMS - it allows you to manage anything, but it is a hell of a long way off from Blogger where we started. ProcessWire is a CMS - except it is a CMS that allows you to imagine and build your own CMS on top of it. So, it is not a CMS then? Certainly, if all the other CMSs are defined by the fact that they are a central system where you can "theme" and build modularly using modules/plugins/whatever, then ProcessWire is possibly not a CMS - it is too flexible and does not have that same central construction mantra. To a certain extent, it is a misuse of the term CMS that is causing all the problems. Out of the box, Blogger, Wordpress and Joomla are probably not CMSs, but AMS - article management systems. Since, unless you stick all kinds of third party additions to them, managing articles is all they do. Drupal is a bit more flexible out of the box. So, it would help marketing if all those others would go off and re-brand themselves as AMSs and leave the more versatile offerings to use the term CMS a little more correctly. Well, that is not going to happen - and in addition, there is quite a gap between what Drupal and Liferay do on one side and what EE, ModX and PW do on another. We have seen in these forums a couple of newer people posting, with quite genuine reasons, that they are confused that PW does not have a theming system like Wordpress has. It doesn't, of course, because it is not doing what Wordpress does - at least not out of the box. You can build a Wordpress out of it (I am having fun doing one at the moment) and you could even build a theming system to go with that - but that would be what you can DO with ProcessWire, not what it is. To my mind, ProcessWire is, at the end of the day, not a CMS as such, or an AMS, possibly more of a CMF, but not even that totally. ProcessWIre is really, a very strong starting point. If you want to develop a web tool of some description, PW is where you start. It allows you to get your visual interface and core data together very quickly and tidily and then gives you enough tools to develop a fine-grained approach to what you actually want to do with that data. In a funny sort of way, it is, for the new browser orientated development world, what Desktop development tools were to users back in the late nineties. It does a lot of the heavy lifting for you while you get on with the presentation and fabrication. So, back to the market - PW is a professional's tool. It can be used by amateurs like me and even quite effectively, but those with better knowledge are always going to be able to take development with PW far further and faster. As such, I think it should be marketed in the first instance as a tool for developers/designers (I really do not like splitting those groups), while making sure it is accessible for those with less knowledge, but like to learn. In practice this means presenting it to the development community through seminars and user-group meets, as well as making sure that each geographical market area has a common focus point (like the German website this thread is meant to be about) that can be used to gather in and grow local communities. Now, this is where I lift the lid on what the marketing industry really thinks of this sort of product. Basically, promoting open source systems is no different to promoting a rock band - you need fansites, reviews, groupies, and everything that goes with it! I am sorry, but I would be hard pressed to put a Rizzla paper between the marketing brief for a highly regarded Open Source system and one for the newest boy band. And having seen the behaviour of some developers on "other" open source projects, there is little difference there either! Joss

I don't know Piwik, but glancing over their API documentation it seems fairly simple to grab and display to the data you want on the site. This would be more robust and flexible i think plus it would allow, as Ryan already mentioned, use in a cached environment.

Ryan, thank you. I will try your suggestions. And, btw, making newbs "Distinguished Members" is hilarious. I love it. Cheers.

Thanks Ryan. The name was in my head since a long time. All these hooking... It's easy, it takes me 5 minutes to update. Download new repo, file search in sublime, copy result file over, hit refresh, upload new index.html.

Thanks guys, looks like I broke that over the weekend, but the fix was easy. Now fixed.

An old, old client of mine (we produced some dramas together in the early 80s) wants to upgrade his website to something a little more "dynamic." He has asked for some help, and to get the ball rolling, he sent me over the specs for the server space he is using. Apparently it is running php 4 or 5.1 - you can choose either! I asked him to send a support ticket to see if they would upgrade to php 5.3 at least. The reply has come back "Newer versions of PHP are still unstable at best, and until they are better tested, we will be staying with the more reliable 5.1" I moved my old friends website in about 30 seconds flat first thing this morning. Joss

I would setup separate templates for your Parish Council and Cricket Club pages. If they are identical, then avoid repeating code and just have the template file from one include the template file from the other. Setup access control only on these templates. You don't need to setup access control on any other templates that are used for pages further in the structure, as they will inherit from the root parent. Meaning, you don't need to maintain multiple templates for the access control, except for the actual root parent pages (Parish Council and Cricket Club). Even if those two templates have identical needs now (except for access), you'll be better prepared down the road when Parish Council needs something that Cricket Club doesn't, or more.

You have to click first on the title, then click on "move". Now you can drag the page somewhere else. If you want to change the parent, you have to click on the new parent first and open its children. Now you can drag a site under this parent. Also make sure that your user has the right to sort / drag children and that the parent template has no sort settings for children defined.

I love the navigation on the photo portfolio. Especially the way the thumbnails get their own subcategories under Clients! I think I actually found a bug with that part, though: If I open one of the client subcategories, then navigate to another main category, then back to clients, the client I opened is still open... so far so good, but if I open another client, that original client node doesn't close.

For those interested. Requires the shop module installed, code not well documented and from the my first steps in PW time. So be honest with me templates.zip

I'm really happy with photoswipe (originally recommended to me by Soma). It really duplicates the native mobile gallery experience beautifully. At the same time, it's quite a nice way to browse photos on non-mobile too (you can even drag the photos with your mouse). Example

And it's very lightweight (under 1000 bytes) cousin tCycle http://jquery.malsup.com/cycle2/tcycle/ which must be the easiest-to-implement image fader available.

Thanks for all the great feedback. Much more enthusiasm than I expected! Yes. The FormBuilder adds a new $forms API variable to your installation from which you can grab forms, results, etc. However, they aren't initially as comprehensive as something like the $pages API var. It initially creates the page in Setup, but you can move the page to be wherever you want it in the admin. This is exactly what I did for a client this week, I dragged /processwire/setup/form-builder/ to /processwire/form-builder/, so that it shows up as a "Forms" nav item in their top admin nav. There are a few reasons, but I worry that taking donations might give a one-man project impression and discourage others from getting involved. We will probably be able to take donations once ProcessWire is incorporated as its own company/organization, and donations would then go specifically towards predefined operating costs and marketing, rather than some individuals wallet. Basically I want to make sure we've got the right structure in place.

If you don't mind managing your own vps, then I would recommend linode: http://www.linode.com/ (one of their data centers is in London). Prices start from 19.95$ / month. I have also dreamhost: http://www.dreamhost.com/ where I manage my domains and few small sites. I like their control panel, but nothing else. (s)ftp is very slow. It runs pw without problems though.