teppo

Moved the topic from "Community Support > General Support" to "Off Topic > Dev Talk".

@Sparrow: not sure if there's any specific documentation for these. FieldsetOpen and FieldsetTabOpen are two of the field types you can choose when you're creating a new field and when applied to a template, you can use them to split one template (in Admin, as these fields rarely have any meaning at template files) into fieldsets and/or tabs. That's all. Edit: fieldsets are also discussed in the overview video. If you're not familiar with that, the entire presentation is worth watching (in fact it's where every new user should always start from, if you ask me) but here's the specific part discussing fields (including fieldsets).

Even if alternatives are not needed (sorry!) and though you've probably already evaluated it, when I used to develop on Windows, XAMPP was all the rage. Cross-platform, well maintained, free, etc. Just saying. Then again, it's way over 100MB package, so if that makes a difference (?), it's probably out of the equation too

Still using Eric Meyer's reset. Always works for me, so never really had a reason not to use it / look elsewhere

Might want to consider a simple module for that task. In a situation like yours, where all affected fields are most likely well known, it wouldn't require too much magic to hook after image descriptions are changed, find references to said images in specific field(s), replace alt texts and then save the field(s). Some regexp required, but that's just about all there is to it

@kongondo: sorry if this is unrelated (I don't have a proper test environment at hand right now) but sorting by dates is entirely doable using MarkupAdminDataTable too. It just requires a bit of extra work: prefixing actual, visible value with hidden, sortable value; something like yyyy-mm-dd etc. This is how I solved it in ProcessLoginHistory. Sorting multi-page values is another issue entirely, but as far as sorting visible results is good enough, no need to complicate things with new 3rd party components

@LostKobrakai: multi-language image description part makes sense, but I'm not so sure about the latter suggestion. IMHO these (image desc and alt text in RTE) are not the same thing and shouldn't be connected in such a way. Description being used as the default alt text is pretty good compromise, actually. For an example, I've used one image multiple times with different alt texts quite often. There's also the point that in this case the alt text should be updated for other pages too, which would make this rather complicated to implement (if it's updated for some cases where the image is used but not all of them, that's just plain confusing). On the other hand this is something I've had to explain to others multiple times, so perhaps some sort of "[ ] define here: ___________ / [x] inherit from image" option would be an optimal solution, though I'm still not quite sure how cases where image from another page is used should be handled..

@SiNNuT: it should probably be noted that Phalcon is not written in PHP but C and thus it's even more difficult to fairly compare it to any framework written in PHP. It's a different type of animal I'd really like to stress that Laravel and other web application frameworks are very different from ProcessWire by nature. ProcessWire does a ton of things they don't (the content management part) and they probably do a bunch of things ProcessWire doesn't. Apples to oranges and so on.

Looks like there's a problem with InputfieldPage. PageListSelectMultiple didn't originally support findPagesCode at all, until Ryan added that feature per my request -- but in that version it was actually broken and the fix was only introduced to dev branch. Since it's essentially a bug with with a module in wire directory, your options are .. a) using another input field type such as AsmSelect (works fine if you're only dealing with direct children of one page), b) using dev branch of ProcessWire (if this site is still a work in progress this might be a good idea anyway) or c) replacing /wire/modules/Inputfield/InputfieldPage/InputfieldPage.module with newer version of same file. Hope this helps a bit.

If you need an image (or thumb) for each individual member, then using it within foreach loop is just fine. Also, size() creates the thumb, but you'll still have to call the URL of said thumb; $member->image->size(100,100)->url etc.

Not going to be a problem for me. Ever. Just saying

Thanks for sharing this! Looks like a very good example of dealing with externals services. You might want to consider taking advantage of __DIR__ (PHP 5.3.0+) or dirname(__FILE__) for includes: include __DIR__ . '/../index.php'. This way it's enough to know what's the relative location of, say, ProcessWire's index.php compared to it, instead of having to hard-code the paths in the file if you use it from multiple locations (php importer_strava.php, php mydomain/importer/importer_strava.php, cron etc.) Strava looks interesting, too -- I've been using SportsTracker for similar purposes, but they don't seem to offer any kind of API for their service. Not sure yet if this is enough of a reason to switch platform, but you've given me some incentive to check out the alternatives

In your template, call $page->image->size(80, 100) to get an image with 80px width and 100px height. It's all explained at the images page. If you've turned on the option for specific image field to display thumbnails in the page editor, ProcessWire will automatically generate some thumbnails (imagename.0x100.jpg), but that doesn't mean anything for you, really.