Leaderboard

A non constructive answer here but just my opinion. I LIKE THE NEW FORUM - thanks for the good work !

This module helps you dynamically create schemas for improved SEO & SERP listings from within your templates. Each schema can be configured to meet your requirements. You can even add your own ProcessWire schema classes to the module. Read about the module on github: https://github.com/clipmagic/MarkupJsonLDSchema Download from github: https://github.com/clipmagic/MarkupJsonLDSchema/zipball/master Download from ProcessWire modules: http://modules.processwire.com/modules/markup-json-ldschema/

Wheee, what a lot of replies I'm going to ignore the silliness in the original title and some of the heated replies and just get straight down to answering some things as quickly as possible. Some changes are do-able, others you guys will have to adapt to unfortunately. Whilst forum software can be customised to an extent, my 10+ years managing these beasts has shown time and again that the more you change the more you suffer through even minor upgrades so we'll be changing some things where simple software settings allow and keeping any potentially upgrade-breaking changes to a minimum. TL;DR not everyone is going to get what they wanted, but that's always the case unless you're working for a single client... and sometimes even then it's not guaranteed. Which headlines do you refer to? I just compared to the previous version and there's very little difference - same with the black bars, most of them were there before but all the elements were smaller along with the font size so perhaps they were just less noticeable? The like buttons were also there before, they're just a stronger blue. Q&A forums - the staff are having a discussion about which should remain this way (probably Pro modules where each topic is usually a question) and which shouldn't (probably the main Modules forum where each module has only one topic. I personally think that will resolve the Q&A debate for the most part, and people will use the right forums for the right things (the descriptions for most of them under Community Support say something along the lines of "for asking questions or getting support" so you'd expect 99% of topics to be questions in those places). I think the Q&A forums will probably work well there even though they're a shock to the system as the community can decide to upvote answers in those topics and it will eventually lead to finding the best answers floating towards the top right below the question itself - if this works as it should it makes finding the answers to things much easier and that's got to be a plus for the community, I suggest we just have to give it time and make a few tweaks to which forums should be Q&A forums in the meantime. More on this after we've had our internal discussion. Well... let's have that internal discussion first and then we can let everyone know what the plans are Really not sure what these headlines are that you're referring to? Nothing is particularly dimmed on my screen - can you please post a screenshot so I can be sure there's not some quirky browser/OS-specific CSS issues going on? The announcement was in the News & Announcements > Site Announcements forum, also linked to in the latest blog post. It was about as visible as we could make it As Soma said further down, the forum upgrades are something we're going to have to suffer every few years and there will be some features we'll miss and others we'll love - until someone recreates all of this in ProcessWire we have to keep moving with the times or face getting hacked which would be far worse than the disorientation we're suffering at the moment whilst we iron things out. It liked that pic - it said so in step #423 of the upgrade routine Can you let me know what version of Firefox and Windows you're using? You'll need to be on a recent Firefox version at least. I'm going to ignore the rest of your post and focus on the important things that are coming out of this discussion. I think it's one of those things - the old version had a dedicated mobile skin but a limited feature-set, the new version is responsive but has every feature more or less. I think those who only browse but don't reply on their mobile will be disappointed by it being slower, but those who regularly reply on mobile will hopefully appreciate the more fully-functional aspect. There are some caching options we'll look into to try and speed things up - one area where this software falls down a bit is no easy CDN integration otherwise we could get some of the CSS and JS assets loading a lot quicker for everyone - hopefully there will be a solution for that further down the line. See my earlier comment - can you let me know your OS and browser version please? I added in the panel that shows who's browsing a topic last night. It just wasn't there by default as it's arguable as to whether it adds anything (and it does make the page load marginally slower doing the extra queries, but we're talking fractions of a second - same with all the blocks at the bottom and side of the main forum view actually). This forum has actually had a huge number of features stripped out compared to the last version, behind the scenes at least - complete rewrite (yay, more bugs :D) to support namespaces, PHP7 and get away from legacy junk code that was going to break soon in a future PHP version. They've made an effort in the code to keep it all nicely up to date and more easily updateable (less fragmented in terms of functions in obscure locations etc) so hopefully all future upgrades will run a bit smoother from a purely technical point of view and actually managing it is a lot nicer and easier, though that doesn't directly help you guys browse around day-to-day of course. The main things that have changed on the frontend are the activity streams which promote status updates alongside forum posts. Member status updates were actually in the last version as well, just so hidden in a person's profile they made no sense being there. We do have the ability to change the default activity streams to ONLY include topics, but I'm actually hoping that status updates might make things a bit more social - you can either post a status update in the software or link your Twitter accounts and it's then a doddle to share information that doesn't warrant a topic of its own but might be interesting to other members - same as the previous forums, just with a lot more visibility. You can also turn it off manually in the streams so it's only topics that show up in the feeds. The layout in that section is of course completely different - no denying that. I don't think commercial discussion forums are in a massive battle with social media platforms so much, more with each other. Whilst they might lose the smaller customers to Facebook groups, I've seen the larger customers - the ones who pay the big money to have everything done and customised for them - stick with them through thick and thin because they, like us, value holding onto our data and keeping it with the rest of the information. We've stuck with IPB because it's a) the one I know and b) still has a decent set of features whereas some others are now over-bloated or too lightweight for us in my opinion. Since I'm the one who has to run it I'm sticking with what I know for now. That may change in future, but we'll always want a hosted forum where we can control the content rather than relying on a slow third party service or shipping everything over to Facebook so we'll always be somewhat at the mercy of "what the devs have done this time" when a new version is released. Pretty sure I'm just agreeing with you at this point ceberlin, but thought I'd comment on what I'm thinking anyway On to CSS - it is possible to change a lot but there is likely to be a new site theme coming along in the next few months so I don't want to spend masses of time changing too much and have to do it all again later - we will focus on usability. Most things are pretty much where they were before though, so some of the things you list there are a bit confusing to me to be honest. If you can give me small screenshots highlighting the things you think are not as they were before or need to be improved that would be a great help to me. I think that's actually an error from import what you've shown above. In some forums we had pre-set prefixes as well as tags and it seems to have kept the prefixes but also applied the prefix title as a tag. No doubt I can work out an SQL query to rectify this at some point so there's no repetition and that should fix most of it. Again, the Q&A issues are likely mostly applicable to the modules forum - everywhere else they're applied they could be an improvement if we give them a chance. Q&A functionality is per-forum and can't be applied only to certain topics unfortunately or else that would solve the problem entirely - as such where you're seeing them that's where the forum is set to be a Q&A forum. That was an accident - it turned out someone yesterday was able to start a new topic in there (definitely not a good idea for everyone to be able to do that there! :D) and I over-did the permissions. You should be able to reply now. You can create custom filters on the activity stream, so if you change Unread Content to work exactly how you want you should then only have to move your mouse over the main Activity menu item and then click Unread Content and that would then function more like before, aside from the layout of course. It really isn't that much different. There was a big black bar across the top and all the forum titles were on a dark background. I feel like I'm going a bit crazy here so here's some screenshots for comparison: OLD: NEW: The elements are all a bit bigger so it's going to be a bit darker overall, but otherwise not much different. I also made the sidebar match a bit more rather than spend too much time customising something that's of less importance I think. I think that's just in Q&A forums, right? That sounds like a browser-specific bug - can you let me know OS, browser and version? Thanks! I do remember all this from the first time around, yes, similar discussions took place then. And yes, the exclamation marks, but that's in the past now. @horst technically everyone's right here. In the "View New Topics" link at the top-right of the old forums (now Activity Streams) the titles went to the first UNREAD post. When browsing topics in a forum normally and not using View New Topics they went to the first post AND had the little dot @adrian was getting annoyed with yesterday to go to the first unread post (I've changed this to an eye with a line through it since I think it's more appropriate and noticeable) so in fact the functionality is now exactly as it was. I've just confirmed this is the case by looking at the old forums which are hidden away for reference. Funny how the mind plays tricks on you isn't it? I think the biggest issue was the new streams not going to the latest unread post by default but we should now be mostly back to the original functionality. To be fair, I would have closed the topics if I thought there was a chance editing old posts would screw things up, but the rebuild would have only changed the parts it needed to. That finished within 2.5 hours instead of 6 due to... well... this server being really fast I think, and leaving the forums open made more sense since I had a list of what needed doing and had timed it in the run-up to actually doing it, getting the bit where I had to delete and re-import the fixed posts table down to 5 minutes or less (guessing nobody spotted those few minutes where every bit of post content disappeared ;)). But yeah, there was an initial feeling we should play it much safer and turn it all off, but there was more benefit in leaving it on in the end despite a little slowness for a few hours. This is as fast as it gets now by the way until myself and Ryan get some time to look into caching options, of which there are very few (I miss all the benefits of ProCache :D). Not sure why this would happen - it really shouldn't have. I'll see if anyone else on the main software support forum is reporting similar issues. The emails do definitely need some tweaking. Avatars are certainly a little superfluous in a notification email, I agree! Well that took a long time, but keep the comments coming. I certainly can't guarantee we'll do everything that's requested but the least I can do is listen and read the replies.

It has happened in the past 2 times already and will happen again sooner or later. Looking back I still liked the first forum the most in terms of overview and browsing. I got annoyed by the changes to something I used everyday and was used to it. Always takes some time to adapt and we all know it can be frustrating. Sometimes it's just the styling that's so different your brain has to adapt. But after a while you'll maybe even appreciate it or forget about it. But then it has to be done and I appreciate all the work put into it, as it's a tedious work done in Pete's spare time. I'm also surprised to how much has changed in the new version as it's completely a new thing, and I it took me a while to see where I find what. I think the "why" isn't the problem it's the how you wrote it with the uppercase and the 4 (edit: oh 5!) exclamation marks!!!!.

When something changes you always get stressed (or delighted, if you're lucky). But changes are the nature of the webdev game we play. So better be prepared. Anyway, someone being here the 1st day probably won't notice anything . The fact that you're used to the old forum just proves how addicted to PW you are! But we can probably tune a few things. Here is my list of butt-hurting new stuff: The question-answer functionality. I think it can be turned off, but for now it still persists in some forum threads. I do not know why. New restrictions. I tried to reply in the News & Announcement forums and could not. My favorite way of using the forums has always been going through the new content list. Now I have to make a few more clicks to get to that page. If this is common, maybe but a link in the top menu? The look of that page with the timeline looks unusual to me and filtering is not as fast, but I can learn to live with that. There is too much dark colors (on the pager, for example). If there is a chance to bring that old light theme to the new forums, it would be great. The pager on the top is below the initial post. I think it previously was above it. I could not insert any smiles. I found the menu icon on the top, but nothing happens when I click on emoticons. Or is it just me? Well i did it with drag-and-drop, but still a bug. Thanks Pete!

It's slightly amusing that the most heated exchanges I recall seeing here in a long time are not about PW, but the forum! FWIW it all looked a bit alien yesterday at first glance, but either @Pete has been working to make it look more familiar or it's easy to get used to. (I suspect maybe a bit of both.) There are obvious improvements - the @ mentions are good, this RTE seems nice and light (although did I notice some funkiness with the first letter of this post being misplaced?) and who knows but the search might be better. I'm sure there will be other good things to discover along the way.

Commercial forum makers are under a brutal competition right now. In the first place with Facebook. So they add features over features to make their stuff more facebookish. One of the use cases where a classic forum is far superior from Facebook is a software support board like this one. The old forum usability was my reference (it was that good!) when setting up my own (xenforo) Forums. The new skin should have all tools on board to get us there again, if we want. (I am not talking about needed learning curves for users, or taste things). I try to focus on usability questions for the speficic needs of a technical support forum. To sum up where we are: No one is denying the fact that it is crucial to keep a forum as up-to-date as possible, for security and support reasons alone. So this step is appreciated! If Pete was not praised enough for doing this step (99% of the really hard work is under the hood and cannot bee seen): A big thank you from us here! I see that it can be seen as "negative" if a first comment is about usability (I was really shocked) and not about the big improvements under the surface. Where some of us agree is that the "Q&A" setup is not suitable for some of the forums, as we use them up to now. Where some of us agree is that (a) the skin (css in the first place) could need a closer look and (b) this should be no big technical problem. There I would like the discussion to continue. - This is, where everyone agrees. I will use this afternoon to be more precise with my wishes. For example: Make navigational elements (headlines, breadcrumbs, search fields) very prominent. Make clutter (location of a member, tags, starter of a thread) less prominent. Small changes can have big effects to bring back the cleanness and usability of the old forum look.

Thanks @Macrura - I have gone with your suggestion and packaged the three required ACE files. I thought about using CDNJS instead, but if it's down, things would break and I'd need to add the textarea fallback anyway. This way just seems simpler. Thanks for your thoughts on the snippets manager - I think it could be quite useful - so expect that to be added sometime soon. The latest version just committed includes ACE editor, along with yet another new panel ProcessWire Version Switcher This new PW Version Panel lets you choose from any of the versions you have available and gives you the ability to switch versions instantly. The available versions come from Ryan's ProcessWire Upgrades module - so any version that you installed via it will be available. When you click change, it swaps the names of: wire/, .htaccess, and index.php - much easier than manually renaming. The icon is green when you are using the latest version that is available on your system, and orange for any other version. Please let me know if you have any problems with either of these additions. PS - It's probably obvious, but the switcher is not recommended for live sites, so don't blame me if a version change breaks your site!

@adrian - I must say, I like the fact that we finally have a mentions system. No need to quote all the time and bloat up threads.

Am I the only one who got turned into a spice girl by the upgrade? Somehow it didn’t migrate my latest pic but the one I had up until a couple of weeks ago?

The modules directory visits github once a day. To force it to refresh, just edit the module in the directory, but don't do anything and just save. That forces the crawler to go back to github and voila, you got it updated Congrats on your new module btw

@psy thanks for this - nicely done, and looking forward to using this. You should probably remove the closing PHP tags, per the style guide: https://processwire.com/api/coding-style-guide/

The title of the thread is pretty negative to me (and i don't want to insist on this because I'm not sure anymore, but I'm pretty sure the original post was edited to be lighter). Anyway, ceverlin already explained his reasons, and I think we are all in peace with it. As for your unbiased opinions, I've learned with time to not give them much credit. You can change that in your activity streams... I'm on mobile, so for now I can't be more specific.

Please, let's get our facts straight. There are no plans to make ProcessWire bloated! In fact, the opposite is true... Pete did not design the new forum. It is a third-party software. All (I say all...it took him months to get to where we are) Pete did was to try and tweak the styles to closely resemble the main ProcessWire site. He has also tried his best to remove stuff not needed and make stuff we use often to be close at hand (+ of course made sure there was no data loss during the upgrade). Other things come with the territory...Pete did not create 'the visual clutter'. That's the way the new version of the forum software looks like. Are things perfect? No, some things will still need tweaking (like the Q/A style forums). Was the upgrade necessary? Definitely (read the posts linked to above)... Please let's be as specific as possible about 'missing stuff' and any other anomalies.

Hi ceberlin. According to the original post, the upgrade was rather important to do. It's different, yes. And it may take a while to get used to. But it's something that needed doing

This topic will serve as the thread for the Selectize.js family of modules, which utilize this popular jQuery plugin for enhanced tagging of images, fields, templates and page selection in Processwire admin. http://selectize.github.io/selectize.js/ The modules will ultimately include: JquerySelectize Base module that provides the library for use by other modules Github: https://github.com/outflux3/JquerySelectize Modules: http://modules.processwire.com/modules/jquery-selectize/ ----- SelectizeTemplateFieldTags Uses the library to init the tags field on fields and templates, and makes the icon searchable by name. Github: https://github.com/outflux3/SelectizeTemplateFieldTags Modules: http://modules.processwire.com/modules/selectize-template-field-tags/ Screens: Tagging a template: *******sorry but the forum upgrade destroyed these images -- you need to click on them to see them now ******** Search icons by name and see the icon: ----- SelectizeImageTags Uses the library for image tags field. Github: https://github.com/outflux3/SelectizeImageTags Modules: http://modules.processwire.com/modules/selectize-image-tags/ Screen:

We will be performing a forum upgrade tomorrow if final testing goes well today. Why are we doing this? The current version is over a year old and the developers have since released a new major version - in fact they're now up to 4.1.x whilst we're still on the 3.x branch. They will not be supplying bug fixes or security patches for much longer. There are a lot of nice changes (and some confusing ones - more on that later) such as responsive design leading to a more complete mobile experience. We can also leverage some caching options to make things even faster when browsing the forums. What does this mean for you? Unfortunately there are a number of down sides to this: The forums will have to be taken offline twice for approx 20-30 minutes each time for several hours. During the upgrade process, the post content gets completely rebuilt and whilst this is in progress things look a mess, code samples look broken etc etc. We think it's better to take it offline than show broken code samples! We've decided to leave the forums open as the forums still technically work, new posts aren't affected, and we need the shop to stay online as well. There will be a learning curve with the new layout, but I'll do my best to post a "this is where to find stuff" post right here after the upgrade. Bizarrely the "best answer" feature has been replaced with a Stack Overflow-style voting feature which doesn't work everywhere we currently have the best answer feature turned on, so we will be making adjustments to some forums. You also can't make the first post in a Q&A forum topic the "chosen answer" which is a bit silly, but I'll be looking for a workaround for that. Possibly the biggest annoyance is that all unread posts you may currently have will get marked as read after the upgrade. Since this forum is a complete rewrite they've been unable (or possibly unwilling?) to do a complete migration of all data to the new version. There are plus sides though, right? Yep, there are: The reason the post content gets rebuilt is so that it's all stored as HTML in the database rather than BBCode that has to be parsed and isn't upgrade-proof. They've also finally stopped using their own-brand post editor and gone with CKEditor, so upgrades should be a little less chaotic as custom tags have been replaced with universally-recognised data-attributes. Theoretically this means that I have less of a headache if they choose to do another complete rewrite in 5 years' time. The code-base has been rewritten and they've removed some of the less used features to speed things up, plus it'll be compatible with PHP 7 soon which means that theoretically everything on the main ProcessWire site can be updated to work with PHP 7 soon and benefit from some nice speed increases. We should be good to stay on the 4.x branch for several years. I'm not anticipating the devs rewriting the codebase for at least another 4-5 years as they've decided to future-proof it as much as possible. Did I mention upgrades will be easier for me to manage in future? Wouldn't it be easier to build a ProcessWire forum module with all the same features? I do think this from time to time, but to be perfectly honest it takes a team of people at least a year to come up with everything you see here. I'm sure I could emulate much of it pretty quickly if I was paid to do it full-time for a year (including BETA testing etc) since the ProcessWire API and module structure is much more sane, but I might also go crazy in the process One day maybe... --- So at some point tomorrow, you will see a message here saying we're upgrading and to check back later. I can't give a precise time estimate, but it is a lengthy process - I would expect it to be at least 6 hours starting around 10am GMT - fortunately most of that is waiting for content to automatically rebuild - and then I have to apply some manual tweaks afterwards which will take about 30 minutes. Schedule TBC - hopefully still tomorrow - some of the final preparations are taking a little longer. Downtime will be kept to 2 blocks of 20-30 minutes maximum if all goes well. Existing post content will look quite odd for the duration, but new posts will be absolutely fine and we'll fix up the old ones afterwards.

@adrian, I haven't actually given it much thought yet - that was a spur-of-the-moment posting, though I definitely wasn't thinking of using it for the core. Now I've spent a few more cycles on it, I can see that I have two different ways of using git for my PW-related stuff; For modules - in which case I just symlink in a subdirectory (suitably git init'd) from my master development directory so only some of the subdris in the site/modules/ directory will be git repos. For whole sites - in which case I install from the latest zip'd version of PW and then git init in the site/ subdirectory. I'm sure there will be other ways to do this too.

I don't know what quiet save does, but isn't that cache question pretty fast to test?

@Ivan Gretsky - you can click the tick mark next to the name of your activity stream, or even next to "Unread Content" on this page: https://processwire.com/talk/discover/unread/ - that will create a shortcut to this page: The tick goes green and results in the "Unread Content" link at the top right of the page. This works for any of your custom Activity Streams.

@horst @Pete changed that setting and now they link to the first unread post by default. One can also change that setting themselves (although I'm not sure it survives across sessions) - see screen grab..

ok, there we go. Changed topic.

Hmmm this is weird I actually like this new upgrade even on mobile, never used to comment via mobile but now it's slick.

...if i'm honest i was a little bit overwhelmed and lost, too. But for me is not really the platform itself important...ok performance and some things are but the really important thing is....the people who are running this are already here And with that community such optical things like the right balanced CSS and colours are only a question of time - to get changed in the right manner and style! Since this is more a opinion topic, this is mine. Regards mr-fan

Cool - thanks Craig, I'll likely set one up soon then I'm actually impressed with myself how I'm managing to keep calories on target most of the time (was hopeless prior to this) and am finding seeing my pace per km increase on the same run every few days is a real incentive to keep going. I have only been exercising properly for a couple of weeks, but have lost half a stone already just by dropping the amount I'm eating to more sensible levels (no crash/fad diets here, just better portion sizes and measuring things properly) and the exercise of course can easily cancel out the calorific intake of one of your meals a day. If I was to try and get to more competitive levels or do longer distances I'd have to look more closely at the diet aspect but... well... I'm finding that whilst it can be a chore if you don't log the food as you eat it and spend 10 mins at the end of the day doing it, the stats are quite fascinating over time. I've also hooked up my Fitbit account to Strava as a lot of friends are on Strava but not Fitbit and the runs get ported across automatically. It's basically a social network for runners/cyclists/hikers but I've not looked into it much at all to be honest beyond linking them together.

i think the ace is an awesome addition, and can't see why anyone would want plain text.. i'm ok with having the ace in for Tracy, as it could be tricky to handle if someone doesn't have it, and since you only need PHP that makes the requirements less. Adding a config to deal with the big Ace could make things overly complex. Snippets manager would be great!

Where do you see somebody posting something negative and why do you call it negative where somebody just gives his opinion ? I could tell you why but if you follow the likes in this forum you can see for your self. What kind of arguement is that ? Going through a lot of trouble and or spending a lot of hours into something does not guarantee a good result. My opinion is that the new forum look has become visually totally cluttered and over exposed. I can't see anymore where online people are looking in what channels in the forum or who is currently reading in a thread like before. If I now hover over an online name the bottom of the popup disappears under the taskbar. The old forum look was clear, without fancy stuff and functional where it needed to be. What now happened with the forum upgrade will eventually also happen with processwire: pumped up with fancy stuff and Apple look a like styles. Status Quo rules everywhere. Am I being negative here or trying again to give my unbiased objective opinion ?

Looking for a little advice. I have just added ACE Editor to the Console panel (not committed yet): Questions: Do you think we need an option to revert to a standard textarea or is having ACE loaded the only option ok? This works without having either of the PW ACE modules installed so I am just packaging the ACE core, the PHP highlighter, and one theme (tomorrow_night). Is everyone ok with this, or would you prefer to have the ability to change themes? If I do this, then I will probably require InputfieldAceExtended to be installed to prevent a huge download included with this module. Any thoughts on whether adding a snippets manager to this panel would be useful? It would allow you to name and save code snippets which can be loaded dynamically from a select field. Any thoughts or suggestions? Thanks!

Hi @ceberlin - glad you are finding it convenient. Sorry there was a problem with your upload though. It shouldn't be a number of entries issue - I have imported thousands of entries without a problem (although field Table itself is slow to render with that many until Ryan adds pagination - hopefully soon). Any chance you could send me the file in it's original form so I can test and add some checks for illegal characters etc. Just to confirm - was the exported file exported using this module? Sounds like I might have an issue there. BTW - what version of PHP and PW are you running? There is already an overwrite option - you just need to enable it:

If it's the colours and sizes, thankfully those can be tweaked...(just as Ryan will be tweaking the store). So, maybe we could create a dedicated topic where we could gather some constructive feedback for @Pete. It would have to be limited to (mainly) the CSS and not the software per se, since due to various reasons touched on above, we can't go back to the older forum. Mind, I am not saying that everyone's wishes would be enacted but at least it would be one central place to gather feedback :-).

Thanks to some testing by @tpr the ToDo panel now supports the "loud" comment operator (/*!). If you don't know what this is, it lets you write comments that won't be lost when a scss file is compiled or a js file is minified, eg: /*! TODO that won't be lost when compiled/minified */ This should be very handy if you you have your source scss and js files above the /site/templates/ folder Also, @tpr mentioned the following which some of you might find useful:

A personal thanks for providing this version.

I made a precompiled edition, here you go : https://github.com/flydev-fr/site-pwbs4/archive/precompiled.zip The installation process is the same, but no command-line or external tools required.

Sure, I'd be glad to elaborate. Here's the outline of the update process: Update the MLS, processing each property type and property status individually for flexibility Get layout of RETS parent class (In my case Property) and RETS listing type tables (In my case A, B, C, and D) using GetClassesMetadata and GetTableMetadata Populate list of available MLS entries with only MLS, internal ID, and modification timestamp. $connection->Search('Property', 'A', '(LIST_15=ON6KCGQ87YK),(LIST_104=Y),(LIST_12=2013-06-02+)', ['Select' => 'LIST_1,LIST_105,LIST_87','Limit' => 'NONE']) The LIST_15 part of the query is a filter for status. Sadly, RETS makes heavy use of lookup fields, so you have to find the code for the value you want on the lookup table before you can find the value to use for the query. Fortunately, this is only an issue for field values used in the RETS queries themselves. Delete listing pages that no longer exist on the MLS For each listing without pages or each listing with a changed timestamp { Populate MLS data using data collected by querying for all fields from only the one property Update all photos if the photo timestamp changed (iterate the media using a GetObject -- PHRETS makes this easy) Update all documents if the document timestamp changed (mostly the same as with photos) Precache the resized images of random listings Precache the long-lived WireCache snippets of random listings Aggressively delete unused asset files, including unneeded and obsolete image sizes. 10 GB of photos and documents is plenty. This code also forces a photo update if photos are missing. Delete expired log files Prerender homepage and pages linked from it with ProCache curl -sS `curl -sS https://website.com/|grep -oE 'listings/([a-z]+)/([a-zA-Z0-9-]+)/|quick-search/([a-zA-Z0-9-]+)/'|sed -e 's/^/https:\/\/website.com\//'|sort|uniq` >/dev/null I'm sure there's so much I missed; I'll be doing well if this even makes sense! One thing I didn't cover above is the replay mechanism. If I make a change to RETS value parsing, I can easily run a complete offline update using the cached JSON data from each listing. It's a big timesaver.

The performance improvement for Inputfield forms sounds incredible. Looking froward to testing that out. The largest number I have to test with is about 60. It was never "slow" before, but it was slower than other templates with 5-10. Great work as always Ryan!

InputfieldSelectize A Inputfield to provide a select interface for Processwire CMS FieldtypePage using the (awesome) Selectize.js jQuery plugin, by Brian Reavis. Selectize: https://github.com/selectize/selectize.js Modules directory: http://modules.processwire.com/modules/inputfield-selectize/ Github: https://github.com/outflux3/InputfieldSelectize Features Custom designed options and items for any page select field. Your select options can use any field or subfield on the page, but also sub-subfields, or any data you provide, since you are not limited by tag replacement: you control the precise data supplied to the options using a PHP array that returns data to the module, which is in turn supplied in JSON to the select as adata-dataattribute. The plugin uses the JSON object for each option meaning you can do whatever you want with that data in designing your options/items. Each instance lets you define which fields are searchable for the select Your selects can use display logic based on the value of any field/data item, for example using ternery conditionals you can avoid empty parenthesis. You can design the options and items (what is seen once an option is selected) independently of each other. Therefore you could have special fields on the options for searching, but exclude those on the item. Likewise you can show elements on your item like an edit button which is not needed on the option. Multiselect pages are sortable, and deletable by backspace or optional remove button. When AceExtended editor is installed, the module will use that for the code input fields. Usage Install the Module Edit your pagefield and choose InputfieldSelectize as inputfield. You will see the empty fields that need to be populated to make this work Notes For examples of what you can do (in general) with your selects when using Selectize.js, view the plugin site at http://selectize.github.io/selectize.js/. The plugin theme is selected on the required JquerySelectize module ----- Examples Basic Example PHP (the data array for each item - this must return a plain array): $data = array( 'title' => $page->title, 'company' => $page->company_select ? $page->company_select->title : 'Not set', 'total' => count($page->recipients), 'editUrl' => $page->editUrl ); return $data; Javascript (item and option same) Here, the item.property each refer to the keys of the PHP array that you returned in the above field. This field must be a valid Javascript string with each of the properties you want to show as demonstrated below, and recommended to use the escape(item.property) syntax. These strings are passed to the render functions of the plugin. '<div class="item">' + '<span style="display:block;font-size:14px;font-weight:bold;">' + escape(item.title) + ' (' + escape(item.total) + ')</span>' + '<span>' + escape(item.company) + '</span>' + '</div>' Example screenshot: A more advanced example This example shows how to use conditionals for the PHP and JS to get the select options to look clean and provide the necessary information to assist users in choosing the correct options: PHP $data = array( 'title' => $page->title, 'year' => $page->year ?: $page->year_sort, 'for_inst' => $page->for_inst, 'edit_href' => $page->editUrl ); return $data; Item Javascript: '<div class="item">' + '<div style="color: black; font-size: 14px;"><span style="font-weight:bold;">' + escape(item.title) + ' (' + escape(item.year) + ')</span>' + ' <a class="pw-modal pw-modal-medium" href="' + escape(item.edit_href) + '">Edit <i class="fa fa-edit"></i></a></div>' + (item.for_inst ? '<div style="color:gray;">for ' + escape(item.for_inst) + '</div>' : '') + '</div>' Option Javascript: '<div class="item" style="width:100%;">' + '<div style="color: black; font-size: 14px;"><span style="font-weight:bold;">' + escape(item.title) + ' (' + escape(item.year) + ')</div>' + (item.for_inst ? '<div style="color:gray;">for ' + escape(item.for_inst) + '</div>' : '') + '</div>' Example with images In this example the selects will feature a thumbnail image: You could also set the width of the selected item to 100% depending on where you place the field (e.g. in a column) $image = $page->images->first(); $thumb = $image->size(100,100); $data = array( 'title' => $page->title, 'thumb_src' => $thumb ->url, 'img_dims' => $image->width . 'x' . $image->height, 'img_desc' => $image->description, 'img_size' => $image->filesizeStr, 'edit_src' => $page->editUrl ); return $data; '<div class="item" style="width:100%;">' + '<div class="image-wrapper" style="float:left;"><img src="' + escape(item.thumb_src) + '" alt=""></div>' + '<div class="info-wrapper" style="float:left; padding:5px;">' + '<span style="font-size:14px;font-weight:bold">' + escape(item.title) + '</span><br>' + '<span>Dimensions: ' + escape(item.img_dims) + 'px</span><br>' + '<span>Filesize: ' + escape(item.img_size) + '</span><br>' + '<span>' + escape(item.img_desc) + '</span><br>' + '<a class="pw-modal pw-modal-medium" href="' + escape(item.edit_src) + '">Edit <span class="ui-icon ui-icon-extlink"></span></a></div>' + '</div>' '<div class="item">' + '<div class="image-wrapper" style="float:left;"><img src="' + escape(item.thumb_src) + '" alt=""></div>' + '<div class="info-wrapper" style="float:left; padding:5px;">' + '<span style="font-size:14px;font-weight:bold">' + escape(item.title) + '</span><br>' + '</div>' + '</div>' Current Notes & Issues: Works with 3.0.23 devns Doesn't currently support creating new options (and may exhibit strange behavior if you try and add one not in the list) Doesn't yet support optgroups

If you're interested in running ProcessWire using PHP's built in Webserver this one's for you: <?php /***************************************************************************** * Router script for emulating Apache's "mod_rewrite" functionality. * This router script is designed for testing ProcessWire instances quickly. * Don't use this script and/or PHP's built in Webserver in production. * * Usage: php -S localhost:8000 -t /ProcessWire /ProcessWire/routing.php *****************************************************************************/ $uri = urldecode(parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH)); if ($uri !== '/' && file_exists(__DIR__ . $uri)) return false; $_GET['it'] = $uri; // emulate index.php?it=$1 require_once __DIR__.'/index.php'; Enjoy!

The only game I got into for a bit was Wurm Online (created by Notch and Rolf) - but to be fair, I did compose the music for it, so it wasn't quite the same. I also messed with their site for a bit, but they have taken that over themselves these days. I was going to use Liferay and weld it into the game itself, so that actions taken in the game (like creating a village with friends) would be reflected in the Liferay community system. But we couldn't find a dev that was up to linking the systems securely, so it fell over. For a bit of fun, I have been playing Age of Empires 1!