Leaderboard

Hi everybody, First of all: Thanks to everybody for keeping the community alive. Every time I search for something in the forum I find the solution. Great work! I wanted to share a small module with you / my first one. I use it in order to switch the user language on page load. Processwire GeoInfo GeoInfo is a small module that Implements Geoplugin PHP web service. Please donate to "geoplugin.com" in order to keep the service alive. The Module ads two methods to retrieve data from the web service. $page->GeoInfoIP('IP ADDRESS'); you can enter the ip address manually. If left blank the server remote address will be used. The retrieved data is then stored to the active session, in order to limit the requests. The web service gives back following data. 'geoplugin_request' 'geoplugin_status' 'geoplugin_credit' 'geoplugin_city' 'geoplugin_region' 'geoplugin_areaCode' 'geoplugin_dmaCode' 'geoplugin_countryCode' 'geoplugin_countryName' 'geoplugin_continentCode' 'geoplugin_latitude' 'geoplugin_longitude' 'geoplugin_regionCode' 'geoplugin_regionName' 'geoplugin_currencyCode' 'geoplugin_currencySymbol' 'geoplugin_currencySymbol_UTF8' 'geoplugin_currencyConverter' for e.g. $page->GeoInfoIP('IP ADDRESS')->geoplugin_countryCode; will give back the country iso code. $page->GeoInfoLatLong('LAT', 'LONG'); Enter Latitude and Longitude in order to get following information: 'geoplugin_place' 'geoplugin_countryCode' 'geoplugin_region' 'geoplugin_regionAbbreviated' 'geoplugin_latitude' 'geoplugin_longitude' 'geoplugin_distanceMiles' 'geoplugin_distanceKilometers' for e.g. $page->GeoInfoLatLong('40.712784', '-74.005941'); will give back the city name "New York City". Todo store places in json file / check if place exists implement nearby "service" https://bitbucket.org/pmichaelis/processwire-geoinfo

A highly configurable and flexible ACE editor input field. This module is sponsored in part by Nibiri, aka forum member Macrura which was a great jump start. So many thanks to him. See this short screencast to get an overview: Get it from Github or the Modules Directory. Roadmap add full screen mode expose a jQuery api for resizing, setting row count etc. add image handling like in Adam Kiss' version

This module does provide two different added functionalities to FormBuilder. 1. The module does allow users to set default "From" email addresses for emails send to administrators. There's a global address, which is set in the modules settings, and a additional field in the settings for "Send an email to administrator(s)", where one can set a form specific emailaddress to override the global one. Both of those are overridden if you chose to use the "Email from field" setting and the returned value is not blank. 2. The module does add an additional syntax for the textfield where administrator emails are set. If you have a pagefield in your form, where one can choose from the potential users, that should be emailed about your form submission, you don't need to write extensive conditional lines like this: personInCharge=SomeUser?someuser@example.com personInCharge=AnotherUser?anotheruser@example.com You can simply add a email field to the template of those users and use the email provided there. !personInCharge?email The syntax says get the user(s) from the field "personInCharge" and send email(s) to the addresses provided by the "email" field of the selected page. https://github.com/LostKobrakai/FormBuilderEmailExtentions Thanks to madeprojects.com for letting me share this. They'll pay the time I spend to build it.

I thought I'd start a thread where we could post links to kickstarters that we find interesting and that might be of interest to others. To kick things off I thought I'd post a link to the kickstarter for the Thunderbirds co-operative board game. For those of you outside of the UK who may not have heard of Thunderbirds before, it was a 1965 Sci-Fi show using puppets as actors that became very popular - I certainly remember it from my childhood. The kickstarter itself has a lot of backing already and is well into its stretch goals, but if anyone is interested in the show and the possibility of playing the game, then check it out and back it if you like it. Thunderbirds are go! Ok, what about kickstarters that interest you?

i think hanna code does need it's own version of ace, since a lot of people won't use this module; unless it is a really simple one, i mostly do hanna codes as files on the server, so the hanna code just includes the file (thx to soma for this idea); would be cool if i Nico's template editor module could have a setting somewhere to select the inputfield type and then one could set it to use this if it is installed; the use cases for the backend ace editor are many though - definitely people wanting to have a markdown editor could use this... I'm also doing YAML settings field with this.

