kongondo

Would you believe me if I said I was just testing something similar

Martijn is right about storage though; they are stored in the fieldgroups_fields table

Maybe this? (see Soma and Adrian's replies) - http://processwire.com/talk/topic/3338-echo-field-label/

You know you can now (PW 2.4) use font awesome icons with PW? E.g. "fa-search, title" in the "List of fields to display in the admin Page List" would, in the page tree, display the title and the search icon next to the pages that use that template. Is that what you are asking? Edit: Hmm.., reading this again, it seems you want to use custom icons?

Hehe...what I'd want is a notification/or marked as unread if a post has been edited ....I don't think that is possible at the moment, no?

Nice quotes in here Joss!

MikeB, welcome to PW and the forums! Thanks for your input. I can understand why things seem to be confusing regarding structure of the file system/layout. I'll give you a straight answer. When it comes to profiles (e.g. the blog profile) and templating, there are no standard or recommended structures of the file system/layout . That is all down to the developer's preference! So, in the blog profile, that is Ryan's preference for structuring the file system/layout. The blog profile is not part of the core. Have a look at the other profiles as well to see the differences in approaches. If you look in the default profile (the default install) that ships with ProcessWire, it is also different (although that is necessarily so to align to a common structuring approach that would be familiar to those coming in to PW with some PHP background). Have a look at the followings thread for discussions about the different templating approaches people use. Some even mix approaches depending on need. http://processwire.com/talk/topic/740-a-different-way-of-using-templates-delegate-approach/ So, in a nutshell, some of us prefer .tpl, .inc, others don't, others prefer to have a /views/ directory inside /site/templates/, others don't, etc., etc. Having said that, when it comes to naming modules, there is a recommended approach: http://processwire.com/talk/topic/741-a-guideline-for-module-naming/ http://processwire.com/talk/topic/2394-how-to-present-your-module/ Edit: Members' attempts at MVC http://processwire.com/talk/topic/4892-an-almost-mvc-approach-to-using-templates/ http://processwire.com/talk/topic/3587-templates-mvc-recursion-etc/ http://processwire.com/talk/topic/4947-the-pw-mvc-project/ http://processwire.com/talk/topic/4507-pw-best-practices-application-structure-form-handling/ http://processwire.com/talk/topic/4507-pw-best-practices-application-structure-form-handling/?p=44338

@saml....thanks for your hard work...helping us to get there!

Haha. Been there, done that. Searching via Google does that a lot to me...

I don't think there is a sum function in PW...PHP can do that .....One approach is to use a hidden field that does the calculations for each rider behind the scenes on each page save. See this thread (especially Ryan's post) for an explanation http://processwire.com/talk/topic/5441-kind-of-calculated-field/. The advantage here is that no calculations are done on the fly on each web request...The sums are there to cherry pick from the DB... Edit: I've just realised Ryan's answer was in response to a similar (well actually the same) question that you Peter asked! Did you even read that thread?

Does sorting by modified work?. But date should work...hmmm...assuming you have that field What doesn't work exactly? PW version? Edited for clarity

Wondering if it's related to this issue? http://processwire.com/talk/topic/4222-custom-field-to-select-unpublished-pages-selectable-but-doesnt-save-selection/ See this too; it might be related http://processwire.com/talk/topic/5083-possible-bug-page-fieldtype-with-custom-selector-to-find-selectable-pages-returns-error-while-saving-page/

@idea96, Apologies if I misunderstood you. Form Builder is a commercial module. You can buy a license from here: http://store.di.net/products/processwire-form-builder

Let's put it this way....if you enjoy microwave dinners, then Joomla or WP is for you. Sometimes the dinner will be easy to cook and may turn out right. On other occassions, the dessert will flop and you will be left frustrated but you will have to do with what you have. If on the other hand, you enjoy having all the ingredients you need and can follow any of several recipes to create some beautiful food with your ingredients, then PW is for you .... What am I saying? If you want to point and click and solve problems by adding more plugins to the system, Joomla and WP are "good". If you want finely grained control over everything, then PW is for you. However, with PW, some work will be required of you. You will have to be willing to learn....The community will be here to guide you along the way if you ask for help where you are stuck... Just my 2p (spoken from the point of view of an unashamedly biased PW addict - but who has been to J and W before...)...Seriously, though, creating a backend admin in PW is not difficult... Welcome to PW and the forums vladar

