Leaderboard

I thought I'd chime in and answer some questions first and foremost as I saw people chatting about this here. We initially moved because we wanted to add some functionality that would have cost too much to develop. My biggest issue myself is that I am not a developer (i'm a tinkerer) and I wanted more advanced product pages, etc. Yes, they could for sure have been built in processwire but I felt that for someone like myself who is not a code guy, I was too limited by the product as I simply don't have the time to learn enough PHP to code and hiring a developer to do work i could theoretically do myself with wordpress seemed like a waste of money. So those were the initial motivations for moving. Now that we've moved, however, the whole "grass is greener" effect has faded and I have some regrets, however, the extra functionality has allowed us to make more sales and bring on new customers that we didn't have before. So it's a catch 22 for me. I'll expand more on this further down. I don't think this is a fair statement, frankly. The initial point of our website was to view things from an end users point of view, not that of a seasoned developer. Our reviews don't go into how easy it is to code with something but rather how easy it is to use, how functional, etc. These are the things most of our readers want to know as we tend to get a lot of traffic from those who are looking for software but don't have a development background. Yes, this grade sucks. Part of the issue for me is again, I'm not a developer so we clearly need to work on things. This is good to know, please do tell me what specifically you feel is missing so we can fix it. ProcessWire is an awesome product and Ryan did a ton for us. Ideally, I would have loved to have simply paid him to make everything we have now work on PW. If that was a possibility and the cost wasn't too high, I would have gone that route. Sadly, it just isn't feasible sometimes and I often look for alternative ways to compensate those who work for us. Before our move to WP, the intent was to search out vendors who were willing to take on the task of building our site on their platform in exchange for an agreed upon advertising term. In other words, they build our site on their platform (which is a bonus as then their product gets noticed more, as was the case for processwire) and in exchange, we offer advertising for an agreed upon term as the form of payment. With the case of PW, however, this didn't work and we needed to pay for the development costs up front which, while worth it since Ryan is so awesome.. tend to get costly when every tweak needs a developer. If I'm able to find someone with a development house who wants on the advertising in exchange for work method, I may be able to pull off a move back to PW but until then, I may have to search out other alternatives. Fortunately, there are plenty of companies that are interested in doing this but I'm picky so moving is a decision that I need to consider deeply. Normally I wouldn't share these kinds of details to this extent but I feel I owe this community, which we've been part of for a long time, an explanation. So here's the pitch: If there's anyone out there who wants to take on the task of making what we need a reality and getting long term advertising for their business in exchange, drop me a line. Until then, the search for an alternative may continue as WP simply seems to be causing too many issues and bloat (I should have seen this coming granted but hey, nobody's perfect and a critic isn't always right). Thanks for reading Mike

Hi, a while ago, we redesigned the corporate identity for the event- and catering agency p.events Event & Catering oHG based in Germany. Along with the new corporate design we also developed a new website based on ProcessWire 2.7: http://www.p-events.de The website's current focus is the presentation of p.event's services and therefore makes use of many images. It is planned to extend the website with a blog and a more sophisticated inquiry form in the future. The website is fully responsive (including images with srcset), uses free-flow image sliders and some CSS3 features like animations. We're looking forward to your feedback Cheers Alex

A quick update folks. A member of the forums has reached out and offered their services so perhaps you'll see our return to ProcessWire after all. We shall see.

No need for a extra Process page. Just send a ajax POST/GET request with a special key you recognize in your module's init(), do the work and send back an result.

v027 is up with the Tooltips submodule. The CSS got a bit complicated but hopefully everything will be fine forever so I don't have to dive into it again You can switch whether to use it for field descriptions and/or notes, and whether to use the "overlay" style.

Thanks Mike for that honest and transparent answer to the discussion. Being low on budget will always force projects to make trade-offs even if one would like to not make them. And as you've experienced it: Not everything that looks shiny in the first place will ultimately be as simple, which is also a valuable insight for anyone here needing to tell that to customers.

@cmscritic Hey Mike, The fact that you can drop in and share with us so much about your reasons for the move says a lot about you. I like that; I respect that. As others have said, we've also gained a lot as a community from your collaboration with Ryan: Hanna Code, the awesome CMS Critic development write-up, and who knows how many people have found ProcessWire because of your site . So, thanks for the ride... Best wishes for the future.

