Leaderboard

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.

Another commit today containing the new Hotkeys submodule. This enables saving page on ctrl+s, even from within CKEditor. What's more, it works on various page types, eg. when editing templates, fields, roles, etc. As there was no general rule I could apply to save pages, I had to manually add the enabled ones, so if you find a page type which doesn't work but should, please report. If enabled, the submodule will disable the default browser Save dialog on all admin pages. I think that dialog has no function in the admin but correct me if I'm wrong. On save there's a white overlay with a fancy css3 animated floppy icon, to indicate something's happening:

In case someone is wondering about the PW 3.0.22 new password field functionality ( InputfieldPasswordComplexify ) compatibility, this is what you will need in the <head>... <link type="text/css" href="/wire/templates-admin/styles/font-awesome/css/font-awesome.min.css?v=17j" rel="stylesheet"> <script type="text/javascript" src="/wire/modules/Inputfield/InputfieldPassword/complexify/jquery.complexify.min.js"></script> <script type="text/javascript" src="/wire/modules/Inputfield/InputfieldPassword/complexify/jquery.complexify.banlist.js"></script> <script type="text/javascript" src="/wire/modules/Jquery/JqueryCore/xregexp.js?v=1466417387"></script> <script src="/wire/modules/Inputfield/InputfieldPassword/InputfieldPassword.min.js?v=101-1466417387"></script>

What about if($PwVersion >= 3) to if($PwVersion >= 2.8) ?

The issue has been solved, thanks to the help from Adrian. For those who might get into a similar situation, the culprit is the mod_security. Here is how it all came about; I have a shared hosting environment and the mod_security had been activated recently for all my domains in the hosting setup. While everything had been fine for a long time, suddenly one day the mod_security decided to kick in. The problem may seem a minor glitch in the beginning, and you may begin by clearing up your cache, refreshing the modules and doing a core upgrade to the latest stable version. If any of these help you to solve the issue, great. If not, then try disabling the mod_security and then refreshing the site. In my case it solved the issue and everything came back to normal. If it does not help, then you might have to look at other possible issues in the forums. Best.

Hi, I'm just posting this in the hope it might save someone else a little time one day. I went to do a database backup using SQLyog Community version. I hit an error which said 'tables used by Event Scheduler were found damaged at server start' . It took me a bit of Googling before I found a fix. I was just about to run an upgrade on MySQL in the hope of fixing the problem and one last Google came up with the solution. Love it. Anyway, the fix was to run this command from the command prompt ( In Windows) : mysql_upgrade -u root -h localhost -p --verbose --force Found the fix here : https://serverfault.com/questions/562282/mysqldump-error-1557-corrupt-event-table/562303

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

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/

Glad it helps - if you want some extended reading, here is the post that spawned my module: Lots of interesting reading on those file/image hooks.

You could use this module: http://modules.processwire.com/modules/process-custom-upload-names/ Or if it looks too heavy for your needs, grab some code from it: Admin InputfieldFile::fileAdded - https://github.com/adrianbj/CustomUploadNames/blob/master/ProcessCustomUploadNames.module#L97 Frontend API calls Pagefile::install - https://github.com/adrianbj/CustomUploadNames/blob/master/ProcessCustomUploadNames.module#L101

Selectors cannot handle multiple level nesting by using the dot-syntax, but you can use subselectors: https://processwire.com/api/selectors/#sub-selectors

@Pete Jones Try this one, as it should prevent duplicate page selections by later selectors: https://github.com/LostKobrakai/Paginator/commit/e515bbba8a33be9259be810ff80ad2ad61078497

Thanks! Glad to hear that. I also use it on my sites and it speeds up navigation and feels better, but of course that can be because it's tailored to my likings. What submodules are you using? I've also thought about adding edit links to fields/templates like HelperFieldLinks do, but without the info popup. v021 is uploaded to GitHub: sticky admin tabs when compact sticky header is enabled stickyCKEditorToolbar fix for multilanguage fields module submitted to modules directory CSS fixes The tabs are sticked to the header so when the site is scrolled down they are still visible, no need to scroll up.

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!!!!.

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!

Hi franciccio, this forum runs using a piece of software called Invision Power Board: https://invisionpower.com/ Building a full forum system can take a team of developers years to implement as many features as you see here, so it's not something you can build yourself easily. All I have done with this forum is change the HTML and CSS to closely match the main ProcessWire.com website.

