ryan

If the number of products isn't large (say less than 100) then the best way is probably to sort them in memory like the way Soma mentioned. But if you need something that can scale infinitely, then you'd want to keep your endprice as a field on the page that you can use for sorting directly from the $pages->find() query. Perhaps as a hidden field that is automatically populated via Pages::saveReady hook. It would be fairly easy to implement, let us know if you'd like an example.

Really great video! Nice job. Thanks for making this. It is the best video demonstration I've seen of ProcessWire. Would you mind if I embedded this on our videos page? http://processwire.com/videos/

ProcessWire will have support contract options available in 2013. I'm still working out the details, but wanted to let you know that option will be there for those that want it. Most of us here don't and won't need support contracts, because we can get pretty much anything resolved in a manner of minutes via these forums. But I would gather that a large portion of PW's user base doesn't actually participate in these forums. I also think that there are companies out there that would feel much better having the insurance of guaranteed support when they need it. Basically, if someone feels they need a support contract, I want to make sure we can accommodate that. I also see this as a way to further support growth of the project. As for EllisLab, I think they may be in a tough spot and trying to find the best way to survive and hopefully thrive. I had heard unsubstantiated rumors on Twitter several months ago that they might make EE free. To me suggested they might not be thriving as a business the way I would have thought. In such a case, change could be necessary in order to grow rather than contract. I have no idea if this is true (it's all guessing), and it's a little hard for me to imagine how they could not be profitable… given that their entire user base pays to use the software. But I don't think they would have made such drastic changes if everything was okay with the business model and finances before. My guess is they were faced with the choice of having to make cutbacks (like staff), stagnate, or make big changes. It appears they opted for big changes and are trying to re-focus their resources towards the high-end. That being the 20% of the audience that can pay the big bucks, at the expense of the other 80% that doesn't pay as well. And have probably accepted the sacrifices that go along with it. For that 20%, these costs are not really that big, and are probably seen to strengthen the B2B commitment (greater cost sometimes feels like greater insurance and less risk). There are other big players out there paying hundreds of thousands of dollars (every year) to companies with products that are inferior to EE. There are more opportunities to grow for them there than there are on the open source side. After all, products like ProcessWire and others are just as capable (and many would say more-so). It's not sustainable and makes little sense in a for-profit business to plan growth competing against a worldwide network of developers working for free. It's hard to grow a business when most of your competition is at least as good, and free. Whereas, I think it makes good business sense for them to carve out some new space where there is opportunity and partnership with bigger players. That's the side where the service matters as much, or more, than the software itself. And they can do well at both. I'm hoping that ProcessWire and other open source CMSs can benefit and grow as a result of changes with EllisLab. But I also hope that EllisLab and ExpressionEngine benefit and grow in the way they want to. Looking at where they are and what they are, it's not hard to understand why they've refocused. Though I say that as an outsider that's not negatively affected by their decision. Regardless of whether you like EE or not, it is in a fairly unique spot in the CMS landscape as a commercial product that is often listed with, and interchanged with, open source products. It's not something that I think could be repeated today, and I've always had a lot of respect for what they've been able to do and the influence they've had. EE is a good software with good people behind it. I'd like to see them do well and think that they will.

It's more of a reverse-honeypot field. Rather than excluding a form based on a populated value, it excludes based on an unpopulated value. This can be even more effective than a regular honeypot, but it does rely on Javascript. In order to eliminate the problem of false positives, you want to hide the CommentForm with CSS and unhide it with Javascript at the same time that you add the security field (as in the examples above).

The opensourcecms.com folks are good people. But I'm not sure they fully understand the extent to which those votes are manipulated. I'm still hopeful they will fix this someday, by at least tying it to some kind of recognized account system (even Facebook). But they will have to throw out the votes they've collected in the past, as they are largely noise. Once they do correct this system and make it honest, we will gladly have ProcessWire there, and I know other CMS projects that will follow suit.

While I'm not in the camp that wants my URLs to go outside my site structure, I can see that it's a need some may have. And you've brought up a very good solution here--we could accomplish this pretty easily. SEO would not be a problem because the module that would implement the solution would hook into the Page::path function to ensure that it's reflecting the alias rather than the original. It would also not be a stretch to have the module perform a 301 to the alias when the page is accessed at the original URL.

