Soma

You don't happend to replace sorounding p tags and the hanna code is inside the text paragraph?

There is no disable just uninstall or install. You could add a checkbox to disable and not execute hooks

Just fixed various issues. - images now get correctly uploaded to the category selected (this was a bug introduced by myself in the JS). - fix issue with category filter not showing nested categories correctly - fix issue with page search link not working correctly, made sure it works also with new 2.5 dev search page using Lister and now uses the textarea fields specified in the module settings. - changed the category select on images upload to a simple select input, with visually nested categories, for easier handling - some cleanup bumped up the version to 0.0.7. https://github.com/somatonic/ImagesManager

Those are nice features. I'm still a little foggy about what now is in what version of PW, and how to use these requires, installs best. But that's maybe just me. Generally, it's getting little hard to follow PW development changes and additions (goes fast) and get a clear picture, for me at least (maybe other developers too), and keep track of them. What I thinking about is about modules that should still work in 2.3 - 2.4 - 2.5. There so many changes across core and modules that the only way to make sure and account of differences using conditional code. What is the simplest way to make a check? if(wire("config")->version >= "2.4.0") does not work obviously. Is there an easy API I'm missing? And something on the js config side could exists too? config.version ? ------- Side note about your example: I guess this example won't work cause this addition is after 2.4.0? 'requires' => 'ProcessHello>=101, ProcessWire>=2.4.0, PHP>=5.4.0', What about the "permission" key on the module info? Was there any additions or changes lately? Can there be multiple "permission".

This is just a notice and not an error. It still works. I just pushed a commit and upped version to 0.0.5 Fixes: - to remove that notice when rendering pages inside a page. - fix template object not showing settings and name Added: - a property "skipChromePhpLogger" you can set to a page object, at runtime before rendering, to skip logging. Example: $somepage->skipChromePhpLogger = 1 echo $somepage->render(); // will not trigger the logging for $somepage

Id is integer and not fulltext. You can't mix them with % but maybe with * . But you may need to have some additional logic to check if search is an Id or text.

I'm not sure usually you search fieldtype page with the id not a string. Or if then using subselector tags.title=value.

Yes here $config->maxPageNum = 999; It's set in wire/config.php but you would add it to your site/config.php

Ok. We just launched our new website today, of course now running on ProcessWire. A long journey with many iterations and somewhat experimental. Still a work in progress, as much as never finished. There's a lot of inter-linkage going on between content news, projects and competence pages. Modules worth mentioning: TextformatterAutoLinks Markup RSS Feed http://update.ch (IE < 9 not supported, sorry. Old Androids may experience strange things)

JS is accessible.

Depends. I don't care about them. They most likely will have many other troubles anyway these days. If you care about them add a noscript tag with a message. Or use the normal honeypot method.

$sesion is a wrapper for the native session. One of the good things is you don't need to do isset($session->data) but just if($session->data) ... If it doesn't exists or is empty it will return NULL.

My and PW honeypots are reversed. There's no field in html source. The hidden field get's added via javascript, and if the field isn't submitted it is counted as spam. I only got troubles when I used captchas years ago. I'm using honeypots since 2-3 years now and never recieved any spam (apart from the 1-2 manual ones).

Just pushed a little but important update to 2.1.3. Previously module files/folder didn't get deleted before updating a module. This would possibly would leave orphaned files that may get removed in a new module version. Now it just deletes folder and writes new folder. Fix small issue with module cache not getting updated when installing new version of a module.

Thanks Horst for bringing this up. I tried some things with using this fieldtype as config field. But it wasn't saving correctly due to it's value type of object. I made some major changes to this fieldtype. In short, the value now is handled as an array value and not as RangeSlider object anymore. See upgrade and changelog here: https://github.com/somatonic/FieldtypeRangeSlider#upgrade-notes (BTW Also renamed the module repo to FieldtypeRangeSlider) These changes now also allow for using the Inputfield as a config field in modules. Previously it wasn't possible, as the value saved wasn't treated as array. Simplest solution seemed to make the Inputfield implement InputfieldHasArrayValue. Regarding the defaultValue. This was only set and used in the Fieldtype and not Inputfield! So the defaultValue will be set to the field value. Inputfield then just deals with the value min and max. Since when using this module as a config field only, there's no fieldtype involved at all. Here just an example how to handle it as a config field. protected static $defaults = array( 'myrange' => array('min' => 10, 'max' => 90), 'myslider' => array('min' => 10) ); public static function getModuleConfigInputfields(array $data){ $data = array_merge(self::$defaults, $data); $fieldset = new InputfieldWrapper(); $modules = wire('modules'); // range with two values $field = $modules->InputfieldRangeSlider; $field->attr('name', 'myrange'); $field->attr('value', array( 'min' => $data['myrange']['min'], 'max' => $data['myrange']['max']) ); $field->isrange = true; $field->width = 90; $field->minValue = 1; // min value config $field->maxValue = 100; // max value config $field->step = 1; $field->label = 'Slider 2 range values'; $fieldset->add($field); // no range, only single value $field = $modules->InputfieldRangeSlider; $field->attr('name', 'myslider'); $field->attr('value', array( 'min' => $data['myslider']['min']) ); $field->isrange = false; $field->width = 90; $field->minValue = 1; $field->maxValue = 100; $field->step = 1; $field->label = 'Slider 1 value'; $fieldset->add($field); return $fieldset; }

Very wise words. ProcessWire have to be careful to not become a module hell. It can easily get out of hand.

Yes in modal. And its superior to other block style as every block is a page and can be published or unpublished etc and all multilang. I don't need visual inpage editing as much as a solid block type. Also you can (I do anyway) make all easy editable when viewing page.

Well those rows when edited have their own template with their own layout.

Page tables field supports multiple templates unlike repeaters. So it's possible now with dev.

I'm not sure why template=admin wouldn't work, just wanted to mention what I observed. I'm also seeing admin template is a system template and not selectable by selector config in PageLister.

Page lister uses has_parent!=2. There could also be pages under admin without admin template.

You're mixing up things. This should be more like include("/home/xyz/public_html/pw/index.php"); wire("user")->language = wire("languages")->get("en"); $referenzen = wire("pages")->get("/referenzen/"); $references = $referenzen->children; foreach($references as $reference) { echo "<li class='references-item'>"; echo "<p>{$reference->title}</p>"; echo "</li>"; }

This get() always returns a page or a null page ( if nothing found)