I certainly shall do. It is not an issue that is causing us bother, it only took me 5 minutes to fix by upgrading the version of CKEditor that comes pre-packed with ProcessWire. The issue is with CKEditor and Safari. Safari uses a version of webkit that introduced a serious bug in the use query selectors (still not fixed either). So CKEditor introduced a fix so that CKEditor would function on Safari. I reference the posts on this CKEditor support ticket: http://dev.ckeditor.com/ticket/12423

There was a lot of focus on enterprise that crept into revo, so I like the sound of the added simplicity with 3.0. When I picked up a ModX evo site because of a new client, I remember being pretty impressed. I felt a sort of bond between myself and the Ukrainian guy who had apparently coded it; we both seemed annoyed by inefficiency. I still wonder if evo made him feel the same way it made me feel, kind of sad but hoping there would still be some nifty changes down the road for ModX. Just the other day while on a hike I was thinking about making some kind of "Bob's Guides"-type site for ProcessWire, because man, that site really helped a few times when I was working with ModX.

If the module extends at least WireData, you could also use setArray: public function __construct() { $this->setArray(self::$defaultSettings); }

@awebcreature I have modified the MapMarker module so you can add a polyline (both admin and front-end). You can download it here: https://github.com/madebymats/FieldtypeMapMarkerDraw Please note that you should not use the module in production, but may give you an idea how to build the functionality you needed.

just found another great tool with very different approach! look at this example of a regex to find emails: ^([a-z0-9_\.-]+)@([\da-z\.-]+)\.([a-z\.]{2,6})$ http://ysono.github.io/pegrex/#47%2C%5E(%5Ba-z0-9_%5C.-%5D%2B)%40(%5B%5Cda-z%5C.-%5D%2B)%5C.(%5Ba-z%5C.%5D%7B2%2C6%7D)%24 to be honest i don't understand the tool at the bottom, but i love the graphical mockup of the regex

u uses title 2 time like.this title%=red, title%=crap If.u no want crap buts do.want reddish crapapples do this title%=red, title%=crap, !title~=crap

While MODX and Symfony are probably great systems, their goals are not necessarily the same as ours. I don't think that anyone here (or anyone in their right mind, for that matter) would ever deny that standardisation is a good thing, but I do believe that Ryan is doing the right thing by always putting things in the right context -- which, in this case, would be ProcessWire, it's target audience, and their needs. Also: all good things take time. Even if we don't act instantly, it doesn't mean we won't act when the time is right. This really isn't something that is going to happen overnight, and sometimes we just need to be patient By the way, I'm absolutely not trying to discourage discussion. I just hope that we're all on the same page here: no-one is opposed to these ideas, and I'm sure we'd all like to see them discussed even further, but especially bigger and more fundamental changes need to be properly evaluated first. "X does it like this" doesn't necessarily mean that it's the best thing for us to do, and so on.

There are a lot of ex modx'ers in here. Does anyone know what happened with modx v.3 ? It was going to merge the best of both evo and revo and was to be released in 2013. http://modx.com/blog/2012/05/25/clarity-focus-and-simplicity/ Then I read this: https://twitter.com/fenton49/status/302791520380141568

try.dev branche it user.4.4.6 for.monthes

