Leaderboard

After months of silence on the forum I've decided to speak out and introduce a brand new admin theme for ProcessWire 2.4.x I've made the theme initially for our internal business project and I've decided to share it with you all The theme itself is designed only for ProcessWire 2.4.x and up because it's wrapped as a module (new theming design approach introduced in ProcessWire 2.4) and it also has it's own options you can configure. It has all the bells and whistles as Default Admin Theme of PW 2.4 as well as some of my own You can download it from here: https://github.com/nvidoni/AdminThemeModesta and please let me know of any mistakes you find during your workflow... Changelog: v1.0.1 Added unpublished pages status icon next to username (fires modal window with unpublished pages list that you can edit) Improved PageList (children are more indented with arrows before them, hidden pages have more lighter color and icons have more darker color - by suggestion from Martijn Geerts) Other CSS improvements UPDATE: You can find version compatible with Processwire 2.4.4 and up on dev branch: https://github.com/nvidoni/AdminThemeModesta/tree/dev and also let me know about any mistakes that should be fixed. Dev version isn't updated to v1.0.1 yet because of strange problem with theme not switching right (doesn't activate) - it started to happen from 2.4.5 dev version of PW...) and it seems it happens only in Windows environments...), hopefully we'll fix this soon. To sum it up and let the images do the talking, here we go:

The best thing would be, if the main ProcessDiagnostics comes together with a DiagnoseRoutine that mimics the same as the installer routine does. I think this is highly needed because of that most "installations" from dev to live do not run the installer process and its checks. Therefor this one should be bundled with the main module and should not be un/installable separately.

Hi Guys, I created a new module to optimize jpegs using the command line tool jpegoptim which yields amazing results, it's comparable to jpegmini.com when using 75 quality. Instructions and usage are available in the readme on github. https://github.com/jdart/JpegOptimImage Let me know what you think! Thanks

even phpinfo have.prollblms ? { apache.need rebooted if can switch php.ver to 5.4 { worth try.mabbe will flush the poops } else { u.need webhost to.rebooter } } just cuz .other site in webbhost works mean nothing. big webhoster have many server .they donut all go bad at.same times unless earthquake or farmer plow wrong field.with webhost internets conneckshion

rename .htaccess to htaccess.tmp reloader page,, 500 error still is ? no ?--- rename it back.and read more instructiones in .htaccess file aboutt 500 err yes ? --- replace /wire/ and index.php fresh copey still 500 ? --- go phpmyadmin.repair tables still??? -- call tell webhost thems must reboot

That's a great intro video. I may be interested once I start editing my screencasts and getting them ready for primetime

alsos u upload testes.php <?php phpinfo(); 500 error or no ??

Updated some stuff and added it to module directory: http://modules.processwire.com/modules/textbox-list/

Hello Martijn, i did something similar as my first attempt to a pw module. Now i discovered yours. My module adds icons to the page actions (requires pw-dev labeled 2.4.4) and does not add js. It's a very quick and dirty module which uses the fotn icons of the wire core. Please check it out on github and let me know if it can be useful to onyone except me. https://github.com/pine3ree/AdminPageIcons kind regards, PS the pw project leader and this community are the kindest i ever found in web development.

Why not just use the <code> tags around it?

Two new small sites, both powered by PW 2.4. Both of them in German only (sorry, people who can't read German), HTML5 and responsive. Both kind of simple in design (per request). http://www.eutin-immobilien.de is a site for a local real-estate agent (in a very small town). Content's become a bit weird since the client started to manage it himself because he used the wrong image formats here and there and also decided to skip my advice to keep the headlines short. Nothing much I can do about that; at some point, you just got to let it go. (I'm not a huge fan of limiting the number of characters there.) http://clic-deutschland.de is for a small, but expanding association which … well, I guess it's best described as a network of support groups for addiction. Kind of like AA, but with a different approach. Especially challenging since they have extremely weird needs in terms of the date formats for their events. Excellent example of how to use the GoogleMap marker module with a jQuery plugin to make it really easy for editors to add individual maps for directions. (The latter was originally requested as a Wordpress site. I suggested PW instead, and the main editor is so impressed by PW that she's considering it for the next relaunch of her own web site.)

I explained that question poorly, I was thinking, while Lister is clearly an uber powerful Admin tool, as a by-product piece of functionality, could a Lister 'view' (a preconstructed 'find') be made visible on a public page (read-only, fixed results, no controls available to the public)? It would be a sort of query and results builder for custom finds. I hope that question makes sense and I've not misunderstood something obvious(!).

Hey Jonathan, Thanks for this. I have just done some initial testing and it's working fine. I haven't yet done any comparisons with GD or Imagick to see if it is any better size/quality wise, but you sound convinced, so I am looking forward to analyzing more. One thing I did notice is that the ".jo" files will be left behind after deletion of the initially uploaded file. It is easy to extend Pageimage::isVariation to handle these. Horst did it with the PIM module and I did it with ImageRasterizer. EDIT - any thoughts in incorporating http://optipng.sourceforge.net/ (or similar) as well for PNGs?

First half Spain was better and the second half the dutch did great.. The system played is not old Dutch, but I don't think the dutch have the players to play the old system. 5-1 is to much for the game played. The Dutch have to watch out for arrogance. They need to keep prepared and stay focused. @dazzyweb, tnx

Here's a video of a module we're working on that I thought you guys might like. The module, Lister, provides a different type of Page List than the tree that you usually interact with in ProcessWire. It gives you a table of pages with customizable columns, filters and actions. Rather than try to explain what it does, I figured I'd show you. This module also uses a new (soon to be released) Inputfield invented by Apeisa, developed by me, and sponsored by Avoine, called InputfieldSelector – it's what you see on the configuration screen as well as the Filters tab. I recommend bumping up the size/quality to 720p so that you can properly see everything. The video has no sound... I tried to do one with narration, but that didn't work out.

Hi everyone! I'd like to introduce PassiveCron - a module, which allows developers to schedule cronjobs - to you. This will be Conclurer's second Pro Module, following ProcessImageMinimize / minimize.pw. PassiveCron is available now as a beta version. What is it going to do? Have you ever been in a situation, in which ProcessWire ran out of PHP's max_execution_time, because you're doing cool tasks like resizing dozens of images using PIM? Or have you noticed site load performance issues when doing a lot of tasks simultaneously? PassiveCron will fix this by giving developers the ability to schedule tasks to future and / or repeating points in time run tasks asynchronously Isn't this exactly the same as LazyCron? No. LazyCron runs your tasks synchronously as your page loads. So running larger tasks will decrease your page's load performance. Instead of this, PassiveCron is able to run those tasks separately from your site loads, thanks to our new web service cron.pw, which will be released together with PassiveCron. How can I use this in my site / module? We will bundle PassiveCron with an easy-to-use API. Let's say you want to call a specific module action tomorrow at 8:00 am: $cron->tomorrow->at('8:00 am')->run('Class', 'Method'); Or do this specific cleanup task, every night at 3:00 am: $cron->every("day")->at("3:00 am")->run("Class", "Method"); Or just run this one large task asynchronously: $cron->run("Class", "Method"); How much will it cost? We are planning to give every ProcessWire site 200 task executions / day for free. For unlimited task executions per site, it'll be around 5€ (pay once, use forever). During the beta period, no payments will be available. Features overview Easy-to-use API for asynchronous task execution Integrable into existing modules for load time improvements No registration at cron.pw needed Pro Cache will be bypassed En- or disable PassiveCron per module Free minimize.pw background tasks Dashboard with reports per task So, what do you think? Is such a module what you need? Can you imagine additional features or do you have wishes for PassiveCron? Please tell us in the comments. Thank you very much!

Hi there, in need for a light knowledge base software and not happy with solutions such as MediaWiki, Dokuwiki or Confluence I decided to try to build such a tool based on ProcessWire. At the moment this profile is lacking of features, but doing well in the context it is created for - a somewhat protected simple knowledge base for internal use. It has some basic features but I'm aware that there's still way to go. So if anyone is interested, please find the code attached here or on GitHub: https://github.com/marcus-herrmann/ProcessWire-KnowledgeBase-SiteProfile I exported the data from a PW 2.4 installation, but not have tested it yet against older versions. Installation Before running the installer of ProcessWire copy/replace /site-default/install/ /site-default/templates/ /site-default/modules/ with the folders from this zip. Constraints It's not possible to export user roles with ProcessWire's Site Export Module this profiles templates are checking just whether they are accessed by an anonymous or logged in user. Features Tagging of wiki-articles Set articles to globally sticky ( = for all users) Personal bookmarking of articles for logged in users When using markdown to author wiki-articles, code highlighting via highlightjs Included modules Fredi MarkupSimpleNavigation Hopefully this profile is useful for you in any way. Best, marcus Edit: Forgot GitHub link... ProcessWire-KnowledgeBase-SiteProfile-master.zip

Glad you like it 1. Sidebar closes if you click anywhere on the page (including the Back to top button), I can change that in the way that only "hamburger" icon has close function assigned to it. 2. I always liked the "hamburger" icon but sure will try some other options - maybe they would look nicer... 3. I've developed this under 2.4 stable, so I'll install latest dev version so I could add those things 4. I'll fix Lister as soon as I install latest dev version... 5. Not sure about the blog, I'll check it out and if it's problem on my side I'll fix it I plan to support this theme for all upcoming releases of PW.

Sporadic errors like this that can't be reproduced consistently suggest it is a problem with your host. It is certainly not an issue with PW or it would happen every time you clicked on the same link. Ask your host to investigate, and if they can't fix it, change hosts. Here are a couple of discussions about the exact same problem that others have had with hostinger: http://forum.youhosting.com/topic6929-client-website-automatically-redirecting-to-hostingerinerror404.html http://www.000webhost.com/forum/customer-assistance/32262-error-404-redirect.html A little reading around about hostinger in general suggests that they are super cheap and unfortunately you get what you pay for You don't need a premium service, but in general it is a good idea to avoid the bargain guys!

i will.look upthat errors.massage for u 404=page.not found it say mabe u.try didfremt url ?

Noticed it probably in Joss's signature on SEBLOD forums. Now I see gebeer has been dropping PW links on them even in 2014

@Jonathan: looks very interesting. Haven't tested now, but have one suggestion regarding metadata: You have set "--strip-all" as default. I really would like to see that IPTC-data would be preserved if populated. This is the default behave in ProcessWire since version 2.3.0. IPTC data only is present if people explicitly have populated them, and in this case they have highly interest in keeping that information within the images and its variations. IPTC data is really small, not like EXIF or XMP. The default is to strip everything but not IPTC. You simply can replace "--strip-all" by --strip-com --strip-exif --strip-icc Or Imagesizer can / should apply a public function that adds it to the resulting files of your and other third party modules. So with jpegoptim it would be a bit faster and more straight forward to use its own flags. ------ I will test it soon, together with ImageSizer, ImagickResizer and the PiM and report back the results.

We already do that for the stable versions (using git tags), see Releases. I think most users would assume that a lang pack always matches the latest stable release of PW. So if you download a lang pack from the modules directory, it should match the current stable version of PW. The link in the modules directory also points to the latest master zip of the lang pack, so the master branch should be “in sync” with the stable releases of PW. Also, in my experience, users downloading from GitHub manually usually just grab the lastest master zip. We should also consider that there's now a module to install languages from the backend. I haven't tested it myself yet, but I assume that always fetches the latest master zip as well, right?

InputfieldSelector is the query builder. PW now has Selector fieldtype and inputfield in a core. That means you can add it to any page, and then you have it's selector value available in your templates. There it is reasonable simple to use that selector to build table and pagination for that data (maybe using jquery datatables and like). I don't think Lister has been develop at all front end in mind, so while it might be possible to it offer a "public view", I am not sure if it's good thing (it is obviously already quite a complex module). I think it could easily end up for something that views is for Drupal, and I remember I never learned that tool (it probably is huge productivity boost for those who can handle it)... InputfieldSelector of course misses the "columns" part, ie. choosing which fields to show. You cannot have it all.. or can you?

5-1 Polonaise Hollandaise

Well, that wasn't too bad of a performance by our guys

Judging from this experience, if you have to enter and emit this massive amount of data for the various types of real-estate objects (the client wanted to here, it might or might not be necessary), you'll probably want to use the new ProFields: Table module. I don't use it here, and it's been a pain in the butt to create fields and code the templates for that. Another option would be to implement the details for any given object simply as a textarea, but since this client is not very experienced in editing content, it did not seem like a viable option. As for moving the heading below the image, I think that while it may technically be possible, it doesn't make much sense. It's probably not really a stable solution, either – the headings could still have a different number of lines below the image, which would ruin the layout as well. Yes, the form is a simple PHP form. See https://processwire.com/talk/topic/6516-%E2%80%9Cpre-set%E2%80%9D-a-form-field-using-session/ for the implementation of “pre-setting” the form field.

Prepare for the Dutch, they will invade this again when they recover from the celebrations...

I just set up a textarea field, add the Textile formatter to it, and then use the appropriate code such as bc.. which is short for block code. bc.. INPUT "What is your name: ", UserName$ PRINT "Hello "; UserName$ DO INPUT "How many stars do you want: ", NumStars Stars$ = STRING$(NumStars, "*") PRINT Stars$ For more info have a look here. Hope that helps?

I would prefer the solution Marc suggested: made a stable and development lang-pack. If we made a 'one-for-all' there will be a lot of abandoned and doubled strings. The updates of the dev PW often change the strings inside. So I think making and maintain two versions of lang-packs is easier. When a new PW stable version is published, we can rename the dev-lang to e.g. version 2.5 and so on. And start the next dev-lang from 2.5.

Include dazzyweb in there. C'mon England! Did Italy really draw 1 - 1 to Luxembourg a few days ago?

I've been working hard on this module this week, and so far, so good - it's now recording and can repeat most changes to Fields, Templates and Fieldgroups. One remaining issue is foreign keys... some field types store Template IDs, Page IDs or other types of ID within the Field data. For the known field types such as PageReference, I can handle those cases explicitly, but for third-party types, there is no saying what they're storing, where, how or when. The only real solution I can think of is some kind of hook that permits other modules to support this module explicitly, by implementing methods that clean up foreign keys and replace them with names, and vice-versa... but that's not really elegant and the module won't work generally with every third-party field type out of the box. Any thoughts?

Why not maintain two branches according to the PW branches? stable and development?

Netcarver, ProcessDiagnostics is beautiful–really enjoying it. I have one suggestion though, which is to either have ProcessDiagnostics install at least one of the diagnostic modules, or to have it display some error if none are installed when you go to Setup > Diagnostics. I tested on a new installation this morning (before I had my coffee) and couldn't figure out why I was getting a blank admin screen when viewing the Diagnostics page. After hunting around in the code trying to figure out why, I eventually slapped myself for forgetting to install any of the related Diagnose modules. But I'm guessing other people might run into the same thing.

Finland for the win! Litmanen is the king!

Update - Just downloaded latest dev version and everything is behaving as it should. No idea what was causing the problem (it occurred using a slightly earlier dev version). Anyhow, everything is good, even if it is Friday 13th!

http://www.webperformancetoday.com/2012/04/02/latency-101-what-is-latency-and-why-is-it-such-a-big-deal/ http://www.webperformancetoday.com/2012/04/02/mobile-versus-desktop-latency/ http://www.webperformancetoday.com/2010/07/09/waterfalls-101/

roger.that is possibile

Roger, Am not sure I follow? What do you mean by 'site guide companies'? Then again, am slow, it's hot outside and all I can think of is the world cup starting in a few hours

i would like to have this for the frontend (filter and refine search). is this possible?

So this reminds me of the joke about the man who asked is friend if the indicators (signals) on his car were working: "Yes it is, no it isn't, yes it is, no it isn't...."

I made a video too: (it's converting currently)

New version available: It now uses an iframe implementation, not as easy as it sounds, because the text area and the iframe somehow need to share the data. At first I went for the session thing (see above), but then realized there would be too many server requests going on. Then I went with cookies, nah 4096 byte limit .. so I now use local storage with a cookie fallback. So now the styles are scoped properly, no clashing of rules. The refresh interval is now configurable. Major code refactoring under the hood and many additions, little optimizations, not so elegant anymore, but whaaateva. It now comes with another optional theme Solarized Dark, it's not as pretty as I thought, will look for better default ones Key strokes of space and enter are ignored, so no unnecessary refreshes are taking place. When updated content is injected (and overflows the browser window), it does not scroll to to the top, but stays at the current position. Summary how it now works (for those interested): The text area is watched for changes, when it changes, the text is sent to the server, converted via text formatters. a local storage item with a unique key of that field and the respective page is set to true meanwhile within the iframe, JS is polling for that value very frequently (no server requests are taking place here), if it's true the text is injected (and only then to prevent constant flickering), the value is set to false so the iframe is only injecting when changes happen in the text area Roadmap: I would love to make the config on a per field basis, but since this module is not an input field but merely hooks into the rendering I am not sure how to, will look into that. Oh, and it's on the module directory now too: http://modules.processwire.com/modules/process-textarea-preview/ Cheers!

Adrian, I agree. I believe it's more about being knowledgeable about the subject you are talking about. Ryan knows web development, PHP, listens and has a comforting way of explaining things. You are never left scratching your head --- you normally say to yourself "Yeah, that makes sense". A slick professional video sometimes can be a hindrance. This project and the videos about the project are very unique. They are not like all the other technical media you see these days. That video that Ryan made, was both honest and sincere. What he talked about was technically brilliant and outstanding. I believe we appreciate the honesty of this project and wouldn't be served much by a slate of Hollywood production type videos. ProcessWire sells itself. It's growing and getting better every month.

If you want to use the values sent as.. email value use $sanitizer->email name for a ProcessWire page that you don't care if it has upper case letters use $sanitizer->name. Name is used to build your url so this will be my-Upper-Case-URL name for ProcessWire page that is more friendly $sanitizer->pageName so url will be my-lower-case-url a valid selector string use $sanitizer->selectorValue a valid string for a ProcesWire page $sanitizer->text etc Unless you are a developer (and even then this is rare) you will not need $sanitizer->fieldName or $sanitizer->selectorField. Note, you are not limited to using the above according to my examples. For your own needs, you may want a string to be cleaned to remove dashes, etc. So, you can use $sanitizer->name in that case... If the above still doesn't make sense...I'll eat my hat

Sorry, it is closed-source for now. It will probably be open-source eventually, but I have to figure out how to dual-license it...

Hi all, I just switched to processwire from MODx and I am really impressed of how clean, fast and intuitive this system is. My first project with processwire happens to be a multi language site, and I am really happy that it can be done with a single page tree. However, I had to dig the forums a lot to find all information i needed to get everything working, so I thought I share my newly gained knowledge... The order of the steps is important, especially if you are working on IIS (which can inflict database damage if you add languages before you change the field types!) 1. Install the Language support modules: - Languages Support - Languages Support - Fields - Languages Support - Page Names 2. Change any existing Fields of types Textfield/Textarea/PageTitle to TextLanguage/TextareaLanguage/PageTitleLanguage You now will have an input field for each language you add. 3. Set up your languages under Setup->Languages (define a name and title for each language. For each new language, you will have to add a title to all the other languages in that new language) 4. Edit your homepage, set it to hidden and unpublished. UPDATE: don't set the homepage to unpublished, the first-child-redirect won't work! (I realized just now, because if you are logged in as admin, it does work) For each language, you have to define a unique name (e.g. "de" and "en") 5. Edit your "home" template to redirect to its first child: <?php $session->redirect($page->children->first()->url); UPDATE: this is not essential... as ryan pointed out, it might even be better not to do it (for SEO-optimization) 6. If you have something like $children->prepend($homepage); in the menu part of your head.inc, remove it (you don't want the home page to show up in your menu) UPDATE: if you left out the redirect option, you'll want to leave this out as well. 7. To switch languages, add this snippet to your head.inc: <ul> <?php $user_lang = $user->language; foreach($languages as $language) { $user->language = $language; if($language->name != $user_lang->name) { echo '<li><a href="'.$page->url.'">'.$language->title.'</a></li> '; } } $user->language = $user_lang; ?> </ul> Each language except the currently active one will be displayed in a list (of course, this can also be done with a select field). UPDATE: Ryan pointed me to a better solution for the langugae switch: http://processwire.c...s-urls/?p=33537 8. Done. Now your page urls should look something like path/to/root/en/my-page, or path/to/root/de/meine-seite It took me less than a day to set up processwire, install my html template and configure the site to be multi-language... this is so great, considering the pain multilanguage sites usually cause with all the other CMSs... Keep it up! UPDATE: I was a bit quick to post a tutorial just after one day working with PW... should have made some more research beforehand. Just got a little too excited there... I'm still impressed by the system and plan on digging deeper into it.

Regarding Approach #1, I think you'd want to use the LanguageSupportPageNames module included with PW 2.3.0 dev branch. I'm responding to your special cases with that context: You have checkboxes next to each language page name. This controls whether the page is published in each language. There is no need to keep track of this since the URL structure dictates the language. This also makes it very SEO friendly. ProcessWire takes care of setting the user's correct language for you, based on the URL. That's what code internationalization is for. For example, an editable footer: <p id='footer'><?php echo __('Thank you for visiting. Copyright 2013 by Somebody.'); ?></p> The following is replying to approach #2, separate trees: The structure is up to you. Whether or not you start your root with an "en/" for your default language is based entirely on how you structure your site. So if you don't want to have "en/" (for example) for your default language, then don't built off a page called "en". Also not necessary since structure would dictate language. You would examine the $page->rootParent to determine language and set it at the top of some common include file (like a head.inc or init.php): if($page->rootParent->template == 'language-home') { // or whatever your template is called $user->language = $languages->get($page->rootParent->name); } else { $user->language = $languages->get('default'); } The same about code internationalization above applies here. Anything static text you put in a __() function becomes translatable. If something is translatable then it is also editable, even for the default language if you want. If you still didn't want to have text originate from the template, then you could always create a settings page in each tree. I would probably just add my "footer_text" as a field in the language-home page.

That actually sounds like a great approach for read-only sites. I suppose, if you used an external (Javascript) service for e.g. comments on a site, that approach would even still work - as long as no new data is being added to the public site. Continuous integration has become the default for me, I never even consider anything else - but I'll have to keep this approach in mind for projects that meet those requirements. Some clients would probably see it as an advantage - that they can tweak and adjust the site, in cooperation with us, and decide precisely when they think it's ready for the public.

I'm responding from phone so keeping it short: $image = $pages->get("template=page-headers, sort=random")->images->getRandom();