Soma

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

Christoph is right, it's not possible to render the repeater field when not logged in as superuser. It must be simply that the repeater pages are located under /admin/ pages. I got similar problems when creating the shop with saved orders as pages under /admin/. I had to do include=all to get it working for other users. I can't imagine you're not able to reproduce this. I got simple repeater and the following code won't show anything when I'm logged out. foreach($page->items as $p) { echo "<p>$p->item_title</p>"; }

There's actually a module for normal selects that can be configured in the field settings: http://processwire.c...-aka-drop-down/

No, you're not dreaming, but it's like a dream!

Just commited an update to this module fixing an issue with brand new repeater field, where the lock message would appear after saving page.

Great thanks formmailer for the testing! Never blame it on something you don't know!

Easiest would be to use $session->redirect(url); to redirect. Not sure what exactly you're trying to archive. Do you really want to redirect a longer url to a shorter one? Or do you want display same content within another url?

Hey, sorry that nobody seems to reply to this. Although it's quite long and difficult to grasp/understand. For me at least. It's always better to try keep it short and clear. From your second post, I can say that it's easily possible to write a module with hooks for page actions like ::save/::delete etc and do something, according to what page is saved. For example write content to over pages in the tree. Or even copy the page to another location. There's quite a lot of functions/events that can be hooked via a module in PW. So it's relatively easy to sync pages, aslo because the API is so powerful and the tree based page structure makes it easy to depend it on certain setup. Of course you could also create custom admin masks using API via bootstrap (including index.php) and access API using $wire->pages or wire("pages") namespace. PW is a great and easy framework to get done whatever you can imagine.

Playing around with it a little I think I've found a solution... in the pwlink/editor_plugin.js on around line 80 I've did the following if($node.is("a")) { anchorText = $node.text(); //alert("A:"+anchorText); } else if($nodeParent.is("a")) { anchorText = $nodeParent.text(); //alert("Parent:"+anchorText); } else { anchorText = selection.getContent(); //alert("Text:"+anchorText); } So the parent node check was somehow needed, otherwise the whole <a...>text</a> get's returned for the link text if a link is already there selected to edit... It surprizes me really that nobody has experienced yet. I would attach the file for you to test but I can't see upload anymore here. Attached modified js file. (Also the inserted twice bug I experienced is gone, when I updated to the 3.4.7 TinyMCE) editor_plugin.js.zip

Ryan, I still get this issue, or related to this: When I insert a link, everthing is fine, but when editing the link again, it doesn't change the url, in my case it just inserts a new "invisible" link as mentioned above. BUT also editing an already placed link to check the "open in new window" option, it doesn't do anything, unless I change the URL. I get this no matter what PW version or tinyMCE version... and it get annoying, cause inserting/editing link is some basic feature every CMS should have no problem at all. The invisible, double link behaviour is something I can't really reproduce in other PW installs other than the one I experience. Can anyone, please test this out on their install? I think it's something in the link dialog from PW, combined with TinyMCE... EDIT: looking again little closer in the PW pwlink/editor_plugin.js if($node.is("a")) anchorText = $node.html(); else anchorText = selection.getContent(); if(target.length > 0) target = ' target="' + target + '"'; if(url.length) { html = '<a href="' + url + '"' + target + '>' + anchorText + '</a>'; tinyMCE.execCommand('mceInsertContent', false, html); alert(html); } There seems to be an issue with the code here. It constructs (if editing a already set link) a link inside a link. So the "html" returned is wrong... I'll try to find a better solution to this... or if anyone wants to help, I'd appreciate it!

I know them Pete, I already used them in projects (even PW), I just can't see that it's something easy to implement for the repeater field the way it's done.. . But maybe I'm wrong. As I see it is that you have a table with text and number, not images, page refs , RT's etc. So I could see an easy implementation that's using datatables and the data stored as serialized array. Just trying to look at it different.