Michael van Laar

I know that I could solve this with a page type field. But for my taste this is still not as easy to use as a “real” tag field. I doubt that my developer skills are sufficient. But I will at least try to build a tag fieldtype. Theoretically it should not be that difficult. One “only” has to preprocess all the content which is stored site wide in this field and create a clickable listing under the text field. A little jQuery onclick action and that’s it – at least in theory And using Nico’s TextboxList module I think it could look really good.

By the way, this is my first ProcessWire logo usage: http://www.spreadshirt.de/t-shirt-selbst-gestalten-C59/product/106913128/view/1/sb/f A shirt which I’ll wear on the 1st CMS Night Nürnberg event, where I’ll tell people a little bit about how wonderful developing with ProcessWire is.

OK, the client I was talking about can not (yet) afford a shop :-( Anyway, I want to start working on a small shop based on ProcessWire. Perhaps we should just make list what has to be done resp. changed or extended, so that the shop module meets German requirements. For my clients I compiled a little summary with all the regulatory requirements a German online shop has to meet. If you want, I’ll send you the PDF. I would also have my lawyer check the outcome of our work, so that we can be sure that at least the development aspect of the module is OK. Content like general business terms, cancellation policy etc. have to be written or at least checked by a lawyer for each individual shop anyway.

I would like to use typical tag fields for some projects. Nothing fancy, just a simple text input field which can either be filled manually with comma separated tags or by clicking on one of the tags listed underneath the field. So basically it should be a text field with an attached list of all the (comma separated) content which was filled into this field on other pages. In MODX there is a special fieldtype for such tag fields, see attached screenshot from one of my MODX projects. I was wandering if anything like this already exists for ProcessWire, since I could not find anything like that.

Great! I need a very simple shopping solution with only invoice payment method. And with lots of design freedom in templates. So a ProcessWire shop seems ideal. But since this will be a German shop I’ll need to make quite a bunch of adaptions. We have quite detailed rules, how certain things have to look like, not to mention all the legal instructions which have to be placed in the right place. The module also needs e-mail messages sent I’m not a big fan of messing around with CMS core or module files. It makes updateing modules a pain. So how about extending the module, so that all the legal stuff can be activated and modified via the PW backend? I mean, if it fits weird and uber-strict German e-commerce laws, it should be OK to be used anywhere in the world ;-) I’ll try my best, but I’m not experienced with module programming (and backend programming at all). So I will definitely need help now and then. But I think, this is a great chance to make ProcessWire the perfect choice for small shops.

Problem solved. I just included the following line at the very beginning of my templates: <?php ini_set("zlib.output_compression", "On"); ?> Update: Don’t use this code. I just noticed that it made ProcessWire output the whole template content two times, one underneath the other. This is not intended.

Hm, I think I should indeed have a PW shirt printed, since I’m playing the ProcessWire missionary on the 1. CMS Night Nürnberg. Promotion is everything ;-)

I know. For the logo it should be enough. But Scribus has not as many drawing functionality, since its orientation is desktop publishing. So I usually work with Inkscape. But I plan to invest in Adobe Creative Cloud soon.

ProcessWire merchandise sounds great By the way, the PW media kit lacks of color definitions in RGB and CMYK. I haven’t included CMYK versions of the logo in my zip file, because I’m working with Inkscape – and I don’t trust its CMYK abilities. (Expscially since simple converting RGB->CMYK results in awful colors. You always have to use a suitable color profile.) But I’ll take care of this soon.

header("Content-Type: text/html"); … doesn’t work. Obviously Apache needs “real” files to perform the compression.

For nearly all of my projects I use SmartOptimizer (to minify CSS and JS resources) in combination with .htaccess rues (Gzip compression, expires headers, ETag removel etc.) of the HTML5 Boilerplate. This combination makes speed optimization pretty easy and effective. But there is still one thing Page Speed and YSlow criticize: The HTML page itself (i.e. the CMS output) is not compressed. Obviously the HTML5 Boilerplate .htaccess rules don’t apply here: # ---------------------------------------------------------------------- # Gzip compression # ---------------------------------------------------------------------- <IfModule mod_deflate.c> # Force deflate for mangled headers developer.yahoo.com/blogs/ydn/posts/2010/12/pushing-beyond-gzipping/ <IfModule mod_setenvif.c> <IfModule mod_headers.c> SetEnvIfNoCase ^(Accept-EncodXng|X-cept-Encoding|X{15}|~{15}|-{15})$ ^((gzip|deflate)\s*,?\s*)+|[X~-]{4,13}$ HAVE_Accept-Encoding RequestHeader append Accept-Encoding "gzip,deflate" env=HAVE_Accept-Encoding </IfModule> </IfModule> # Compress all output labeled with one of the following MIME-types <IfModule mod_filter.c> AddOutputFilterByType DEFLATE application/atom+xml \ application/javascript \ application/json \ application/rss+xml \ application/vnd.ms-fontobject \ application/x-font-ttf \ application/xhtml+xml \ application/xml \ font/opentype \ image/svg+xml \ image/x-icon \ text/css \ text/html \ text/plain \ text/x-component \ text/xml </IfModule> </IfModule> Even if compressing HTML output is not that critical for speed optimization, it annoys me every time I see a Page Speed or YSlow report ;-) Does anyone know how to compress ProcessWire’s HTML output?

