apeisa

Oh, it seems my latest reply from few months went to Marty's message (it seems I pushed edit instead of reply)... so here it is: How about now guys? In my tests this works great now on FF, Chrome (older ones too), Safari and IE9+. Tom: I believe that your JS-issue is also fixed by this update. Also implemented the overflow: hidden, thanks for that - it works great. Marty: Should work, but those image positions and repeater stuff still missing from AjaxSave method in PW core. I will start looking for that next (probably something that is relatively easy to support, but not sure yet and needs to be committed into core too).

Hi guys We are thinking about organizing a little PW-meetup for all the Finnish PW-developers (of course, people from other countries are also welcome). Logical location could be Tampere, since we have people there, and I know many from these forums who are also there. Avoine can provide meeting place and something to eat/drink. I am thinking about having the meetup at workday (maybe Friday), but if that makes it harder for people to join, we can think of weekend or evening also. What I have in mind is half day long (maybe from 12:00 - 16:00), very free form meeting, where people can just discuss about pw, projects they have done, talk about modules etc. Also few more "official" presentations are welcome. I don't have actual date yet - but I think meeting would be in end of March. If you are interested, please let me know by personal message here on these forums or by emailing: antti@avoine.fi

Of course there can be security issues on pw. And since it is full framework instead of just sandbox for simple sites, developer can create bunch of holes themselves. But so far there has been zero vulnerabilities found from pw or pw admin. Of course it doesn't have millions of eyes watching like more popular frameworks out there. But all the most common web security pitfalls are very well taken care of in pw. Things like session capturing, brute force login, crsf protection, password encryption, sql injections... no software is 100% safe, but what comes to processwire, I know that we have pretty darn great foundation.

aiom is already one of my favourite modules.

form builder is easiest, but it is commercial (although offers great value for money). Building forms with API is great one too, soma has written easy to follow tutorial about it. form template processor is more like poc, while it works, I dont really recommend using it.

You have typing mistake, $option vs. $options

Your treemenu->render() should render whole pagetree. You do have published and not hidden pages on your site? If you think they could be hidden by css or js, check the actual markup of your page (ctrl + u, at least on firefox and chrome). If you already have a markup that you want to implement one to one, then try this: Create folder "markup" inside your site/templates/. Create file index.php inside that and copypaste the markup you have bought there. Copy all css and js files of your design to /site/templates/styles/ and /site/templates/scripts/ Edit the /site/templates/markup/index.php and changes urls to your css and js. Ie. <link rel="stylesheet" type="text/css" href="<?= $config->urls->templates ?>styles/style.css" /> Edit your template files (say, basic-page.php and home.php for starters) and leave there only this: <?php // this will load your actual markup include($config->paths->templates . "markup/index.php"); Edit your /site/templates/markup/index.php and replace the body content with <?= $page->body ?> and page title with <?= $page->title ?>.. well you know this part already Now you have nice clean html page with very little code in there. Of course you can start adding logic (like navigation) there, but if you follow my steps, then you will start from "final design" and then bring it live step by step.

Hmm - I think it would be much better, if no repeater template settings would be involved? If someone has time to check what it would require to support repeaters without access stuff, please send pr.

Jason - just post your actual code examples, with results what you are excepting and what you are getting instead. I am sure you will understand and get forward after a little guidance from community. Oh, and blog profile is very advanced, not a starter profile for sure.

One correction: currently, yes. But there is no hard coded requirement for field to store data in database. It could be Amazon S3, flat file, 3rd party api... anything really.

You need a fieldtype, if you have content, that is specific to a page. Field belongs to a template, and page has a template - so the content in fields is always tied into pages. Since 404 pages aren't actual pages, having field doesn't have much sense. What you need is database (or flat file or anything really) where you just store those results. Then autoload module is your way to find those 404 hits and save that data. Then if you want to provide admin ui for that data, then you would build process-module.

Better approach would be autoload module, that will hook into 404 error, and saves hits into a custom db table (instead of fieldtype). See https://github.com/apeisa/ProcessRedirects/blob/master/ProcessRedirects.module module, since it is pretty close (it checks 404:s for redirects). Here is the relevant hook: https://github.com/apeisa/ProcessRedirects/blob/master/ProcessRedirects.module#L20

This topic didn't get too much action earlier, but I do think something along these lines is definitely needed. I would love to send all PW-mails through mailgun or similar service, or at least smtp. Ryan and others, do you see any drawbacks in Teppo's approach?

Find concerthouses first: $concerthouses = $pages->find("template=concerthouse, title~=$q"); Then find events that are held in any of those: $concerts = $pages->find("template=concert, event.concerthouse=$concerthouses"); Ah, sorry, missed the repeater part... updated above.

There is no need for autocomplete search to return all the pages... only 10 or 100 most relevant. PW admin has autocomplete search for all pages and also templates, fields and users (well, they are pages too). Of course there are cases where all pages, or at least more than can be loaded on memory, need to be loaded. Then it's again cron job (or probably paginated results and memory flush, but I haven't ever had need for that).

Ups - I accidentally removed Teppo's reply, while using mobile UI. Pete - do we have any way to restore it? Sorry Teppo...

Vita, how is your template code? (I should release new version of this module soon, some little tweaks I have made)

if we have 5000 active developers/agencies working with pw and 10% are interested in image sizes, then your current audience is 500 people. No clue about usual conversion rates, but to really make money you do need superb product and marketing. And most importantly: time. Disclaimer: I don't have any clue about how many devs actually use pw or how big percentage really cares about image optimization.

thanks for the honest post. Your service definitely got me interested right from beginning. I think main reason for only one free account - there is not much to test. Your service is super helpful, but I have no rush to test it before I have need for it. I already know how it works and what it does. Also - pw community is pretty small compared to many others. I think you should offer rest api and plugins for other platforms too, if you really want to focus on your service. About your site - it definitely promotes the service well... but maybe you should focus on why page speed matters and how much images affect on that? Finally - I think service that does it on runtime (when uploaded) would be preferable, since no need for any custom template code then.

Image uploads are working fine here on 2.4.

Marty - thanks for pushing Fredi. It is neat little module for sure! Just as a notice: it is the dev branch that uses ajax saving, current master is more old school.

just as a reminder: there is no need to use profile exporter when upgrading from 2.3 to 2.4. It was required on 2.0 to 2.1 upgrade only.

Nope, version numbers go like this: 5.3.0 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.3.7 5.3.8 5.3.9 5.3.10 5.3.11 etc...

5.3.28 > 5.3.8 As always, you can play safe take copy or install fresh PW on same environment.