Soma

It would be a clacks with the new repeater field.

Hmm i just installed it on my fresh local install and can't reporduce this error.

You can just go to github download the zip file (button top left) https://github.com/r...ramerdesign/P21, nothing special. And then rename the wire folder in your install to "wire_old" and copy the new wire from the zip over. Repeaters aren't installed by default so it should be no problem. If you experience any problems you can roll back to the old wire folder. Also may report the issue you got in case.

Thanks so much Ryan for the active help! But finally we sorted it out, and she agreed to add the /var/.../phptmp folder, that was already there in the web root, to the php ini "upload_tmp_dir". Now it works again flawless. Anyway, the new available option you implemented may come in useful for someone.

Hey Frikki! Nice to have you here, welcome to the forum! Enjoy your stay and the small bits.

Is the url the correct image url? /site/assets/files/... If you really can call url on the object but not do a size() on it have you tried debug mode on? Also can you do a var_dump on the image object and see what you got if($tdobject) var_dump($tdobject); Strange but I think I got once a similar issue, but can't recall what it was at the end. I'm starring at your post and code trying to figure out what you're actually doing here with your setup and code. I can't really decipher it in my head right now how this really makes sense all. Would you be able to make a profil export https://github.com/ryancramerdesign/ProcessExportProfile of your PW site and post that so one could try out locally? Or explain a little more about the exact setup so one could possibly reproduce? Also are you using very latest commit? I don't know if it may a issue with repeater fields which are still pretty fresh.

Rofl WillyC! Welcome to the future!

Yeah, I wasn't able to get the editor publish unpublished pages. Although I managed to get some strange behaviors, when I remove the page-publish permission from the editor role I suddenly can't even edit pages anymore except for the unpublished ones, for example... I think only Ryan would know what's going on. Certainly a bug or alike.

I just reinstalled a fresh and latest PW. And I have just added a editor role with view edit delete permissions. Gave access right (all) on template basic-page for editor role. After that when creating a new page I can't publish it, only save and keep unpublished. There seems to be something wrong with current access system. Ryan?

WOw I should first think then write I didn't test correctly I didn't logout and login with editor... mmm I will try again an see. Edit: Ok this is getting messy, it's so odd I can't even describe it. I added page-publish permission, and tried different settings. First time I try the editor could only edit the one unpublished page an all others only view... and when trying to edit the page I got. Duplicate entry 'for-page-1010-1070' for key 'name_parent_id' So trying to find a reason, I looked at the settings on page with superuser, and published and unpublished - and it showed me different permission for the editor role, in each state. After that I removed the page-publish permisson, and now the editor can edit all pages again, although the error stays and won't go away... So I don't know if my install is messed up after all those tests and updates. I would have to reinstall a fresh one and test again to see.

http://processwire.c...__fromsearch__1 Have you tried really and added it to the template access settings too? Edit: Upps, that isn't really the issue I think. I just tried in my local install latest PW and no problem with publishing pages even without the page-publish permission. Edit: The page-publish permission is only if you want to hide it... So maybe you haven't checked it, take a look if you have access setting enabled in your PW template.

Add a "page-publish" permission and try again?

The hoster reponded that the function http://php.net/manua...et-temp-dir.php is the problem, in that it returns the default temp dir /tmp always, and she's not confident with adding this because of security reasons. Edit: and she says that this sys_get_temp_dir isn't compatible with open_basedir... what do you think? Edit: Strange, when I add instead of sys_get_temp_dir -> realpath( $_ENV['TMPDIR']); the upload works, althought it throws an notice which hinders the image to be shown. It show after reloading the page. So it seems to upload. The notice I get is: <b>Notice</b>: Undefined index: TMPDIR in <b>/var/www/web8/web/pw/wire/core/Upload.php</b> on line <b>125</b><br /> [{"error":false,"message":"Added file: teflon2.jpg","file":"\/pw\/site\/assets\/files\/1001\/teflon2.jpg","size":129854,"markup": realpath( $_ENV['TMPDIR']) : returns -> /var/www/web8/web sys_get_temp_dir: returns -> /tmp Edit: When I add @ before the @realpath( $_ENV['TMPDIR'] ); it works without the notice... What you do think Ryan? How is this possible, and how to fix it so it works for all scenarios?