PrevNextTabs Module Github: https://github.com/outflux3/PrevNextTabs Processwire helper modules for adding page navigation within the editor. Overview This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.) Usage This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links. Warnings If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits. For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed. http://modules.processwire.com/modules/prev-next-tabs/

Was it really necessary to change the forum to this? This is a real down tuner for me.

No, - no other / better ideas here. Just trying hard to follow up with most of the new stuff here (in the forums). Wondering how to best store / load / exchange them between different sites / installations. Textarea populated with json or simple json files?

Could you possibly give us a little bit more information on how your templates are set up etc?

Thanks for this, adrian. Really useful.

Carousel: http://kenwheeler.github.io/slick/ As for the grid im using susy and make my own grids: http://susy.oddbird.net/ I dont use templates, all is custom build.

Hey @teppo, just tried the module on 2.8 and i get the error Argument 1 passed to VersionControl::isEnabledTemplate() must be an instance of Template on line 897, you have any idea of why that might be?

Hello Community, I'm glad I discovered processwire and there are no words to tell you, how amazed I am by now. My first post is a question, as just reading wasn't enough to find a solution this time - just to mention my great first impressions by the community. So hello all. Enough love for now, I'm stuck at a problem which I thought would be easy to solve - sitting here for a day now. Before going in detail, maybe I am missing something out in general: Is it possible to render a complete, specific page inside a template? With all the markup rendered just like an include + the content? In case it is, here are my details: I want to include my footer on every template via the '_main.php', as the footer does not change. The footer is a custom template with 4 textfields and a page ('/footer/'), as I want to fill in the content from the backend - there are no files prepended or appended on it. The footer-page renders fine, I can access '/footer/', but how can I render this page in the '_main.php'? So that I can change the footer in the backend (in all languages) and it prints on all pages? I tried the following: _init.php: $footer = $pages->get('id=1036'); // also get('/footer/') just to make sure - knowing now all this returns just the id $ftvar = $pages->get('id=1036'); $footer = $ftvar->render(); // This crashes my mysql $footer = $ftvar->children->render(); // Just tried everything I could find $footer = $ftvar->render('partial=true') // Throws error with and without '' - just found it, seems to be wrong as render does not take arguments $footer = wireRenderFile("/footer/"); // Understanding it now _main.php: echo $footer; And quite much other variations and possible solutions I can't remember anymore. I learned a lot about what the API can get out of templates and specific fields - but my problem remains. I hope somebody can clear some things up for me as I just started with pw. Thanks for your time!

I see you're using a limit, therefore I assume you're using pagination, where this one won't work. Use OR-groups to put both searches into a single selector, if you need pagination to work. If you need more control over the sorting of results take a look at this topic:

Thanks @Klenkes, my mistake was the wrong architecture in mind. No need to include a whole rendered page or a special template. Markup of footer inside of '_main.php', filling it with the fields from the page via get(); - done. Sorry for the extra long post and thanks!

Welcome to the forum! Just put this in your _main.php where the footer is: $footer = $pages->get("1036"); And you have all the fields of your footer page. (you can omit the id= in your selector) Then output your fields like that: echo $footer->yourfieldname; It's just one way of doing it.

Thanks Pete, love the newer feel and grateful (again) to you for the work. I noticed in my profile it says I have no 'Friends' <--insert joke here-->. I assume that's just some data that their migration process was not able to include, or should I start to worry o_O / change my brand of toothpaste etc?

SOLVED!!!! OK, here is, what I discovered, and a workaround: if you have errors on upload (database error, "not properly escaped"), look for single quotes ' in your file. If you cannot change and save the page any more (you click save and the page tries to save but nothing gets actually saved any more - and no php- or js error is given) try this: in PHP set "max_input_vars = 5000" as a workaround. max_input_vars = 5000 is unusual (there is a reason why the limit is normally 1000), so there is a possible bug in the pro table field which I will report now accordingly.

@Doug G It'll just give you desktop notifications (little boxes that pop-up in the bottom right of your screen) whether you've got your browser maximised or minimised. You do still see the same notification icon at the top right of the forums so you can turn them off if you like or turn them on - personal preference really. @flydev I think the idea is to keep it shorter so it fits on even the smallest mobile screens. Technically using the word "hour" make that bit of text wider than the photo above it so they've abbreviated it to be really short.

@adrian, Git branch integration next?

@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..