Hi, Just experienced a couple of bugs with this module which happen when the save messages setting is off. SimpleContactForm.module First bug: if (!$this->pages->findOne('name=' . $this->pageName) instanceof Pages) { I believe this should be without the "!" at the start as it is currently the wrong way around. Removing it fixed it for me. Next bug: } elseif (!in_array($currentIp, $excludeIps)) { This line should also check if the saveMessages setting is on, i.e.: } elseif (!in_array($currentIp, $excludeIps) && $this->saveMessages) { I haven't tested any of these with other settings and I'm not sure they are correct - just needs some looking into.

You should be able to set permanent=false in your module info, and then in your admin do a Modules > Refresh. But if that doesn't do it, you could always update the 'flags' column for that module to be 0 (in the modules table), and then after a Modules > Refresh it should definitely let you uninstall/remove it.

the issue happens either way, being set in config or per user; i had to remove the config setting for now, until it gets resolved... definitely a strange issue and that it only seems to blow out the adminthemereno module; though Wanze reported it happening with another module..

Yes, the CMS will be used by clients. Even when entering text, and then making a quick edit, you can't. As soon as you enter a new line, it messes stuff up. CKEditor (≤ 4.4.4) is unusable on Safari 7.1+. There is no reason I can see that it shouldn't be upgraded. Would that not be a naive decision to leave this unfixed? Especially since this is an easy fix, and it causes the editor to be unusable? This problem was even more of an issue because we installed the ProcessWire blog module, which used the version of CKEditor pre-packed with ProcessWire. You couldn't edit text, or write new text at all, unless you switched browser. But we can't say to the client, you can't use Safari because the editor doesn't work on that. They won't have it. The client's knowledge is limited, and the client just wants to edit the way he/she normally edits stuff. No faff. Obviously I can just do what I've already done each time we use ProcessWire, but surely it shouldn't be up to the user to fix bugs just so they can use ProcessWire?

Now you only have to convince Ryan to use this for Hanna Code, so we don't need to have two big ace installations

Seems like it's not insertBefore per se. I could get the fieldset by using numeral keys on all the children and insertBefore() on the fieldset does work as expected. var_dump($form->children[1]->children[3]->id); // "fieldsetEmail" var_dump($form->get('fieldsetEmail')); // null There's just something with getting the fieldset that just does not work.

Jason Coward (lead developer) has published some info on Medium within the last few weeks. I believe things are ramping up again and taking direction.

I've added and changed a lot of things on the dev branch. It'd be cool if you guys could test the current state to spot issues I have not encountered yet, so I can call it 1.0.0, merge it into master, and then publish it to the modules directory. Thanks! Changes, since the first post: 0.6.x - 0.12.x use noconflict version of ace implement possibility to add built-in extensions, by default emmet is enabled apply major PHP code refactoring 0.5.x enable field to be instantiated via API add interval check on editor.renderer.lineHeight and only initalize everything via callback when it is available add option to enable/disable localStorage make advancedOptions use the the Inputfield itself, INCEPTION! Regarding built-in extensions: They are sparsely documented, there are only two examples here. I have no idea what they all do. Some might even need additional libs, like emmet, which needs the core parser, that I included in this module.

I really feel the exact opposite way. You are trying to stuff a permission decision (is the user allowed to do something based on payment) into something that limits viewability but does not change the permissions of a user. The right way to go would much rather be something like a role "has_payed", which can get permissions like "can access feature X", "can access feature Y". If you're later getting to a stage of different subscriptions you can easily modify it to have roles like "has_payed_model_basic", "has_payed_model_advanced" and reuse all the permissions you used before, without even the need to touch you code.

I've been learning Python alongside PHP, and it's good that PHP is catching up in the realm of middleware/interoperability. Coding standards are baked into the Python language, and the entire Python ecosystem (including web framework middleware) is very modular/DRY (Don't Repeat Yourself). It will be great to see how ProcessWire addresses these issues while keeping its guiding principles - fun, simplicity, brilliant/powerful API and designer-friendliness - intact. It's worth checking out Symfony2's CMF documentation to see their approach. These posts are interesting as much for what they don't say as what they do. MODX may indeed be facing "irrelevance" partly because it hasn't been based on a decoupled framework... But there's also: the whole Evolution/Revolution fork the decision to use EXTJS in the bloated/slow Revolution back end an LLC whose business practices and project priorities seem out of sync with the wants/needs of the typical MODX user Also it's interesting how much the author disparages in-house innovation (developing new tools that may duplicate existing functionality) as an expression of "Not Invented Here." I like opinionated projects that take new approaches to solving problems. Maybe it's because I'm a musician, and love to see people offer their creative take on existing forms.

See the last post here: https://processwire.com/talk/topic/5857-using-pages-in-custom-function/#entry88975

I just tried to see if I've the same problem, but in the current dev there's no setting to un-/publish a user, even with advanced mode enabled. So maybe it's because Ryan never anticipated this to be used. To circumvent the issue you could maybe use a additional role, which you set/unset for users.

@teppo i get what you mean, am more thinking for in the long run things we should look at against 3.0 not immediate changes, also is there a forum where 3.0 discussion takes place i'd be interested in keeping up with updates and see if there's any code contribution needed.

When it comes to pure PHP regex testing, http://www.phpliveregex.com/ beats the crap out of every other tester out there. (Though regex101 looks pretty neat too.)

I know alot of people won't be pleased to hear this but Hari is right, Standardization is very important, that way framework interoperability can be a reality, its not fun for a dev to switch different programming practice, a good example is the Symfony Components which is easily used in other Projects, an example of such project is the MonoLogger. That way we can leverage on exisiting libraries and boost Processwire rather than building everything from scratch. however these are my personal opinions.

I don't believe in donations at all. If you want money from module, make it commercial. Of course there are plenty of possibilities regarding licensing, like making it free for personal usage.

Hi all, http://axisanimation.com http://axis-vfx.com http://flauntproductions.com I've added these to the directory but you might like to check some of the more interesting details written up in a blog post here - http://newnow.co/blog/the-4k-website/ They use: Modified multisite module to mix shared and site-specific content in one instance Modified thumbnail inputfield for cropping Custom inputfield to retrieve video details from Vimeo API Form builder module They are responsive from mobile to 4K, built on Zurb Foundation, and use the new picture element in conjunction with Processwire to serve images at the most appropriate size, and double size for higher pixel density displays. Wouldn't have been possible without the great forum content and documentation so thanks to everyone in the community! Crawford. New Now Ltd. http://newnow.co

If {team->body} has hanna code formatter enabled, then it will not work as Hanna Code 1.9 does not support recursive Hanna code processing. Refer to my earlier post. Remove the {$team->body} statement from your code snippet and check the result whether it then outputs all 9 members. Once you see that working, try using the patched version of Hanna Code I submitted on Github.

That's true for sure. I'm not sure if we can and if we should. But - instead of walking in circles - I wanted to make another point: It seems to be widely agreed, that PW is not yet popular enough and that a lot more has to be done, to make it more popular. I'm not sure if I agree to that. Imo, PW is already on a good way to become more popular. I'm not saying marketing activities are unnecessary, but almost every day we see more and more PW prestigious projects go online, we see the community grow from day to day, we see more blogposts etc. etc. This is all very promising and we should relax a bit. PW is such a nice baby, it will make its way ...

In some ways this discussion still keeps going in circles. "We want to have more site profiles / markup modules / modules in general for beginners" vs "ProcessWire is awesome for seasoned developers and we don't want that to change". Quite frankly it's still not an either-or choice; ProcessWire is extendable (modules, site profiles, templates) and we can -- easily -- cater for both sides. We've got a lot of good ideas floating around here. We know that we need to actively promote ProcessWire and we also know that we need to provide more resources and tools for users of all levels. What we need more than anything else right now is, in my opinion, more action. For this reason alone I have enormous respect for projects like ProcessWire.tv, Cheatsheet, Captain Hook.. and all the people writing blog posts, tweeting and otherwise helping to spread the word. That's the kind of thing we need if we ever want to be noticed by wider audience. I also think that catering for (ProcessWire) beginners is where we're currently a bit weaker than we should be. We need more easy-to-use modules that make common tasks trivial and -- especially -- resources that help people get acquainted with ProcessWire. I'd also love to invest some time in creating site profiles performing specific tasks; I for one have learned much of what I know through the process of taking things apart and, when I'm confident that I know what makes them tick, modifying them to better suit my needs (a process also known as hacking). That's what I see as the biggest benefit of extensive site profile library, by the way -- it's definitely not about us having everything thought out and ready to install, it's much more about us having a good starting point for a wide range of things.. and a lot of raw material to bend and twist and study as one sees fit. For the record, one thing I've been kind of disappointed about is that the more I discuss things like CMS' with people making the decisions (or helping others make the decisions), the more I see how much they value safety. Such safety is generated by long track record, popularity and sheer numbers (end-users, developers, modules, extensions, etc.) This makes a lot of sense, really, but it's also a bit annoying when you're rooting for "the underdog"; in order to get larger audience you need to have larger audience..

I think there is just a fundamental difference between what you are looking for in a CMS, and what ProcessWire is. That's not a bad thing. Some people think cucumbers taste better pickled. I currently work with ProcessWire in a University environment (300-500 active users, depending on the number of faculty during a semester). ProcessWire has not only been up to the task, but has far exceeded everyone's expectations. Both from a design/development standpoint, as well as UX for the site editors. One install powers a fairly complex public site (launching in the next few weeks), a faculty/staff intranet, a travel authorization and payment system, a news and events management system that handles around 500 events a semester with dozens of editors, an automated user management system that queries LDAP to determine user access and roles (runs via cron 3 times a day), Faculty syllabus manager (800+ documents a semester, maintained by hundreds of different users). Integration with MailChimp, some basic integration with BaseCamp, user generated forms (powered by FormBuilder), custom user dashboards, etc…, etc… Do you need to know how to code to use ProcessWire at this level? Absolutely. At least a little. In my opinion, that's a good thing. It means you can respond quickly to development needs. It means you can build solutions to suit, and not rely on pre-packed solutions that may not meet all project requirements. It means that you aren't constantly dealing with security patches, upgrade, etc… From a frontend development standpoint it means you aren't trying to work with markup that is bad/dated or has 17 classes on each element. I've been able to accomplish things fairly easily with ProcessWire that I bashed my head against for ages with other CMSs. Are all the typical "enterprise" checkmarks present in ProcessWire? No, but that isn't what ProcessWire is — and I hope it's not something it ever tries to become. At least not in the traditional sense. Depending on your needs and skillset; other CMSs may be better suited. ProcessWire might be a pickle—when what you really want is a cucumber.

Well said!

I do understand the user-friendly request, but I'm just concerned about how it can be done without making it not be ProcessWire any more. It's hard to make a bunch of templates when you don't know that the user is definitely looking for a blog or example - any templates that make too many assumptions will come with too many fields people won't use, and if you just stick with the default fields from the default installation but offer templates around that (there will be several with the 2.5 release coming soon) then those same people are still going to be confused even if they can see different template options The other option that has been talked about before is having several different installation profiles aimed at the question "what do you want to build?" with options like blog, company site, photo gallery etc and have some nice tailored options that can be installed at the start to show off different options. I think this is the more viable route as it offers choice rather than just theming the default template, plus is able to perhaps better show off some of the options depending on what someone wants. The rest of your points are easier to do, which is great! For Enterprise, I think we're getting the kind of case studies we can point to for those clients - the one I absolutely love being this one: https://processwire.com/talk/topic/7494-case-study-the-triumph-of-national-geographic-traveller-india-in-processwire/ - big project, large team and high-profile client. And as a bonus they switched from another system after facing numerous hurdles which speaks volumes - that particular development team have experience with the tools they've used in the past but they still made that switch and left their familiar territory behind for the benefit of the project.

I'm still interested !

I look forward to getting ProcessWire compatible with Composer. That's one of the things I'd wanted to do with 2.4 though other priorities for ProcessWire have gone ahead of it and likely won't be supporting it till after 2.4, but hopefully soon after. We may need to make changes to directory structure, but I'm averse to doing anything major there as I think we need to give priority to what's best for the web sites that ProcessWire powers over what's best for Composer. But we'll do what we have to do, just always in the context of our intended audience over Composer's (which have crossover, but are also different in many ways). Our audience veers much further towards web developers than dedicated PHP coders. Most of our audience is not integrating multiple PHP projects, but we do want to better support the few that are. 2.4 development is pretty much finished. Just trying to work out all the bugs before releasing it. Though I think it is already just as stable as 2.3 for the most part. I am also very interested in evaluating PSR-4 for ProcessWire. With regard to PSR-2, I'm less enthusiastic. Standards are great, and I support the PSR-2 standard for new projects looking to adopt a standard. But I think it's silly for projects that have already adopted a standard, as PSR-2 is a lot of compromise. ProcessWire's own code standard doesn't compromise so much, and in our context PSR-2 is a downgrade. However, I also see it as largely a non-issue. I don't care what standard people contribute code in, as IDEs make it largely irrelevant, at least for the way we merge code here. PhpStorm converts code to ProcessWire's standard automatically. I just encourage people to code in a standard that they find most readable and usable for them, so long as it's consistent.

If it's Git in general you want to use on Windows (not specifically Github), I would recommend adding SourceTree to your list of software to evaluate. It's free, and works really well with local and remote Git repositories. I use it at home and at work, and find it really easy to use.

I would think you've got all the 'native' PW options down. If it's a 'little' project i would first see how things perform without any caching. Also remember the usual stuff for pagespeed optimizations, this can greatly impact the feeling you get when visiting a site. If you do want/need caching it's hard to say which one from your ts; this depends on the structure of the project and exactly what kind of dynamic stuff there is. For template caching there are also a couple of different cache expiration options; which may or may nor work for you in this particular project. Performance-wise i think it would be: ProCache > template cache > MarkupCache. Teppo's got a nice article on PW caching on his blog: http://www.flamingruby.com/blog/processwire-caching-explained/ Of course there's lot's more you can do (memcached, varnish etc.) but this is not directly related to PW, and probably overkill.