Jeroen_1980

I don't see any malice here - just a playful comment that only references PW because we are leading in this little race. If it had been someone else, then PW would not have been mentioned.

Certainly not worth beating up the MODX chaps over - probably a nice enough bunch!

Guess I was one of the few that misinterpreted this tweet, as that is exactly what I got back from the MODX team a few minutes ago. It was indeed about beating the one in the lead, not about PW at all. Sorry folks, let's carry on with whatever we were doing and forget about this nonexistent issue.

edit: clarification here: https://twitter.com/modx/status/425235379185541120

Apart from that: Elasticsearch deserves beeing picked, too. It's an awesome piece of software.

Sure. Just no need to mention PW that way. Not the nicest way to ask people to vote, is it?

Just for the record; I, a MODX Ambassador, don't agree with this tweet at all. Already told the MODX core team not to do this again. I love both MODX and ProcessWire and hate tweets like these. These two CMSs should work together to improve both products and not start fighting each other...

Please, let me know if you're still looking for someone. I'm not a Shopify expert, but I do work with APIs a lot (currently building a PW based VPS management system using DigitalOcean's API) so I guess we'll be fine.

I'm not US-based (The Netherlands), but work a lot with US-based clients. Thanks to Skype and me being used to "freelance times" location is hardly an issue these days. Since you mentioned US-only I thought it would be better to post here instead of contacting you by mail though...

What about Conditional Output modifiers.

http://rtfm.modx.com/display/revolution20/Input+and+Output+Filters+(Output+Modifiers)#InputandOutputFilters%28OutputModifiers%29-Conditionaloutputmodifiers

In MODX I sometimes specify a field or content or a chunk based on the page ID or a TV being populated. I also use conditions such as

• If this field is not empty, use this field else use this field
• If this page id is X then show this html / field

How does PW handle this?

You can use plain PHP, so  there is no need for output filters in PW?

Does PW have something to replace MODX Revolution's "Contexts"? I really love to work with contexts when using multilingual sites (or even 2 different sites sharing a single install for some reason). It's really easy to set the URL/language/other settings per context and have all pages of that context respect those settings automatically.

Ollie, it is stunning fast.

Just out of curiosity, what selector are you using to get the "Ook op deze site..." carousel? Cause the pages it is referring to use different templates/parents I guess..

$pages->find('template=article, article_images!=, sort=random, limit=10, id!='.$page->id);

Quite simple (as most things in PW)

Not sure if this will be the best idea ever (just getting started with PW too), but maybe you can simply add a "Page" field to the project template (single page selection will do just fine)? If a page is selected, just replace any empty field on the current page with the selected page's field. This way you can decide per page what you want to translate and what can be taken from the original page.

Very cool Jeroen. Can you tell us more about how you are using it? Would love to hear more about the use cases and benefits. Maybe it's something that belongs as an option in MarkupCache. 

The markup depends on a few factors (page the user is on, current time, etc) so caching the data as a PHP array saves quite a bit of database lookups and even some processing (like price calculations etc), while still allowing me to do the needed markup changes per request. Regular markup cache would not work in this case or would require many markup caches per page.

@jeroen,

You've a familiar name. Think I recognize your name from some dutch MODX meeting or something.

Good to see you here.

Still using MODX (I'm even a "MODX Ambassador") so maybe we indeed met at a meetup or MODXpo in Utrecht last year. Having both MODX and ProcessWire really makes web development fun. Both are great systems to work with.

I know this is an old thread, but it was one of the first results when I searched for 'ProcessWire Object Cache'.

I wanted to store a lot of objects in the cache, so I just converted the MarkupCache module to an ObjectCache module. Nothing fancy; it just adds (un)serialize to the get/save methods. But that alone saves me quite a but of time in this project and results in cleaner (less logic) templates.

The code is available for free (and at your own risk ) at https://gist.github.com/jkenters/5019089