Thanks for adding to the modules directory. I have updated your listing with some additional text description and your screenshots. Feel free to change if you'd like: http://modules.processwire.com/modules/delegate-profile/

ProcessWire will also handle this for you automatically (with redirects) if you install the Page Path History module (already included with the core).

To Geocode from the API side, you need to set the address field and save the page: $page->map->address = '411 Holly Road, Hopkins, MN'; $page->save(); If that doesn't do it, you may sometimes need to give $page a hint: $page->trackChange('map'); $page->save(); If it still doesn't work, you might want to double check that your PHP install supports allow_url_fopen. The 'status' field is not meant to be set by you. It is set by Google Maps geocoder.

Some very impressive functionality here! Thanks for your efforts here. Nicely coded and documented too. Please add to the modules directory when you get the chance.

If you need the same form in multiple languages, the best way to go is create multiple forms. Create the first one, then create the same form in another language -- Form Builder makes this as easy as copy+paste with it's "export" tab on the form, and "import" option when creating a new form. This is preferable to a single form with multiple languages because it ensures that the form entries/results are separated by language.

I had thought that the Options +FollowSymLinks was necessary for the RewriteEngine. Maybe it's not. Looks like Drupal includes that directive in their htaccess file, but MODx doesn't.

MapMarker was originally built as an example module, ready for people to modify and extend. This sounds like a good extension. Admittedly I have no idea how to do it, but would definitely be interested if anyone does come up with something like this.l

I can't seem to duplicate here. Can you double check that your new Concat field is attached to the template used by your selectable pages?

"Manual drag-n-drop" is the unselected state, meaning it's the one state that wouldn't store anything in the DB. I've tried to duplicate, but not sure I understand. I've tried changing between Manual and other sort fields, changing back to manual, and drag-sorting pages, but all seems to work. Is there anything else I need to do to duplicate?

That's correct, that is what it has populated in there by default. Hiding your admin URL is a good practice. But if strong passwords are used, as they should be, there's no security problem with having a known admin URL either.

Your best bet is to make your default value the unselected state. All it usually takes is adding a little text description to your field to say "Leave blank for [default]". This is something that will scale and can be plugged into existing sites without having to go back and change existing pages to have the right value. More information in this thread:

Thanks for testing. I'll upgrade the dev branch here.

This type of error can usually be resolved by doing this: rm /site/assets/cache/Modules* This is something that ProcessWire does internally when it detects an upgrade. So you may be able to resolve it just by hitting reload on the page once or twice too.

Pete, you can replace your find()->count() lines with just count(), which would be a little more efficient, i.e. $count += wire('pages')->count("authors=" . $u . ", include=all");

I removed the joke links, so they shouldn't be there anymore. Is anyone seeing any more links? Matthew, in your Firefox go to Preferences > General > Manage Addons. Personally, I disable all addons in Firefox. Then in the left menu, click "Extensions". Look for anything you don't recognize or don't need and disable it.

No that stuff is real. I go to that page on Amazon whenever I need a good laugh. Read a few of the reviews and you will fall out of your chair laughing. It is a real product, basically today's equivalent of a stink bomb prank, but apparently much stronger. I don't see those script tags on any of our sites. Anybody else? I think they are getting dynamically inserted by a browser extension. Have you tried another browser?

Matthew, regarding the Happy New Year links: I thought that either you were kidding, or you weren't and could use a laugh. So I manually linked them myself, just for fun. I did a search for "worst designed websites ever" and used those for the links. Sorry guys, my sense of humor sometimes gets the best of me. I'll unlink them. With a clearer head this morning, it seems clear that you really are seeing actual spam links and you aren't kidding? It really does sound like browser spyware to me. Also, you mentioned this Skimresources thing, which I'm not familiar with. Can you explain more about where you are seeing this? We are not using any affiliate networks or advertising here, so this is not coming from processwire.com (unless there's some problem with IP.Board). I'm guessing you've got a browser extension that is inserting <script> tags into sites that you visit to automatically link words. Can you try from another browser to double check? For instance, if in Chrome, try Firefox, etc.

The ProcessWire 2.3 installer now lets you set the admin URL as part of the install process.

This should now be fixed on dev.