The headlines ever have linked to the first post. To go to the exact post, you need to click the date / time links (those with the clock). This behave also is unchanged, it is like before! The only thing what have changed is that the circles and or stars are gone, what should bring us to the first unread post. But this only have moved. Now you personally can set this as your default behave. And with the new forum we can adjust a lot to our personal likes, what we couldn't do with the older one. I like it more and more. The embedded search is better now too. (Not that good than the google one, but better than the old one) I really appreciate @Petes hard work here. To me it looks like he is figthing a big thing. If you read the first announcement, he said that the forum would be down for 6 hours +, but later he changed this to an estimated downtime of only 30 minutes!, but with an uggly presentation for the first hours, as there have to run a massive background task to incorporate the old content into the new forums presentation. Alone this one is a massive support to the community. And if something wouldn't have went well, it would have been only up to him to fix this. He really trusts into the coumminty to do well with (not editing) the old contents during this period. (To be honest, I wouldn't have done so. I would have totally closed it for 12 hours. ) So, a big thanks @Pete!

@ceberlin Yes, you should be able to. In the old forum you would edit the first post and select 'full editor' or something like that. In the new one it should take you directly to a full editor, I think. For people searching where they could post their views about the new forum a title like 'New Forum: Feedback' is more obvious than why!!!! (which btw, is very different from why? ).

I especially found the frontpage forum overview to be a visual mess. Giving a fast overview does work different. The "explore questions" thing in some subforums (Q&A style ones I think) is also taking up way to much space imho. This might work as a sidebar element, but not above the actual content. Also the modules forum does suffer a lot in readability because of duplicated tags. I think everything else might really work out over time.

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.

After the update the forum is much slower here on mobile, but maybe my phone is slow. I hope the conversion is still running so that's why its slower. What bugs me more is that headlines link to first post and not to the last. Is there a setting to change this? Clicking the last comment date links there but it's inconvenient.

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.

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!

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?

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 :-).

Diego, I am normally a very positive guy. This forum has become a very important tool for me. I need to be able to find things quickly and easily. I was trying to look up a problem I have in the pro modules area and was stuck (which was not because of learning curves). Now the headlines are dimmed (40% or less grayscale??) and unimportant stuff (back TAGS, "who asked"-line, and the green check icons get much more attention.) I have not read the announcement yet (actually I was looking for it an did not find it) and understand that the update was necessary. I think that some setting tweaks with colors and sizes can help a lot already. And it is good to read that the Q&A style is not the final word for every forum (thanks for the info, adrian).

The Q&A style is probably going to go away for most boards - it certainly doesn't work for example in the Modules/Plugins board.

Looking closer at it, the structure is maybe not the problem. It's the choice of colors and opacity. The most important thing are the headlines, they should not be dimmed. That's the main difference with the previous look. Other elements are attention-grabber but have no important function (huge black bars, like buttons that look like facebook buttons). And time will show if the simple question/answer methodology (yes it's trendy) helps. Usually the threads here are much more complex than simple question/answers.

Just a heads up that the newest version (ProcessWire 3.0.22 devns) breaks some things, one of which is module settings fields on some modules, this being one of them (the Placeholder Text field will not save any value). (Still looking into the cause and hope to discover fix soon as it also affects my inputfield modules). **This is now fixed in 3.0.23 devns**

I have setup an online test server and uploaded/installed the pre-compiled profile (template) inside a processwire 2.7.2 setup. It looks everything is working well and also nicely responsive. I find this great. I am going to have a look in the back and front end and see how I can change it into some website and learn bootstrap and tether. You can see the online setup here: http://dev9.pe.hu

Thanks! As for js/css comments: silly me, they are stripped on minification My source files are one dir up from /site dir, maybe that's why their comments are not showing up? But there was an umninified Js file whose comment was shown before the update (baguetteBox.js), and it's in site/scripts folder.

Just added a ToDo panel: It reports the following comment types: 'todo', 'fixme', 'pending', 'xxx', 'hack', 'bug' If you have your editor configured, the comment text link opens the file to the line of the comment. The icon reports: the number of items in the template file for the current file / the total number of items across all files. Red: there are items for the current page's template file. Orange: there are items in other files, but none in the current page's template file. Green: no items in any files under /site/templates/ Please let me know if you find any items that aren't being reported, or items repotred that shouldn't be. One other key change in the last commit is to the Console Panel - you can now use CTRL+Enter or CMD+Enter to run the code. This keeps your hands on the keyboard and keeps the code textarea focused making it much easier to quickly make and test changes to your code.