apeisa

I have to disagree. Never actually tried this module (since I don't fully understand it's purpose). If you compare instructions for this module (https://github.com/ocorreiododiogo/pw-admin-custom-pages) and those provided by boilerplate for Process modules (https://github.com/ryancramerdesign/ProcessHello), there is no much difference in complexity. I actually find latter easier (only changing file, class and constant names if you want to make it your own instead of "hello"). There is designed way to extend PW admin with own pages, and that is through Process modules (which are super simple, just install ProcessHello, play with it 15 minutes and you get it). Anything else is just looking for troubles in long run. I am sure there is something that makes Process-modules seem harder than they are. I guess that is the reason why Diogo has build this module..?

Error you are getting means you are using size method on Pageimages array, not on single pageimage object.

Does it work if you check the vedette field, save and then upload file after page save (when image field is already visible)?

What are responses from the image processing? You can see those from your browsers debug tools, network tab (or console in case of error).

Probably you are either hitting the time limit of your php script or then your server runs out of the memory. To avoid time limit issue, put this on top of your script: set_time_limit(0); That might be all you need. But probably you will hit memory issues too, since PW keeps pages in cache. At some point memory issues come - if not with 2000 pages, then probably with 20000 pages or so. That is easy to avoid, just call this at the end of your foreach loop: wire("pages")->uncacheAll(); Also make sure you don't have debug mode on when running this kind of scripts (there will be memory leak, since debug mode logs all queries in memory). I myself like to create this kind of scripts as a command line script. More information here: http://processwire.com/api/include/

Quick update on schedule - it seems difficult to find organizing this so fast (if we want some content and not just drinking beer). But this is definitely something I and our company wants to organize, so just more hands up. Realistic schedule would April or June, Tampere is still the best location.

Of course. How are you saving the pages now?

Ah, sorry. On mobile so it seems I skipped few posts. Because of its chrome, it might get fixed soon (in case our css is right and chrome is doing its own things).

The css animation have gone wild on sidebar on latest chrome (maybe other browsers too). I can take a look on that.

For voting I would require fb, google, twitter (etc...) or email authentication. Makes it harder to cheat the system.

I have always read/typed your nick as marcura (noticed it on last reply I wrote). Now I noticed something strange on the way you typed my nick You are gonna love process modules, they are great!

Just like with regular images, you need to check that image exists before outputting any img tags.

Has anyone tried to test this yet? Any bugs or non logical stuff you have noticed?

Macrura: http://modules.processwire.com/modules/process-hello/

You are right Adrian, I was the one confusing this Teppo is right too, error comes with using %= with id. It doesn't make any sense to use %= with id, since id%=1000 would match id:s like 910003 etc.. (if those would be strings).

That kind of selector isn't supported yet, see roadmap for 2.5: http://processwire.com/about/roadmap/ (either-or)

Also, why not try to get some results to browser screen before jQuery? Is url correct?

Just change select box to PageAutocomplete or Pagelistmultiple inputfield and you are good to go. 20000 items is heavy to generate on server side and just insane for browser / ui to render.

I have no idea. Probably some tricks soma is doing again, and reno is following blindly (as usual)...

It is indeed very fast - but also very impressive, lot's of content and high quality design! I like it!

Citizens! The first bug has been destroyed. Those nasty characters (sometimes invisible, other times %32c - or something) are now removed and the hyperlink is functioning fine. Comrads renobird and adrian, you have been awarded an award.

It was no surprise

About a month ago I announced UserGroups module, which I gave humble beginning, but Nik and Teppo really pushed forward (not sure if there is anything of my original code left anymore...). We are getting closer to initial 1.0 release feature wise, so this is good time to get more feedback from you guys. We have been focusing on finding all the different situations, where user access is defined and finding the right balance of features and simplicity. I am pretty sure there must be some cases where this module fails, so please do test all kind of combinations you can imagine and hunt some bugs! Grab the module from here and install it on big, popular and complex live site and go wild (or actually.. maybe not): https://github.com/apeisa/UserGroups/ Module is based on groups instead of roles. Idea here is that groups are something that your client can manage, but roles & permissions are not. There is no documentation or tutorial yet, but just install it - I think you will figure it soon (just create few groups, look for access tab on pages and try). Also check out this companion module that Teppo has build. It allows access management right from page tree: https://github.com/Aldone/PageListPermissions/

Can you post the code that is causing the problem?

Oh boy, Joss's list is perfect for those moments, when every line you code takes you deeper into the neverending loop.