A woff file is a container format, too. It is a repackaged version of a TrueType or OpenType font in a compressed form. TTF and also EOT (since an EOT file is created based on a TTF file) always trigger ClearType font smoothing. SVG is only for old iOS devices.

It’s not that easy. The display quality of a font file, using ClearType technology, depends on what’s in the font file. E.g. the OTF font format is only a container. The “real” font file inside the OTF container can be either PostScript or TrueType. If a PostScript File is inside, chances are good that it looks smooth in big font sizes. That’s because Windows falls back to standard (which means grayscale) font smooting instead of ClearType for PostScript fonts. Grayscale smoothing is not crips enough for small font sizes, but usually looks good for big sizes. So wether a webfont looks good on a windows machine depends on the type of font file combined with the used font size and font smoothing technology.

@yellowled: The font is available via Typekit. That’s not the problem. But it looks really awful on Windows machines – even with the latest version of ClearType activated. So I decided to use cufón (for the first and hopefully only time, by the way).

After reading the PW documentation I decided to utilize a small client project as a CMS test case. Fortunately everything went well I only needed 40 minutes to show my colleague who did the content editing part, how the CMS works. I never did such a short CMS training, even if I always customize every CMS backend I use in such a way to make it as DAU-proof as possible ;-) So here it is – just a nice little website which makes quite heavy use of PW’s image and thumbnail handling (e.g. for all the different logo and image sizes): www.campusroethelheimpark-erlangen.de

Solved! Using double quites instead of single quotes does the trick.

I want to display a list of news items (= pages) in the sidebar. Of course, the current page should not appear in this list – even if it would match the criteria. So I tried $current_page_id = $page->id; $all_news = $pages->find('template=news, id!=$current_page_id, sort=-news_date'); But that doesn’s work. I get the error message “Selector operator: '!=$' -- was your selector value properly escaped?”. But all examples have no excaping. So what’s wrong?

Indeed I checked this with the default admin theme. The problem is there, too. The only thing I haven’t checked yet (because I just didn’t have the time) was if a plug-in might cause this behavior.

Got the bad boy! Uninstalling ProcessPreview fixes the problem. I already posted an issue on Github. Thanks for the hint

I tested this in Chrome 20 and Firefox 13 under Windows 7. After moving a page to a new place the following error message appears in the console: POST http://[mydomain]/processwire/page/sort/ 500 Internal Server Error Error Exception: Page /roethelheimpark/ may not be rendered because outputFormatting is set to false. Call $page->setOutputFormatting(true) before rendering the page. (in /var/www/1061077/html/wire/modules/PageRender.module line 229) #0 [internal function]: PageRender->___renderPage(Object(HookEvent)) #1 /var/www/1061077/html/wire/core/Wire.php(269): call_user_func_array(Array, Array) #2 /var/www/1061077/html/wire/core/Wire.php(229): Wire->runHooks('renderPage', Array) #3 /var/www/1061077/html/wire/core/Wire.php(291): Wire->__call('renderPage', Array) #4 /var/www/1061077/html/wire/core/Wire.php(291): PageRender->renderPage(Object(HookEvent)) #5 /var/www/1061077/html/wire/core/Wire.php(229): Wire->runHooks('render', Array) #6 /var/www/1061077/html/site/modules/ProcessPreview/ProcessPreview.module(43): Wire->__call('render', Array) #7 /var/www/1061077/html/site/modules/ProcessPreview/ProcessPreview.module(43): Page->render() #8 /var/www/1061077/html/wire/core/Wire.php(291): ProcessPreview->changeView(Object(HookEven This error message was shown because you are using the command line API. Error has been logged. Line 18 in /wire/modules/Jquery/JqueryCore/JqueryCore.js is referenced along with the error message. I have a few additional modules installed: FormSaveReminder HelperFieldLinks PageEditSoftLock ProcessPreview ProcessRedirects TextboxList Thumbnails FieldtypeSelect Form TemplateProcessor MarkupSimpleNavigation PageLinkAbstractor ProcessPageDelete SchedulePages

This newbie question may be stupid, but I dare to ask it anyway ;-) After moving a page around in the ProcessWire backend I can’t click any other page name (well, of course I can click, but nothing happens) and have to press F5 for a reload before I can go on with any editing. Is that intended or am I doing anything wrong?

I’m working on my first ProcessWire project and so far I’m really glad that I found this CMS But I discovered that nesting a Fieldset into a FieldsetTab doesn’t work. I tested it with and without the custom admin theme – with the same result. That’s how part of the fields I use in the template look like: There’s a new tab “seo_tab” which contains the fieldset “seo_serp” and a few fields before and after this fieldset. But the result doesn’t look like intended: The fieldset “seo_serp” doesn’t end where it should end. Instead it also covers all the following fields. Any mistake I made? Or is this a bug?