ceberlin

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.

kongondo - sounds great. Exactly what I was trying to say (English isn't my first language). Where would be a good place for it? (When I started the thread, I thought only a skin was changed, not the whole software.)

First of all: thank you very much for the great module. This is so convenient to have!!!! Just a small feedback: I managed to shoot my table down. Maybe to many entries (250) maybe and invalid file. No big deal, I have backups and the full database saved as CSV. I got warnings from PW about not properly escaped things (don't remember exactly the wording). And, yes, I found some single and double quotes in table cells from the import file (actually an exported and then re-imported CSV file), After deleting those chars, the import worked. If this is possible, maybe a warning about illegal chars or a proper escape during import would be very useful? Also in my situation it would help if there was an "import & replace" feature. So I can do another import that is properly replacing a malfunctioning previous one. Right now the import was added. (Now my table has double entries - and maybe even double IDs because I cannot select and delete an entry any more, it re-appears after a save) A replace would be a convenient way to clean this mess up quickly.

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

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.

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

What I basically would need is that the ratio is fixed (and there is a minimum of height/width it can't go below). So users can select parts from the image to crop but that crop would always fit 100% and no further cropping would apply when using the image.

Trashing images stopped working for normal image fields (PW 3.17 and 3.18)

Hi Horst, thank you for your quick replies (I know you are busy)! If I can say thank you with a little invitation, send me a pm. That said, I was really inadvertently resetting all crops (many, many) on my test site. But I had a backup in place, I know I run on thin ice with early beta software but I am so extremely happy that the cropping is working again. I was expecting that - as you wrote earlier here - it does not matter if the cropped versions are deleted, they would be recreated with the stored cropping coordinates. But in fact they were all reset to default instead. Maybe that had to do with the fact I was updating the module only and had no fresh setup. After the page is saved once, the positions get remembered most of the time, but still not always. - If I have more information, I will file a report at your GitHub page.

A compatibility warning: After testing this with the new Croppable module (which is currently in beta and works with PW3 beta): https://processwire.com/talk/topic/8709-croppableimage/page-7#entry119754 Right now this SpringCleaning module treats crops as "variations" and resets then too! - This is not desired in most cases!

By the way, for anyone interested: For an aforementioned spring cleaning there is a little module existing already (credits to Horst and tpr): https://processwire.com/talk/topic/261-where-to-set-image-resizing-quality-and-how-to-re-resize-images/page-2 Update: A WARNING: Right now, that spring cleaning module treats crops as "variations" and resets them too - which normally is not desired.

Interesting. Did not know about forceNew although it's in the core for a year already. Thank you for the hint. Very useful for spring cleanings. To add an automated approach I could try to find all variants and see if any of their dates are older than the one of the master image. In each template where the image occurs. Is it this what you mean? I am just worried of the overhead and it makes the implementation of variants of cropped images in templates more complicated. Isn't it a much easier and newbie friendly approach to just have the module remove existing variants (if any) on saving if the crop, so PW simply can recreate them if and where needed? (If that helps: the old module version / PW2 worked flawlessly already with those recreations, no further action needed.)

Thanks a lot again, Horst. Looks like the update created no problem. During the process I run into an Exception after hitting "Update Modules". But clearing the compiler cache files another time and hitting "Update Modules" again, fixed it. I have something funny because I use the cropped image to resize it further with PW. Here's what I tried I change the crop and save the page I check with FTP that a new cropped version is saved that looks like I want it In my code I work with that image as source for further manipulation, like so: $img_medium = $child->keyvisual->getCrop('header_thumb')->width(767, array( 'upscaling' => false, 'cropping' => false, 'quality' => 70 ) ); Expected behavior: those get updated too. Current behavior: No change to the images (PW does not detect them as changes and to be redrawn) I delete those variants manually with FTP to force a redraw - PW redraws them correctly now Is this an issue to report for PW or is this something with the module so PW3 does not know about the change?

This is SOOO cool - thank you Horst!!!!!! If the module was previously installed (old version with PW2.x) - can I just continue using it (with PW3.x) or are special steps needed/recommended now to update to the beta? (My first impression was it works right away but I am still testing.)

Hi Teppo, is it possible to use Swift Mailer's S/MIME encryption capabilities somehow with this module?

Hi Horst, a quick question to the roadmap: is this module still maintained or do I need start looking for an alternative? In PW 3.x I have the problem that, if I change the crop later, it is reflected in the preview but the frontend image does not always update to the new cropped version. (If I am the only one having this it could be also a misconfiguration or rights problem?)

I solved it by doing it a little bit differently - now sorting and filtering works: $siblings = $page->siblings("sort=date"); $prev = $siblings->getNext($page); $next = $siblings->getPrev($page); "Last" and "first" can be tested easily: if you reach the last or first item, $next or §prev return NULL (or have no ID) - LostKobrakai's code works great to catch that. So the difference was that I build my own pageArray ($siblings) instead of using $page, as suggested, to enable sorting. It was so easy to solve that I did not see it right before my eyes

Do you have the demo without/or different music? The German GEMA and SME had YouTube blocking the video for Germany.

One more idea For testing and debugging malfunctioning redirects (redirects can come from so many sources, htaccess, PW core, modules) it would be great to being able to either deactivating the module temporarily (preferred) or to temporarily uninstall the module without loosing all the stored data.

Avoiding cross language linking are a big SEO topic. An option like the one you mentioned would be great. (And maybe that all is only needed if Languages are active (module installed, more than 1 language counted?) Or leaving it as it is and adding a language selector for the installed languages placed before the target link and shown for multilingual setups? - Just thinking loud. What the module has and what I like is a very good search for links substrings on the source and target side (think of cases of 500+ redirections). And a debug option where every redirect is logged and shown the same way as 404 errors, with listing source and target for each incident. In case of redirect problems (first of all: loops) those information can be extremely valuable. And it has an optional cache.

(3)The buttons are there: Do you want to have access to a website where you can see the plugin in action? It's pretty advanced. Maybe it is inspiring for your new project? I installed the beta from today: I set this and still got this after save: The string that I had set manually "en/helium-vola/" had been replaced again by the page-id and ignoring the language. If you touched that in the beta, the behavior is still unchanged...

Yes en is replaced with de on save (or maybe without any language path information and PW adds this later) That the module does not handle languages is a surprise because I thought it did - South Africa alone has so many languages ) OK, what I see: it keeps the paths at the source. If there is an /en/ in it stays there. The target is "treated" somehow. It appears that it shows the path always in the language I use as a user. If I change my user language, the target paths change. Not sure how the effects are if a bot comes. Probably always en or what I set as hreflang='x-default. Test buttons: The idea was to have a quick possibility to check if the redirect is still needed and still valid. I am used to this from a very good Wordpress plugin. (That plugin is a very clever beast, by the way: http://codecanyon.net/item/seo-redirection-pro/7596396 it even has a history for any redirects made - which is usefull to track errors, if you have many redirects - on of our sites has 500 redirects) I would not have a problem with wildcards are left out and the source button is inactive in that case.

Small ideas: I would love a lot if there was an "external-link" button before the Source string and the Target string. Clicking on it would send me to a new window with the page loaded (or not). So I can quickly test the Target (valid) and the Source (if the redirect applied is working). I would like a dupe check - So the same string is not entered twice. If I use the 404 monitor to fix a link the link should be removed from the 404 monitor so I do not fix it twice

Not sure how this works... If the source link has a language in it (en) then I want to redirect always to that language: en/label/carl/ --> en/label/management/ Jumplinks does some autocorrection after save, and because I as a user have my profile language set as de (German), I see this: en/label/carl/ --> de/label/management/ Did I set it up wrongly or is this something that goes wrong? (Google does not like cross-language linkings)

Interesting. The very trendy Google font "Merriweather" I use seems to be incomplete at Google (outdated?), it is missing the "fi" ligature and instead only shows an "i". Safari is now using ligatures. With this code I could tell Safari to stop using ligatures: -webkit-font-variant-ligatures: no-common-ligatures;