Ian, I'm not sure what components of the URL correspond to each URL segment, but it looks to me like possibly the issue is urlSegment2 not urlSegment1. You've got lots of good URLs to test with there from that screenshot, so you'll want to make sure that when you access the page at a URL like that, you get a 404. That will solve the issue. Also, if you are only needing 1 level of URL segments, I would suggest doing your comparisons against $input->urlSegmentStr rather than $input->urlSegment1. For instance: $fam = $input->urlSegmentStr; if(strlen($fam)) { if(!isValidFamily($fam)) throw new Wire404Exception(); $specieslist = $pages->find("template=species, limit=12, fam=$fam"); if(!count($specieslist)) throw new Wire404Exception(); $fam = $sanitizer->entities($fam); $metatitle = "British Moths | Thumbnail List by Family | $fam"; $title = "Families: $fam"; } Using $input->urlSegmentStr is better because it is inclusive of all URL segments. So if there are extra URL segments packed on to the end (like the bogus ones we see after the family names) then this will catch it, without you having to check $input->urlSegment2 separately. For example, the $input->urlSegmentStr of the page accessed at /thumbnails/gracillariidae/ would simply be "gracillariidae". Whereas if accessed at /thumbnails/gracillariidae/some-bongus-junk, then the urlSegmentStr would be "gracillariidae/some-bogus-junk", which presumably your isValidFamily() function would be able to exclude.

Thanks! Actually it's not the module's CSS but the base (Reno) theme. My module only overwrites values, though I tried to fix this but with only partial success (on load the initial CSS styling was still visible). Now I corrected this text color issue (no version change).

Wow! Works like a charme!! The only thing I would change is the color of the bold text in the tooltipps. I dont know why but, you use #777 as color. I think the contrast between the background and the color of the bold text is not really good. Here is your CSS part: .description strong, .notes strong { color: #777; font-weight: 700; } I would use #fff for bold text too so it would be better readable. Congratulations to this awesome module!

Wow! Thanks for sharing, @adrian. Glad to see that the article seems useful. I was afraid that this idiom is very emotional, and thought to delete it later. Now I'm going to keep it

Hello folks I have updated the code in my rest helper. Since It was created nearly 2 years ago! Now its much easier to create rest endpoints in Processwire You can download the code here. https://github.com/NinjasCL/pw-rest This is and example simple login code. $response = new Response(); $params = Request::params(); if (!Request::isPost()) { $response->setError(MethodNotAllowed::error()); } else { $username = $params['username']; $password = $params['password']; if ((!isset($username) || $username == '') || (!isset($password) || $password == '')) { $response->setError(Login\Errors\InvalidCredentials::error()); } else { if ($username == 'hello' && $password == 'world') { $response->output['data']['name'] = 'Tony'; $response->output['data']['lastname'] = 'Stark'; $response->output['data']['job'] = 'Ironman'; } else { $response->setError(Login\Errors\InvalidCredentials::error()); } } } $response->render(); Will render something similar to { "data": { "name": "Tony", "lastname": "Stark", "job": "Ironman" } } Any questions or comments are welcome

Great, glad you got it figured out! You must have literally fixed it between the time I reloaded the page, and clicked "view source", since one tab had the issue and the other didn't.

Yes, I think so - and you posted while I was writing my reply!

Hi Mike thanks most times i come to cms critic so i can know what cms exists for different platform e.g CMS for .NET or CMS for Python you guys had that feature and it was awesome but now it's missing and it makes it harder for me to explore other CMS out there. If you can bring it back i'd be extremely happy, because it was very easy and convenient with your site.

Thanks, I haven't noticed that (I'm using the "Compact header"). This should be fixed in v028 that is just uploaded + some small other fixes.

AsmSelector doesn't seem to be loading if it's in a repeater or matrix repeater 3.0.24. However putting an Asm field outside of the matrix will load the javascript needed to make it work inside the matrix.

What I have also discovered is a z-index issue of the tooltip icons. As you can see the icons are always visible if you scroll the page down.

Hello friends, I saw the great videos tutorials that Processwire got in English and German, but not in Spanish. So this is my first video, also was a good practice for learning ScreenFlow and Video Edition. This video covers a simple Installation on a local server using MAMP.

Que bien, hace falta mucho para la comunidad hispano hablante.

Works really well TPR. Thank you for adding this feature.

Wow - I was surprised to read this and even thought it was a joke. I'm sorry to see CMS Critic go. They did a lot for ProcessWire in that short space of time. Then again, ProcessWire does a lot for ProcessWire too I'm sure both parties will survive their CMS Brexit! Regardless of the CMS which powers CMS Critic, I must admit I almost never visit the site. IMHO they primarily have a design and information architecture problem and not a CMS problem. Ok, they're running on WP now so they have a CMS problem once again but you know what I mean ...

A really great article from @M.O.Z.G highlighting his migration from WP to PW. It talks about structuring and retrieving data, multi-language output, creating your own module, and debugging using Tracy. Thanks for a great writeup - really nice work! http://mozg-studio.org/blog/migration2pw/ I have to include this quote from the article