By putting a semi-colon in front of the line in your php.ini...i.e. ; Example - this line is commented out. Comment out the below line.. ; allow_call_time_pass_reference//comment this out; deprecated and now removed in php 5.4 The directive has been removed from PHP 5.4. Hence, comment it out as suggested. Have a read here: http://uk1.php.net/manual/en/ini.core.php#ini.allow-call-time-pass-reference

Path http://processwire.com/api/variables/config/ E.g.: $config->urls->assets PagefilesManager class http://processwire.com/apigen/class-PagefilesManager.html Save pages via API (including images...) http://processwire.com/api/variables/pages/

Nope; rootParent is not a PW selector These could help: http://processwire.com/talk/topic/3018-rootparent-selector/ http://processwire.com/talk/topic/5269-rootparent-selector/

Just guessing... 1. Copy contents of /wire/modules/AdminTheme/AdminThemeDefault to site/modules/AdminThemePete 2. Duplicate and rename AdminThemeDefault.module to say AdminThemePete.module + change the name of the class in the new file.... 3. Since you want to add to rather than take from the AdminThemeDefault.module, add your Pete theme selection option here...(in your module file) $field->addOption('pete', __('Pete')); , i.e. public static function getModuleConfigInputfields(array $data) { $inputfields = new InputfieldWrapper(); $field = wire('modules')->get('InputfieldRadios'); $field->attr('name', 'colors'); $field->label = __('Color Set'); $field->addOption('classic', __('Classic')); $field->addOption('warm', __('Warm')); $field->addOption('modern', __('Modern')); $field->addOption('futura', __('Futura')); $field->addOption('pete', __('Pete'));//Pete's new awesome colors! $field->attr('value', isset($data['colors']) ? $data['colors'] : ''); $field->optionColumns = 1; $inputfields->add($field); return $inputfields; } } 4. In site/modules/AdminThemePete/styles add your css file - main-pete.css 5. Cross fingers and install Just guessing...but see also... http://processwire.com/talk/topic/4650-new-processwire-admin-theme-on-dev-branch/?p=50881 Edit 1: I have a feeling though that this would duplicate the warm, classic, etc in Admin! This is because admin themes can now co-exists...so, maybe, remove all the other options in the field as well as their CSS, etc. and only leave yours... Edit 2: Just duplicate as in my first attempt, change the css as you wish, but remove radio options.....? Edit 3: I give up; am confused too....Ryan or Soma will clarify

...and don't forget you also have $pages->get if you only need to return one specific item...(i.e. something other than this page)... http://processwire.com/api/

Yes...an mp3 is just another filetype to the browser just like .pdf, .doc, .zip, .exe.....It just needs to be told what to do with it

This is always useful...http://processwire.com/api/selectors/

Welcome to ProcessWire gunter... Just to add on to what Adrian has said..., technically, there is no relationship between a template file and fields. There is a relationship between templates and fields. That's why you need to clarify your situation. If you want to change the template of a page (call it template 1), and the new template (template 2) you are changing to does not have the same fields that are in template 1, then PW will give you a warning: "Warning, changing the template will delete the following fields:". It will list the fields that will be deleted. If you click the checkbox "Are you sure? Please confirm that you understand the above by clicking the checkbox below." they will then be deleted...Other than that, template files are used by the user (technically instructed by the user) to grab what's in your fields and display the output to the browser

Welcome to PW sozoclive But we have this... http://processwire.com/talk/topic/3439-idea-and-proof-of-concept-mailer-class/ and... http://processwire.com/talk/topic/335-imap-mailbox-functions-in-flourish/

Check in your site/config.php $config->adminEmail = ''; It notifies on "fatal errors".... Make sure to test that the server environment can send emails, of course... Maybe there is a module about too? I can't remember..

Then I suggest you really have a lot of reading to do bram. To be able to use ProcessWire, you need some understanding of PHP, CSS and HTML. jQuery is optional.