Thanks for the suggestions. I tried and not luck. It seems it can't be overwritten.

I tried again with debug turned on. This seems to be issue with open_basedir Warning: tempnam() [<a href=function.tempnam'>function.tempnam</a>]: open_basedir restriction in effect. File(/tmp) is not within the allowed path(s): (/var/www:/usr/share/php) in /var/www/web8/web/pw/wire/core/Upload.php on line 126 Can you tell me what I should tell them?

I sent you a PM. Thanks. Safe mode is off.

Diogo already said it better than I could ... What would gives you the reason to put a place of a content into a container called "/footer-navigation/"? Will those be special pages completely separate from the "main" navigation? So what if you find a more meaningful name that would put meaning to the content placed inside? mb /services/ ? ... In 99% of the projects I've worked on the so called footer, meta or service navigation are just a few "hard" coded into the template links that won't change a lot anyway. Also not areas where one would often add pages. It's true that the content structure reflects the navigation 1:1 that what makes it easy to recognize as it represents the websites structure. Not layout related informations. Your approach is solely coming from the desire to give a visual structure to the editors to work with. That's what I meant by mixing up. SO thinking about it a little more, I think some sort of visual named "separator" that can be but in between the pages inside the hierarchy might be a better solutions to this. It's just the way PW works with it's hierarchical approach, and not every case and desire others might have, has been put into thought by Ryan or others. It's pretty much he's effort alone all of what you see in PW atm and done for he's needs and clients. It's still evolving and I think there will be some sort of solutions coming up. Just have to either wait or get active and try to get things discussed/done.

This is just awesome stuff! Thanks for bringing this in Ryan!

Glad you found it working again! Thanks for letting me know anyway

Your content structure shouldn't be trying to completely reflect the menu structure how you want to appear on page through hierarchy. You're mixing things up. Just looking at your structure something feels wrong. The most elegant way, is to have a setting on page or various other options. You could have a menu structure and a content structure. Then have a page ref field to select the page you want to render for a menu entry. Then use $page->render() to render the referenced page. And the url will be the one from the menu. Not sure how this would affect the handling on the menu heighlights. But I think there's ways to get it working. But at the end there would be some sort of base "dir" that you don't want to have in the address, so you're at the same point again. Although some clever custom handling of the urls outputted would maybe make it possible. While this can be a desired situation to divide the structure but not have the structure reflect in the address, it would require URI routing. This could be done through htaccess, although this would require adapting the navigation urls you output from PW, think of headaches. Another way would be to have PW allow for configuring URI routes like in CI for example http://codeigniter.c...l/routing.html. Not sure how this all would work internally well regarding urls and the page finder functions etc. Though I also would like to hear from Ryan what he thinks about this subject, and if he sees anything possible like URI routing in the future in PW, as this subject popped up already in an other thread at least once.

Turn on advanced mode in your site config.php, then in the field settings you see additional setting, though "required" is only working for text fields I think.

Hmm can you tell me your browsers name? Version... it works for me in Chrome, FF I think but not really tested in other browsers.

Thanks for testing. Can you try clearing cache again? I also once thought it isn't working but then it suddenly worked.

Once again, I got a problem with a hosting where I can't upload images/files. It just uploads to 100% then the bar disappears and it's like before. In the post I see this message: error: false message: "Page not saved (no changes)" Filepermission seems ok. Install went normal. Any ideas what to look for? I can provide phpinfo if needed. PHP version is: PHP/5.2.4-2ubuntu5.23

Just pulled it down, copied over, refreshed page... it's working now! Thanks Ryan