Soma

I don't see what this should be good for. If you set the current page to be another instead, then just get the other page. $page = $pages->get("/someotherpage/"); Doing this at start of output will change current page to the other, so it's indentical and all will render as it would be the other page just having the url of the previous.

Made a little update to the ImageManager.module. Haven't recognized something before when testing. - fixed issue with pagination not working in PW 2.4 when using has_parent=/path/, turned out that has_parent=1009 with ID works. Looks like this has been fixed in latest dev.

Hello guys Just committed a larger update to 0.1.0: lots of cleanup and major changes, but still backwards compatible some fixes to tag parser as there were issues with multi language major rewrite of the image results table to get rid of bundled jQueryDataTable and Fancybox (saves a lot of files and resources that where not necessary) now uses PW MarkupAdminDataTable with custom ajax overall nicer and solider UI integration into PW new admin theme other small improvements and fixes To update, just replace the module folder with the new one. There's a lot of files deleted, so don't just merge. So a lot of changes behind the scenes you won't notice much, but also UI wise it's much nicer now. It should works nice and I think requires PW 2.4 now. Not tested in 2.3, but mainly I think the use of JqueryMagnicfic Lightbox script (in core 2.4) now for image preview zoom. Otherwise it should work the same. I removed alpha status, whatever that means. After all it's not meant to be the solution to all problems people might have with PW's media management. It's a nice little helper tool to upload images and create pages from them. In the end it's all saved in a form you could even uninstall ImagesManager and plug your own to handle the data. It can also be seen as a resource. I'm not sure I'll add it to the modules directory.

Well the cool kids use remote control, Airplane bahh... Glad you found it. I have no idea why.

APC php cache? Is there anything on the title field? Textformatter? It's hard without sitting in front.

I'm not sure. Can you hand a copy? Cache?

Yes those two pages have same template. It doesn't matter what template. I've never used the save and test. But I think you would see the current admin page title if anything at all.

I tested something like this in latest dev and 2.4 installation, works fine. I can't see any text not outputting. Default site. Added hanna code formatter to body field. In /templates/ page in the body I place a hanna code inside text [[model-name]] and output that text on the About page. Hanna code <?php echo wire("page")->title; In template basic-page.php echo $pages->get("/templates/")->body; The hanna tag gets replaced with the page title and the surrounding text is still there.

I have hard time following what code is where and what doesn't work.

Sorry can't really follow what you're doing. Mostly confused why you'd need hanna code at all just for a page title?

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.